Project

General

Profile

Feature #178

Advance the ability of themes / styles for Amahi

Added by Ryu almost 11 years ago. Updated almost 11 years ago.

Status:
New
Priority:
Medium
Assignee:
Category:
-
Target version:
-
Start date:
05/12/2009
Due date:
% Done:

0%


Description

Hiho cpg ;)
For the next Major-Release i would love to be able, to virtually overwrite the standard-templates with modified or maybe new templates from a theme. So the theme-designer is much more flexible, if he wants to!
If there are no templates inside the theme-package the system will use the standard-templates automatically. This way the designer/programmer could contribute a very customized styled design for the entire dashboard :)

Hope you like, talk to me or comment if you have any ideas to add to this! :)

History

#1 Updated by cpg almost 11 years ago

the themes work a bit as you described. there is a standard theme called "main".

the main theme is being included so that the other themes can override the css there.

i assume you mean CSS when you say templates (if not please clarify).

the idea is that the new themes inherit from this theme and new functionality, like, say, icons for the search engine results, are in the standard theme and the new themes don't have to provide it right away.

one thing that needs to be done is segmenting the main theme into a "base.css" that will have all the basics as a standard template and make "main" a theme proper, included and used by default. not a big issue, though, as it works.

just to be specific ... the main theme is in /var/hda/platform/html/public/themes/main/ and the stylesheet is style.css and the base stylesheet where we should put the standard things (still, can be overwritten is in /var/hda/platform/html/public/stylesheets/base.css).

now - is this what you had in mind? i suspect there is more, however, i am not sure. so if you can provide specifics, it will help!

#2 Updated by Ryu almost 11 years ago

cpg wrote:

the themes work a bit as you described. there is a standard theme called "main".

the main theme is being included so that the other themes can override the css there.

i assume you mean CSS when you say templates (if not please clarify).

the idea is that the new themes inherit from this theme and new functionality, like, say, icons for the search engine results, are in the standard theme and the new themes don't have to provide it right away.

one thing that needs to be done is segmenting the main theme into a "base.css" that will have all the basics as a standard template and make "main" a theme proper, included and used by default. not a big issue, though, as it works.

just to be specific ... the main theme is in /var/hda/platform/html/public/themes/main/ and the stylesheet is style.css and the base stylesheet where we should put the standard things (still, can be overwritten is in /var/hda/platform/html/public/stylesheets/base.css).

now - is this what you had in mind? i suspect there is more, however, i am not sure. so if you can provide specifics, it will help!

nope, you got me wrong! :)
when i say templates, i mean the bare html-structure, the skeleton you're filling with dynamic contents.
so, say, the theme-developer (just say so) would be able to restructure the menu with the stylepack :)

#3 Updated by cpg almost 11 years ago

  • Priority changed from High to Medium

moving to medium, for the next milestone.

is there a specific example of target implementation that we could choose?

i believe in incremental change, since revolutionary changes take a long time to really get done.

Also available in: Atom