From: <ste...@gm...> - 2007-10-14 17:41:27
|
Oh -- one thing: we should ensure we tell the user we're making a copy of the old database. Versus converting the old database to a new format. This way the users know they still will have their old database for use with GRAMPS 2.2.x should they run into an issue with 3.0. Thinking aloud here... St=E9phane On 10/14/07, St=E9phane Charette <ste...@gm...> wrote: > I like either or both of these suggestions. > > From the recent files list, do we see all of their databases? Or just > the last one? If we see all of their previous 2.x databases, could we > not offer to import each one instead of just the last one? > > St=E9phane > > > On 10/14/07, Duncan Lithgow <dli...@gm...> wrote: > > > > On Sat, 2007-10-13 at 13:16 -0600, Don Allingham wrote: > > > My personal suggest (which someone else is free to implement) is that > > > the first time that 3.x is brought up, we look for the last 2.2 datab= ase > > > that was opened (from the Recent Files list) and offer to import it f= or > > > the user. > > What about a button marked 'Import' which creates a new database and > > imports the selected file in one action. That would hopefully be obviou= s > > enough that most people would try it before saying "how do I open my > > existing databases and GEDCOM files?" > > > > Duncan > > > > -- > > Linux user: 372812 | GPG key ID: 21A8C63A | http://lithgow-schmidt.dk > > > > -----------------------------------------------------------------------= -- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > |