|
Hi there,
as more time I spend with redShop, I'm want more and more templates as files, not in database. I think, that put code into db is huge mistake. Look at points I've got:
Pros:
1) easier edit of files using ordenary code editor
2) possibility to use subersion tools (SVN, CVS, GID etc.)
3) templates in teplate overrides
-You can have directory /components/com_redshop/templates with all templates (in directory structure like template types are now in db for ex.)
- You can have directory /templates/yourtemplate/html/com_redshop/templates with overrides (in directory structure like template types are now in db for ex.)
- You can distribute redshop templates within template (think about joomla theme clubs like rocket, art or yoo...)
- You can distribute main templates in updates with new features etc. Now you can not to include new template into db, there's no override possibility! So people must digg into code, try what works and how.
4) You can leave admin interface as it is now, just change handling from db to files as it should be. (if one of my devs come with idea to store templates in db, I'll cut his wate I'm sure about it. Mixing data an layout, uff, big step out of basic programer rules. And for sure step out of joomla system....).
Against:
1) multilingual support (but anyway, I you put template to translate to translator, who thinks, that HTML is Internet explorer, you know what's going to happend).
So could you put some arguments against my point of view? I agreee with your template system, but I totaly do NOT agree how it's handled. No svn, no overrides, no eclipse or another code editor.
Consider this carefully. There are not too much shops atm, maybee there's no one live shop... More time with this not reasonable system of template handling, more difficult to change it....
One more time, this is serious thing, just think about it with all aspects. If you have some pros or agains, just put it here.
Thank you for cooperation. Jan.
|