On 10/23/2007 11:29 AM, Bill Moseley wrote:

>>  lib/My/Thing.pm
>>  lib/My/Thing/Form.pm
> 
> Is that one form for each table kind of mapping?
> 
> I might have multiple forms for each table (or groups to tables) and
> they are more related to the specific request (update user profile vs.
> update user via admin interface) that to the table.  Validation
> requirements might be different for the same field on different forms.
> 

Yes, I expect that real-world scenarios will demand that a single Form actually
interacts with multiple tables via a single RDBO object, and/or multiple Forms
might end up representing the same table(s). That's ok. This project is just to
bootstrap some same defaults based on a 1 table = 1 form formula. Kind of like
Rose on Rails. ;)

Think of it basically like adding a make_forms() method to the RDBO Loader.

> So my form module names tend to be based on the request name.  So in
> Catalyst, for example, my forms are basically found in
> $App/Form/<Controller>/<Action>.pm  Makes it easy to auto-load the
> forms for any given action.

Cool idea.

> 
>> But of course, I can see the advantage of a totally different namespace for
>> Form classes. I have been trying to go down the route of using a .yml file to
>> define the basic Form class, and to make that available to non-programmers to
>> edit, especially for labels, etc. That way I don't have to go in and modify a
>> .pm file every time marketing changes their minds about what they want a
>> customer to see. But exposing just the labels is about all I think I want to
>> do, and it might end up being more work to go the .yml route. I haven't made 
>> up
>> my mind yet.
> 
> I keep the labels in the html templates.  I started using YAML files
> to define the fields and labels, but then I ended up with more places
> to define things than I felt was reasonable.
> 

Yes, that (labels in HTML) is what I do currently as well. I'm inching closer
to letting go of the 'labels with yaml' idea.

-- 
Peter Karman  .  [EMAIL PROTECTED]  .  http://peknet.com/


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object

Reply via email to