Felix Riesterer wrote:
Could you imagine using part of tinyMCE's functionality to create a similar thing?
While I would also highly appreciate such a functionality, IMHO the TinyMCE team has many other much more important things to concentrate on(as they already mentioned on these forums).
There are also a few arguments against such a feture in TinyMCE:
- it adds another layer of complexity in a place considered "uncomplex".
- it removes the "last chance" to se "What You Really Get" when the browser goes crazy and the WYSIWYG does not behave as desired (this happens more ofthen that one might think).
- TinyMCE WYSIWYG is mostly made for "users" (at least most of the "users" of CMSes have no idea of programming, nor HTML), and only very few of them use that functionality at all.
So, IMHO, where it would be nice and look cool, it would not be worth the effort.
There are other many features that would be usefull for more potential MCE users.
Felix Riesterer wrote:
What do you think? In my CMS I added a second code editor for additional CSS code, so this syntax highlighting feature would be a great benefit! It could also lead to some better HTML code layout in the main editor... ;-)
IMHO if one still wants such a funtionality, it should not be in TinyMCE, but as a separated project, independent
of TinyMCE. If you feel that you can, you could help improve the highlighter you proposed so that it's not that buggy and integrate it as a separated thing.
I already used (and saw in other projects - so it wasn't my idea ) a similar approach:
1.- in the FileManager/Browser or Menu from where one would call the WYSIWYG, add an extra entry: "Edit as Plain Text".
2.- allow this only for advanced users (and admins) so that simple users won't mess the site up - not even by mistake.
3.- now this "editor" should/could be enabled with hightlight since it can edit CSS/JSPs ,etc.
I did the above approach and after a while I always reverted #3 back to a normal textarea because the editor highlighter you mentioned is not reliable enough and pretty complex to be able to improve it from my point of view. Everything I tried to improve on it, was not enough. I such cases when one is not using the WYSIWYG to edit CSS and JSPs (and somethimes to clean up HTML), reliability is much much more important than other fancy highlight.
If highlight is is still very important, I do a copy and paste in an intelliget IDE like IntelliJ IDEA and there I have not just highilight but also "live inspections", "completion", "error checking" etc. (I suppose no one wants to build on the Web what desktop IDEs can - since this is hard enough on the desktop).