Sormas-project: Android list view improvements

Created on 15 Mar 2019  路  5Comments  路  Source: hzi-braunschweig/SORMAS-Project

Fix the following problems:

  • [ ] List view changes after preloader is already hidden (i.e. the visual effect of the fragment replacement takes place too late or the preloader is hidden too early)
  • [ ] When changing the main filter of a list view with more than 16 items in it, the new list is opened scrolled down to the 16th item
minor sormas-app

Most helpful comment

@blongho Have you followed the instructions that Martin posted here above your comment? The Android app is designed to work in cooperation with a server for things like user authentication and data synchronization, which means you'll not be able to log in and test your code (unless you do some heavy code commenting while testing) without a server. Also, this error you're getting probably means you haven't run "mvn install" yet which is why the app does not have access to the required API.

All 5 comments

Hi, @MartinWahnschaffeSymeda, i would love to contribute to this project by "fixing" some of the sormas-app issues.

I have forked and cloned this project but when i import the app in android studio,and try to build the project, i get

ERROR: Failed to resolve: de.symeda.sormas:sormas-api:1.16.0-SNAPSHOT

My environment:

  • Windows 10 Pro
  • Android Studio 3.3.2

I would appreciate to have instructions on how to fix this so that i can take a look at the code base and see which features i can fix.

Thanks in advance.

Hi @blongho, great to hear that - we are eager to help other developers get involved!

In order to build the android app you need the sormas-api.jar of the development branch version in your local maven repository. The easiest way to do that is to go to the sormas-base path in your workspace and call ''mvn install'' to build the whole project with maven (see https://maven.apache.org/). This will also include the sormas-api. Afterwards you should be able to build the app.

If you really want to work with the android app, you will need to connect it to a server, so you can login with a user name and password and try to create new cases and other things.

There are two ways to do this:

  1. Setup your development enviroment with eclipse, as decribed here: https://github.com/hzi-braunschweig/SORMAS-Project/blob/development/DEVELOPMENT_ENVIRONMENT.md (you will still use Android Studio for development of the Android app)
  2. Only install your local server: https://github.com/hzi-braunschweig/SORMAS-Project/blob/development/SERVER_SETUP.md Calling mvn install on sormas-base will build the needed ear and war files. Copy the sormas-ear.ear, sormas-rest.war and sormas-ui.war form the workspace /target sub directories into the deploy directory of ther server domain.

Hope that helps.

Hi!
I am interested in working only on the sormas-app. Do i have to do everything that is listed in https://github.com/hzi-braunschweig/SORMAS-Project/blob/development/DEVELOPMENT_ENVIRONMENT.md#sormas-development-environment ?

So far, i have followed just the instructions for Android studio https://github.com/hzi-braunschweig/SORMAS-Project/blob/development/DEVELOPMENT_ENVIRONMENT.md#android-studio and i get

Could not find de.symeda.sormas:sormas-api:1.16.0-SNAPSHOT.
Required by:
    project :app

I have set up my keystore.properties as in the instructions. I doubt if this is the problem as a result of the keystore not properly placed and assigned since signing.gradle sets the keystore properties if none is detected).

What am i missing?

@blongho Have you followed the instructions that Martin posted here above your comment? The Android app is designed to work in cooperation with a server for things like user authentication and data synchronization, which means you'll not be able to log in and test your code (unless you do some heavy code commenting while testing) without a server. Also, this error you're getting probably means you haven't run "mvn install" yet which is why the app does not have access to the required API.

Will setup the server and try again. I thought it were not necessary for the Android app

Was this page helpful?
0 / 5 - 0 ratings