Community
Participate
Working Groups
The "classic" theme has been created when changing the default theme in 1.4. It contains the theme that resembles the RAP 1.3 default theme. Since this theme looks very old fashioned, and currently would have to be adjusted for every theme change, I'd propose to remove it entirely.
+1
(In reply to comment #0) > I'd propose to remove it entirely. +1, I think we should remove themes based on their relevance to our core user base. But if RAP provides several theme bundles, what would be the lifecycle for them? I just envision that if have several themes (Default, Dark, Business, Fancy, etc.) that eventually it will become a maintenance burden anyway. Do we want to just maintain a static number or do we want to push those themes to the incubator and allow others to maintain them?
(In reply to comment #3) > I just envision that if have several themes (Default, Dark, Business, Fancy, > etc.) that eventually it will become a maintenance burden anyway. Do we want to > just maintain a static number or do we want to push those themes to the > incubator and allow others to maintain them? I agree that we have to keep the number of "official" themes small to minimize the maintenance cost. Currently, we have the default, business, and fancy theme. I doubt that we'll have the time to create more themes (Dark, mobile, etc.) for 1.5. Once we do so, we may consider to replace the fancy theme, which doesn't seem to be really used...
I've replaced the contents of the rwt.theme.classic project with a readme file in CVS HEAD.
