Templates Systematization Similar to Modules
I think everybody knows the way modules for Hookie works now.. and I bet everybody is happy the way they organized modules in folders and the install/uninstall system in administration..
Installing modules and playing with them is very easy now.. but are the templates in the same situation? Can we administrate templates from the control panel? Can we install and uninstall them with grace? No we have to still use the FTP to do the things most other scripts do for many years now - The install and uninstall/modifying template settings and style from the administration..
Everybody knows that a great script is nothing without a great range of free and commercial templates.. How can we make Hookie a great success without easing things out for new users..Why should we make 99% of the things right and let that 1% ruin the rest? What I propose is that templates should be organised just as modules (folder structure) and admins should also have the possibility to uninstall templates just like the modules.
I also propose If it's possible to allow the installation of modules and templates by uploading them in the original zip right into the admin control panel.. Take Joomla as example..
What is your opinion about this? Please speak free and tell me what you think..
The new Dolphin solution is powered by UNA Community Management System.
> Get rid of the import statements in the CSS files - they are not a good idea - Not only are they an additional overhead (File open / close transactions are memory intensive - much more so than the few bytes of data contained within the files), but handling templates in the manner that you recommend (ie only including the items that you require) is a VERY BAD IDEA...
CSS inheritance is unpredictable at best - overwriting selected statements as you are suggesting see more
We need to reduce the number of files loading in each page as DeeEmm said by melting them into one or as few as possible.. I've raised this problem a few months ago just after the first public alpha (alpha 13 I think) was released, boonex team did a great job reducing the size and the ammount of the external files..
We really need to do something with this and continue improving see more
Best policy is to only get the client to retrieve two / three files at most - HTML + CSS + JS function file is all that is really needed.
Additionally put the JS calls at the END of the HTML file NOT the head. The functions are generally all called post runtime, so there's no need to hold everything else up by loading them upfront.
DM.