I think I've about finished the rich-text project. At least I feel like that I reached the most important goal of it, a 'rich text editor'. Details like integration into generic or editwizard editors I'll leave as an exercise for the reader.
There remain some things to be done though. First of all some application must be composed which can install and demonstrate the new features. Until know I've done my work on three places: 1 CVS repository for the site I was needing this for 2 mmbase head. 3 mmbase speeltuin I want to change this in: 1 richtext application - This contains example object-model and templates, xslts - Perhaps some plug-ins on core. (processors, importers etc). - I'm intending to provide a 'mmbase documentation import utility' to provide example data 2 mmbase head - Some of the more generic or cumbersomely moved stuff can simply remain here. 3 kupu's repository? - I've created extensions on 'kupu' (now in speeltuin). This can be moved to '1', but I could perhaps also check it in in the subversion repository of kupu itself (I figure it can either be seen as a kupu-plugin on mmbase or as an mmbase plugin on kupu....) Question: I think we should 'maintain' richtext, so I would be going to make a new subdir in the 'applications' module. But if people feel differently I can also make it under 'contributions'. Without reactions on this question I will, on behalf of the rich-text project, create a 'richtext' sub directory in 'applications' soon, and finish development there, approximately along the lines as described. Michiel -- mihxil' http://mihxil.komputilo.org/ nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
