19 Oct
2008
19 Oct
'08
1:27 p.m.
Vincent Massol wrote:
On Oct 17, 2008, at 11:20 AM, Marius Dumitru Florea
wrote:
+1
Hi Vincent,
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 because:
** I haven't received an answer to my question on GWT Google Groups
(see
http://tinyurl.com/67v4do ).
Maybe you could ping them kindly again?
** The selection support from rocket-gwt library
is very limited right
now which makes it unusable for WYSIWYG editing (see
http://tinyurl.com/5pvul5 ).
** Jorgen's Range implementation is generic, independent of any
browser,
relying only on DOM API, but in order to use it you need to be able to
make the browser aware of that range and for this you need of course
browser dependent code. I think that using such a generic
implementation
and writing the code to apply it to IE will result in a slower editor
than using an implementation for Range that relies directly on IE's
API,
which I did in the end.
* I spent some time with my evaluation and Ludovic's trainings.
Thus I propose we postpone 1.7M1 with 3 days (23rd of October, in the
morning) so that I can finish the rest of the points for this release.
I don't think we should do that. There's no warranty it's going to be
only 3 days and it'll probably slip by more. I prefer that we keep our
defined dates and release 1.7M1 as planned. It won't change anything
for you since you can finish those for 1.7M2 if you don't succeed in
finishing them for 1.7M1 (would be best of course).
> 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.
>
> Thanks,
> Marius
>
> Vincent Massol wrote:
>> Hi Marius,
>>
>> On Oct 7, 2008, at 12:30 AM, Marius Dumitru Florea wrote:
>>
>>> Hi there,
>>>
>>> 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-…
>>> . 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
>> 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.
>>
>> Thanks
>> -Vincent
--
Sergiu Dumitriu
http://purl.org/net/sergiu/