Pascal Voitot wrote: Hi Pascal, I will try to write as less code as possible on the client side and use the work we already have on the platform. The reason I started with MS Office is the market share, which as far as I know is something like this: - By revenue: 95% Microsoft Office, 5% the rest; - By number of users: 75-80% MSO, 20% OOo. Some users are using multiple online/offline tools. This are the worldwide numbers. It will be interesting to have them for France. It will be great to have a OOs plugin, but we don't have the resources to handle both, yet. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Florin, Sounds good. One thing you need to make sure is to have a pluggable network component on the .Net side so that you can use different ways to connect to the XWiki server. You need to specify for the server guys what the ideal server API is for your application to work. We could provide these in standard in XWiki so that we don't need scripts with programming rights in the Wiki to handle the connection. I think ideally the work done in the summer of code for the REST api would be a good candidate to receive the appropriate apis for that. Can you specify the server API in your document that you need. I see: - list pages as tree / list them by space / list them by parent-child (we need to choose which one and it needs to scale) - get wiki page as html - put html as wiki page (new or existing) - put office file as wiki page (full server conversion) -> this is if we want to use the OpenOffice importer for the Office->HTML conversion - get wiki page as office file (optional also) - put office file as attachment

Ludovic Florin Ciubotaru wrote:

Dragă Florin, A few preexisting systems to consider/look at: http://www.pdfonline.com/ http://casesblog.blogspot.com/2005/08/blogger-for-word-publish-to-web-from.… http://www.openxmlcommunity.org/daisy/ Unfortunately, when using Word for web-publishing directly, it seems to bloat the structured document terribly ( http://www.uwec.edu/help/Webpub/wordweb.htm ); also there's issues with conversion to UTF-8 ( http://www.ljmu.ac.uk/cis/webpublishing/81434.htm ) or foisting nonstandard charsets like Windows-1232 on web-viewers. Cutting/pasting between word and Xwiki, Roller or other rich-text capable web-editors seems to work nicely. It's too bad one can't automate the "cut/paste" of the data that flows through the windows GUI between Word and Web-Browser, but instead, directly saves an Xwiki doc... Maybe it's just a matter of having a service on the Xwiki-end that saves an RTF document as an Xwiki doc, combined with a simple plugin on the Word-end to invoke the data-translation which normally occurs during cut/paste. On Wed, Oct 15, 2008 at 9:03 AM, Florin Ciubotaru &lt;florinciu(a)gmail.com <mailto:florinciu@gmail.com>> wrote: Hi devs, I started writing an Add-in for Microsoft Word that could be a part of our Office integration strategy. In the next period I'm going to spend 50% of my time on developing this, here at XWiki Romania. The technology I use is .NET + VSTO. Yes, I know that .NET it's not in XWiki's area, but this technology is very powerfull and it can bring an advantage for our platform. Here is the design page: http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin Please read it and give me some feedback. -- Niels http://nielsmayer.com