*My reply was sent too fast once again today. Here's the full version.* Hi guys, > > [lots of snapping below] > > *Marius* > >> >> Marcela is working on the UI and underlying services (Insert Link >> >> dialog mainly and needed services) and as soon as I finish the points >> for >> >> 1.7M1 I'll review and integrate her code. >> > *Guillaume*
> I have pinged Laurent on the topic, he will deliver his UI mockups before > the end of the week so that Marcela can keep her work going. > > *Marius* > >> >>>> Here's the roadmap I propose: >> >>>> >> >>>> * Fix current issues >> >>>> >> >>>> ** Write Selenium tests for all current features (JV). >> >>>> ** Provide a Range/Selection implementation for IE. (fixes >> >>>> XWIKI-2737, >> >>>> XWIKI-2738, XWIKI-2739). One option is to wrap this JavaScript code >> >>>> >> http://jorgenhorstink.nl/2006/07/05/dom-range-implementation-in-ecmascript-completed/ >> >>>> . I have Jorgen's permision to use his code. This will save me from >> >>>> implemeting it by myself (which is the second option). The third >> >>>> option >> >>>> is to use the selection support from rocket-gwt library ( >> >>>> http://code.google.com/p/rocket-gwt/wiki/Selections ), which is >> >>>> limited >> >>>> right now. I'm waiting for an answer regarding their roadmap. 24 >> >>>> man-hours >> >>>> ** Reimplement list support. (fixes XWIKI-2734). The default >> >>>> implementation doesn't wrap nested lits in a list item element and >> >>>> fails to detect the presence of a list when the cursor is on a list >> item >> >>>> with a nested list inside (generated by the wiki editor). >> Indent/outdent >> >>>> for nested lists have to be reimplemented also. 16 man-hours >> >>>> ** Improve history mechanism (fixes XWIKI-2731). I should restore >> >>>> the previous selection on Undo/Redo. Right now, only the cursor >> position >> >>>> is restored. 8 man-hours >> >>>> ** Reimplement the heading (using id's and possibly named anchors) >> >>>> and improve the Format plugin (by adding Inline and Paragraph options >> >>>> besides Title X). 8 man-hours >> >>>> ** Fix horizontal rule generation. (fixes XWIKI-2729) 2 man-hours >> >>>> ** Fix Insert Symbol features so it won't require any special >> >>>> encoding. (fixes XWIKI-2669) Right now I have no idea on how fix >> this. 6 man- >> >>>> hours >> >>>> ** Use the same styling in edit mode as in view mode. (fixes >> >>>> XWIKI-2721). I have to check what CSS rules from the Toucan style >> sheet >> >>>> messes up the editor. 8 man-hours >> >>>> ** Fix cursor issues (navigation through empty DOM nodes using arrow >> >>>> keys; avoid cursor hiding when the user clicks on an empty DOM >> >>>> element). 8 man-hours >> > > *Vincent* > >>> Since we're getting very close to the 1.7M1 release (on Monday), > >>> could you please let us know the status for each item above? > >>> > >>> This will also allows us to help you in re-testing them all. > > *Marius* > >> >> Unfortunately I managed to do only the second point so far. I'll commit >> >> today the W3C Range and Selection implementation for IE. It took >> >> longer because in the end I had to do my own implementation. >> > *Guillaume* > Since work on the new editor is taking longer than expected, I made a > prioritized list of the features that are crucial for XE 1.7 final. Marius & > Marcela, please tell me if you need more details (aside from upcoming > mockups). > > *Features we cannot ship the rich text editor without (those features have > to work the same in IE6 / IE7 / FF2 / FF3):* > > 1. Hitting return creates a new paragraph > 2. Clicking on the Bold / Italics / Underline / Strikethrough buttons > applies the style to the current text selection > 3. Clicking on H1 / H2 / H3 / H4 / H5 turns the current line into a > header. Other style options are greyed. Clicking again turns the line of > text back into normal text. > 4. Clicking on a list button triggers the matching list behavior > (either bulleted or numbered). Lists can be indented. > 5. The user can turn a text selection into a wiki link. He can browse > for the wiki page he wants to link to or search for it. > 6. The user can turn a highlighted text selection into a link towards > an external URL > 7. The user can turn a highlighted text selection into a link towards a > new (currently not existing) wiki page > 8. The user can select an image on his local computer and insert it > into the wiki page > 9. The user can select a file on his local computer and attach it to > the wiki page > 10. Table insertion: the user can insert a standard wiki table and > define how many rows / columns it should have. > 11. A table cell can include a list, an image or a header > 12. Macro insertion: the user can select a macro from a list and click > on insert to add that macro to the page > 13. Macro rendering: the macro content is shown with a rectangular line > around it. When the cursor is put within that line, the macro background > color changes. A "refresh" button is available for the users to refresh the > macro's rendered content. > > In this order of priority. I'd like to highlight the fact that the single biggest complaint about the current editor is that, often, clicking on a button does not lead to the expected behaviour on the part of the application. Therefore, we need to make sure each feature behaves as expected under all 4 browsers before starting work on the next one. I know this sounds obvious - so let's make sure it becomes a reality ;-) Thanks all for your hard work making the editor real ! Guillaume > -- > Guillaume Lerouge > Product Manager - XWiki > Skype ID : wikibc > http://blog.xwiki.com/ > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
