On Jan 18, 2013, at 09:25, Colin A. Smith wrote: > On Jan 18, 2013, at 17:56, "Maxwell, Adam R" <[email protected]> wrote: > >> Good point. I was heading down that road by asking if Dropbox always used >> ~/Dropbox/.whatever, but hardcoding that would be wrong. Checking for a >> ".*" directory somewhere in the path would be slow and error prone (handling >> things like symlinks and aliases), and still just a heuristic. If Dropbox >> is moving a file, that's a bug in Dropbox. > > > Perhaps this isn't the case, but I'd be really surprised if there aren't > already pieces of code and/or heuristics in BibDesk that workaround odd > behaviors or bugs in OS X for the sake of user experience. One could always > say that because a bug exists in OS X, even though there's a workaround that > could be implemented, users have to suffer until Apple fixes it. I don't > think that's necessarily the best position to take.
Of course there are workarounds for bugs in OS X...because you can't use BibDesk without OS X! Dropbox != OS X. Heuristics applied to display issues aren't a big deal (view & controller layers), but heuristics applied to user data will invariably come back to bite you, IME. > I highly doubt ([resolvedLinkedFilePath rangeOfString:@"/."].location != > NSNotFound) or something like it would cause performance penalties detectable > for all but the most sensitive profiling. Rather than assuming your path separator is always /, you'd be better off to split the path using -pathComponents. Would you first use -stringByStandardizingPath? Would you first use -stringByResolvingSymlinksInPath, in case you were in a directory symlinked to a hidden directory? You're now creating an autoreleased NSArray, iterating it, and possibly hitting the filesystem if you standardize/resolve the path...every time -URL is called. Maybe no big deal. This is all a side note, though, as I still don't think it's good to do this :). > Even if it did, using a hidden preference to enable such behavior, like I > previously suggested, would avoid those problems for "normal" users. Personally, I regret almost every hidden preference we added to BibDesk. Christiaan may have different opinions, of course. Has anyone contacted Dropbox about this? I'd like to understand what they do. Adam ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
