Yariv Sadan wrote: > 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 > >
It's not that I'm complaining about the feature :) I just thought there would be an easier way right now :) The question then is: will it be ok to place, say, an admin_view_login.et alongside admin_view.et and import it? Since ElryWeb assumes that everything that is not ending in controller or view is a model --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
