Sorry if this have already been discussed, I don’t have the time to read all posts. I don’t think the theme options should be stored in db. It should instead be stored as an xml file. This would give ppl two possibilities. Firstly users could exchange theme-files if someone likes the colors, settings of a theme (s)he could easily get it from the user that created the settings. Secondly the theme author could include multiple setting files for a theme allowing the user to change between them. This would require some kind of simple option to change between settings files. (Shouldn’t be hard to just iterate a theme- name/settings folder and add a dropdown for it.)
On 30 Apr, 03:52, Owen Winkler <[email protected]> wrote: > Matthijs wrote: > > > Also, being able to use PHP in templates is a big plus for me. Say you > > want a special template in which you put a form for example, then you > > can just put any php logic needed inside that template > > Please allow me to correct one point: > > If you put PHP in a HiEngine theme, it will execute normally. > > If you were to change the theme you're using from RawPHPEngine to > HiEngine and do nothing to your existing PHP, nothing different would > happen -- your theme would look exactly the same. > > The HiEngine uses PHP stream classes to filter the template files before > PHP includes them. It literally converts {hi:foo} into <?php echo $foo; > ?> before PHP executes the template code. It leaves existing PHP code > alone, and it is executed just like the code written by HiEngine. > That's how it works. Implying that HiEngine somehow abstracts the PHP > capabilities away from the themer is absolutely incorrect. They can > easily be intermingled. > > Owen --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
