Community
Participate
Working Groups
In ThemeEngine starting in line 105, I found: //Check for old css files File oldModDir= new File( System.getProperty("user.home") + System.getProperty("file.separator") + ".e4css" + System.getProperty("file.separator")); //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ if (oldModDir.exists()) { File done = new File(oldM I'm not aware that we support CSS files in the user.home. Does anyone know if that is old testing or migration code? Git history points to Bug 374485 but the discussion there is very small. https://bugs.eclipse.org/bugs/show_bug.cgi?id=374485#c1 indicates that the SDK used to write to this location. I don't think we still doing that. I suggest to delete this code, unless someone remembers why this is still necessary.
Tom, Brian, does user.home/.e4css bring back any memory?
I think this was to support user customizations of the CSS via the Preferences > Appearances.
(In reply to Brian de Alwis from comment #2) > I think this was to support user customizations of the CSS via the > Preferences > Appearances. Do we still support this? I remember this used to be possible but I have not seen that in a file.
(In reply to Lars Vogel from comment #3) > Do we still support this? I remember this used to be possible but I have not > seen that in a file. After thinking about this feature, I think it is actually super useful. This would allow the user to customize the L&L of Eclipse without the need to develop plug-ins. So I plan to polish the code a little bit, test if this still works and afterwards publish it.
I thought it was supported, but the little appearances doesn't show up. We should place this directory in the appropriate application-data location rather than ~/.e4css or some other directory in $HOME.
Mass move to M4.
Mass move. Please move back to M6, if necessary
*** Bug 535580 has been marked as a duplicate of this bug. ***
From a end-user perspective, here is a workflow that I think would be really nice: 1. User open the "Appearance" preference page 2. In the theme selection combo, there is a "custom theme..." entry 3. Upon selection user is suggested to create a new CSS file, and is asked whether they want to use one of the existing themes (CSS) as template 4. User selects a template and clicks apply. 5. The CSS theme is applied and the e4css file (hosted under workspace metadata probably in a 1st time) is opened in the editor 6. Whenever author saves the file, the theme is automatically refreshed. 7. From the preference, when "Custom theme..." is used, there is a link "open CSS theme file" to easily find the CSS if the user closed it.
