It would seem this was implemented for the patient system. Has there been any effort to move it to a more common place, so it can be used by other modules?
I am asking for two reasons. 1) Currently, ALL data elements are loaded when editing data elements. In our case, this results in a lot data being sent across a very small pipeline. Operations with data elements (sort for example) are very, very sluggish. This might help to improve the situation. 2) Bob and I have had a very lengthy discussion about the data set sections. It is quite a mess. I think Bob is working on a fix, but it would be useful to have this functionality here. One may have many data elements in a given section, and it would be useful to be able to sort/filter them efficiently. Regards, Jason 2010/3/9 Lars Helge Øverland <[email protected]>: > > > 2010/3/9 Viet Nguyen <[email protected]> >> >> >> 2010/3/9 Viet Nguyen <[email protected]> >>> >>>> >>>> Hi Viet, this looks quite elegant.. >>>> If the PagingUtil class is general, any chance we can move it to the >>>> dhis-support-system project so that it can be used by other modules if >>>> required later? >>>> Lars >>>> >>> >>> Yeah, I can move the PageUtil class to dhis-support-system, paging.vm and >>> paging.css to common-resource. >>> >>> If I remember correctly...I think you also have a RequestUtil class >>> somewhere.... >>> >>> Actually, to get current request path I just call the method >>> request.getServletPath() , but I'm not sure it works for all modules... so >>> I put it in a util class, then later I can modify that link ( maybe add or >>> remove a "/" , or something like that.... ) >>> >>> -- >>> Viet Nguyen >>> >> >> Sorry, I forgot to mention the javascript methods. >> >> function changePageSize( baseLink ) >> { >> var pageSize = jQuery("#sizeOfPage").val(); >> window.location.href = baseLink +"pageSize=" + pageSize ; >> } >> function jumpToPage( baseLink ) >> { >> var pageSize = jQuery("#sizeOfPage").val(); >> var currentPage = jQuery("#jumpToPage").val(); >> window.location.href = baseLink +"pageSize=" + pageSize >> +"¤tPage=" +currentPage; >> } >> >> So I guess, this will have to be moved to common-resources... >> Should I create new file or put it in common.js ? >> > > commons.js would be fine. Also moving the vm templates to commons-resources > is good. > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > > -- -- Jason P. Pickering email: [email protected] tel:+260968395190 _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
