22 Mar
2009
22 Mar
'09
2:46 p.m.
Vincent Massol wrote:
On Mar 20, 2009, at 7:01 PM, Jerome Velociter wrote:
I agree it makes a lot of senses in XEclipse. But, how do you tight the
version of XWiki to the XEclipse instance ? Even for this use case I
think the best is that XEclipse retrieves and download the API from the
wiki for each connection, so that you get a documentation matching the
wiki you are editing.
Jerome.
Hello devs,
I am thinking it would be good to automatically attach the javadoc
generated for XWiki apis (XWiki, Document, Context, Utils, etc) +
maybe
velocity tools (listtool, mathtool, etc.) in a wiki document of XE at
build time. We could embed the HTML javadoc in view mode with an
iframe
(or using getURLContent API), or just link to it with the zipexplorer
plugin.
I think this would make it easier for developers to find out the
documentation for the exact version they are running, and without the
need of an Internet connection.
Tell me what you think,
I'm not sure. I'd be +1 to do that in XEclipse for sure since XEclipse
is our XWiki IDE now. XEclipse also works offline so it looks perfect
for your use case.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs