13 Aug
2010
13 Aug
'10
6:39 p.m.
[...]
Interesting point.
I've watch at it, but it seems to be a different approach to me.
Cause, I've had a more complete batch migration in mind, not so much
focussed on having a fancy wizard for.
I don't understand what you mean here, wiki importer goal is to import
complete wikis. The UI part is just on the framework side and when you
wriite a wiki importer module you don't really care about that and
just declare what you want to get as parameter (the file containing an
exported wiki, the URL of a wiki to import using REST, etc...), then
you do whatever you want with this.
IMO both project could use the exact same code for the MediaWiki ->
XWiki convertion which is what is in the MediaWiki module of wiki
importer, then the UI and the way to store the produced documents
depends of the tool.
> Additionally setting up my Eclipse workspace with just XMLRPC-API
and
wikimodel was
way easier ;-) So it was simpler to patch/enhance
wikimodel
for my tasks.
With M2Eclipse it's very easy to use XWiki Rendering in a new project. But as I read
on page 'RenderingModel' your importer also uses
wikimodel.
Thus my patches also benefit your project :-)
Actually wiki importer use XWiki Rendering which use WikiModel
specifically for the MediaWiki parser but use it's own XWiki 2.0
serializer, use Doxia for other languages etc...