Hi Guys, Hi Morten, how about we formulate this as a project and submit it to Google's Summer of Code as an application?
They sponsor students to work on Open Source projects for three months and pay them roughly 5000 USD. The sponsoring organisation (we) get 500 USD for mentoring the student. Applications can be created from 3rd-12th of March. What do you think? Christopher On Thu, 28 Feb 2008 22:05:46 +0100, Francois Pepin <[EMAIL PROTECTED]> wrote: > Like James, I would recommend using a source control system, but I agree > it's not ideal in many cases especially since most Windows users aren't > familiar with them. > > > 3. A solution as with MS Office documents: the first user to open the > > file is granted write-access, each other user subsequently attempting > > to open the file is granted Read-only access and receives a > > notification if the file can be accessed excusively again. > > I don't like very much the idea of having jabref changing the permission > on the files if it doesn't have to. I agree with Morten that a lock file > has issues also. > > My solution for this would be to have a warning if you try to overwrite > a message that has been modified since you last opened it. This could be > done either by getting a hash of the file content > (java.security.MessageDigest could do this easily), the modification > date or both. While it doesn't solve the full problem, preventing people > from unwittingly overwriting a modified file this is a good idea to have > no matter what. I can get a patch to do that if people think this is a > good idea. > > Francois > > [EMAIL PROTECTED] wrote: >> Hi, >> >> >> >> I would like to discuss some of the issues connected with using JabRef >> bibliographies in a multi-user environment. >> >> >> >> Currently, in order to keep all contributions (added, modified or >> deleted records) from several users accessing a bib-file in parallel, >> you have to rely on that each user reviews and accepts all external >> changes each time before he himself saves the file. >> >> It is, however, possible to simply close the "File Changed" snippet or >> to cancel the review of external changes. These external changes will >> not be notified again and may be lost if the file is saved subsequently. >> >> >> >> The current solution might be inadequate in the certain multi-user >> environments. Possible changes to increase data security could include: >> >> >> >> 1. It should not be possible to close the "File Changed" Snippet window. >> The only way to get rid of it should be the "Review Changes" button. >> >> 2. Make it mandatory before saving to review and accept (or reject) all >> external changes. Saving with unreviewed changes should not be possible. >> If the review dialogue is closed by "Cancel" the "File Changed" Snippet >> window should reappear and should show the complete list of unreviewed >> external changes the next time the button "Review Changes" is clicked. >> >> >> >> >> >> >> I'd be curious if the developers would be interested in this and if this >> could be included in one of the next releases. >> >> >> >> Keep up the good work! >> >> >> >> Chris >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Jabref-users mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jabref-users > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Jabref-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jabref-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jabref-devel mailing list Jabref-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jabref-devel
