You can always explicitly forward the calls to functions defined in other view modules.
Also, it would be possible to add a mode to ErlyWeb that changes the default view mapping for a component to a function-per-file mapping. It's not a high priority for me right now because I prefer to have few medium-large view files than a large number of small ones, but you you want to implement it I'll accept the patch. The way I think it should work is by adding to a controller the line -view_module_per_function(true). and then each function would be mapped to a file of the name [component]_view_[function].et Yariv On Jan 16, 2008 12:01 AM, Dmitrii 'Mamut' Dimandt <[EMAIL PROTECTED]> wrote: > > Can a view be split up in separate small files? > > Let's say I have an admin_controller that defines up to 20 methods and > each one needs to be renedered involving lot's of HTML. > > > What I've seen so far is that you have to put all of your rendering > functions inside the admin_view.et file which can grow really big really > fast. > > What would be the easiest way to split the file up? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" 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/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
