Re: [Health-dev] Access right for gnuhealth.patient.cage

2015-12-11 Thread Luis Falcon
> 
> I don't agree to remove access rights from the base. I think if they
> are well define they will match most of the needs. It is done like
> that in Tryton. If for a local installation, someone need some access
> right tuning, he still can by adding new records (that's why a
> default access right is needed).
> 
Then might as well we leave it the way it is, and we can de-activate
the demo users.

Bests.



pgpaJybORpga6.pgp
Description: OpenPGP digital signature


[Health-dev] [task #13769] Flexible name on party (person)

2015-12-11 Thread Luis Falcon
Follow-up Comment #6, task #13769 (project health):

changeset 2224:6993f32d7154 tip

health : Allow searching for any alias(nickname), temporal, oficial person
name

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/




Re: [Health-dev] Access right for gnuhealth.patient.cage

2015-12-11 Thread Cédric Krier
On 2015-12-11 09:30, Luis Falcon wrote:
> > 
> > I don't agree to remove access rights from the base. I think if they
> > are well define they will match most of the needs. It is done like
> > that in Tryton. If for a local installation, someone need some access
> > right tuning, he still can by adding new records (that's why a
> > default access right is needed).
> > 
> Then might as well we leave it the way it is, and we can de-activate
> the demo users.

I think you did not understand me.
I think it is good to have default access rights with pre defined group
(people are free to use such groups or not) but it is not good to have
predefined users as you can not change the password or anything else.

For the cage model, the problem is to define what is the default access
right (for user without any group) and is there other group that should
have more access rights than the default.

-- 
Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/


pgpjHPo0hRppF.pgp
Description: PGP signature


Re: [Health-dev] Access right for gnuhealth.patient.cage

2015-12-11 Thread Luis Falcon
Hi there !
On Fri, 11 Dec 2015 22:31:23 +0700
Cédric Krier  wrote:

> On 2015-12-11 09:30, Luis Falcon wrote:
> > > 
> > > I don't agree to remove access rights from the base. I think if
> > > they are well define they will match most of the needs. It is
> > > done like that in Tryton. If for a local installation, someone
> > > need some access right tuning, he still can by adding new records
> > > (that's why a default access right is needed).
> > >   
> > Then might as well we leave it the way it is, and we can de-activate
> > the demo users.  
> 
> I think you did not understand me.
> I think it is good to have default access rights with pre defined
> group (people are free to use such groups or not) but it is not good
> to have predefined users as you can not change the password or
> anything else.
Yes. That's why I'm proposing leaving the definition of the access
groups, and removing / deactivating the demo users.
> 
> For the cage model, the problem is to define what is the default
> access right (for user without any group) and is there other group
> that should have more access rights than the default.
> 
OK.



pgppz2N2jVo2M.pgp
Description: OpenPGP digital signature


[Health-dev] [task #13769] Flexible name on party (person)

2015-12-11 Thread Luis Falcon
Follow-up Comment #7, task #13769 (project health):

Move the person alias on the party to the PersonName model of type "nickname",
and drop the field name.

 
PS: I had to rename the "alias" attribute / field name to "nick", on the
party, since Python SQL tracebacked with this party.alias. 

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/




[Health-dev] [task #13769] Flexible name on party (person)

2015-12-11 Thread Cédric Krier
Follow-up Comment #8, task #13769 (project health):

Because alias is a method of Table.
In such case, you must use: Column(table, 'alias')

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/




Re: [Health-dev] Access right for gnuhealth.patient.cage

2015-12-11 Thread Cédric Krier
On 2015-12-11 16:40, Luis Falcon wrote:
> > For the cage model, the problem is to define what is the default
> > access right (for user without any group) and is there other group
> > that should have more access rights than the default.
> > 
> OK.

So what should be the default access right? I guess the current one from
the frontdesk group but this means anybody will be able to create/write
so what are the groups that should have such access?


-- 
Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/


pgp9PCDglfT2t.pgp
Description: PGP signature


Re: [Health-dev] Access right for gnuhealth.patient.cage

2015-12-11 Thread Luis Falcon
On Sat, 12 Dec 2015 00:01:08 +0700
Cédric Krier  wrote:

> On 2015-12-11 16:40, Luis Falcon wrote:
> > > For the cage model, the problem is to define what is the default
> > > access right (for user without any group) and is there other group
> > > that should have more access rights than the default.
> > >   
> > OK.  
> 
> So what should be the default access right? I guess the current one
> from the frontdesk group but this means anybody will be able to
> create/write so what are the groups that should have such access?
> 
> 
CAGE is limited to health professionals only.

Thanks !
Luis



pgp5FgBBCh4j_.pgp
Description: OpenPGP digital signature


[Health-dev] [task #13769] Flexible name on party (person)

2015-12-11 Thread Luis Falcon
Follow-up Comment #9, task #13769 (project health):

Thanks.
In any case, since that column was to be dropped, the workaround was OK.

best,

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/




[Health-dev] [task #13769] Flexible name on party (person)

2015-12-11 Thread Luis Falcon
Update of task #13769 (project health):

Percent Complete: 50% => 80%

___

Follow-up Comment #10:

changeset 2226:6c01efd232c6 tip

- Use the name format representation of the official name
- Use a selection field with a predefined name representation options

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/




Re: [Health-dev] [bug #46666] Resize the party photo

2015-12-11 Thread Bounmy Sihaphom
On Fri, Dec 11, 2015 at 11:57 AM, Cédric Krier 
wrote:

> URL:
>   
>
>  Summary: Resize the party photo
>  Project: GNU Health
> Submitted by: cedk
> Submitted on: Fri 11 Dec 2015 05:57:08 AM CET
> Category: Functionality
> Severity: 2 - Minor
>   Item Group: None
>   Status: Ready For Test
>  Privacy: Public
>  Assigned to: None
>  Open/Closed: Open
>  Discussion Lock: Any
>  Release: None
>   Module: health
>
> ___
>
> Details:
>
> The party photo is displayed with the image widget using a size of 200x200
> but
> if the user select a bigger image, it is this bigger image that is stored
> because the client don't make any modification to the data input.
> So here is a patch that resize the photo to 200x200 on create and write
> like
> that the database is not filled by big pictures (as user often doesn't care
> about the size nor know how to resize an image).
>
> https://codereview.appspot.com/280980043
>
>
> This is great , we will save a lot of space.Thanks Cedric.
>
> ___
>
> Reply to this item at:
>
>   
>
> ___
>   Message sent via/by Savannah
>   http://savannah.gnu.org/
>
>
>


Re: [Health-dev] [bug #46666] Resize the party photo

2015-12-11 Thread Anousak Souphavanh
Excellent guys, especially cedric and Nicolas whom worked hard on these
issues. Appreciated for seeing big improvements.

Anousak
On Dec 12, 2015 8:12 AM, "Bounmy Sihaphom"  wrote:

>
>
>
> On Fri, Dec 11, 2015 at 11:57 AM, Cédric Krier 
> wrote:
>
>> URL:
>>   
>>
>>  Summary: Resize the party photo
>>  Project: GNU Health
>> Submitted by: cedk
>> Submitted on: Fri 11 Dec 2015 05:57:08 AM CET
>> Category: Functionality
>> Severity: 2 - Minor
>>   Item Group: None
>>   Status: Ready For Test
>>  Privacy: Public
>>  Assigned to: None
>>  Open/Closed: Open
>>  Discussion Lock: Any
>>  Release: None
>>   Module: health
>>
>> ___
>>
>> Details:
>>
>> The party photo is displayed with the image widget using a size of
>> 200x200 but
>> if the user select a bigger image, it is this bigger image that is stored
>> because the client don't make any modification to the data input.
>> So here is a patch that resize the photo to 200x200 on create and write
>> like
>> that the database is not filled by big pictures (as user often doesn't
>> care
>> about the size nor know how to resize an image).
>>
>> https://codereview.appspot.com/280980043
>>
>>
>> This is great , we will save a lot of space.Thanks Cedric.
>>
>> ___
>>
>> Reply to this item at:
>>
>>   
>>
>> ___
>>   Message sent via/by Savannah
>>   http://savannah.gnu.org/
>>
>>
>>
>


Re: [Health-dev] Appoitments schedule

2015-12-11 Thread Carlos Eduardo Sotelo Pinto
Dear Comunity

I am looking a way to customize this behavior, in order to add two filters
to the Appoitments, however I couldnt find wich views I must edit or
customize. I am trying to understand the workflow on this appointments
modules and notice that there are more than one module related, any suggest
on wich module have to be customized? ( I am thinking on a new module for
do the customiztion )

best regards

2015-12-10 12:09 GMT-05:00 Carlos Eduardo Sotelo Pinto <
carlos.sotelo.pi...@gmail.com>:

> Dear Comunity
>
> About the work schedule on the health, I have show the module to a users
> and give me some feedback, no so good (I will do a customization)​, but I
> woul like to share this feedback and have suggestions
>
> 1. Choice an appoitment is no usable, to much information. Could be better
> if we have a a sequence like Choose the Date -> Choose speciality -> Choose
> medician -> Choose appoitment
> 2. There is no a schedule where I could check the professional work
> schedule screen ( I have not found it if it exists ), I mean something like
> a week calendar and check, wich pfoessional are on which day on which
> schedule
>
> Any suggest
>
>
> --
> Carlos Eduardo Sotelo Pinto
> Senior Software Analyst Developer
> Claro RPC +51983265994 | MOV RPM( # ) +51 966110066
> GTalk: carlos.sotelo.pi...@gmail.com | Skype: csotelop
> GNULinux RU #379182 | GNULinux RM #277661
>
> No availability between 08:30 and 18:00, I will answer as soon as posible
>
> Please consider the environment before printing this email
> Join the campaign at http://thinkBeforePrinting.org
>
> 
>  Este
> correo electrónico se ha enviado desde un equipo libre de virus y protegido
> por Avast.
> www.avast.com
> 
> <#1518cde64de44694_DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>



-- 
Carlos Eduardo Sotelo Pinto
Senior Software Analyst Developer
Claro RPC +51983265994 | MOV RPM( # ) +51 966110066
GTalk: carlos.sotelo.pi...@gmail.com | Skype: csotelop
GNULinux RU #379182 | GNULinux RM #277661

No availability between 08:30 and 18:00, I will answer as soon as posible

Please consider the environment before printing this email
Join the campaign at http://thinkBeforePrinting.org