From: Victor B. <vb...@op...> - 2002-06-08 00:03:11
|
Hi, Following are my 2-cents: 1. We should also add an option to disallow users from selecting a theme that is different from the default (hence removing the option from the preferences). Some admins might like consistent of look 'n' feel specially when it comes to status colours. 2. When running this script, it include by default config_inc1.php and config_inc.php and use the old $g_ values as defaults. This will allow users to generate their custom theme without having to re-configure it. $g_ values that are not defined are to assume the same defaults as the values that were included in config_inc1.php in release 0_17_3 3. It would be good to allow editing a theme, and not only generating it. This can be done by maintaining two files for each theme: .css, .inf (or whatever extension). The .inf should look like this: font=courier small-font=xxxxx Hence, we the users edits a theme, this file is loaded, stored in the old $g_ values and hence being automatically used as the default for the script. For consistency, we can format it as: $g_<old name>=<value> Regards, Victor. -----Original Message----- From: man...@li... [mailto:man...@li...]On Behalf Of Kenzaburo Ito Sent: Saturday, 8 June 2002 2:07 AM To: Mantis Developers Subject: [Mantisbt-dev] CSS and Themes Hello all, I'm going to dive into theming with the 0.18.0 release. Here is basically how I want to lay it out. Right now we dynamically generate the CSS and include it on every page. This adds almost 4KB of unnecessary text to each page. A link to a static CSS file will probably save us a few KB on each page load. To eliminate this we'll create a new directory called themes/ In this directory we'll place CSS files. Naming will be simple: <theme_name>.css These will be static files with no PHP in them. Users can create their own and select them. To generate them we'll move the various table, color, and font variables out of default/config_inc1.php and into the admin/ directory. We'll create a small script that takes the color variables and dumps out a CSS file which the admin can then save into the themes directory. A nice addition would be to create a simple page that shows the use of each of the css elements. The files are then read out of the themes/ directory and then processed in an option_list. Users can then select a theme preference. It will be the site default unless specified otherwise. A system global will control what the default theme is. PROBLEMS: The status colors will also need to be represented in the theme colors. I also believe there will be some issues with the bgcolor td cells. I consider these fairly minor issues. Comments? Thanks, -Ken _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Mantisbt-dev mailing list Man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |