27 Jun
2008
27 Jun
'08
5:22 p.m.
On Jun 27, 2008, at 9:07 AM, Fabio Mancinelli wrote:
On 25 juin 08, at 23:11, malaka ekanayake wrote:
sounds cool :)
In order to undestand how the parser wokes i exaimed it with
several xwiki
documents.I think there are some points needed to be clarified
about the
parser.It would be greate if you can tell me the criteria which has
been
used to build the xdom tree from the xwiki.
Hi Malaka,
in order to make things easier for you and us, I've coded a simple
XDOM explorer.
Basically it opens a plain editor when you open an .xwiki file and
displays in the outline the XDOM structure.
Not all the blocks are displayed with pretty string, it suffices to
complete the org.xwiki.xdomexplorer.editors.XDOMLabelProvider with
all the possible cases. The explorer is nice to see in real time
(every time you save) how the XDOM is structured.
Maybe it could be also a debugging tool for testing the parsing
infrastructure.
The parsing is done in the XDOMOutlinePage.parse function and I've
followed what you did in your code. I found that I cannot commit to the sandbox so I am
attaching the
file to this mail so that you can commit it.
Now you can!
Thanks
-Vincent
Please do it in the http://svn.xwiki.org/svnroot/sandbox/xeclipse-gsoc/
so that everything XEclipse GSOC related will be there.
In order to setup things for Eclipse, you have to do a "mvn
compile" (don't worry if it fails) from the command line and then
refresh the project into Eclipse. This is needed because in this way
Maven will copy all the dependencies jars in the project directory
(PDE requires this).
On your side, did you make some step forward?
Let's talk later.
-Fabio
<org.xwiki.xdomexplorer.tar.gz>