Hello developers,
I've stumbled across this issue while developing Pagemanager. I didn't want to have too many config options, so I decided, the user can have additional functionality by customising the stylesheet. To make that easier, I've added comments and out-commented code to the stylesheet.
The current situation: if the user want to edit his content (i.e. the pages), he could use a modern WYSIWYG editor, with all the bells and whistles one could expect from a modern word processor. But if he wants to edit the template, the stylesheet or a plugin's stylesheet, all he has is a plain textarea.
An idea: what if the textarea would be replaced by a syntax highlighting editor? As I just found out, there several available under licenses, which would allow them to be shipped with CMSimple. Particularly I found CodeMirror which has recently released new version, and which seems to be easy to integrate, and could be used for either html or css.
My considerations: would that be really useful? Most end-users won't mess with the template or stylesheets at all, because they're not experienced in HTML or CSS; having syntax highlighting might not help them. Power users probably prefer to edit those files with an ftp capable editor of their choice.
OTOH: the possibility to edit template and stylesheets from the back-end is already given. And IMO it's a reasonable feature, so anybody is able to do at least minor changes to them, without the need to have a ftp capable editor available, or even the need to download-edit-upload the files. If this is already possible, why not increase the usability by including syntax highlighting (and perhaps some more common aids in writing source code)?
Because my considerations given above, I'm not sure if it should be integrated to CMSimple's core. But it can't be developed IMO as a plugin, because of missing hooks. Shouldn't those be added to the core, to make it possible to develop a plugin that will give better editing capabilities for template and stylesheets?
I will have a further look at the possibilities to implement such a solution, if there is interest.
Any comments appreciated.
Christoph
PS: You don't need to worry about the general overhead of having just another plugin. I've already found a very simple solution not to include any plugin files for back-end-only plugins, in the case there is no /plugins/PLUGINNAME/index.php.

