gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] Plug-in management in 0.4.6


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Plug-in management in 0.4.6
Date: Sun, 21 Jun 2009 12:14:16 +0200

> Do you want me to upload the following info as low-priority bug in  
> Launchpad?
yes

> > On my platform SPACE allows selecting/unselecting.
> 
> Is it possible that although we are both (?)
+1

> using Debian, your XCFE
Believe it or not, KDE :-)  However, GNUmed is GTK, no matter
the desktop system.
 
> and my Gnome have different selection policies?
That is certainly possible even though GNUmed runs
on GTK under both Gnome and KDE.

> Can the text inside the editor be changed to say:
> 
>       Select the plugin(s) to be loaded the next time the client is  
> restarted:
Yes, but it needs to point out that that's only valid if the
client is started under the workplace that is edited.

> ... I would simplify by removing "Note that he plugins currently  
> associated with this workplace are preselected."
OK

> ... I would modify the tooltip to say "A discontinuous selection may  
> depend on your holding down a modifier key, or key combination (ctrl- 
> shift, space etc.) while clicking."
OK, put all of that into the wishlist item.

> >> or changing their position amongst each other.
> > That isn't supported yet :-(
> 
> Actually, it is, indirectly!
I know but I didn't dare call that "supported" :-)

> > Edit the config file to make that workplace the one GNUmed is  
> > started with
> 
> Not necessary when people are satisfied to use "GNUmed default"  
> workplace,
correct

> which I imagine will persist despite installation of a  
> newer client and maybe even across database upgrades.
It will, however, we take the liberty to change it at will. That is
why it is called "default". It will, for example, always include all
the available plugins after a database upgrade.
 
> Alternatively gnumed.conf can be altered in
>       ~.gnumed/gnumed.conf
> or apparently (I did not test) via system-wide default such as  
> backend profile:
>       /etc/gnumed/gnumed-client.conf
> ... one adds, into this .conf file, the lines
>       [workplace]
>       name = desiredWorkplaceName
> e.g.  name = minimal

That is right. The local .conf (in .gnumed) will override the system
one. So will an explicit --conf-file= one.

> I did attempt what I believed used to allow a selection from the  
> login dialog
>       [workplace]
>       names = $names$
>       minimal
>       GNUmed Default
>       $names$
> but the above hung the client on attempted restart
Weeeell, a list isn't supported for that option.

The reason being that at that point we don't have a database
connection yet which would create a maintenance nightmare.

Karsten
-- 
GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate und Telefonanschluss
für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02




reply via email to

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