#57 - Theme Wizard upgrade
-
By Chris Graham
- Added
- 15 views
| Identifier | #57 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Theme Wizard upgrade |
| Status | Completed |
| Tags |
Risk: Breaks themes (custom) |
| Handling member | Chris Graham |
| Addon | core_themeing |
| Description | Instead of the concept of a single seed theme which needs each CSS color to have an algorithm to re-create it, ditch the whole notion of algorithms and seeds and rely completely on HSV alterations to what is already there.
Allow the Theme Wizard to select a source theme. For source themes other than 'default', it would have to actually copy all theme files to the new theme whether they were changed or not. Move the sources/themes2.php lines 312-403 and sources/themes.php lines 22-23 code actually into the themes, but via a file format rather than as code. This allows themes to specify their own Theme Wizard image generation technique/process. Do similar things to allow the logo wizard parameterisation to be different for different themes. More theme options... - Fixed-width setting - Different background settings (fixed position, standard, tiling) Save theme creation options within the Theme, and allow re-application of the original parameters, or tweaked versions there-of, to any theme aspects of the users choice. This would be done for a specific theme-image on that theme-image's edit screen (using the default theme's version as the base, and providing a good preview). |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
pull some of our CSS out to a settings.css file that has really basic CSS stuff, like header height, fixed width, font, block spacing; allow the theme wizard to write it out and encourage customisation
This is a nice elegant solution, as the end result is easy to edit and explain too, and it pulls away complexities without changing our core architecture at all.
Composr should be smart enough to merge global.css and settings.css at run-time, for performance reasons.
1) Different background settings (fixed position, standard, tiling)
REASON) Trivial CSS changes that people can make themselves. At this point we'd be second guessing people and nannying them too much.
2) Save theme creation options within the Theme, and allow re-application of the original parameters, or tweaked versions there-of, to any theme aspects of the users choice.
REASON) New Equation solver added to edit-css screen to allow changes on CSS done easily. For anything else user can add a new theme and copy the theme image back over.
3) The stuff in the note above. People need to learn CSS or pick a closer base theme. Allowing little tweaks won't really get people much closer to their goal so is a distraction.
Also instead of removing the old themegen algorithm, we're providing a choice. This gives the best of both worlds.
Also dark themes are now supported.