I started out by creating index.dryml, show.dryml, edit.dryml, etc for all my model classes, but then I started defining custom tags for things like field lists in application.dryml that are used in multiple pages for the same model. I found it a little odd to have closely related elements of the UI split between views/<model> files and views/ taglibs/application.dryml. So I switched to creating <model>.dryml files in taglibs and including them all into application.dryml, and eliminating just about everything from the views/<model>. That way all aspects of the UI for a given model are in a single file, and application.dryml contains only strictly system wide stuff. So far I like this arrangement, but I'm always experimenting.
On Nov 13, 12:17 am, Tom Locke <[EMAIL PROTECTED]> wrote: > Just as a style point, note that it's strongly encouraged to create > app/view/contacts/index.dryml, as opposed to: > > > <extend tag="index-page" for="Contact"> > > And a small comment: > > > scopes[:not_may_email] = true if params[:may_email]._?.== 'No' > > The _? is not needed as == is defined on nil anyway > > Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
