The goal of default template included in hfs (especially the beta!) is, from my point of view, to test and show the new features included in hfs.
Rejetto has done a great work in hfs, including a lot of features that users in the forum asked for, also a some of them only are useful to very few users ( Who needs renaming, creation of folders and delete functions on a small server throung the web interface? This are admin tasks, and i think that any admin can access his server directly or through remote access). But as the features are already written, it's ok to include them in the template.
Also some people complain that the new template has a lot of javascript, it's use is not slower than previous versions. More, it can be even faster. You may split the template, putting javascript and stylesheet in separate files, that will only be loades once and after they will be available from caché, what will even increase the speed of next load of a page. But as the default template may change with the further builds, it's a good idea to leave all in one common file which goas with every build.
Think that we most all use a beta, and that the default template allows new users to use hfs 'out of the box', but most users would like a template with a personal touch. For those, all te features hfs already has, may be available - as are already from the rawr team - more and more templates. People may select then if they want to use simple html files, or more sofisticated solutions making use of javascript. If someone makes a 'stable template' surely he would not pack everything in one file, he would use separate files for scripts and rest of the template.
It's clear that the new template may not be that simple to use for 'designers' used to the method of copy and paste. But a little effort to learn javascript and to use ajax will not be more difficult and be more usefull for people than learning 'macro'.
« Last Edit: July 17, 2010, 01:35:21 PM by Mars »
your computer has no brain - use your own !