bjorn wrote:I think it is hard to figure out how to integrate external editors.
Indeed, that's quite tricky. The increased complexity is primarily due to the possibility that plugins can use the editors now very easily. Before CMSimple_XH 1.5 a plugin requiring an HTML editor had to include one itself (cf.
SMU vs.
Extedit_XH) or did offer a textarea only (cf.
Also vs.
Coco_XH). After all, there is
some documentation available in the
CMSimple_XH wiki (should be improved, however).
bjorn wrote:I also find it difficult to understand why there is both a defaultconfig and a config to be included one after the other.
That was meant as a simple way to solve update issues. When doing an update, one only has to upload defaultconfig.php (not config.php), and any new settings will be added to the (possibly modified) settings of the old version. That's basically the same for the language files, what's documented in the
CMSimple_XH wiki. After saving the new configuration (resp. language settings) one can delete defaultconfig.php (resp. default.php). However, in the long run we should have an update script, so merging of the configuration and localization can be done there, so it's not necessary to read the default(config).php on each page request.
bjorn wrote:If we want to attract more developers I think we need a better manual and especially some good examples of plugins and user functions.
I agree (and IMO attracting more developers is mandatory for the success of CMSimple_XH in the long run). A bit is already there in the
developer manual (the plugin tutorial tackles the basics of writing a plugin). For CMSimple_XH 1.6 generated code documentation will be available (a somewhat outdated version can be seen on
http://3-magi.net/doc/).