On May 20, 2010, at 1:11 PM, Michael Kim wrote:
Thanks guys. I'm just starting out with hobo and wanted to try
putting dryml there to see it work. I soon realized that I'd be
doing the same thing for my edit page so I'm back to extending it
admin_site.dryml. I'm having a similar problem there....
The closest I've come is to extend the new-page and redefine the
form and field-list. With a route like /service_orders/new its
perfect, but it does not work for /service_orders/1-cust/new. What
is the proper way to let it know that it will be extending for
new_for_customer too.
Moreover, can I somehow extend the form tag or do I define a new tag
and add it both new and edit pages?
You can extend the form tag and it will get picked up on all the
relevant pages - see the cookbook for details.
However, there aren't typically many situations where you'll end up
with both a new.dryml and new_for_something.dryml - I've mostly seen
it with *index* actions, where the 'for' version is a handy way to
designate subsets of records. In your case, does it actually make
sense (according to the application domain) to have a service_order
without a customer?
--Matt Jones
--
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.
