Summary: | The e4 CSS editor to edit Eclipse themes, once installed, replaces the default CSS editor from WTP | ||
---|---|---|---|
Product: | [Eclipse Project] e4 | Reporter: | Mauro Molinari <mauromol> |
Component: | Tools | Assignee: | Project Inbox <tmf.xtext-inbox> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | davewb, dennis.huebner, Lars.Vogel, psuzzi |
Version: | 0.15 | Keywords: | bugday, helpwanted |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Whiteboard: |
Description
Mauro Molinari
2014-05-29 04:59:08 EDT
Moving to e4, since I just reproduced that this problem starts to happen as soon as I install the e4 CSS Editor. In Luna too. In my original report, I put a wrong reference to another bug. The correct one is bug #345945. Anyway, I also think there's a second problem here: can't the inclusion of Xtext, at least in this invasive way, be avoided if the user just wants the e4 CSS Editor tool? No one is looking at this editor at the moment, but we'd consider a contribution. PW Hi Paul, in bug 388476 you say to use this to restore the MRU functionality of tabs, but at the same time no one is taking care of this editor which is invasive even if you install it only to enable the aforementioned feature. Not a good user experience :-( What I recently observed is that once this starts to happen (i.e.: after installing the e4 CSS Editor for Eclpise theme CSS tweaking), you end up with two "CSS Editors" in the "Open With" contextual menu. The one which is set as default is the one that continuously asks to add the Xtext nature to the project. Also, this "broken" editor has many problems with CSS validation (code assist does not work, invalid errors are reported on valid CSS text, etc.). As a workaround, the user can change the default editor for *.css files in Window | Preferences | General | Editors | File Associations. However, user experience is severely affected, especially because the workaround is not obvious (it took me a while to discover that I had two "CSS Editor"s installed). FYI: #345945 was fixed. Thanks Dennis, surely useful but, paradoxically, the possibility to "remember" the decision may hurt for the very specific defect described here, because the user may not realize any more he's using the wrong CSS editor, with all the consequences it brings. I'm going to update this report title based on what I lately discovered. I too have this problem: basically e4 completely overtakes the CSS Editor in eclipse. I've uninstall e4 plugin as it basically completely overtakes the CSS Editor in eclipse and my issues go away. You cannot select the WTP/PHP CSS editor over the e4 CSS editor from the 'open with' menu. e4 causes all the WPT/PHP CSS files to be reported with errors. The following is a valid CSS, but e4 reports 1-3 issues with the '.' and missing/mismatched curly brackets. .bullNote { font-size: 0.8em } e4 has made a bad decision to 'hi-jack' css file extension for what is its own form of css. Ouch. e4 css editor has been retired a while ago. |