NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
help them think they understand.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
templating (Score:1)
Yeah, Continuity::Widget is just a sketch, and separate from Continuity itself on purpose. Even if I get that going the way I like, I definitely don't expect it to be The Way to use Continuity. More like a demonstration of what can be done. Well... and for my own use :)
I unfortunately don't know the full HTML::Mason request cycle and how that all works. One thing you can do, I believe, is to just use Mason as a template engine. You could then use Mason components to organize your views, and outter Continuity structures to organize the control flow.
Another possibility (or maybe along with the above) is to take the Continuity request and turn it into a Mason request, so that the request-oriented features of Mason can be utilized.
One thing that I have no idea how to do (without research at least) would be the other way around -- allow for Continuity based control flow inside a Mason component.
Reply to This