This is an archived low-energy page for bots and other anonmyous visitors.
Please sign up if you are a human and want to interact.
in reply to Themes Design Quest
I usually include a "do-it-yourself" theme design page in my perl web-applications.
On this page the user can choose the colors, by clicking on a color sample, and fonts of the menus, table headers,
table data, or whatever I choose to be user setable.
I store the settings in a cookie which I read and apply when they load a page.
I guess that isn't really what this quest is all about, but it saves me a lot of job and the users
will benefit (or face the concequences) of their personal taste.
/brother t0mas
|
RE: RE: Themes Design Quest
by Maqs (Deacon) on Jun 14, 2000 at 08:28 UTC
|
Good idea but... It has more 'minuses' then 'pluses' IMHO. Cause it'll bring another headache to mantainers, make the code more complicated and will take more time to load. Besides that I do really like the things like 'perlmonks colors' - the identification sign of the site, which is by all means a community, covering common interests of programming perl.
As I mentioned it was my humble opinion :)
/Maqs. | [reply] |
|
|
I disagree with you (since I've wrote the code in the first place) that it brings another headache to maintainers.
If I want more than one possible color/font schema in my app, I'm faced with the headache anyway. I really don't know how
vroom handles this in his code, but somehow he "knows" that you've selected (default) in your user settings Theme container,
and applies the default colors. In the same way he could "know" that you like lime green 20 pts Helvetica fonts on a pink background, without
hurting performance.
My solution was to let the users get controlled access to some of the settings I was applying anyway, and made them able to set
theese as they saw fit.
I do think that colors/fonts is a matter of taste and if you like the original colors, vroom has done a good job.
/brother t0mas
| [reply] |
|
