As the discussion in above talk, we are trying to avoid writing code in old-style JSPs (ie legacy UI). Can anyone suggest me the best way to add admin UI with REST + AngularJs in bed management module?
What about bringing in an OWA layer bundled with the Bed Management module (so not as a separate OWA add-on)? This OWA would deliver the React or Angular MVC stack.
There would still be the need of bringing in the âManage Admission Locationsâ link the old way, however this link would simply take the user to the new app shipped as an OWA. Inserting the link would be the only thing to be done in the legacy admin UI.
So:
The user goes to Administration > Admission Locations > Manage Admission Locations.
This link takes the user to your OWA-shipped new app.
Is there any reason to bind this specific admin management to the Bahmni UI? This is supposedly an OpenMRS module, providing a REST and Java API to manage beds and admission locations.
I have updated the JIRA ticket (BAH-378) accordingly, links to our new OWA page(s) should be available from both the Bahmni Admin app and the legacy admin UI.
@darius@angshuonline, any preference(s) as to what JS MVC stack to go for? I had a feeling that React is getting more and more in favour, is that correct?
Or is Angular fine as the title of this thread suggests?
@mjsanish I would suggest you to go through this: âOpen Web App Development Workflowâ. I just tested this using the SDK and it worked fine, in particular I did not stumble on the file permission error that you mentioned.
ReactJS is more and more the preferred way to go, yes.
That said, if @mjsanish is already an Angular wizard, but has never used React, I would be fine with building this in Angular. Itâs pretty much standalone in any case.
@darius Iâd like to get your opinion as to how much it is preferrable to leverage the existing Yeoman generators. âŠand hence have the front-end scaffolded the same way any other generated OWA would (such as openmrs-owa-addonmanager for example).
This could be the opportunity to put together generators that could scaffold apps for multiple distributions at the same time, but of course this increases the overall complexity.
I havenât looked at those yeoman generators in a while so I donât know if theyâre any good [edit: for React]. I have a slight preference for using the generator vs not doing so, but for a small self-contained application I donât feel very strongly.
It would be a nice bonus to have a best-practice generator that could scaffold an app suitable for multiple OpenMRS distros, but I wouldnât expect @mjsanish to work on that as part of this ticket. If you (@mksd) see a specific opportunity based on your experience with multiple OpenMRS distros, then do please highlight it.