This is an invitation for everyone to join a sprint around developing an Open Web App for managing concepts. During the sprint we will set the path for developing Open Web Apps for OpenMRS. It means we will employ the hottest tools and design patterns available for developing AngularJS apps for OpenMRS.
Start from getting to know the AngularJS style guide we will follow.
Next have a look at our openmrsRest service, which will be your best companion connecting to OpenMRS REST API.
Finally setup your development environment following the README.md file.
And join on board by picking up any issue from the sprint here.
We are still learning so you will find some of the code do not comply with the style guide, but we are in the process of fixing it. When working on issues please do follow the new style guide!
Please please please donāt repeat a s specific mistakes that the Mirebalais team originally made (and has been replicated throughout the uicommons module).
Particularly, youāve copied the bad āmagicā thing we did, by returning response.results. This is bad because it loses the paging information, so someone who calls this API has no idea if they got all results or not, and they have no way to requesting a second page.
Thatās right @r0bby. In addition we chose Open Web Apps, because they are more convenient to develop than our regular OpenMRS modules. They are lightweight and load extremely fast. In addition the skills required are typical for front-end developers, who donāt need to do any Java coding.
Thatās right @r0bbyhttps://talk.openmrs.org/users/r0bby. In addition
we chose Open Web Apps, because they are more convenient to develop than
our regular OpenMRS modules. They are lightweight and load extremely fast.
In addition the skills required are typical for front-end developers, who
donāt need to do any Java coding.
Yes, we should use ES6 with Babel. Iām planning on updating the OWA generator to use Webpack instead of Grunt. Iāll include the Babel loader for transpiling ES6.
Anyone have any other ideas for the generator? Iām thinking we probably need a CSS preprocessor in the pipeline too.
Pascal, any idea when that work will be done? Webpack will be key to properly managing dependencies once the Concepts OWA starts moving to the ā1 component per fileā approach as dictated by the style guide. This work would seem to have a big impact on https://issues.openmrs.org/browse/RA-1077 which calls for use of a tool like webpack and is currently assigned to Tomasz Marzeion. Should make sure to coordinate these effortsā¦?
Will the dictionary tab in the classic dashboard be done away with? Still dont see a classic use case (beyond showing how to do WebApps) for the sprint. Help me understand
Judy, the purpose of this sprint is to replicate the concept management
functionality from the legacy UI for use in the 2.x UI.
Building this as an OWA will make it easier to reuse in both the reference
application, and other distributions.
(The legacy UI will broadly stay the same, in the new module or currently
lives on. We arenāt intending to ādo away withā anything, or add anything
to it either.)
-Darius (by phone)
Ā·Ā·Ā·
On Mar 13, 2016 12:25 PM, "Judy Gichoya" wrote:
Will the dictionary tab in the classic dashboard be done away with? Still
dont see a classic use case (beyond showing how to do WebApps) for the
sprint. Help me understand
In Reply To
kristopherschmidt https://talk.openmrs.org/users/kristopherschmidt
/dev/4
March 13
Pascal, any idea when that work will be done? Webpack will be key to
properly managing dependencies once the Concepts OWA starts moving to the
ā1 component per fileā approach as dictated by the style guide. This work
would seem to have a big impact on
[RA-1077] - OpenMRS Issues which ā¦
One other thought if you are moving in the direction Webpack / ES6+Babel ā have you considered switching the dependency management from Bower to relying more on npm? Webpack suggests preferring npm/CommonJS modules to bower modules (http://webpack.github.io/docs/usage-with-bower.html). There seems to be a decent amount of momentum in this direction. I can also envision that npmās nested dependency management could become important to reduce ādependency ā ā ā ā ā as the number of OWAs and re-usable front-end components/libraries for OpenMRS increases.
One other thought if you are moving in the direction Webpack / ES6+Babel
ā have you considered switching the dependency management from Bower to
relying more on npm? Webpack suggests preferring npm/CommonJS modules to
bower modules (http://webpack.github.io/docs/usage-with-bower.html).
There seems to be a decent amount of momentum in this direction. I can also
envision that npmās nested dependency management could become important to
reduce ādependency ā ā ā ā ā as the number of OWAs and re-usable front-end
components/libraries for OpenMRS increases.
In Reply To
pascal https://talk.openmrs.org/users/pascal Pascal Brandt
https://talk.openmrs.org/users/pascal Community Manager, EMEA Region
March 12
Yes, we should use ES6 with Babel. Iām planning on updating the OWA
generator to use Webpack instead of Grunt. Iāll include the Babel loader
for transpiling ES6. Anyone have any other ideas for the generator? Iām
thinking we probably need a CSS preprocessor in the pipeline too.
