Hi
There is a need (for RTL guys ...) to search themes based on there RTL support
today the only way to know this is by the title , or the text supplied by the themer
My suggestion is to add an RTL attribute to themes in the repository.
the default will be false, when a theme will support RTL (this means Bi-directional), this attribute will be set to true
this way when RTLing a theme the RTL css files can be added to original theme project, and there will be no need to add a new (another) theme with RTL name
This is needed now more than ever because of drupal 6 rtl support
Avior
Comments
Comment #1
dwwYet another good use case for http://drupal.org/node/93055
Comment #2
avior commentedyes you right,
As more as i think about this there is need for more attributes for themes like
browsers compatibility , layout ...
[ ]rtl
browsers compatibility
[ ]firefox 1.X
[ ]firefox 2.X
[ ]ie 6.x
...
..
layout
[ ] 2 columns
[ ] 3 columns
------------------
[ ] flexible
[ ] fixed
and so on
Comment #3
druvision commentedI suggest to create a new vocabulary in Drupal.org, which will be special for themes, then add those attributes as terms. This will allow themes to be categorized, in a similar way to what's done for modules today. The copy the module's code and display the themes in a similar way. This is a good idea, since the themes list is way too long anyway. And it is relatively simple to implement. This will allow the theme owner to update the information via drupal.org, when the theme is uploaded.
Another option would be to add those attributes to the theme's ".info" files. This will be harder to implement, harder to add new attributes, with the only adventage that the information will be more structured. I tend to avoid this option.
How to update the attributes for existing themes? The 'RTL' attribute on the info file may be automatically updated whenever an style-rtl.css file exists for the theme. But there is a limited number of such theme, so I suggest that the update will be done manually. Also - it's the responsibility of the theme creators to update the other attributes but I suggest the initial update would be done centerally, in order to initiate the process and encourage people to continue
Themes classification won't catch the sub-themes (which may not be RTLised yet), but I think it's fairly general so I would say go with - add the needed vocabulary and associate it with themes.
This is fairly easy to implement and would be a great addition to the drupal.org infrastructure. Moreover, it can be implemented immediately, without waiting for drupal6.
I suggest that the new vocabulary will contain all the mentioned terms in an hierarchical way:
Let's begin with this basic list that will grow over time.
Amnon
-
Professional: Drupal Hebrew | Drupal Search
Personal: Hitech Dolphin: Regain Simple Joy :)
Comment #4
gábor hojtsyWell, the problem is explained by the issue dww pointed to. All projects use the same node type, either if they are modules, translations or something else. So it is not possible to assign them different taxonomy vocabularies. This can be either fixed by tweaking this around, or forking the project node type to specific node types per project type. (I have also commented on the issue dww pointed to).
Comment #5
killes@www.drop.org commentedComment #6
s.daniel commentedThis feature could be helpfull to find subthemes of Zen theme for example.
tracking
Comment #7
silverwing commentedMarking this as a duplicate of #852342: Configure extra fields for theme projects