[xwiki-devs] [GSOC] [WebDAV] Interoperability
Hi Asiri, I've worked a little on WebDAV interoperability and made quite some progress. We now have on Mac: - WebDAV working for browsing and downloading files - WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true) - WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice). And on Windows XP: With Novell NetDrive (mapping webdav to a driver letter): - WebDAV allowing browsing, dowloading , drag and dropping - WebDAV working with notepad and OpenOffice in view, edit, save With Microsoft Web Folders (2 versions on SP2 tested including the latest patch from Microsoft, SP3 would need to be tested) - WebDAV allowing browsing, dowloading , drag and dropping - WebDAV allowing to double click or open from notepad or OpenOffice but by copying to a temp read only file. You then can SAVE AS to the WebDAV folder. It might be possible that MS Office allows to handle this differently. With Microsoft WebDAV redirector (same one available on Vista) - Nothing works at all. I've tried almost all I could to try to use it to map a network drive on the webdav folder.. The constraints are pretty hard on the web dav server and even though I was not able to have it fully working. I find it a dead end. On Windows Vista: - Nothing works at all It seems possible to install a Web Folders package on Vista and have the behavior of XP. In any case, the Microsoft solution is sub-optimal on Windows. Novell NetDrive (free download findable on the web) or WebDrive (it's commercial counterpart) seem to be much more efficient. Maybe MSOffice works correctly with WebFolders but this needs to be tested. On Mac the behavior is pretty nice with the patched version of OpenOffice (patch is published there: http://tools.openoffice.org/issues/show_bug.cgi?id=81536 let's hope they put it in the standard distrib). Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
Some even better news.. After some testing I was able to make the drive mapping work on Windows XP with mod_dav and from there I made it work with XWiki's WebDAV... It is still a pain because it requires changing a registry setting, a command line and some constraints on the server (like replying with the WebDAV protocol on the root path of your web server) Ludovic Ludovic Dubost wrote:
Hi Asiri,
I've worked a little on WebDAV interoperability and made quite some progress.
We now have on Mac:
- WebDAV working for browsing and downloading files - WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true) - WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save
Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice).
And on Windows XP:
With Novell NetDrive (mapping webdav to a driver letter):
- WebDAV allowing browsing, dowloading , drag and dropping - WebDAV working with notepad and OpenOffice in view, edit, save
With Microsoft Web Folders (2 versions on SP2 tested including the latest patch from Microsoft, SP3 would need to be tested)
- WebDAV allowing browsing, dowloading , drag and dropping - WebDAV allowing to double click or open from notepad or OpenOffice but by copying to a temp read only file. You then can SAVE AS to the WebDAV folder.
It might be possible that MS Office allows to handle this differently.
With Microsoft WebDAV redirector (same one available on Vista)
- Nothing works at all. I've tried almost all I could to try to use it to map a network drive on the webdav folder.. The constraints are pretty hard on the web dav server and even though I was not able to have it fully working. I find it a dead end.
On Windows Vista:
- Nothing works at all
It seems possible to install a Web Folders package on Vista and have the behavior of XP.
In any case, the Microsoft solution is sub-optimal on Windows. Novell NetDrive (free download findable on the web) or WebDrive (it's commercial counterpart) seem to be much more efficient. Maybe MSOffice works correctly with WebFolders but this needs to be tested.
On Mac the behavior is pretty nice with the patched version of OpenOffice (patch is published there: http://tools.openoffice.org/issues/show_bug.cgi?id=81536 let's hope they put it in the standard distrib).
Ludovic
_______________________________________________ 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
2008/7/30 Ludovic Dubost <[email protected]>
Hi Asiri,
I've worked a little on WebDAV interoperability and made quite some progress.
We now have on Mac:
- WebDAV working for browsing and downloading files - WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true) - WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save
Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice).
And on Windows XP:
With Novell NetDrive (mapping webdav to a driver letter):
I will also install NetDrive asap.
- WebDAV allowing browsing, dowloading , drag and dropping - WebDAV working with notepad and OpenOffice in view, edit, save
With Microsoft Web Folders (2 versions on SP2 tested including the latest patch from Microsoft, SP3 would need to be tested)
- WebDAV allowing browsing, dowloading , drag and dropping - WebDAV allowing to double click or open from notepad or OpenOffice but by copying to a temp read only file. You then can SAVE AS to the WebDAV folder.
This is great! Btw, today i figured out that attachments view is not working on XP. And when i found the bug and fixed it, i got a conflict trying to commit, seems like you were quicker than me :) Thanks. - Asiri
It might be possible that MS Office allows to handle this differently.
With Microsoft WebDAV redirector (same one available on Vista)
- Nothing works at all. I've tried almost all I could to try to use it to map a network drive on the webdav folder.. The constraints are pretty hard on the web dav server and even though I was not able to have it fully working. I find it a dead end.
On Windows Vista:
- Nothing works at all
It seems possible to install a Web Folders package on Vista and have the behavior of XP.
In any case, the Microsoft solution is sub-optimal on Windows. Novell NetDrive (free download findable on the web) or WebDrive (it's commercial counterpart) seem to be much more efficient. Maybe MSOffice works correctly with WebFolders but this needs to be tested.
On Mac the behavior is pretty nice with the patched version of OpenOffice (patch is published there: http://tools.openoffice.org/issues/show_bug.cgi?id=81536 let's hope they put it in the standard distrib).
Ludovic
-- 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
Hi Ludovic, 2008/7/30 Ludovic Dubost <[email protected]>
Hi Asiri,
I've worked a little on WebDAV interoperability and made quite some progress.
We now have on Mac:
- WebDAV working for browsing and downloading files - WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true) - WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save
Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice).
And on Windows XP:
With Novell NetDrive (mapping webdav to a driver letter):
- WebDAV allowing browsing, dowloading , drag and dropping - WebDAV working with notepad and OpenOffice in view, edit, save
With Microsoft Web Folders (2 versions on SP2 tested including the latest patch from Microsoft, SP3 would need to be tested)
- WebDAV allowing browsing, dowloading , drag and dropping - WebDAV allowing to double click or open from notepad or OpenOffice but by copying to a temp read only file. You then can SAVE AS to the WebDAV folder.
It might be possible that MS Office allows to handle this differently.
With Microsoft WebDAV redirector (same one available on Vista)
- Nothing works at all. I've tried almost all I could to try to use it to map a network drive on the webdav folder.. The constraints are pretty hard on the web dav server and even though I was not able to have it fully working. I find it a dead end.
On Windows Vista:
- Nothing works at all
It seems possible to install a Web Folders package on Vista and have the behavior of XP.
In any case, the Microsoft solution is sub-optimal on Windows. Novell NetDrive (free download findable on the web) or WebDrive (it's commercial counterpart) seem to be much more efficient. Maybe MSOffice works correctly with WebFolders but this needs to be tested.
So, should we not worry about native vista support ? (I think so, since NetDrive would do the trick) Thanks. - Asiri
On Mac the behavior is pretty nice with the patched version of OpenOffice (patch is published there: http://tools.openoffice.org/issues/show_bug.cgi?id=81536 let's hope they put it in the standard distrib).
Ludovic
-- 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
Asiri Rathnayake wrote:
With Microsoft WebDAV redirector (same one available on Vista)
- Nothing works at all. I've tried almost all I could to try to use it to map a network drive on the webdav folder.. The constraints are pretty hard on the web dav server and even though I was not able to have it fully working. I find it a dead end.
On Windows Vista:
- Nothing works at all
It seems possible to install a Web Folders package on Vista and have the behavior of XP.
In any case, the Microsoft solution is sub-optimal on Windows. Novell NetDrive (free download findable on the web) or WebDrive (it's commercial counterpart) seem to be much more efficient. Maybe MSOffice works correctly with WebFolders but this needs to be tested.
So, should we not worry about native vista support ? (I think so, since NetDrive would do the trick)
I haven't tried NetDrive on Vista though. However I just validated XWiki on Vista and on the WebDAV redirector on Windows. The constraint is about some registry change to allow Basic Authentication (unless we want to support Digest Auth). The second constraint is that the web server needs to reply with webdav on the root URL and for XP the Webdav folder needs to be in a sub filter I find it very nice to build a webdav client that requires your app to respond with webdav at the root BUT that does not accept your webdav to actually be at the root.. I think we can handle these constraints and provide installations requirements to the Windows XP and Vista users so that the redirector works natively. The support in VISTA is actually better than in XP. Double clicking inside Webfolders directly works when in XP you absuletely need to have mapped a drive letter. Concerning interoperability we need now to focus on the following issues: - verify interoperability with standard MSOffice (98, 2003) clients on Windows XP and Vista - how to have webdav integrated properly in XWiki and respond on a WebDAV OPTIONS request at the root of the web server (we could provide a special webapp for that). - implement MOVE which is necessary for some application and is usefull for renaming directory and files - handle file starting with . or ~ as temporary files in memory (just for that user and IP) otherwise we'll have crappy files in our wiki - how to handle bad characters in some file names (we can just change the file name because some application are actually looking at the file they just saved and won't like it if they don't find it). We could refuse bad file names but we need to not be to selective. - nice to have: implement Digest Auth so that we can avoid updating the registry on Windows clients I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent. Ludovic
-- 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
_______________________________________________ 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
Hi Ludovic, On Wed, Jul 30, 2008 at 9:06 PM, Ludovic Dubost <[email protected]> wrote:
Asiri Rathnayake wrote:
With Microsoft WebDAV redirector (same one available on Vista)
- Nothing works at all. I've tried almost all I could to try to use it to map a network drive on the webdav folder.. The constraints are pretty hard on the web dav server and even though I was not able to have it fully working. I find it a dead end.
On Windows Vista:
- Nothing works at all
It seems possible to install a Web Folders package on Vista and have the behavior of XP.
In any case, the Microsoft solution is sub-optimal on Windows. Novell NetDrive (free download findable on the web) or WebDrive (it's commercial counterpart) seem to be much more efficient. Maybe MSOffice works correctly with WebFolders but this needs to be tested.
So, should we not worry about native vista support ? (I think so, since NetDrive would do the trick)
I haven't tried NetDrive on Vista though. However I just validated XWiki on Vista and on the WebDAV redirector on Windows. The constraint is about some registry change to allow Basic Authentication (unless we want to support Digest Auth). The second constraint is that the web server needs to reply with webdav on the root URL and for XP the Webdav folder needs to be in a sub filter
I find it very nice to build a webdav client that requires your app to respond with webdav at the root BUT that does not accept your webdav to actually be at the root..
Yep, that would be absolutely crazy ... :D
I think we can handle these constraints and provide installations requirements to the Windows XP and Vista users so that the redirector works natively.
Agreed, like we did with xeclipse, we can document everything on xwiki.org
The support in VISTA is actually better than in XP. Double clicking inside Webfolders directly works when in XP you absuletely need to have mapped a drive letter.
Concerning interoperability we need now to focus on the following issues:
- verify interoperability with standard MSOffice (98, 2003) clients on Windows XP and Vista - how to have webdav integrated properly in XWiki and respond on a WebDAV OPTIONS request at the root of the web server (we could provide a special webapp for that). - implement MOVE which is necessary for some application and is usefull for renaming directory and files
Working on this right now. About renaming files, we can't rename wiki.txt and wiki.xml, so i guess this only applies to attachments. Space renaming is already there and i'm working on page renaming, i've hit a little wall with it but i will fix it by tomorrow :)
- handle file starting with . or ~ as temporary files in memory (just for that user and IP) otherwise we'll have crappy files in our wiki
Good thinking, we can put them as session variables may be.
- how to handle bad characters in some file names (we can just change the file name because some application are actually looking at the file they just saved and won't like it if they don't find it). We could refuse bad file names but we need to not be to selective. - nice to have: implement Digest Auth so that we can avoid updating the registry on Windows clients
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
Great! looking forward to it. I'll be so happy to move xwiki-webdav out of sandbox... :P Thanks. - Asiri
Ludovic
-- 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
_______________________________________________ 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
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote: [snip]
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org). At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more? Does it need modification to the core/platform? Once we decide where it could go in the main svn we should start a vote to add it there. From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc. Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki-webdav out of sandbox... :P
Thanks.
- Asiri
Hi Vincent, On Wed, Jul 30, 2008 at 11:28 PM, Vincent Massol <[email protected]> wrote:
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote:
[snip]
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org).
At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more?
It's another way of exposing an xwiki repository ...
Does it need modification to the core/platform?
Nope. None! This is my view of xwiki-webdav, we better ask someone other than myself to comment on this :) Thanks. - Asiri
Once we decide where it could go in the main svn we should start a vote to add it there.
From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc.
Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki-webdav out of sandbox... :P
Thanks.
- Asiri
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Jul 31, 2008, at 7:43 AM, Asiri Rathnayake wrote:
Hi Vincent,
On Wed, Jul 30, 2008 at 11:28 PM, Vincent Massol <[email protected]> wrote:
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote:
[snip]
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org).
At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more?
It's another way of exposing an xwiki repository ...
My question was different... I'm talking in term of integration in the platform. Where should it go in the source tree? Again, is it only a plugin or more?
Does it need modification to the core/platform?
Nope. None!
This is my view of xwiki-webdav, we better ask someone other than myself to comment on this :)
Well you should know since you coded it... :) Thanks -Vincent
Once we decide where it could go in the main svn we should start a vote to add it there.
From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc.
Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki-webdav out of sandbox... :P
Thanks.
- Asiri
Hi Vincent, On Thu, Jul 31, 2008 at 1:01 PM, Vincent Massol <[email protected]> wrote:
On Jul 31, 2008, at 7:43 AM, Asiri Rathnayake wrote:
Hi Vincent,
On Wed, Jul 30, 2008 at 11:28 PM, Vincent Massol <[email protected]> wrote:
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote:
[snip]
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org).
At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more?
It's another way of exposing an xwiki repository ...
My question was different... I'm talking in term of integration in the platform. Where should it go in the source tree? Again, is it only a plugin or more?
Well, if we consider xeclipse as a plugin, yes xwiki-webdav is also a plugin :) And i'm not clear what is meant by "More" ... hey, may be ludovic has a better idea ? :) Thanks. - Asiri
Does it need modification to the core/platform?
Nope. None!
This is my view of xwiki-webdav, we better ask someone other than myself to comment on this :)
Well you should know since you coded it... :)
Thanks -Vincent
Once we decide where it could go in the main svn we should start a vote to add it there.
From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc.
Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki-webdav out of sandbox... :P
Thanks.
- Asiri
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Jul 31, 2008, at 10:10 AM, Asiri Rathnayake wrote:
Hi Vincent,
On Thu, Jul 31, 2008 at 1:01 PM, Vincent Massol <[email protected]> wrote:
On Jul 31, 2008, at 7:43 AM, Asiri Rathnayake wrote:
Hi Vincent,
On Wed, Jul 30, 2008 at 11:28 PM, Vincent Massol <[email protected]> wrote:
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote:
[snip]
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org).
At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more?
It's another way of exposing an xwiki repository ...
My question was different... I'm talking in term of integration in the platform. Where should it go in the source tree? Again, is it only a plugin or more?
Well, if we consider xeclipse as a plugin, yes xwiki-webdav is also a plugin :)
xeclipse is NOT a xwiki plugin. It's an Eclipse plugin or a standalone RCP application. Just answer this question: how does your webdav code integrates with xwiki? Where should it go in the source tree? Thanks -Vincent
And i'm not clear what is meant by "More" ... hey, may be ludovic has a better idea ? :)
Thanks.
- Asiri
Does it need modification to the core/platform?
Nope. None!
This is my view of xwiki-webdav, we better ask someone other than myself to comment on this :)
Well you should know since you coded it... :)
Thanks -Vincent
Once we decide where it could go in the main svn we should start a vote to add it there.
From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc.
Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki- webdav out of sandbox... :P
Thanks.
- Asiri
Hi Vincent, Sorry for the late reply, On Thu, Jul 31, 2008 at 1:44 PM, Vincent Massol <[email protected]> wrote:
On Jul 31, 2008, at 10:10 AM, Asiri Rathnayake wrote:
Hi Vincent,
On Thu, Jul 31, 2008 at 1:01 PM, Vincent Massol <[email protected]> wrote:
On Jul 31, 2008, at 7:43 AM, Asiri Rathnayake wrote:
Hi Vincent,
On Wed, Jul 30, 2008 at 11:28 PM, Vincent Massol <[email protected]> wrote:
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote:
[snip]
> I think we should start having our plugin app in Jira and have > these as > independent bug.. > I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org).
At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more?
It's another way of exposing an xwiki repository ...
My question was different... I'm talking in term of integration in the platform. Where should it go in the source tree? Again, is it only a plugin or more?
Well, if we consider xeclipse as a plugin, yes xwiki-webdav is also a plugin :)
xeclipse is NOT a xwiki plugin. It's an Eclipse plugin or a standalone RCP application.
Just answer this question: how does your webdav code integrates with xwiki?
hmmm ... xwiki-webdav uses xwiki-core, that's all. Throguh xwiki-core it accesses an xwiki repository (a data base) which it presents to the out-side world via a WebDAV interface. Is this what you expected ? sorry about the confusion .. :) Thanks. - Asiri
Where should it go in the source tree?
Thanks -Vincent
And i'm not clear what is meant by "More" ... hey, may be ludovic has a better idea ? :)
Thanks.
- Asiri
Does it need modification to the core/platform?
Nope. None!
This is my view of xwiki-webdav, we better ask someone other than myself to comment on this :)
Well you should know since you coded it... :)
Thanks -Vincent
Once we decide where it could go in the main svn we should start a vote to add it there.
From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc.
Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki- webdav out of sandbox... :P
Thanks.
- Asiri
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Asiri Rathnayake wrote:
Hi Vincent,
On Thu, Jul 31, 2008 at 1:01 PM, Vincent Massol <[email protected]> wrote:
On Jul 31, 2008, at 7:43 AM, Asiri Rathnayake wrote:
Hi Vincent,
On Wed, Jul 30, 2008 at 11:28 PM, Vincent Massol <[email protected]> wrote:
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote:
[snip]
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org).
At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more?
It's another way of exposing an xwiki repository ...
My question was different... I'm talking in term of integration in the platform. Where should it go in the source tree? Again, is it only a plugin or more?
Well, if we consider xeclipse as a plugin, yes xwiki-webdav is also a plugin :) And i'm not clear what is meant by "More" ... hey, may be ludovic has a better idea ? :)
No XEclipse is a "client" allowing to connect to the repository. And WebDAV is an XWiki extension API. It allows to browse the repository with WebDAV client. It's at the same level as GWT API and XMP-RPC API and REST API However it's a bit more "application level" since the way we present the WebDAV repository to the user is important. It is "end-user". Thanks to this users will be able to browse XWiki repositories, read and edit files with their favorite editors, drag and drop attachments, etc... Ludovic
Thanks.
- Asiri
Does it need modification to the core/platform?
Nope. None!
This is my view of xwiki-webdav, we better ask someone other than myself to comment on this :)
Well you should know since you coded it... :)
Thanks -Vincent
Once we decide where it could go in the main svn we should start a vote to add it there.
From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc.
Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki-webdav out of sandbox... :P
Thanks.
- Asiri
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ 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
Asiri Rathnayake wrote:
Hi Vincent,
On Wed, Jul 30, 2008 at 11:28 PM, Vincent Massol <[email protected]> wrote:
On Jul 30, 2008, at 7:37 PM, Asiri Rathnayake wrote:
[snip]
I think we should start having our plugin app in Jira and have these as independent bug.. I let you handle this with Vincent.
A committer should first review the code, verify its production ready, that it follows xwiki best practices in term of coding standards, test frameworks used, etc. (as described on dev.xwiki.org).
At the same time we need to decide what structure the webdav feature will have. Is it only a xwiki plugin? Is it more?
It's another way of exposing an xwiki repository ...
It is more a new servlet than a plugin. A plugin would be to allow browsing external webdav directories using the xwiki api. This is different. It's like the GWT API. A new view of the xwiki repository.
Does it need modification to the core/platform?
It can be kept separate. It will just need additions to web.xml to be installed.
The only possible modification, is linked to compatibility issues with the Windows WebDAV client. We need the root of the web server (the web server yes.. not the webapp) to respond to a webdav OPTIONS request. This could have some interactions with platform web. But this is only in the case we put the xwiki as the root webapp. Otherwise we can just provide a phony webapp to respond to this root request. Ludovic
Nope. None!
This is my view of xwiki-webdav, we better ask someone other than myself to comment on this :)
Thanks.
- Asiri
Once we decide where it could go in the main svn we should start a vote to add it there.
From that point forward we can create related jira project, release a first version, add the pages on xwiki.org, etc.
Thanks -Vincent
Great! looking forward to it. I'll be so happy to move xwiki-webdav out of sandbox... :P
Thanks.
- Asiri
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ 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
Bit more hints from the Mac front: Le 30-juil.-08 à 01:52, Ludovic Dubost a écrit :
We now have on Mac: - WebDAV working for browsing and downloading files
that's cool. It generates .DS_Store files in each directory that is browsed btw... you may want to care to allow temporarily these (they used to have weird permissions). Also, it would be nice to generate the .localized files to have directory names that change according to language.
- WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true)
that is a major annoyance.
- WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice).
Note: this practice of write then move is the de-facto standard, it is also used in emacs and jEdit (though the latter makes it configurable), and, I think, BBedit. The simple reason is that you don't want to crash the previous version if you crash in the middle of a save (which happens). I suppose, it's the same on other platforms. paul
Hi Paul, On Tue, Aug 5, 2008 at 3:56 PM, Paul Libbrecht <[email protected]> wrote:
Bit more hints from the Mac front:
Le 30-juil.-08 à 01:52, Ludovic Dubost a écrit :
We now have on Mac:
- WebDAV working for browsing and downloading files
that's cool. It generates .DS_Store files in each directory that is browsed btw... you may want to care to allow temporarily these (they used to have weird permissions). Also, it would be nice to generate the .localized files to have directory names that change according to language.
I'm working on this issue these days, will put a fix soon :)
- WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true)
that is a major annoyance.
- WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice).
Note: this practice of write then move is the de-facto standard, it is also used in emacs and jEdit (though the latter makes it configurable), and, I think, BBedit. The simple reason is that you don't want to crash the previous version if you crash in the middle of a save (which happens).
I suppose, it's the same on other platforms.
paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Asiri Rathnayake wrote:
Hi Paul,
On Tue, Aug 5, 2008 at 3:56 PM, Paul Libbrecht <[email protected]> wrote:
Bit more hints from the Mac front:
Le 30-juil.-08 à 01:52, Ludovic Dubost a écrit :
We now have on Mac:
- WebDAV working for browsing and downloading files
that's cool. It generates .DS_Store files in each directory that is browsed btw... you may want to care to allow temporarily these (they used to have weird permissions).
Yes.. we have work on handling . files in memory.. We have do to the same with . directories.
Also, it would be nice to generate the .localized files to have directory names that change according to language.
I'm working on this issue these days, will put a fix soon :)
- WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true)
that is a major annoyance.
Yes.. We have to look into this. Our biggest priority is Office tools however..
- WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice).
Note: this practice of write then move is the de-facto standard, it is also used in emacs and jEdit (though the latter makes it configurable), and, I think, BBedit. The simple reason is that you don't want to crash the previous version if you crash in the middle of a save (which happens).
This should actually work now. OpenOffice Writer now works and I think it was failing because this was missing. TextEdit is more complex because it's not a temp file but a temporary directory. It stills fails currently. Ludovic
I suppose, it's the same on other platforms.
paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ 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
participants (5)
-
Asiri Rathnayake -
Ludovic Dubost -
Ludovic Dubost -
Paul Libbrecht -
Vincent Massol