[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] a series of Blog entries
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] a series of Blog entries |
Date: |
Fri, 15 Apr 2011 09:21:41 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Apr 15, 2011 at 02:14:38AM +0200, Tonatiuh de San Juli�n wrote:
> Slowly progress in the blog entries, today:
>
> http://tonatiuhsanjulian.blogspot.com/2011/04/conectar-la-base-de-datos-de-gnumed.html
nice
> Log in, and fix the missing plug-ins in gnumed-client.conf
A word of explanation. You are not "fixing" the "missing"
plugins. What you do is to configure GNUmed to use a certain
pre-configured workplace.
If no workplace is selected in the config file then GNUmed
will use a built-in, hardcoded workplace which only loads
one single plugin. The reason is to minimize problems with
plugin load so that - if there ARE problems - one can
comment out any workplace selections and start up with a
minimum workplace. Now, Debian and by extension Ubuntu did
not pre-select a workplace for their users. Hence they start
up with the built-in workplace.
Workplace can be set up from within the client. There's a
few pre-configured ones, among which "GNUmed Default" is
just one.
If one selects a not-yet-existing workplace in the config
file GNUmed will create this workplace upon startup and load
*all* available plugins within that workplace.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Re: [Gnumed-devel] a series of Blog entries, Tonatiuh de San Julián, 2011/04/15