GSoC 2017 - Android Client Feature Parity

I forked repo and cloned and then build this project take too much time Please help me why it take much time to build Gradle.

Gradle sync issue Warning:WARNING: Dependency org.apache.httpcomponents:httpclient:4.5.2 is ignored for release as it may be conflicting with the internal version provided by Android. In case of problem, please repackage it with jarjar to change the class packages

Gradle build : Information:Gradle tasks [:openmrs-client:generateDebugSources, :openmrs-client:mockableAndroidJar, :openmrs-client:prepareDebugUnitTestDependencies, :openmrs-client:generateDebugAndroidTestSources]

Hey all,

My name is Harikrishnan Rajan. Iā€™m an undergraduate student from Mumbai, India studying Computer Science. Iā€™m trying to find some issues to work on. I canā€™t find anything in the ā€˜Ready to workā€™ section that is not marked as ā€˜Code Reviewā€™ or ā€˜In progessā€™. Can I create my own issues and work on them ?

Thanks, Hari

Hi everyone,

This is for clarification. Some of the features mentioned in my original project page have little or no documentation, which is why Iā€™ve opened up the project for suggestions/ideas. Therefore, while submitting your proposal, you may add any feature/fix that you think is suitable, anything that seems better to you!

Iā€™ve been getting quality proposals and I just wanted to say that donā€™t let the unavailability of documentation be a bother to you.

The REST documentation will be improved this year, among other things, so things will be smoother from now on.

Best of luck!

To answer some queries:

@hao555sky, the Scheduled queries are to be implemented using a Syncadapter. Ideally, all the sync operations should happen via syncadapters to maximize battery life. This can technically solve the problem of ā€œforcingā€ a manual sync while there is a valid network connection.

In the web app, the appointments are scheduled, but your question on talk made me think in a different direction, about synadapters :slight_smile:

@defcon, about the Provider module : http://devtest04.openmrs.org:8080/openmrs/adminui/metadata/configureMetadata.page This has a provider attributes link.

Also see the REST Api :

https://wiki.openmrs.org/display/docs/REST+Web+Service+Resources+in+OpenMRS+1.9#RESTWebServiceResourcesinOpenMRS1.9-Provider https://wiki.openmrs.org/display/docs/REST+Web+Service+Resources+in+OpenMRS+1.9#RESTWebServiceResourcesinOpenMRS1.9-ProviderAttribute https://wiki.openmrs.org/display/docs/REST+Web+Service+Resources+in+OpenMRS+1.9#RESTWebServiceResourcesinOpenMRS1.9-ProviderAttributeType https://wiki.openmrs.org/display/docs/REST+Web+Service+Resources+in+OpenMRS+1.9#RESTWebServiceResourcesinOpenMRS1.9-Role

The implementation will be similar to all other rest endpoints, like Patient.