30 Nov
2009
30 Nov
'09
7:19 p.m.
Hi devs,
coming back with a fourth solution for this problem, described here:
http://dev.xwiki.org/xwiki/bin/view/Design/AnnotationFeature#HSolution4adda…
based on leaving the annotation rendering job to a specialized renderer
depending on the format in which we want to render (an extension of the default
renderer for that format).
It also provides an incremental approach to solving the optional features
desired for annotations.
We really hope this solution is final, as we should start implementing something
by now.
WDYT? Any blocker in the vision described there?
Also, with this solution being slightly complex and the delay caused by
converging to it, the roadmap should be delayed by 2 weeks, to the end december
/ mid january.
If we prefer to have a working version of the annotations as they are right now
(with serious limitations in what concerns the annotated content and quality of
UX), we could move UI stabilization (test js, cleanup the xwiki annotations
application, etc) closer and add the annotation module on the platform to be
released / used.
WDYT?
Thanks for your involvement,
Anca
On 10/30/2009 05:21 PM, Anca Luca wrote:
Hi devs,
following a discussion with Fabio about the second desired feature for
the annotations, namely the ability to add annotations on any document,
no matter how its content is generated, we came up with the solution
described at
http://dev.xwiki.org/xwiki/bin/view/Design/AnnotationFeature#HSolution1stor…
, the main idea being that annotations would be defined by their
selected text and a context (as opposed to offsets) and would be
identified to be rendered in a document on a serialization of the
transformed XDOM of the document, this way taking into account any macro
rendering, document inclusion, etc.
WDYT about this solution?
Also, because the implementation of this, though relatively localized,
comes together with refactor and cleanup of the annotations module
(update everything so that annotations don't store and use offsets
anymore, remove classes & functions which are not needed in this
simplified process), I propose to include this improvement in version
1.0 of the annotations module (so that we don't cleanup and release what
we know for sure we'll delete) and push the 1.0 version further to mid
to end December.
here's my +1 for this,
WDYT?
Happy coding,
Anca