#668: Allow customization of the way Actions, Views etc. are laid out in the
filesystem
-------------------------+--------------------------------------------------
Reporter: david | Owner: david
Type: enhancement | Status: closed
Priority: low | Milestone: 1.0
Component: _OTHER_ | Version:
Severity: normal | Resolution: fixed
Keywords: | Has_patch: 0
-------------------------+--------------------------------------------------
Comment(by david):
I should mention that the following structure is much nicer:
{{{
<setting
name="agavi.action.path">%core.module_dir%/${moduleName}/impl/${actionName}/Action.class.php</setting>
<setting
name="agavi.cache.path">%core.module_dir%/${moduleName}/impl/${actionName}/cache.xml</setting>
<setting
name="agavi.template.directory">%core.module_dir%/${module}/impl/</setting>
<setting
name="agavi.validate.path">%core.module_dir%/${moduleName}/impl/${actionName}/validate.xml</setting>
<setting
name="agavi.view.path">%core.module_dir%/${moduleName}/impl/${viewName}View.class.php</setting>
<setting name="agavi.view.name">${actionName}/${viewName}</setting>
}}}
as you then have this structure:
{{{
app
modules
Default
config
impl
lib
models
}}}
with all actions, views, templates and cache/validation configs inside
{{{impl/}}}
note that the example (has to) customize the view name, so you now have a
slash (subdir) in the view filename (and an underscore in the class name)
between action name and view shortname (Success, Input etc)... example:
{{{Default_Sub_Marine_SuccessView}}} instead of
{{{Default_Sub_MarineSuccessView}}}
also, using the template lookup pattern where there is a directory per
locale does not make much sense with this layout
--
Ticket URL: <http://trac.agavi.org/ticket/668#comment:8>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
