These suggested changes to the dialog sound good--I opened one of the nightlies to look at another feature, and was quite alarmed by the "migrate" dialog.
I wonder if it would be a good idea to include a reminder to make a backup before clicking "ok"? --Ingrid On 1/1/08 7:52 PM, "Adam R. Maxwell" <[EMAIL PROTECTED]> wrote: > > On Jan 1, 2008, at 6:30 PM, Michael McCracken wrote: > >> Hi, I just tried the nightly for the first time in a while, and I was >> a little confused by the file migration dialog on the first run. > > Excellent! I was hoping someone would provide feedback like this. > Since you have commit access you can even fix it :). > >> What's actually changing - will migration move my files on disk or >> will it just change the file contents? > > No. It converts local file fields to opaque data, which will be saved > as Bdsk-File-N fields. Remote URL fields will be saved as Bdsk-Url-N > fields. It's undoable, and the only thing changed is the BibTeX file > when you save it. > > If the appropriate box is checked, the old fields will be removed. > >> I think the dialog should be clearer about what's actually going on. >> >> It now reads: >> "Local File and URL fields have been converted to use a more flexible >> storage format. Choose "Migrate" to display the migration interface, >> which can show problems and convert permanently to the new format." >> >> I suggest: (assuming I understand it correctly:) >> >> "BibDesk would like to update all Local File and URL fields in your >> database to a more flexible format. >> Choose "Migrate" to begin the process. No changes will be made yet. >> This can also be run at any time from the "Database" menu. >> " >> >> The fact that it shows errors and converts permanently can then be >> explained in the migrate window. > > Changes will be made to the file if you check the box, but other than > that this sounds easier to grok. There's a help button in the window > that links to some discussion of this, and if you have time to comment > on or fix that I'd appreciate it. I don't want anyone to get burned > on a new feature... > >> Also, the menu item for Database->"migrate files" was confusing. I >> thought it was going to move files on disk. Perhaps "update File and >> URL fields"? > > Sounds good to me...or maybe "Convert" instead of "Update"? This > makes it clear that it doesn't just affect files (and we should > probably rename bits of the API to make that clear as well). > >> Happy new year, > > same to you, > > adam > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
