We've received two requests for adding support for the R: StatET editor (http://www.walware.de/goto/statet)

PHPeclipse for me no color change :(

Currently, all the semanticHighlighting Keys are RGB values, this is not correct, these should be Hex values.

We've received a request to provide FreeMarker (*.ftl) support (FreeMarker editor is part of the JBoss IDE)

I used color theme for a few days, and set a color theme I liked. Now when I go to Window -> Preferences -> General -> Appearance, "Color Theme" is no longer listed.

It does however, show up in the installed list under Help -> Eclipse Marketplace -> Installed.

I tried uninstalling, restart, reinstall of color theme. Did not fix the problem. I see nothing about colortheme (or even the word 'color') in .log

We've received a request for TCL editor support.

It would be great to get the PHP editor added to the supported list.

Thanks!

hi!

IMHO the current preference page is at it's limits in terms of number of visible themes. Would you consider switching to a table (e.g. with checkbox)? It seems more convenient and common to see very long choice lists implemented as tables.
I'd be happy to contribute necessary changes to make this happen.

This was reported by someone in a Marketplace review, this screenshot demonstrates the problem:
https://skitch.com/fmaida/rmkek/eclipse-color-theme-issue

It not shown in the appearance menu at all after installing it

I use Eclipse Helios with FlashBuilder plugin to develop AS3/Flex projects with.

Upon downloading the plugin (4/28 release) I am required to restart eclipse after applying a theme.
If I don't, the only colors that change is the background color, and general text color - but not the rest of the color types.

I have verified with another install on a separate computer, and a friend also noted this behavior.

We've received a request for adding support for the TeXlipse editor. (http://texlipse.sourceforge.net/)

We've received the following issue:

I’m using both with CDT, and I have a remaining problem: The C editor evaluates #ifdef’s and insists on forcing the background color on #ifdef’d out code to some light gray. This makes anything in those sections mostly unreadable (and a bright eye nuisance). I have not found a way to either disable this behavior or change the default color it uses to something more suitable.
Would you have any clue?

Please add support for Scala

Comparison view (I don't know if it's a view - what you get when you do file comparison e. g. when synchronizing with CVS) has color definitions for incoming / outgoing changes. Lines with a difference are marked with a thin line using those colors. The changed part of the line itself has the "change color" as an overlay.
This works well with bright backgrounds e. g.: http://home.datacomm.ch/charon/bright.jpg but not for themes with dark backgrounds e. g.: http://home.datacomm.ch/charon/dark.jpg

You can barely see changes when using a theme with a dark background (e. g. compare the word 'outgoing' / 'incoming' that is marked with a red overlay in both screenshots or look at the 'outgoing addition' / 'incoming addition' lines - visibility is heavily reduced with a dark background).

Because of the overlay behaviour, changing colors for incoming / outgoing to some brighter colors does not help much - a bright background variant will always have superior visual clarity. It should therefore be possible to exclude the "comparison view" (or whatever that is) from being "themed".
(Ideally, there should be some sort of configurable 'exclude' mechanism for whatever editor / view ends up with a problematic visual appearance when themed because of some hard-coded colors or unfortunate color usage)

Is it possible?

Default mappings, for e.g. debugInstructionPointer (currentIPColor) are not working. Thanks to Rodrigo Baquero for pointing out that issue.

We've received a request for Ruby support.

Unable to create the selected preference page.
java.lang.String.isEmpty()Z

eclipse ganymede, jdk 1.5 and windows xp,

can u help me on this?

The background of source hover tooltips is configurable for C/C++ editors In Eclipse CDT Helios by going to the "C/C++ -> Editor" preference panel and changing the "Source hover background" setting in the "Appearance color options".

However, when you select a theme using the Eclipse Color Theme plugin, this setting is not changed. Instead it is left to whichever color was selected before. The default setting is to use the "System color" which is often (at least in windows) a light yellow color. This means that if you select a dark background theme, such as "Oblivion" or "Vibrant ink" which configure the default text foreground text to a light color, then the source hover tooltips become unreadable.

Thus, I think that the plugin should change the "source hover background" color setting automatically, either to the same color as the general text background selected by the theme, or to an approriate color selected by the theme.

java.lang.NullPointerException
at org.eclipse.wst.jsdt.web.ui.internal.style.java.LineStyleProviderForJSDT.handlePropertyChange(LineStyleProviderForJSDT.java:259)
at org.eclipse.wst.jsdt.web.ui.internal.style.java.LineStyleProviderForJSDT$1.propertyChange(LineStyleProviderForJSDT.java:55)
at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:375)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:372)
at org.eclipse.ui.preferences.ScopedPreferenceStore$2.preferenceChange(ScopedPreferenceStore.java:194)
at org.eclipse.core.internal.preferences.EclipsePreferences$2.run(EclipsePreferences.java:753)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:756)
at org.eclipse.core.internal.preferences.EclipsePreferences.put(EclipsePreferences.java:769)
at com.github.fhd.eclipsecolortheme.mapper.ThemePreferenceMapper.putPreference(ThemePreferenceMapper.java:50)
at com.github.fhd.eclipsecolortheme.mapper.JavaScriptEditorMapper.map(JavaScriptEditorMapper.java:33)
at com.github.fhd.eclipsecolortheme.ColorThemeManager.applyTheme(ColorThemeManager.java:144)
at com.github.fhd.eclipsecolortheme.preferences.ColorThemePreferencePage.performOk(ColorThemePreferencePage.java:46)
at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:964)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:447)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:169)
at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)

session data:

eclipse.buildId=M20100909-0800
java.version=1.6.0_22
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -showlocation
Command-line arguments: -os win32 -ws win32 -arch x86_64 -data c:/users/nfeger/workspace -showlocation

This is a continuation of log file C:\Users\nfeger\workspace.metadata.bak_0.log
Created Time: 2011-01-14 13:13:02.894

Flash Builder support seems to be broken in Flash Builder 4.5. Needs more checks and testing.

It would be awesome if we could customize the themes within eclipse, that way we don't need to create a whole new theme on the website for little alterations and we don't have to look at plain xml for editing

Open Window > Preferences. Click General > Appearance > Color Themes. Right pane of preferences window does not change, does not update to show color themes. Click away to some other settings pane on the left. Right pane updates. Click back to General > Appearance > Color Themes, and now see a theme list. Click a new theme, click OK.

Attempt to re-open Window > Preferences, get this error:

Unhandled event loop exception
org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
at org.eclipse.swt.SWT.error(SWT.java:4109)
at org.eclipse.swt.browser.Mozilla.initMozilla(Mozilla.java:1739)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:656)
at org.eclipse.swt.browser.Browser.(Browser.java:119)
at com.github.eclipsecolortheme.preferences.ColorThemePreferencePage.createContents(ColorThemePreferencePage.java:100)
at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232)
at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501)
at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674)
at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:867)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:865)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1700)
at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139)
at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1054)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:729)
at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:375)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:371)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.createDialogOn(WorkbenchPreferenceDialog.java:100)
at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:192)
at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:116)
at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:64)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

eclipse.buildId=M20110210-1200
java.version=1.6.0_25
Eclipse Color Theme: 0.11.0.201104281646

It would be great to have support for properties editor.

Here's a screenshot:
http://twitpic.com/3xfy2q

We should add support for the JAR Manifest editor.

The JSP files appear on a dark background and any contained Java is themed correctly, but JSP-specific code usually at the top of the file is still themed for use against a light background. For example:

<%@ taglib prefix="XXX" uri="XXX"
%>

Thanks!

We received a request for Groovy and GSP editor support in Spring Source Tool Suite. I'm not sure if our Groovy support works for SSTS.

Here's what oblivion looks like in pydev with the default settings http://imageupload.org/?di=012989945211, note the [] are black. This comes from prefs > pydev > editor > appearance and color options http://imageupload.org/?di=13129899485210

The colors in the theme should override these values, alternatively they should be set to the theme colors.

PHP variables are black with the Inkpot theme - that's very hard to read.

Plugin Development Environment (plugin.xml, MANIFEST.MF)

It seems that the pydev plugin uses a separate entry in General->Editors->Text Editors->Annotations->Occurances. There is the default one which is being updated correctly and then there is one labeled "Occurances (Pydev)" which is not being set eclipse-color-theme plugin.

We've got a request to provide support for the Perl editor (EPIC).

Unable to create the selected preference page.
java.lang.String.isEmpty()Z

that is the message i got with the "Z" included
3.6, MAC OSX 10.5.8

Due to a few requests, it should be possible to delete imported themes.

Hi guys! I tried a visual studio color theme for Eclipse. Works almost perfect :)

If i decalre a variable of type String. It color as it should be (light blue). But if i declare a View (android class) object or an instance of my own created class they are all just black instead of light blue (which the String is colored as)

public void MyMethod()
{
String myString; // String will be blue and myString black.
MyOwnClass myOwnClass; // Both will be black.
}

Any ideas? =)

We've received a request from @diwakergupta to add support for coloring checkstyle warnings.

We've received a request for adding CFML / ColdFusion (CFEclipse) support.

Hi, thanks for the great plugin!

Would it be possible to please extend the theme coloring to the views (e.g. project explorer, outline, etc.) as well?

This would make the entire UI consistent and for those of us blinded by the default white, the ability to use a dark theme for the sidebar (i.e. the entire visible area).

Aptana Studio 3 editors (specifically Pydev) don't currently work with either the plugin or the .epf files.

AS3 merges all of Aptana's plugins (including Pydev) into one big package, and while most things about Pydev appear to still be separate-ish, it merges their syntax highlighting features into Aptana Themes (Preferences > Aptana > Themes).

Indeed, when I export an .epf of my own configuration, the preferences applied by eclipse-color-theme (in org.python.pydev) are there, but the preference which (I'm guessing) controls what's actually seen is this: /instance/com.aptana.theme/ACTIVE_THEME=Mac Classic. I've discovered a page which documents how Aptana themes are laid out but I've still no idea exactly where the "Mac Classic" theme data is actually stored.

I'm using the 2011-02-16 Release Candidate version of AS3 (according to the release notes there'll be a stable release in Q1, which I presume means sometime this month).

from Valentin Simonov:
The most annoying color is ActionScript Occurrences at Preferences -> General -> Editors -> Text Editors -> Annotations. It’s that color with which similar stuff is highlighted when you select some lexem.

Install ir_black theme via epf file. Theme installs fine and updates editors fine.

However, go to theme preferences, and ir_black does not show in themes list.

We've received a request for Erlang (ErlIDE) support.

We've received a request for adding support for the Force.com IDE (http://wiki.developerforce.com/index.php/Force.com_IDE_Installation)

We've received a request for providing XSLT editor support.

This is a new bug in 0.9. It was working as expected in 0.8.

We've received a few requests for Adobe CFBuilder Support.

We've received a request on providing support for the Flash Development Tools (FDT4).