For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 11 replies, 4 voices, and was last updated 7 years, 4 months ago by
.
-
Posts
-
We prefer the JSF XHTML support already in Eclipse and its editors, but every time we open the workspace CodeMix is automatically setting the default editor for XHTML type files to the CodeMix HTML editor. Looking at the CodeMix preferences Languages -> Preferred Editors do not see an entry for XHTML file types, so can not find a way to turn this off.
This topic was linked to an Issue on April 20, 2018 at 7:24 amEric,
Thank you for the report, we’ve been able to replicate this problem.
We have a hot-fix release due today, and we’ll try to get the fix in – will let you know when the fix is available.
Eric,
Sorry that we could’t get the fix in for the hot-fix release.
The reported issue has been logged in our issue tracker – see the top of this thread for a link. Feel free to vote-up this issue, as well as others you find important!
https://www.genuitec.com/go/codemix-top-issues–Swapna
Genuitec SupportEric,
I’ll just note that we already have the fix in hand – it was a bit complex as there were multiple edge cases for how content types and file extensions are used as part of editor registration and prioritization. This will be out in the release this coming Monday.
Cheers,
TimEric,
The fix for the problem with files defaulting to open with CodeMix editors is out with the April 30th release. Please update to the latest version of CodeMix from Help > Check for Updates and let us know how it works for you.
Appreciate your feedback.
–Swapna
Genuitec SupportI have updated to Release CI 2018.4.30, did a clean start of Eclipse, did a restart of the computer, and the issue is still there. This is a show stopper for the development team. Until CodeMix is fixed and honors the defaults that are set in the Editor – File Association we can not recommend CodeMix to the rest of the development team.
Eric,
We ran a few quick tests and this setting appeared to be working fine.
A quick sanity check: I realize you mentioned in your first post that you couldn’t find an entry for XHTML – the entry is under the HTML node (see attached screenshot). Did you find it later, and do you have this entry unchecked?
Following up with another question, Eric – when you uncheck / check the
*.xhtmlentry, it takes effect immediately, without no restart required. So double clicking an XHTML file immediately after clicking “Apply & Close” on this page should result in it being opened with the CodeMix editor (or not).After you restart, if you go to this page again, do you find that the setting has been reverted?
Also, if you had explicitly opened a file with a particular editor using the “Open With” option, that setting will stick irrespective of the settings on this page – the selected editor would always be used.
My fault, I misunderstood how the fix was implemented into CodeMix. The screen shot helped to explain the change that was made, so when I unchecked *.xhtml it did immediately change from the CodeMix default editor back to the editor that understands JSF Facelets. After restarting Eclipse the workspace preferences are now being preserved. Opening with a specific editor has always worked and stick between opening the workspace. We feel much better about this now and can recommend CodeMix to the rest of the development team. Thanks very much for the responsive fixes, changes, and correspondence!
Eric,
No problem – we’re relieved that the fixes we made are working as expected. We’ll look at making this setting more intuitive as well.
We feel much better about this now and can recommend CodeMix to the rest of the development team.
Fantastic! We’re curious to know what you are using CodeMix for in your current environment – if you can spare some time to share some brief notes, that would be great!
We are a Java Enterprise shop and several of us are part of the front-end development team. We will use CodeMix for SASS and SCSS/CSS file types; Node.js; JavaScript and ES6 modules/classes; knockout.js and nunjucks templating/frameworks; and TestCafe test scripts in JavaScript ES6.
