We currently do a lot of view determination in an old hack based
expCore::resolveFilePaths() method. We also do much of our
framework view determination in the expFramework
get_common_template() & get_template_for_action() methods. It
would be MUCH more efficient to create new template subclasses
which allow easy creation of config, form, action, etc... views by
placing a generic framework/template name method (suffix selection)
and handled things within the template class. Evenmoreso, it would
allow a standardized approach to looking for template variations
based on the current framework such as global views, etc... which
we currently do/can not do.
So, in addition to the controllertemplate &
standalonetemplate having access to a common framework/template
name method, we'd have:
- actiontemplate, but this may be handled by
controllertemplate?
- commontemplate
and perhaps
accompanied by some new general expTemplate methods such as:
- get_views() - (static) list of available type views
- get_template() - retrieve existing framework factored available
view name