> On Nov 19, 2015, at 17:59, Maxwell, Adam R <[email protected]> wrote: > > >> On Nov 19, 2015, at 02:44, Christiaan Hofman <[email protected]> wrote: >> >> For now this is just for testing purposes. I am not sure what to do with >> this, whether to advertise this on the Wiki, integrate this as an actual >> pref (that could be dangerous), or remove it later. > > Just spitballing, but the only safe way I see to make it an actual pref is by > adding a new field type (like Bdsk-Path-n) and doing a conversion process > when opening and saving. > > -- > Adam
Why? I don’t get that. The data would be forward compatible, and also be compatible between the situation with or without the option. The data will be of the same format, it’s just how many versions of the file will be saved in the dictionary. So the relative path would always be saved, while the alias will only be saved when the option is not set. If you’d think saving just the relative path is too fragile, than adding a new field type would not solve anything, because that would be the exact same. BTW, the only reason this would not be backward compatible is because the data without alias was explicitly rejected previously, not because the code could not have handled it. Christiaan
------------------------------------------------------------------------------
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
