Dowson_Jim(a)emc.com wrote:
Specific issues to implement/fix
================================
WYSIWYG editor stability
- Table behavior (a new table editor would be welcome)
- Whitespace processing
- Misbehavior in the presence of code or complex styles
Thanks for the WYSIWYG wishlist. We'll take all this into account with
the new editor.
We believe that by using GWT we can build an editor that is much more
stable and capable of advanced stuff usefull in the wiki.
This will be possible especially thanks to unit testing since the GWT
code is java compiled to JS. GWT also gives us the possiblity to have
browser specific implementation of some of the code which allows to not
polute the JS code with browser specific stuff when it's not necessary.
Furthermore we will built real-time editing (multiple persons editing
the same page) in the editor. We already have a prototype working of this.
Attachment handling
- memory / resource demands
- proper versioning (if 2 different users upload the same
document name)
Wishlist
========
- Table of contents macro a la mediawiki
There is {toc}. It might just be a style issue to make it like mediawiki.
- WebDAV would be nice...
We also have a prototype of this, though it doesn't currently make it in
our priority list. We have proposed it for the Google Summer of Code. If
any student is interested it's a fun project.
We're looking to contribute the notion of a simple
reputation engine
(user and content rating) that we have in prototype now.
Great ! We want it !
Ludovic
--
Jim Dowson
CTO, Global Services, EMC Corporation
Linx: (617) 598-0505
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Ludovic Dubost
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost