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:
> 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.
>
> Florin Ciubotaru
>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>
>   


-- 
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost

_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to