Re: [Gramps-devel] Hidding the GRDB files

[<ste...@gm...>]

As someone who was bitten by this when I first started using Gramps 6
few months ago, I agree 100% that this is necessary.

Unfortunately, seeing the "database" file on the desktop makes you
believe that it can be moved around, renamed, etc.  In my case, I
thought all I had to do to backup my data was simply copy this one
file.

I think your proposal of having "generic database names" from within
Gramps -- and thus hiding the underlying file structure -- is a great
solution.

Stephane


On 3/20/07, Don Allingham <don...@co...> wrote:
> Over and over again, we are getting the same error(s) reported. People
> are renaming the GRDB files, moving them to different machines, or doing
> other strange things to the files. This has the effect of breaking the
> databases, and then we get error reports.
>
> After discussing this problem with both Brian and Alex, we are coming to
> the conclusion that the databases files should not be user visible. This
> is very similar to how other databases work (where do your MySQL
> databases reside?)
>
> In this case, the user would not specify a GRDB file name, but a more
> generic "database name", without regard to a directory path.
> Transferring files will be done via XML import and export.
>
> This should eliminate the BSDDB version issues, along with the problems
> with log files. And it should actually be simpler for Aunt Martha, who
> may not understand the concept of file systems.
>
> Any thoughts?
>
> Don
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>
>
>