3 Jul
2008
3 Jul
'08
4:30 p.m.
Hi Fabio,
I think the Xdomexplorer can be a replacement (a better one that too)
to the content outline that I had done.. just minor changes required..
I'll keep you posted.
Venkatesh
On Wed, Jul 2, 2008 at 21:19, Fabio Mancinelli
<fabio.mancinelli(a)xwiki.com> wrote:
On 2 juil. 08, at 20:12, malaka ekanayake wrote:
Thank you very much for the finding.I think what you are saying is
correct.I wrote a wrapper class of FastPartitioner and see what are
the methods which are called when typeing.It shows that for each
keyperss the following methodes woll be called to repartition the
document
getContentType
documentAboutToBeChanged
getPartition
documentChanged
getPartition
computePartitioning
If I'm going to use the rendering passer then I need to recompute
the XDOM for each keypress and it would be too costly to do.
Right.
I will first look at the sample parseres you
have given above and
try to write a xwiki parser that suite the job.Is that ok.Then for
the syntax coloring,we can use the rule base partitioning which is
already available in jface because it is done in per partition basis.
WDYT ? .
What do you mean by "write an xwiki parser"?
Anyway, please have a look at what Venkatesh has already done and that
he has committed in
http://svn.xwiki.org/svnroot/sandbox/xeclipse-gsoc/org.xwiki.eclipse.ui/
. You can propose changes and improvements starting from that code
without restarting from scratch.
-Fabio
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs