I develop these modules as single OWA now, but at the end of the project, We would like to combine all the related modules into single OWA.
Creating separate OWAs may increase the user complexity to access the fungal sites and a user can’t get the related functionalities with only that OWA.
@dkayiwa also suggested me to develop two OWAs at the end of the project.
If the openmrs-owa-admin-metadata haven’t proper meaning, then we want to add that missing ‘a’ . But it seems ugly
Thank you @dkayiwa for the help. I read and requested.
I have completed half part of my first section. I have updated my blog with the development progress and Screen Shots of the Module Management OWA development. Please take a look and give me your suggestions to the improvement.
There are two ways to achieve this action, (Search and Click install)
My backend service will download the module file(.omod) and save it to the local storage, then It will POST to the Module API automatically to load that module
My backend service will read the file data using GET method and combine it to Multipart File inside the controller. Then it will send that file to Module API to load that module.
Which is the best way to achieve the Seach and Install Modules?
I have used 2nd way here (because 1st way may cause some privilege problems to download and save the module inside the local storage)
I like your thinking which led you to choose the second option because local storage may be turned off by some clients, or not even have enough space left for the module size.
Next, I want to implement another OWA to display the system information which was currently displayed under admin/maintenance/systemInfo.htm. Module part was implemented through legacy-UI module - System Information Controller class.
It’s required the WebServices REST feature to display that system information through the OWA. Currently, It hasn’t REST feature for this section, So I want implement REST feature for SystemInfo section.
I just created SystemInfomationResource1_8 and implemented REST feature for this section. Now, I can reterive SystemInformation to my OWA through this REST service using JSON format.
But there are some issues want to fix for the better REST implementation. I have raised the problem in this talk thread, @dkayiwa take a look at here and help to improve this REST part.
Apart from that, I would like to implement some other features in this section.
I would like to implement this as Tap Panel based details then each tap will contain separated information. The user wants to click each tap to get that information.
Here why we want to include module information? There is another module(Manage Modules OWA) for module management. So Can I remove module information from this part?
If module information should be included here, under the module information Section, I would like to include one button to get More details about that module.
Display Memory details using PiChart with Percentages. It will easy to identify by the user.
Want to clearly state the values (System Language : en should be like English)
I would like to get you ideas to improve this part
My take on this is that, let us start by reproducing only that functionality which existed in the legacyui. After all is done, and you still have the guts to do more, we can then think of those extra features.
Having said the above, allow me to also say that you are making great progress! Plese keep it up.