I plan to move the HTML module (and some other) out of the core.
What kind of change do you want to do ?
The first change we are making is using a wysiwyg editor. We're implementing http://www.kevinroth.com/rte/demo.htm. But more importantly nukes shouldn't ristrict te user to a certain editor. Maybe its possible to use some kind of template or something (because the code for a normal textfield doesn't differ much from the rte textfield). That way admins kan implement the edit facilities they like without 'hacking' it into nukes.
Maybe its reusable to. Just have 1 wysiwyg editor and not only use it for editing a whole page, but also for news items or something (maybe even for the forum, but they use bbcode so that's a little different ;) )
I'd definitely agree that Nukes needs to be a bit more user friendly. But i do understand from my own developments in the past, that it's often more important to get the project up and running before worrying about ease of use and look & feel. My own personal usablity issue is that when i login it sends me back to the home page. So if I'm trying to post to a forum and i have to login, then i'm back at the home page and have to go find the right forum message again. But i know how to fix that one so it's no big deal.
The first change we are making is using a wysiwyg editor. We're implementing http://www.kevinroth.com/rte/demo.htm. But more importantly nukes shouldn't ristrict te user to a certain editor.
A WYSIWYG editor would be great, and making it pluggable would also be very nice. If you're looking for a good, free, open-source one to use, take a look at HTMLArea (http://www.dynarch.com/mishoo/htmlarea.epl). Originally made by interactivetools for IE, it now works great in Mozilla and has a plugin architecture for things like spell checking and table operations.
I am thinking of bringing the concept of plugin in the HTML module. A plugin would be responsible for editing, modifying, etc... a file in that module. Do you think that could bring flexibility ?