I agree with Christiaan that we shouldn't rely on just Apple's NSDocument checking. It is nice in the sense that it alerts the user when the file he tries to save has been changed on disk, but it does not help resolve the conflict well. Here is one such scenario: if I changed the main .bib file from computer B (while my bibdesk on A was open), and I come back to A, make some change to the main .bib file on A, and try to save, there is conflict, and Apple asks me should I save or not. But there is no easier way to resolve that if I don't want to lose changes made on B or A.
If Dropbox doesn't provide a good way to notify about a file change, what is wrong with polling from Bibdesk to see if it has changed (as some one already mentioned). Agreed that it is not efficient and elegant, but one can use heuristics to make the polling efficient, for example: poll when Bibdesk is in focus, or when the user attempts to make a change, etc. And make it elegant when better file change notification support is available. Harris PS. The thread is old, but I think the discussion didn't reach any conclusion, so my attempt to revive it. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
