Peter, thank you for your feedbak. 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. >
If you mean to split the auto generated taglibs (the app/views/taglibs/auto/rapid/pages.dryml) into separated files, I think it would complicate things, because you will have to search the right file when you want to copy some tag in order to extend it. IMHO the all in one file structure is perfect, for its use (i.e. open it to copy some tag). If you mean the tagibs that YOU add, actually the current structure is more flexible that what you are proposing, since it allows your structure, but also allow ANY other structure that might be more appropriate in other contexts or developing styles. 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. > The viewhints are model related hints for displaying data into pages: sort of general directives, so it seems quite appropriate to express them in a ruby file, anyway, could you plase give us some practical example to do the same in dryml? 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. > For example? ciao 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.
