Yup.On 09/05/2012 11:03 AM, Max Rydahl Andersen wrote:What few classes exactly ? link to github ?For the example I've just checked, only this one seems necessary: https://github.com/jeeeyul/eclipse-themes/blob/master/net.jeeeyul.eclipse.themes/src/net/jeeeyul/eclipse/themes/rendering/ChromeTabRendering.javathis class seem to depend heavily on HackedCTabRendering and themes* classes ?
Maintainance effort are probably very low. But we could also ask to split the bundle into several bundles (common, renderers, editor) so we could reuse only common and renderers.for me it seriously feels like overkill to start depending on an external project for something like css theming.It also provides the nice Theme editor in preferences. But I'm not sure that's something we want to provide.well, I don't find it like something we would want to maintain would we ?
Yes it is.Would it make sense to fork these classes instead ?Sure we could.is this class something the css styles would reference as a "alternative rendering" ? What does this one actually fix ?