Thats cool, I like.  I would go so far as to suggest/brainstorm some
bigger refactoring for default: a folder for each model.  Keep all the
page front-end stuff in the view directory.

1) Each model folder would hav a .dryml for the tags as well.  Similar
to application_helper.rb, have a application_tags.dryml in the views
root folder.  This begins to separate code for different models.

2) Viewhints.  Replace these with special tags in the model-specific
tag files.  They effect a page layout similar to how a view does, and
this helps keep all relevant code in one place.  This also keeps to
the tags convention and is therefore well-expandable in the future.

Hopefully this would be more intuitive and easy to use.  Other cleanup
could be done, such as moving automatic tags to their on files within
model view directories.  To keep things neat, prefiex underscores
could be used, which might be nicer than a folder.

Thoughts?  Y/n/maybe?
--Peter

PS: rvm 1.0.16, I'm pretty sure I upgraded right before jumping in to
all this.

On Nov 5, 5:43 pm, kevinpfromnm <[email protected]> wrote:
> That is nice.  I've got one that I've split off 9 dryml files,
> basically one for each model with complicated overrides and still have
> a 368 line long application.dryml.
>
> On Nov 5, 2:42 pm, Domizio Demichelis <[email protected]> wrote:
>
>
>
>
>
>
>
> > I forgot to mention that you can also organize the taglibs in that dir
> > hierarchically, and they will get autoloaded anyway. It's quite handy
> > because you can move tags and files around without having to add/change any
> > include tag.
>
> > dd

-- 
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.

Reply via email to