From: Peter L. <pet...@te...> - 2007-12-19 14:34:23
|
Brian, > > > Is that really important? The user should only > > > > care > > > > > about one database directory. What is the value in > > > storing other database locations? > > > > The user can change database locations in > > "Edit->Prefernces->Database path:". > > The Family Tree dialog does only look at the current > > database path to find > > Family Trees because it does not no anything about > > other database paths. So > > if the user for some reason has chaged the database > > path, it is still > > possible to use a Family Tree that is not in the > > current database path if the > > user uses "Famlily Tree"-> "Open recent" or the > > little black arrow with > > tooltip "Connect to recent database". > > I think this deserves some discussion. I wonder if we > should ignore all databases that are not in the > current database directory. If we don't, here is one > possible scenario: > > A user uses Gramps for the first time and creates a > database. Then, they learn about the database > directory and change it. They create a new database > and go on their merry way. Then, one day they look in > the "open recent" and see their old database. Thy open > it because they can, realize that it is garbage, and > they want to delete it. But they can't delete it using > the family tree manager. And they have forgotten what > the previous database location was. The GUI gives no > indication where that database resides. The entry is > stuck in their "Open Recent" list forever. Yes, a database can only be deleted if it is in the current database path. One way to have this to work would be to update the database path every time a database from "recent-files.xml" is loaded. > Is that a possible scenario? Is this even important? It's possible. I think manu users want to have control over where there databases are stored. Maybe they use a filserver, then they need to change the database path. In that case I think its' important. > Comments welcome. > You are "some developer", Peter. You have commit > access to the Subversion repository. Go ahead and > commit your changes. All the other developers will > update to get your changes, and we'll let you know if > we see any issues. Well, I know how to commit my sv.po file when I commit the complete file. Do I do the same here patch the latest version with my patch/diff files and commit the patcked files (DbManage.py and RecentFiles.py)? Do the same with Changelog? /Peter > Keep up the good work! > ~Brian Thanks, /Peter |