[Catalyst] Re: [RHTMLO] RDBO/RHTMLO integration with Catalyst
- work in progress
Alexandre Jousset
mid at gtmp.org
Sat Jul 21 20:36:49 GMT 2007
Peter Karman a écrit :
>> I'm still studying them to be sure what is the right thing to
>> do... But any advice is welcome...
>
> C::C::Rose takes the "thin controller/fat model" approach. Look at the
> example app in the t/examples dir to see one implementation.
Done.
> I prefer to follow the RHTMLO convention of a Perl class for each form,
> rather than YAML magic, etc. So C::C::Rose basically is a thin glue
I understand your point.
My goal is to provide a "form framework" that can speed up form
creation and modification. In this aspect a YAML file is far quickly
updatable than a Perl class. In a sense it is like the class loader in
RDBO but only in its dynamic version (of course, I generate the forms at
start, not each time the action is called, like C::C::FormBuilder does).
But I want best of both worlds, i.e. the nice Rose framework with the
very easy C::C::FormBuilder approach, and in the case of the Rose
framework I want RHTMLO and RDBO glued together.
> between a Rose::HTML::Form subclass and a Rose::DB::Object subclass (via
> Catalyst::Model::RDBO, which is also thin glue).
>
> My approach has been to write just enough code to get RHTMLO and RDBO
> working in a Catalyst context, in a generic CRUD fashion. The idea is
> that my RHTMLO and RDBO subclasses can exist happily on their own, or
> pulled into Catalyst with the thin glue of the C::C::Rose and C::M::RDBO
> base classes.
Thank you for your explanation.
I think I could name my module C::C::Rose::FormManager, or something
like that...? ;-) I plan to use your C::C::Rose and C::M::RDBO base classes.
--
\^/
-/ O \----------------------------------------
| |/ \| Alexandre (Midnite) Jousset |
-|___|----------------------------------------
More information about the Catalyst
mailing list