Trouble with (or misunderstanding of) -dryml evaluation order.
Reported by Don Ziesig | December 18th, 2010 @ 04:42 PM
According to several documentation versions (probably all old) dryml for a given object type (for example clients)is evaluated in the order:
-
app/views/clients/
page.dryml -\ form.dryml -- I think this is what is implied by the docs, but I don't remember seeing it exactly. edit.dryml -/ -
app/taglibs/application.dryml
-
app/taglibs/auto/rapid/
pages.dryml forms.dryml edit.dryml
#3 works (obviously or no app would work) #2 works, but for a rapidly growing app, application.dryml is becoming rotundus maximus (really big). #1 doesn't work. I can't even seem to get it to compile - good code, deliberately erroneous code, empty files - are all silently ignored by the system.
My "best practices" coding style says that I should isolate functionality just as the above hobo hierarchy shows, but until someone tells me what I am doing wrong, everything goes into application.dryml, which is now getting so large as to have a significant negative impact on my editing productivity.
Comments and changes to this ticket
-
Domizio Demichelis December 19th, 2010 @ 04:23 PM
- State changed from new to invalid
- Assigned user set to Domizio Demichelis
The dryml document name in the app/views/clients dir must be the name of the action, not the generic 'form' name.
Besides, if you are using the 1.3, you can also add a app/views/taglibs/application/
and app/views/taglibs/<subsite>site/ dirs. All the .dryml files in that dirs will be automatically included in the main application.dryml or <subsite>site.dryml, so you can deflate your application.dryml.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »