Difference between revisions of "ZTeamMilestone1"

From mn/ifi/inf5750
Jump to: navigation, search
m (Tasks)
Line 3: Line 3:
 
The reason for using Leaflet is that it's light weight (good for mobile/low bw connections). It also seems that Google Maps will discontinue some of it's services in 2016.
 
The reason for using Leaflet is that it's light weight (good for mobile/low bw connections). It also seems that Google Maps will discontinue some of it's services in 2016.
  
We are planning to write the app basically from scratch, but borrow code from the existing OrgUnit app, that is in the standard DHIS2 package.
+
We are planning to write the app basically from scratch (using , but borrow code from the existing OrgU as starting point)nit app, that is in the standard DHIS2 package.
  
 
== Tasks ==
 
== Tasks ==
Figuring out map solution, and how to get the map data (coords) from the api.
+
* Creating wiki pages
 
+
* Figuring out map solution, and how to get the map data (coords) from the api.
Starting the base app
+
* Creating the git repo, and importing base app
 
+
* Implementing
Implementing
+
** Search (showing results both in table, and on map)
 
+
** Adding new facility (and deleting existing one)
Search
+
** Show info when clicking the map
 
 
Adding new facility (and deleting existing one)
 

Revision as of 17:17, 5 November 2015

We are planning to make a web app, using AngularJS and LeafletJS on the client side, and communicate to the server, using the API.

The reason for using Leaflet is that it's light weight (good for mobile/low bw connections). It also seems that Google Maps will discontinue some of it's services in 2016.

We are planning to write the app basically from scratch (using , but borrow code from the existing OrgU as starting point)nit app, that is in the standard DHIS2 package.

Tasks

  • Creating wiki pages
  • Figuring out map solution, and how to get the map data (coords) from the api.
  • Creating the git repo, and importing base app
  • Implementing
    • Search (showing results both in table, and on map)
    • Adding new facility (and deleting existing one)
    • Show info when clicking the map