health-dev
[Top][All Lists]
Advanced

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

Re: [Health-dev] adding setup.py to medical


From: Luis Falcon
Subject: Re: [Health-dev] adding setup.py to medical
Date: Thu, 1 Sep 2011 06:51:55 -0300



2011/9/1 Cédric Krier <address@hidden>
On 01/09/11 05:04 -0300, Luis Falcon wrote:
> 2011/9/1 Cédric Krier <address@hidden>
>
> > On 31/08/11 22:02 -0500, zodman wrote:
> > > http://codereview.appspot.com/4968056
> >
> > I think also it will be good to create a repository/package per medical
> > module. This will allow to install only required modules and this is good
> > for
> > security/stability because even if the module is not activated in the
> > database
> > the code is any way loaded.
> >
> > Agree. Today I'm using a "profile" module (medical_profile) that loads a
> set of modules for the typical health center.
>
> I like to concept of profile because the end user does not need to know
> which modules or dependencies to install.

If you was using the setuptools of Python, it will not be a problem because
dependencies will be installed for free.

> He / She can just say, I need to
> install the functionality for "laboratory" or the "primary care center".

Exactly:

   pip install medical_lab

How could you make it simplier :-)

I make it simpler... just one click .

By just clicking in the "medical_profile" from the Tryton menu. So, if they know about the concept of "profile" they can even create their own. 

No complains so far about it.


--
Luis Falcón
GNU Health
www.gnuhealth.org

reply via email to

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