From: Stefan P. <st...@gm...> - 2011-04-13 21:37:29
|
On Wed, Apr 13, 2011 at 15:34, David Hicks <d...@hx...> wrote: > > The 1.3.x branch has already seen a large number of minor changes (from > a variety of contributors) that have added classes, IDs, etc to allow > better CSS targeting. Further development in this area is very much > welcomed. Great! I just forked the Github mirror and had a further look and saw some of the changes made in the 1.3.x branch. I also noticed the status_config.php file in the css directory that dynamically creates css classes based on values in config_inc.php/config_defaults_inc.php. Is this design the desired way to go? I.e. keeping all kinds of visual customizations to the PHP config files, rather than having the user do a custom css file for inclusion? The downside I see is that it's really mixing up and creates dependencies between presentation (css) and logic (php) layers, instead of leveraging the natural separation of concerns achievable with css. The upside is of course that all customization options are kept to the config_inc.php file. Best regards, Stefan |