gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Portable GNUmed issue


From: Rogerio Luz
Subject: Re: [Gnumed-devel] Portable GNUmed issue
Date: Tue, 23 Sep 2008 22:00:27 -0300

Writing the directory /.gnumed to the stick would be awesome :) it would make everything easier :)

By the way I have succesfully backed up my "production" DB so will try to port it to the stick as soon I get my hands on a Windows machine again (think tomorrow)

Hey Sebastian ... I know this is the first run for the Portable GNUmed, so donĀ“t sweat :)

BTW ... I got to write a Python program that counts to 10 and one that you have to guess the number "25" ... next I will be fixing bugs ... u just wait :))))))))))

Rogerio 

2008/9/23 Sebastian Hilbert <address@hidden>
On Dienstag 23 September 2008, Karsten Hilbert wrote:
> > Maybe the portable could recognize when \.gnumed resides on a volume
> > that (being the hard drive) is different than the volume (the
> > portable drive) from which the software is being run. This might
> > permit both the GNUmed menu > "Exit" command as well as the exception
> > handler "Close GNUmed" buttons to delete \.gnumed as part of the exit
> > process. (?)
>
> There is no such thing as different "drive" under Unix. Determining whether
> something hangs off a different mount point is arbitrarily complex.

Yeah. But GNUmed can be told to write to a certain location. It could even
test for the platform and handle things differently if on win32. I believe
the only issue here is to tell gnumed not to make a directory .gnumed
in /home/user or Windows equivalent but under a specified path. Which should
be possible if we require that path to be within the gnumed subdirectory
under windows or any path that is writeable by any windows user.


--
Sebastian Hilbert
Leipzig / Germany
[www.gnumed.de]  -> PGP welcome, HTML ->/dev/null


_______________________________________________


reply via email to

[Prev in Thread] Current Thread [Next in Thread]