Defect #31
Themes :: Support for Themable component resources
| Status: | New | Start date: | 12/15/2009 | |
|---|---|---|---|---|
| Priority: | Baixo | Due date: | 01/27/2010 | |
| Assignee: |  Marcelo Coraça de Freitas |
% Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Support for themable component support isn't available. Actually, the resource can have templates but they don't support themes. Thus, when changing the layout of a page the user must hard code some component changes which isn't good at all.
This should be available so we make a really nice public release.
History
Updated by Marcelo Coraça de Freitas about 2 years ago
- Status changed from New to Accepted
as this is very important for the implementation of the kvdriver utility and other tasks (such as packaging web applications into zip files and stuff), I'm going to spend some time brainstorming on this.
Updated by Marcelo Coraça de Freitas almost 2 years ago
- Status changed from Accepted to New
- Priority changed from Alto to Baixo
I haven't really had the time to work on this and it's not a high priority task at all! It's just a nice feature to have in the framework.. gonna work on this in a few months.
Updated by Marcelo Coraça de Freitas 10 months ago
I've just had one idea on how the resource searching could work.
The Locate_Resource method already supports locale. Other thing we can add is support to the Themes doing like this:
look for:
[data]/[component]/[theme_name]/resource/path.extension
then
[data]/[component]/resource_path.extension
in case the first one can't be found. In other words, just add the theme name to the path URI.
There is a catch though. Checking if every one of those files exists can be resource consuming (as it will check up to 3 times in each path thanks to the locale support). Some kind of registry could be built then for this functionality.
As the locate_resource function is the same, used everywhere in the framework, it could be easy to implement;