On Thu, 2009-07-16 at 11:36 +0200, Jean Bréfort wrote: > Le jeudi 16 juillet 2009 à 11:22 +0200, J.M. Maurer a écrit : > > On Wed, 2009-07-15 at 17:24 +0200, Jean Bréfort wrote: > > > We might also implement a collaboration framework analog to what exists > > > in Abiword. > > > > Yay! In that case you probably would want to steal most of the abicollab > > plugin :) > > May be the code can go to a shared library? (not goffice at the moment > because of the license issue).
With some poking around that should be doable... Marc > > > Marc > > > > > Regards, > > > Jean > > > > > > > > > Le mardi 14 juillet 2009 à 22:26 -0300, Felipe Castro a écrit : > > > > 2009/7/14 bill lam <cbill....@gmail.com>: > > > > > I might not remember correctly, excel (application) changes and flush > > > > > a few bytes in the excel file when opening it. If another user opens > > > > > that file again using excel, excel will issue a warning to the second > > > > > user that the file is read only. This does not depend on file system > > > > > lock. There are cases where an excel file is incorrectly flagged as > > > > > readonly if that file was not closed properly. > > > > > > > > Yes, that's it. And it's not only a simple "handy" feature. It's a > > > > vital one, for any work in group over a bunch of files which are > > > > located somewhere in a network. I'm using Excel and want to migrate to > > > > Gnumeric. But this thing is keeping me away from the changing... > > > > > > > > So it's not a Windows only problem. This would be useful in any kind > > > > of OS. The Vim program gives the following message, when the file is > > > > already opened an the internal buffer changed (or when it wasn't > > > > closed properly before saving): > > > > > > > > -------------------------------------- > > > > Found a swap file by the name ".teste.txt.swp" > > > > owned by: ipe dated: Tue Jul 14 22:21:30 2009 > > > > file name: ~ipe/tmp/Windows/teste.txt > > > > modified: YES > > > > user name: ipe host name: feo > > > > process ID: 4830 > > > > While opening file "teste.txt" > > > > dated: Tue Jul 14 22:21:05 2009 > > > > > > > > (1) Another program may be editing the same file. > > > > If this is the case, be careful not to end up with two > > > > different instances of the same file when making changes. > > > > Quit, or continue with caution. > > > > > > > > (2) An edit session for this file crashed. > > > > If this is the case, use ":recover" or "vim -r teste.txt" > > > > to recover the changes (see ":help recovery"). > > > > If you did this already, delete the swap file ".teste.txt.swp" > > > > to avoid this message. > > > > > > > > Swap file ".teste.txt.swp" already exists! > > > > [O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, > > > > (A)bort: > > > > -------------------------------------- > > > > > > > > > > > > So, that's my suggestion, don't know if it's too difficult to > > > > implement. Anyway, it's really very useful. > > > > > > > > Regards, > > > > > > > > Felipe Castro. > > > > _______________________________________________ > > > > gnumeric-list mailing list > > > > gnumeric-list@gnome.org > > > > http://mail.gnome.org/mailman/listinfo/gnumeric-list > > > > > > _______________________________________________ > > > gnumeric-list mailing list > > > gnumeric-list@gnome.org > > > http://mail.gnome.org/mailman/listinfo/gnumeric-list > > > > _______________________________________________ > > gnumeric-list mailing list > > gnumeric-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnumeric-list > _______________________________________________ gnumeric-list mailing list gnumeric-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnumeric-list
