On 2 Jan 2007, at 21:20, Daniel McBrearty wrote:
gotcha. The only part I had to put in Root.pm was the
__PACKAGE__->config( ... ), which is logical.
I found a lot of templates under root/base ... including 'xhtml' which
at some point calls
[% INCLUDE header;
window.render_viewport(self.inner); %]
which I guess then runs down the various objects that were added with
$self->push_viewport(ViewPort, 'blah') in the controllers.
Basically, yes.
These templates have lots of apparently widget-orientated stuff ... is
this library code or app code used to generate the crud stuff? how do
I set up where it lives in my app?
Currently, using a symlink, because I've not come up with a general
solution and wanted something trivial to rip out once I do.
To add your own templates, stick 'em in root/ of your app, do an
INCLUDE on whichever base template you're subclassing and then define
BLOCKS appropriately plus setting the appropriate foo_block var to
the name of your own blocks - ISTR listview subclasses listview_base
in the default stuff as a reasonably simple example.
--
Matt S Trout, Technical Director, Shadowcat Systems Ltd.
Offering custom development, consultancy and support contracts for
Catalyst,
DBIx::Class and BAST. Contact mst (at) shadowcatsystems.co.uk for
details.
+ Help us build a better perl ORM: http://dbix-
class.shadowcatsystems.co.uk/ +
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
