diff options
| author | mateu <mateu@03d0b0b2-0e1a-0410-a411-fdb2f4bd65d7> | 2009-08-11 14:35:33 +0000 |
|---|---|---|
| committer | mateu <mateu@03d0b0b2-0e1a-0410-a411-fdb2f4bd65d7> | 2009-08-11 14:35:33 +0000 |
| commit | 753f8f1d3d3d5a7efc2cb8416f6b7f09b3a722a0 (patch) | |
| tree | 644ab93d038be03408b429706b69f823c1e858b5 /lib/Reaction | |
| parent | 4b70129e4e977a51616faaaeefd61a39367861f0 (diff) | |
| download | reaction-753f8f1d3d3d5a7efc2cb8416f6b7f09b3a722a0.tar.gz reaction-753f8f1d3d3d5a7efc2cb8416f6b7f09b3a722a0.zip | |
extending Reaction core skins and call_next POD additions.
Diffstat (limited to 'lib/Reaction')
| -rw-r--r-- | lib/Reaction/Manual/Tutorial.pod | 33 |
1 files changed, 30 insertions, 3 deletions
diff --git a/lib/Reaction/Manual/Tutorial.pod b/lib/Reaction/Manual/Tutorial.pod index ca0fdc3..46a49c1 100644 --- a/lib/Reaction/Manual/Tutorial.pod +++ b/lib/Reaction/Manual/Tutorial.pod @@ -142,7 +142,23 @@ a relative name like and it would try to extend a skin named C<foo> in your own application's C<share/skin> directory. -Now we create C<share/skin/defaults.conf> to allow settings that concern all skins of +In general, the Reaction distribution provides two skin choices to build upon: +C</Reaction/default> and C</Reaction/base>. C<base> is Reaction's most basic skin +while the C<default> skin extends the base by embellishing the layouts with more XHTML. +The default skin is designed to be a working skin. + +In other words, if you want to write most of the low-level XHTML yourself +then put the following in your skin.conf: + + extends /Reaction/base + +If you want to use more XHTML out of the box, then configure your application to extend +the default skin. + +It's worth noting that you are not bound to the XHTML of the default or base skin layouts, +because you are able to override layout fragments in your own skin. + +Next we create C<share/skin/defaults.conf> to allow settings that concern all skins of the application. It should contain only this: widget_search_path MyApp::View::Site::Widget @@ -195,8 +211,19 @@ containing the common C<body> for all pages using this site layout. The C<[% inn where the deeper parts of the stack will be included, in the case of our C<root> action that would be the C<Reaction::UI::ViewPort> with the C<root> layout. -If we wanted to override a specific fragment, we could do just that. And inside that fragment -we could call C<[% call_next %]> to include the layout fragment from the extended layout. +If we want to override a specific fragment, we can do just that. There are two choices +when overriding a specific fragment. One can disregard the parent fragment all together +and start from scratch or they could reuse the parent fragment and add to it. The key to +re-using a parent (extended) layout fragment is the keyword C<call_next>. Specifically, +we insert C<[% call_next %]> to include the layout fragment of the parent. + +The parent layout fragment is found either in another layout template named in the +C<=extends> directive or it's in a subclass of Reaction::UI::Widget. +In the latter case, the Widget subclass name matches the name of the template or +the widget name posed at the top of the layout file via the C<=widget> directive. + +Once you know the hierarchy C<call_next> follows, then you know where to examine +the details of the parent layouts or widgets. The layout representing the root action is called C<share/skin/myapp/layout/root.tt>: |