Re: [Dhis2-users] dataset section

[Lars Helge Øverland]

Hi Tom,

you are right - sections are currently not exchanged. For 2.9 we are
releasing a new solution for import-export which will include all
objects in the system including sections (except for patient/tracker
related ones).

regards,

Lars


On Mon, Jun 18, 2012 at 11:06 AM,   wrote:
> Should I report this somewhere else?
>
>
>
> Just a simple suggestion: I recently exported metadata from one 2.8 instance
> and imported into another. Everything transferred except for the dataset
> sections. It would be nice to have those included as well.
>
>
>
> Thanks,
>
> Tom
>
>
>
>
>
>
>
> 
>
> This message was scanned for viruses with Trend Micro ScanMail, GFI
> MailSecurity and GFI MailEssentials by the World Health Organization
> Regional Office for the Western Pacific. However, the recipient is advised
> to scan this e-mail and any attached files for viruses.
>
> Disclaimer:
>
> This e-mail, together with any attachments, is intended for the named
> recipients only and is confidential. It may also be privileged or otherwise
> protected by law.
>
> If you have received it in error, please notify the sender immediately by
> reply e-mail and delete it and any attachments from your system. You may not
> copy or disclose its contents to anyone.
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] dataset section

[hiattt]

Thanks, Lars. I keep running into little things that I think could improve 
functionality. Is there a good way to communicate them/see if they're already 
upcoming? 

Tom

-Original Message-
From: Lars Helge Øverland [mailto:larshe...@gmail.com] 
Sent: 19 June 2012 17:54
To: Hiatt, Mr Tom (WPRO)
Cc: dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] dataset section

Hi Tom,

you are right - sections are currently not exchanged. For 2.9 we are
releasing a new solution for import-export which will include all
objects in the system including sections (except for patient/tracker
related ones).

regards,

Lars


On Mon, Jun 18, 2012 at 11:06 AM,   wrote:
> Should I report this somewhere else?
>
>
>
> Just a simple suggestion: I recently exported metadata from one 2.8 instance
> and imported into another. Everything transferred except for the dataset
> sections. It would be nice to have those included as well.
>
>
>
> Thanks,
>
> Tom
>
>
>
>
>
>
>
> 
>
> This message was scanned for viruses with Trend Micro ScanMail, GFI
> MailSecurity and GFI MailEssentials by the World Health Organization
> Regional Office for the Western Pacific. However, the recipient is advised
> to scan this e-mail and any attached files for viruses.
>
> Disclaimer:
>
> This e-mail, together with any attachments, is intended for the named
> recipients only and is confidential. It may also be privileged or otherwise
> protected by law.
>
> If you have received it in error, please notify the sender immediately by
> reply e-mail and delete it and any attachments from your system. You may not
> copy or disclose its contents to anyone.
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>





This message was scanned for viruses with Trend Micro ScanMail, GFI 
MailSecurity and  GFI MailEssentials by the World Health Organization Regional 
Office for the Western Pacific.  However, the recipient is advised to scan this 
e-mail and any attached files for viruses.

Disclaimer:

This e-mail, together with any attachments, is intended for the named 
recipients only and is confidential. It may also be privileged or otherwise 
protected by law.

If you have received it in error, please notify the sender immediately by reply 
e-mail and delete it and any attachments from your system. You may not copy or 
disclose its contents to anyone.


___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] dataset section

[Lars Helge Øverland]

Hi Tom,

future features can be browsed from launchpad:

https://blueprints.launchpad.net/dhis2/+milestone/2.9

https://blueprints.launchpad.net/dhis2/+milestone/2.10

We are grateful for suggestions on how the software can be improved,
feel free to post at the dhis2-dev list.

best regards,

Lars


On Wed, Jun 20, 2012 at 2:31 AM,   wrote:
> Thanks, Lars. I keep running into little things that I think could improve 
> functionality. Is there a good way to communicate them/see if they're already 
> upcoming?
>
> Tom
>
> -Original Message-
> From: Lars Helge Øverland [mailto:larshe...@gmail.com]
> Sent: 19 June 2012 17:54
> To: Hiatt, Mr Tom (WPRO)
> Cc: dhis2-users@lists.launchpad.net
> Subject: Re: [Dhis2-users] dataset section
>
> Hi Tom,
>
> you are right - sections are currently not exchanged. For 2.9 we are
> releasing a new solution for import-export which will include all
> objects in the system including sections (except for patient/tracker
> related ones).
>
> regards,
>
> Lars
>
>
> On Mon, Jun 18, 2012 at 11:06 AM,   wrote:
>> Should I report this somewhere else?
>>
>>
>>
>> Just a simple suggestion: I recently exported metadata from one 2.8 instance
>> and imported into another. Everything transferred except for the dataset
>> sections. It would be nice to have those included as well.
>>
>>
>>
>> Thanks,
>>
>> Tom
>>
>>
>>
>>
>>
>>
>>
>> 
>>
>> This message was scanned for viruses with Trend Micro ScanMail, GFI
>> MailSecurity and GFI MailEssentials by the World Health Organization
>> Regional Office for the Western Pacific. However, the recipient is advised
>> to scan this e-mail and any attached files for viruses.
>>
>> Disclaimer:
>>
>> This e-mail, together with any attachments, is intended for the named
>> recipients only and is confidential. It may also be privileged or otherwise
>> protected by law.
>>
>> If you have received it in error, please notify the sender immediately by
>> reply e-mail and delete it and any attachments from your system. You may not
>> copy or disclose its contents to anyone.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
>
> 
> This message was scanned for viruses with Trend Micro ScanMail, GFI 
> MailSecurity and  GFI MailEssentials by the World Health Organization 
> Regional Office for the Western Pacific.  However, the recipient is advised 
> to scan this e-mail and any attached files for viruses.
>
> Disclaimer:
>
> This e-mail, together with any attachments, is intended for the named 
> recipients only and is confidential. It may also be privileged or otherwise 
> protected by law.
>
> If you have received it in error, please notify the sender immediately by 
> reply e-mail and delete it and any attachments from your system. You may not 
> copy or disclose its contents to anyone.
>

___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Knut Staring]

Related to this, we have a big form where most sections are very simple
and broken down only by gender, but one is also broken down by A LOT of age
groupings, so the auto-generated form becomes extremely wide and the users
have to scroll a lot horizontally. This also means it is very easy for them
to lose track of where they are, though of course they do have the little
box in the upper right corner which is meant to help with exactly those
cases.

So, in general we are very happy with the autogenerated form (and it is
huge, with 10 sections), but would like to be able to customize the layout
for this particular section (actually, the IDEAL option would be to be able
to specify the width of the cells - as we could well have cells only a
third of the automatic width).

I suppose the best solution for now is to separate out this particular
section into a separate form, but are we planning to support custom forms
for sections?

Knut




On Wed, Jul 23, 2014 at 6:23 AM,  wrote:

>  Hi all developers,
> *MY SUGGESTION:*
> In “section grey field management” of combo category options. Has
> only “Disable field” for disable entry value. But I think it is
> important, we should have “Hide field” to hide some combo category. Because
> it effect on showing in Data Entry, if we has many combo category option
> cross with data element.
>
> thank you
> CHANNARA
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
http://dhis2.org
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[rin.channara]

YES knut, custom forms is good for user can do any things to design and assign 
any DE to show. but the main problem of custom forms is when I go to report → 
dataset report. I can’t export in excel or pdf. It work only printing function…





From: Knut Staring
Sent: ‎Wednesday‎, ‎July‎ ‎23‎, ‎2014 ‎11‎:‎42‎ ‎Morning
To: channara rin
Cc: DHIS 2 Users list, DHIS 2 Developers list





Related to this, we have a big form where most sections are very simple and 
broken down only by gender, but one is also broken down by A LOT of age 
groupings, so the auto-generated form becomes extremely wide and the users have 
to scroll a lot horizontally. This also means it is very easy for them to lose 
track of where they are, though of course they do have the little box in the 
upper right corner which is meant to help with exactly those cases.



So, in general we are very happy with the autogenerated form (and it is huge, 
with 10 sections), but would like to be able to customize the layout for this 
particular section (actually, the IDEAL option would be to be able to specify 
the width of the cells - as we could well have cells only a third of the 
automatic width).




I suppose the best solution for now is to separate out this particular section 
into a separate form, but are we planning to support custom forms for sections?




Knut










On Wed, Jul 23, 2014 at 6:23 AM,  wrote:




Hi all developers,

MY SUGGESTION:

In “section grey field management” of combo category options. Has only “Disable 
field” for disable entry value. But I think it is important, we should have 
“Hide field” to hide some combo category. Because it effect on showing in Data 
Entry, if we has many combo category option cross with data element.




thank you

CHANNARA


___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp






-- 

Knut Staring

Dept. of Informatics, University of Oslo

+4791880522

http://dhis2.org___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Neranga]

Hi,

I faced a similar issue when I was customizing DHIS2 tracked instance to
collect patient-based data for the cancer screening clinic in Sri Lanka.
(DHIS2.15)
In our case, client details are collected for registration and then for the
visit clinical history, examination, investigations and follow up details
are recorded. As you understand there are elements which are very specific
to females and males, however it was difficult to implement the "hiding
fields" according to the value given to the sex attribute. I couldn't find
a way to implement that logic. Instead we designed 2 separate programs for
males and females, and it was not too bad to do so.
On the other hand I also found the "sections" in the program stages quite
useful too. But I had to give up the custom designed forms and go ahead
with the auto generated forms, because when I designed the form, the
section tab was no longer available.
I think these experiences will help developers to make future changes.
Thanks.


*L.A. Neranga Prabhath*
*Trainee - MSc in Medical Informatics*
*Postgraduate Institute of Medicine*
*University of Colombo-Sri Lanka.*
*Telephone: +94772531559*



On 23 July 2014 10:12, Knut Staring  wrote:

> Related to this, we have a big form where most sections are very simple
> and broken down only by gender, but one is also broken down by A LOT of age
> groupings, so the auto-generated form becomes extremely wide and the users
> have to scroll a lot horizontally. This also means it is very easy for them
> to lose track of where they are, though of course they do have the little
> box in the upper right corner which is meant to help with exactly those
> cases.
>
> So, in general we are very happy with the autogenerated form (and it is
> huge, with 10 sections), but would like to be able to customize the layout
> for this particular section (actually, the IDEAL option would be to be able
> to specify the width of the cells - as we could well have cells only a
> third of the automatic width).
>
> I suppose the best solution for now is to separate out this particular
> section into a separate form, but are we planning to support custom forms
> for sections?
>
> Knut
>
>
>
>
> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>
>>  Hi all developers,
>> *MY SUGGESTION:*
>> In “section grey field management” of combo category options. Has
>> only “Disable field” for disable entry value. But I think it is
>> important, we should have “Hide field” to hide some combo category. Because
>> it effect on showing in Data Entry, if we has many combo category option
>> cross with data element.
>>
>> thank you
>> CHANNARA
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> +4791880522
> http://dhis2.org
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Lars Helge Øverland]

Hi there,

thanks for the input. I don't think we will implement custom forms in
section forms in the near future. When you have a form which is super-wide
with mostly unused fields then that's usually a sign that the form itself
should be re-designed.

I have been thinking of a function for using the section form HTML as basis
for custom forms - ie. you could get the section form layout as a starting
point and then go on to modify the parts you need.

Neranga: If you need tabs also for custom forms we have jquery ui included
in the page and its pretty simple to set up the "tabs" widget with a little
bit of HTML/javascript, see docs here .

best regards,

Lars




On Wed, Jul 23, 2014 at 7:02 AM, Neranga 
wrote:

> Hi,
>
> I faced a similar issue when I was customizing DHIS2 tracked instance to
> collect patient-based data for the cancer screening clinic in Sri Lanka.
> (DHIS2.15)
> In our case, client details are collected for registration and then for
> the visit clinical history, examination, investigations and follow up
> details are recorded. As you understand there are elements which are very
> specific to females and males, however it was difficult to implement the
> "hiding fields" according to the value given to the sex attribute. I
> couldn't find a way to implement that logic. Instead we designed 2 separate
> programs for males and females, and it was not too bad to do so.
> On the other hand I also found the "sections" in the program stages quite
> useful too. But I had to give up the custom designed forms and go ahead
> with the auto generated forms, because when I designed the form, the
> section tab was no longer available.
> I think these experiences will help developers to make future changes.
> Thanks.
>
>
> *L.A. Neranga Prabhath*
> *Trainee - MSc in Medical Informatics*
> *Postgraduate Institute of Medicine*
> *University of Colombo-Sri Lanka.*
> *Telephone: +94772531559 <%2B94772531559>*
>
>
>
> On 23 July 2014 10:12, Knut Staring  wrote:
>
>> Related to this, we have a big form where most sections are very simple
>> and broken down only by gender, but one is also broken down by A LOT of age
>> groupings, so the auto-generated form becomes extremely wide and the users
>> have to scroll a lot horizontally. This also means it is very easy for them
>> to lose track of where they are, though of course they do have the little
>> box in the upper right corner which is meant to help with exactly those
>> cases.
>>
>> So, in general we are very happy with the autogenerated form (and it is
>> huge, with 10 sections), but would like to be able to customize the layout
>> for this particular section (actually, the IDEAL option would be to be able
>> to specify the width of the cells - as we could well have cells only a
>> third of the automatic width).
>>
>> I suppose the best solution for now is to separate out this particular
>> section into a separate form, but are we planning to support custom forms
>> for sections?
>>
>> Knut
>>
>>
>>
>>
>> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>>
>>>  Hi all developers,
>>> *MY SUGGESTION:*
>>> In “section grey field management” of combo category options. Has
>>> only “Disable field” for disable entry value. But I think it is
>>> important, we should have “Hide field” to hide some combo category. Because
>>> it effect on showing in Data Entry, if we has many combo category option
>>> cross with data element.
>>>
>>> thank you
>>> CHANNARA
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Knut Staring
>> Dept. of Informatics, University of Oslo
>> +4791880522
>> http://dhis2.org
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Neranga]

Hi,

My main concern at this moment is on implementing name-based datasets in
DHIS2.
I have been through a real "hectic" process to come up with a Minimum
clinical dataset for cancer screening
In my view, practically it is better for our generic software to
accommodate needed functions rather than redesigning the form form the
point where it is declared "essential" by the progremme officialsAnd I
think the aggregate side forms and patient side forms are functionally
different. For example, branching logic is quite handy in name-based forms.

Lars: Thanks for the docs.I will try it out and comeback to you if needed.
And I like your idea on section forms.

Neranga


On 23 July 2014 12:06, Lars Helge Øverland  wrote:

>
> Hi there,
>
> thanks for the input. I don't think we will implement custom forms in
> section forms in the near future. When you have a form which is super-wide
> with mostly unused fields then that's usually a sign that the form itself
> should be re-designed.
>
> I have been thinking of a function for using the section form HTML as
> basis for custom forms - ie. you could get the section form layout as a
> starting point and then go on to modify the parts you need.
>
> Neranga: If you need tabs also for custom forms we have jquery ui included
> in the page and its pretty simple to set up the "tabs" widget with a little
> bit of HTML/javascript, see docs here .
>
> best regards,
>
> Lars
>
>
>
>
> On Wed, Jul 23, 2014 at 7:02 AM, Neranga  > wrote:
>
>> Hi,
>>
>> I faced a similar issue when I was customizing DHIS2 tracked instance to
>> collect patient-based data for the cancer screening clinic in Sri Lanka.
>> (DHIS2.15)
>> In our case, client details are collected for registration and then for
>> the visit clinical history, examination, investigations and follow up
>> details are recorded. As you understand there are elements which are very
>> specific to females and males, however it was difficult to implement the
>> "hiding fields" according to the value given to the sex attribute. I
>> couldn't find a way to implement that logic. Instead we designed 2 separate
>> programs for males and females, and it was not too bad to do so.
>> On the other hand I also found the "sections" in the program stages quite
>> useful too. But I had to give up the custom designed forms and go ahead
>> with the auto generated forms, because when I designed the form, the
>> section tab was no longer available.
>> I think these experiences will help developers to make future changes.
>> Thanks.
>>
>>
>> *L.A. Neranga Prabhath*
>> *Trainee - MSc in Medical Informatics*
>> *Postgraduate Institute of Medicine*
>> *University of Colombo-Sri Lanka.*
>> *Telephone: +94772531559 <%2B94772531559>*
>>
>>
>>
>> On 23 July 2014 10:12, Knut Staring  wrote:
>>
>>> Related to this, we have a big form where most sections are very simple
>>> and broken down only by gender, but one is also broken down by A LOT of age
>>> groupings, so the auto-generated form becomes extremely wide and the users
>>> have to scroll a lot horizontally. This also means it is very easy for them
>>> to lose track of where they are, though of course they do have the little
>>> box in the upper right corner which is meant to help with exactly those
>>> cases.
>>>
>>> So, in general we are very happy with the autogenerated form (and it is
>>> huge, with 10 sections), but would like to be able to customize the layout
>>> for this particular section (actually, the IDEAL option would be to be able
>>> to specify the width of the cells - as we could well have cells only a
>>> third of the automatic width).
>>>
>>> I suppose the best solution for now is to separate out this particular
>>> section into a separate form, but are we planning to support custom forms
>>> for sections?
>>>
>>> Knut
>>>
>>>
>>>
>>>
>>> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>>>
  Hi all developers,
 *MY SUGGESTION:*
 In “section grey field management” of combo category options. Has
 only “Disable field” for disable entry value. But I think it is
 important, we should have “Hide field” to hide some combo category. Because
 it effect on showing in Data Entry, if we has many combo category option
 cross with data element.

 thank you
 CHANNARA

 ___
 Mailing list: https://launchpad.net/~dhis2-users
 Post to : dhis2-users@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~dhis2-users
 More help   : https://help.launchpad.net/ListHelp


>>>
>>>
>>> --
>>> Knut Staring
>>> Dept. of Informatics, University of Oslo
>>> +4791880522
>>> http://dhis2.org
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>

Re: [Dhis2-users] Dataset Section

[Knut Staring]

Hm...I thought custom forms would do the trick, but unfortunately the very
act of binding each cell in the table to a dataelement/categoryoptioncombe
makes in the online editor makes the cells far too wide (see the attached
form).

Would be greateful for tips on how to keep the cells the same width as they
are in the right hand columns.



On Wed, Jul 23, 2014 at 6:42 AM, Knut Staring  wrote:

> Related to this, we have a big form where most sections are very simple
> and broken down only by gender, but one is also broken down by A LOT of age
> groupings, so the auto-generated form becomes extremely wide and the users
> have to scroll a lot horizontally. This also means it is very easy for them
> to lose track of where they are, though of course they do have the little
> box in the upper right corner which is meant to help with exactly those
> cases.
>
> So, in general we are very happy with the autogenerated form (and it is
> huge, with 10 sections), but would like to be able to customize the layout
> for this particular section (actually, the IDEAL option would be to be able
> to specify the width of the cells - as we could well have cells only a
> third of the automatic width).
>
> I suppose the best solution for now is to separate out this particular
> section into a separate form, but are we planning to support custom forms
> for sections?
>
> Knut
>
>
>
>
> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>
>>  Hi all developers,
>> *MY SUGGESTION:*
>> In “section grey field management” of combo category options. Has
>> only “Disable field” for disable entry value. But I think it is
>> important, we should have “Hide field” to hide some combo category. Because
>> it effect on showing in Data Entry, if we has many combo category option
>> cross with data element.
>>
>> thank you
>> CHANNARA
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> +4791880522
> http://dhis2.org
>



-- 
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
http://dhis2.org


Form with too wide cells.pdf
Description: Adobe PDF document
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Kader Irchad Barry]

Hi Knut,

For customizing the forms, I move all the source code to a html wysiwyg
editor, such as frontpage. This gives me the ability to identify the form
elements and give them the layout I want.

For the cell width, I add a _style_ attribute in the input tag. This is one
example:



You can adapt the size with the width attribute (here 4em, but could be
more or even less, depending on how you want to manage the inputs)

Best regards
Kader


2014-07-24 19:47 GMT+03:00 Knut Staring :

> Hm...I thought custom forms would do the trick, but unfortunately the very
> act of binding each cell in the table to a dataelement/categoryoptioncombe
> makes in the online editor makes the cells far too wide (see the attached
> form).
>
> Would be greateful for tips on how to keep the cells the same width as
> they are in the right hand columns.
>
>
>
> On Wed, Jul 23, 2014 at 6:42 AM, Knut Staring  wrote:
>
>> Related to this, we have a big form where most sections are very simple
>> and broken down only by gender, but one is also broken down by A LOT of age
>> groupings, so the auto-generated form becomes extremely wide and the users
>> have to scroll a lot horizontally. This also means it is very easy for them
>> to lose track of where they are, though of course they do have the little
>> box in the upper right corner which is meant to help with exactly those
>> cases.
>>
>> So, in general we are very happy with the autogenerated form (and it is
>> huge, with 10 sections), but would like to be able to customize the layout
>> for this particular section (actually, the IDEAL option would be to be able
>> to specify the width of the cells - as we could well have cells only a
>> third of the automatic width).
>>
>> I suppose the best solution for now is to separate out this particular
>> section into a separate form, but are we planning to support custom forms
>> for sections?
>>
>> Knut
>>
>>
>>
>>
>> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>>
>>>  Hi all developers,
>>> *MY SUGGESTION:*
>>> In “section grey field management” of combo category options. Has
>>> only “Disable field” for disable entry value. But I think it is
>>> important, we should have “Hide field” to hide some combo category. Because
>>> it effect on showing in Data Entry, if we has many combo category option
>>> cross with data element.
>>>
>>> thank you
>>> CHANNARA
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Knut Staring
>> Dept. of Informatics, University of Oslo
>> +4791880522
>> http://dhis2.org
>>
>
>
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> +4791880522
> http://dhis2.org
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Knut Staring]

Thanks Kader,

I was thinking there would be a more elegant method than to insert a style
for each of the 24x20 cells, but your suggestion works well with a simple
search/replace of "input" in Notepad++ (no need for an HTML editor).

I would also love to get rid of the excessive padding to the left and right
of the input field in the cell.

And of course it would be nice to not have to manually insert the 240 data
bindings, so would very much welcome the realization of Lars' thoughts on
making the auto-generated form available as a starting point for the
customization.



On Thu, Jul 24, 2014 at 7:01 PM, Kader Irchad Barry 
wrote:

> Hi Knut,
>
> For customizing the forms, I move all the source code to a html wysiwyg
> editor, such as frontpage. This gives me the ability to identify the form
> elements and give them the layout I want.
>
> For the cell width, I add a _style_ attribute in the input tag. This is
> one example:
>
>   id="TCTY9boIn41-j5CfAgw1uth-val" title="TCTY9boIn41 -xxx" value="xxx" />
>
> You can adapt the size with the width attribute (here 4em, but could be
> more or even less, depending on how you want to manage the inputs)
>
> Best regards
> Kader
>
>
> 2014-07-24 19:47 GMT+03:00 Knut Staring :
>
> Hm...I thought custom forms would do the trick, but unfortunately the very
>> act of binding each cell in the table to a dataelement/categoryoptioncombe
>> makes in the online editor makes the cells far too wide (see the attached
>> form).
>>
>> Would be greateful for tips on how to keep the cells the same width as
>> they are in the right hand columns.
>>
>>
>>
>> On Wed, Jul 23, 2014 at 6:42 AM, Knut Staring  wrote:
>>
>>> Related to this, we have a big form where most sections are very simple
>>> and broken down only by gender, but one is also broken down by A LOT of age
>>> groupings, so the auto-generated form becomes extremely wide and the users
>>> have to scroll a lot horizontally. This also means it is very easy for them
>>> to lose track of where they are, though of course they do have the little
>>> box in the upper right corner which is meant to help with exactly those
>>> cases.
>>>
>>> So, in general we are very happy with the autogenerated form (and it is
>>> huge, with 10 sections), but would like to be able to customize the layout
>>> for this particular section (actually, the IDEAL option would be to be able
>>> to specify the width of the cells - as we could well have cells only a
>>> third of the automatic width).
>>>
>>> I suppose the best solution for now is to separate out this particular
>>> section into a separate form, but are we planning to support custom forms
>>> for sections?
>>>
>>> Knut
>>>
>>>
>>>
>>>
>>> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>>>
  Hi all developers,
 *MY SUGGESTION:*
 In “section grey field management” of combo category options. Has
 only “Disable field” for disable entry value. But I think it is
 important, we should have “Hide field” to hide some combo category. Because
 it effect on showing in Data Entry, if we has many combo category option
 cross with data element.

 thank you
 CHANNARA

 ___
 Mailing list: https://launchpad.net/~dhis2-users
 Post to : dhis2-users@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~dhis2-users
 More help   : https://help.launchpad.net/ListHelp


>>>
>>>
>>> --
>>> Knut Staring
>>> Dept. of Informatics, University of Oslo
>>> +4791880522
>>> http://dhis2.org
>>>
>>
>>
>>
>> --
>> Knut Staring
>> Dept. of Informatics, University of Oslo
>> +4791880522
>> http://dhis2.org
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
http://dhis2.org


Excessive padding.pdf
Description: Adobe PDF document
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Kader Irchad Barry]

I agree with you.
In fact, I think it would be nice to complete the ability to create custom
forms, by giving the possibility to edit its css styles in a separate file.
This way, we could have a more complete control on the look-and-feel of the
forms.
Adding cellspadding style in the td tags ()
didn't work for me, and I did not look more forward to solve this problem,
guessing that the problem came from the management of the style sheets.
Do you think developers can have a look at it more closely? It could be
nice to give this ability in order to complete the creation of customized
forms.




2014-07-24 20:19 GMT+03:00 Knut Staring :

> Thanks Kader,
>
> I was thinking there would be a more elegant method than to insert a style
> for each of the 24x20 cells, but your suggestion works well with a simple
> search/replace of "input" in Notepad++ (no need for an HTML editor).
>
> I would also love to get rid of the excessive padding to the left and
> right of the input field in the cell.
>
> And of course it would be nice to not have to manually insert the 240 data
> bindings, so would very much welcome the realization of Lars' thoughts on
> making the auto-generated form available as a starting point for the
> customization.
>
>
>
> On Thu, Jul 24, 2014 at 7:01 PM, Kader Irchad Barry 
> wrote:
>
>> Hi Knut,
>>
>> For customizing the forms, I move all the source code to a html wysiwyg
>> editor, such as frontpage. This gives me the ability to identify the form
>> elements and give them the layout I want.
>>
>> For the cell width, I add a _style_ attribute in the input tag. This is
>> one example:
>>
>> >  id="TCTY9boIn41-j5CfAgw1uth-val" title="TCTY9boIn41 -xxx" value="xxx" />
>>
>> You can adapt the size with the width attribute (here 4em, but could be
>> more or even less, depending on how you want to manage the inputs)
>>
>> Best regards
>> Kader
>>
>>
>> 2014-07-24 19:47 GMT+03:00 Knut Staring :
>>
>> Hm...I thought custom forms would do the trick, but unfortunately the
>>> very act of binding each cell in the table to a
>>> dataelement/categoryoptioncombe makes in the online editor makes the cells
>>> far too wide (see the attached form).
>>>
>>> Would be greateful for tips on how to keep the cells the same width as
>>> they are in the right hand columns.
>>>
>>>
>>>
>>> On Wed, Jul 23, 2014 at 6:42 AM, Knut Staring  wrote:
>>>
 Related to this, we have a big form where most sections are very simple
 and broken down only by gender, but one is also broken down by A LOT of age
 groupings, so the auto-generated form becomes extremely wide and the users
 have to scroll a lot horizontally. This also means it is very easy for them
 to lose track of where they are, though of course they do have the little
 box in the upper right corner which is meant to help with exactly those
 cases.

 So, in general we are very happy with the autogenerated form (and it is
 huge, with 10 sections), but would like to be able to customize the layout
 for this particular section (actually, the IDEAL option would be to be able
 to specify the width of the cells - as we could well have cells only a
 third of the automatic width).

 I suppose the best solution for now is to separate out this particular
 section into a separate form, but are we planning to support custom forms
 for sections?

 Knut




 On Wed, Jul 23, 2014 at 6:23 AM,  wrote:

>  Hi all developers,
> *MY SUGGESTION:*
> In “section grey field management” of combo category options. Has
> only “Disable field” for disable entry value. But I think it is
> important, we should have “Hide field” to hide some combo category. 
> Because
> it effect on showing in Data Entry, if we has many combo category option
> cross with data element.
>
> thank you
> CHANNARA
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


 --
 Knut Staring
 Dept. of Informatics, University of Oslo
 +4791880522
 http://dhis2.org

>>>
>>>
>>>
>>> --
>>> Knut Staring
>>> Dept. of Informatics, University of Oslo
>>> +4791880522
>>> http://dhis2.org
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> +4791880522
> http://dhis2.org
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~d

Re: [Dhis2-users] Dataset Section

[Lars Helge Øverland]

Wrong link due to cache, this is it:
https://www.dhis2.org/doc/snapshot/en/user/html/ch32s38.html
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Lars Helge Øverland]

Hi Kader,

actually what you suggest is already implemented in 2.16. You can upload
arbitrary CSS and Javascript through the Web API. So e.g. put an id
"form-table" on your custom form table, and then something like that in the
CSS:

#form-table td {
  width: 3em;
}

Docs here: https://www.dhis2.org/doc/snapshot/en/user/html/ch32s37.html

2.16 will be out shortly.

Lars






On Thu, Jul 24, 2014 at 7:40 PM, Kader Irchad Barry 
wrote:

> I agree with you.
> In fact, I think it would be nice to complete the ability to create custom
> forms, by giving the possibility to edit its css styles in a separate file.
> This way, we could have a more complete control on the look-and-feel of the
> forms.
> Adding cellspadding style in the td tags ( ...>) didn't work for me, and I did not look more forward to solve this
> problem, guessing that the problem came from the management of the style
> sheets.
> Do you think developers can have a look at it more closely? It could be
> nice to give this ability in order to complete the creation of customized
> forms.
>
>
>
>
> 2014-07-24 20:19 GMT+03:00 Knut Staring :
>
> Thanks Kader,
>>
>> I was thinking there would be a more elegant method than to insert a
>> style for each of the 24x20 cells, but your suggestion works well with a
>> simple search/replace of "input" in Notepad++ (no need for an HTML editor).
>>
>> I would also love to get rid of the excessive padding to the left and
>> right of the input field in the cell.
>>
>> And of course it would be nice to not have to manually insert the 240
>> data bindings, so would very much welcome the realization of Lars' thoughts
>> on making the auto-generated form available as a starting point for the
>> customization.
>>
>>
>>
>> On Thu, Jul 24, 2014 at 7:01 PM, Kader Irchad Barry 
>> wrote:
>>
>>> Hi Knut,
>>>
>>> For customizing the forms, I move all the source code to a html wysiwyg
>>> editor, such as frontpage. This gives me the ability to identify the form
>>> elements and give them the layout I want.
>>>
>>> For the cell width, I add a _style_ attribute in the input tag. This is
>>> one example:
>>>
>>> >>  id="TCTY9boIn41-j5CfAgw1uth-val" title="TCTY9boIn41 -xxx" value="xxx" />
>>>
>>> You can adapt the size with the width attribute (here 4em, but could be
>>> more or even less, depending on how you want to manage the inputs)
>>>
>>> Best regards
>>> Kader
>>>
>>>
>>> 2014-07-24 19:47 GMT+03:00 Knut Staring :
>>>
>>> Hm...I thought custom forms would do the trick, but unfortunately the
 very act of binding each cell in the table to a
 dataelement/categoryoptioncombe makes in the online editor makes the cells
 far too wide (see the attached form).

 Would be greateful for tips on how to keep the cells the same width as
 they are in the right hand columns.



 On Wed, Jul 23, 2014 at 6:42 AM, Knut Staring  wrote:

> Related to this, we have a big form where most sections are very
> simple and broken down only by gender, but one is also broken down by A 
> LOT
> of age groupings, so the auto-generated form becomes extremely wide and 
> the
> users have to scroll a lot horizontally. This also means it is very easy
> for them to lose track of where they are, though of course they do have 
> the
> little box in the upper right corner which is meant to help with exactly
> those cases.
>
> So, in general we are very happy with the autogenerated form (and it
> is huge, with 10 sections), but would like to be able to customize the
> layout for this particular section (actually, the IDEAL option would be to
> be able to specify the width of the cells - as we could well have cells
> only a third of the automatic width).
>
> I suppose the best solution for now is to separate out this particular
> section into a separate form, but are we planning to support custom forms
> for sections?
>
> Knut
>
>
>
>
> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>
>>  Hi all developers,
>> *MY SUGGESTION:*
>> In “section grey field management” of combo category options. Has
>> only “Disable field” for disable entry value. But I think it is
>> important, we should have “Hide field” to hide some combo category. 
>> Because
>> it effect on showing in Data Entry, if we has many combo category option
>> cross with data element.
>>
>> thank you
>> CHANNARA
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> +4791880522
> http://dhis2.org
>



 --
 Knut Staring
 Dept. of Informatics, University o

Re: [Dhis2-users] Dataset Section

[Knut Staring]

Nice, but any idea how to get rid of other padding??
On Jul 25, 2014 2:20 AM, "Lars Helge Øverland"  wrote:

> Wrong link due to cache, this is it:
> https://www.dhis2.org/doc/snapshot/en/user/html/ch32s38.html
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Knut Staring]

Since spreadsheet-like grids are really common (occur pretty much whenever
we have a dimensional breakdown), we could also consider providing a CSS
template for this scenario, to avoid everyone reinventing that wheel.


On Thu, Jul 24, 2014 at 9:49 PM, Lars Helge Øverland 
wrote:

> Hi Kader,
>
> actually what you suggest is already implemented in 2.16. You can upload
> arbitrary CSS and Javascript through the Web API. So e.g. put an id
> "form-table" on your custom form table, and then something like that in the
> CSS:
>
> #form-table td {
>   width: 3em;
> }
>
> Docs here: https://www.dhis2.org/doc/snapshot/en/user/html/ch32s37.html
>
> 2.16 will be out shortly.
>
> Lars
>
>
>
>
>
>
> On Thu, Jul 24, 2014 at 7:40 PM, Kader Irchad Barry 
> wrote:
>
>> I agree with you.
>> In fact, I think it would be nice to complete the ability to create
>> custom forms, by giving the possibility to edit its css styles in a
>> separate file. This way, we could have a more complete control on the
>> look-and-feel of the forms.
>> Adding cellspadding style in the td tags (> ...>) didn't work for me, and I did not look more forward to solve this
>> problem, guessing that the problem came from the management of the style
>> sheets.
>> Do you think developers can have a look at it more closely? It could be
>> nice to give this ability in order to complete the creation of customized
>> forms.
>>
>>
>>
>>
>> 2014-07-24 20:19 GMT+03:00 Knut Staring :
>>
>> Thanks Kader,
>>>
>>> I was thinking there would be a more elegant method than to insert a
>>> style for each of the 24x20 cells, but your suggestion works well with a
>>> simple search/replace of "input" in Notepad++ (no need for an HTML editor).
>>>
>>> I would also love to get rid of the excessive padding to the left and
>>> right of the input field in the cell.
>>>
>>> And of course it would be nice to not have to manually insert the 240
>>> data bindings, so would very much welcome the realization of Lars' thoughts
>>> on making the auto-generated form available as a starting point for the
>>> customization.
>>>
>>>
>>>
>>> On Thu, Jul 24, 2014 at 7:01 PM, Kader Irchad Barry >> > wrote:
>>>
 Hi Knut,

 For customizing the forms, I move all the source code to a html wysiwyg
 editor, such as frontpage. This gives me the ability to identify the form
 elements and give them the layout I want.

 For the cell width, I add a _style_ attribute in the input tag. This is
 one example:

 >>>  id="TCTY9boIn41-j5CfAgw1uth-val" title="TCTY9boIn41 -xxx" value="xxx" />

 You can adapt the size with the width attribute (here 4em, but could be
 more or even less, depending on how you want to manage the inputs)

 Best regards
 Kader


 2014-07-24 19:47 GMT+03:00 Knut Staring :

 Hm...I thought custom forms would do the trick, but unfortunately the
> very act of binding each cell in the table to a
> dataelement/categoryoptioncombe makes in the online editor makes the cells
> far too wide (see the attached form).
>
> Would be greateful for tips on how to keep the cells the same width as
> they are in the right hand columns.
>
>
>
> On Wed, Jul 23, 2014 at 6:42 AM, Knut Staring 
> wrote:
>
>> Related to this, we have a big form where most sections are very
>> simple and broken down only by gender, but one is also broken down by A 
>> LOT
>> of age groupings, so the auto-generated form becomes extremely wide and 
>> the
>> users have to scroll a lot horizontally. This also means it is very easy
>> for them to lose track of where they are, though of course they do have 
>> the
>> little box in the upper right corner which is meant to help with exactly
>> those cases.
>>
>> So, in general we are very happy with the autogenerated form (and it
>> is huge, with 10 sections), but would like to be able to customize the
>> layout for this particular section (actually, the IDEAL option would be 
>> to
>> be able to specify the width of the cells - as we could well have cells
>> only a third of the automatic width).
>>
>> I suppose the best solution for now is to separate out this
>> particular section into a separate form, but are we planning to support
>> custom forms for sections?
>>
>> Knut
>>
>>
>>
>>
>> On Wed, Jul 23, 2014 at 6:23 AM,  wrote:
>>
>>>  Hi all developers,
>>> *MY SUGGESTION:*
>>> In “section grey field management” of combo category options. Has
>>> only “Disable field” for disable entry value. But I think it is
>>> important, we should have “Hide field” to hide some combo category. 
>>> Because
>>> it effect on showing in Data Entry, if we has many combo category option
>>> cross with data element.
>>>
>>> thank you
>>> CHANNARA
>>>
>>> ___
>

Re: [Dhis2-users] Dataset Section

[Kader Irchad Barry]

Hi Lars,
This is a great feature indeed. Just in case it would be considered not
obvious to implement, would it be possible to fill automatically a template
for the custom forms with style configuration infos provided in a
configuration form? This meets Knut's last suggestion and simplifies the
design process for most users.
Best regards,
Kader
Le 24 juil. 2014 22:50, "Lars Helge Øverland"  a
écrit :

> Wrong link due to cache, this is it:
> https://www.dhis2.org/doc/snapshot/en/user/html/ch32s38.html
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Dataset Section

[Lars Helge Øverland]

To make the custom more compact you can go to the custom form editor screen
and select "compact" under "style".

Lars



On Fri, Jul 25, 2014 at 6:59 AM, Kader Irchad Barry 
wrote:

> Hi Lars,
> This is a great feature indeed. Just in case it would be considered not
> obvious to implement, would it be possible to fill automatically a template
> for the custom forms with style configuration infos provided in a
> configuration form? This meets Knut's last suggestion and simplifies the
> design process for most users.
> Best regards,
> Kader
> Le 24 juil. 2014 22:50, "Lars Helge Øverland"  a
> écrit :
>
> Wrong link due to cache, this is it:
>> https://www.dhis2.org/doc/snapshot/en/user/html/ch32s38.html
>>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp