Template Class
I have finally thought it out and I think the template would be best served if the template class was the only class. The different tags will be split out into the same class, but separate from the main one. This way it would be easy to add support for new tags, once the supported tags gets above 10 or 15 and makes it somewhat difficult to tell the main class from the other functions.
Module Page Class
The template data could either be displayed once parsed or passed to the Module Page class, which will continue the parsing and add to the page, it is needs to be dynamic. This is easier to do than what is currently done. It will also separate a lot of the parts, so that it will (hopefully) be easier to change the template and have the content morph.
Possibly Related Posts:
- Mecha Asylum Design Document
- Data Store is Finished, but Still Imperfect
- If You Look at it This Way
- Configuration SPL Usage
- New Configuration Factory Possible Features
Comments are closed.