---------- Forwarded message ---------- From: Viet Nguyen <[email protected]> Date: Thu, Dec 10, 2009 at 10:28 AM Subject: Re: [Branch ~dhis2-devs-core/dhis2/dhis-patient] Rev 825: Add DataEntryFormAssociation. This will allow DataEntryForm to associate with both DataSet and Pr... To: Abyot Gizaw <[email protected]> Cc: bharath kumar <[email protected]>, Lars Helge Øverland < [email protected]>, John lewis <[email protected]>
Hi Abyot, I commit new code. One thing is left to do is populating CalculatedDataElement in dataentryscreen. I will work on this after the demo for the ministry, as I am having a tight deadline for the aggregation things now. By the way, in the programStage's dataentryscreen design form. I used the javascript library : jQuery.metadata . It allow me do declare a custom attribute for a html tag and then get the value of that attribute. I think this library is very useful. I even wanted to use it in the dataentryscreen for all the metadata info, which you are using span tag for them. But again, I do not want to change so much old codes. Please tell me what you think about this library . If its ok, I will use it later on. Thanks, On Thu, Dec 10, 2009 at 10:41 AM, bharath kumar <[email protected]>wrote: > > Hi Abyot, > > Sorry I didn't understand clearly. > > You are saying one dataset say dataset1 can have multiple dataentry screens > like dataentryscreen1,dataentryscreen2,dataentryscreen3. > > When we select dataset1 in the dataentry module we should display these 3 > screens for dataentry? > > These 3 screens can have same dataelements or different dataelements? > > > > On Wed, Dec 9, 2009 at 9:53 PM, Abyot Gizaw <[email protected]> wrote: > >> and also assigning multiple forms for datasets or programstages. For >> example a dataset might have dataelements having different >> categorycombos.... for such cases it makes sense to group those datalements >> having the same categorycombo together then create a form.... in the end >> such datasets will have a set of forms. So when displaying the dataentry >> screen we can display a list of forms and come up a nice looking dataentry >> screen. >> >> abyot. >> >> >> On Wed, Dec 9, 2009 at 5:59 AM, bharath kumar <[email protected]>wrote: >> >>> Hi, >>> >>> >>> Regarding DataEntryScreen, as we (Abyot & Me) discussed on his last visit >>> we agreed to make CustomDataEntryScreen as Genric. >>> >>> For that what we started is: >>> >>> We changed DataEntryForm object to contain its id, name and html code >>> only. (before it was bound with datasetid). >>> All the CustomScreen associations we kept in another table * >>> dataentryformassociation* which contains associationtablename( >>> represents which object DataSet/ProgramStage etc), associationid ( >>> represents datasetid/programstage id), dataentryformid. >>> >>> *From the GUI:* >>> If you goto dataset screen there will be icon to design custom screen for >>> dataset like before. only change is before it was saving in dataentryform >>> table. now it will save the design in dataentryform table and association >>> will be saved in dataentryformassociation table. >>> >>> Similarly for ProgramState also we can design screens. >>> >>> Breifly that is what we are doing regarding CustomScreens. Is it OK or >>> any changes? >>> >>> >>> >>> 2009/12/9 Lars Helge Øverland <[email protected]> >>> >>> >>>> >>>> 2009/12/8 Viet Nguyen <[email protected]> >>>> >>>> Hi Lars and Abyot, >>>>> >>>>> I am sorry, the message of that commit was missing some information. >>>>> >>>>> I had some problem while committing the source. It was locked, and I >>>>> tried to use the break-lock command many times and finally it worked. That >>>>> is why I did not write the full commit message. >>>>> >>>>> So, that commit include >>>>> >>>>> - Custom DataEntryForm design form for ProgramStage ( this is what >>>>> the FCK editor is for ). >>>>> - I Added class DataEntryFormAssociation. And yes Abyot, when I was >>>>> creating that class, I also wanted to create another package for all >>>>> the >>>>> dataentryform things. But that was like just a few days I touch the >>>>> dhis >>>>> code and I did not want to change so much. I just tried to follow the >>>>> old >>>>> work flow. Please do not worry, after read your email, I changed it >>>>> immediately ( really happy to do that :) ) . You will see it in the >>>>> next >>>>> commit. >>>>> - Custom data entry screen for case ( patient ) . This is not >>>>> completely done, I am still working on it. >>>>> >>>>> The reason for this commit is to merge my local changes with your >>>>> trunk. Because I have been coding for about two weeks on this module with >>>>> my >>>>> local source code, not on any branch...so it really need to be merged as >>>>> soon as possible. >>>>> >>>>> And actually , I have not been in the [email protected] >>>>> Abyot send me and Bharath the email. I have just subscribed to the list >>>>> yesterday. I did not know about that mailing list. When you added me to >>>>> the >>>>> core-dev team, I looked for mailing list of this team, but I could not. >>>>> >>>>> About Abyot 's question : >>>>> >>>>> The other thing, if you remember we even talked about having a set of >>>>> forms for datasets/programstages. Because sometimes you might have >>>>> multiple >>>>> tables/sections. Do you think you can include these things? >>>>> >>>>> Sorry, I do not know about this... Please explain it again if you have >>>>> time. >>>>> >>>>> Thank you, >>>>> >>>>> >>>>> >>>> Thanks Viet for your reply.. Don't misunderstand, we're happy to see u >>>> contributing and I'm exited to see the new code/functionality. Its just >>>> important that Abyot understands whats going on and gets the change to >>>> review things as he is leading the patient system work... Now that you have >>>> enlisted for the dev list that's will be easier:-) Tell me if you there is >>>> other stuff u are wondering about. >>>> >>>> cheers Lars >>>> >>>> >>>> >>> >>> >>> -- >>> >>> Regards, >>> Bharath Kumar. Ch >>> >> >> > > > -- > > Regards, > Bharath Kumar. Ch > -- Nguyen Pham Hoang Quoc Viet
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
