Difference between revisions of "Groupname.js"

From mn/ifi/inf5750
Jump to: navigation, search
(Fixed broken formatting)
(Screenshots and screen flows)
Line 46: Line 46:
 
== Screenshots and screen flows ==
 
== Screenshots and screen flows ==
  
No.
+
Screenshot of Maps
 +
 
 +
[[File:Maps_groupname.png|800px]]
 +
 
 +
Sreenshot of Charts
 +
 
 +
[[File:Charts_groupname.png|800px]]
 +
 
 +
Screenshot of Table
 +
 
 +
[[File:ReportTables_groupname.png|800px]]
 +
 
 +
Sreenshot of Event Charts
 +
 
 +
[[File:EventCharts_groupname.png|800px]]
 +
 
 +
 
 +
.
  
 
== Documented learning during project ==
 
== Documented learning during project ==

Revision as of 15:15, 30 November 2016

Group members

  • Rune Johan Borgli (runejb@uio.no)
  • Matias Hermanrud Fjeld (matiashf@student.matnat.uio.no)
  • Pål Mathias Brandsvoll (paalmbr@uio.no)
  • Joakim Misund (joakimmi@student.matnat.uio.no)

Repository: https://github.uio.no/matiashf/groupname.js

Summary of requirements

Implement listing and sharing of favorites to Facebook and Twitter as a DHIS2 webapp using javascript.

Required features:

  • List favorites by type (maps, charts, tables)
  • Share favorite to Facebook
  • Share favorite to Twitter

Desired features:

  • Show enlarged favorite
  • Sorting
  • Filtering/searching

Architecture / Tools

We will implement a DHIS2-webapp based on DHIS2 App skeleton. We will use React for code structure, D2 to communicate with the backend, and D2-ui + material-ui for the frontend. Using Webpack, we will play around with ES2016 using Babel. Also, SASS is cool!

While developing we will set up DHIS2-live locally (alternatively depend on [DHIS2-play](https://play.dhis2.org/)).

Milestones / Time Schedule

  • Milestone 1: 28/10 - Implementation plan
  • Milestone 2: 6/11 - Implement core features
  • Milestone 3: 13/11 - Optional features and polish
  • Milestone 4: 27/11 - Final delivery
  • Milestone 5: 7-9/12 - Group Presentation

Potential problems

  • Will we need image conversion for Twitter?
  • Should we make a responsive page?

How we are dividing tasks within the group

Coming ~1/11.

Screenshots and screen flows

Screenshot of Maps

Maps groupname.png

Sreenshot of Charts

Charts groupname.png

Screenshot of Table

ReportTables groupname.png

Sreenshot of Event Charts

EventCharts groupname.png


.

Documented learning during project

Yes.

Suggested improvements to the API

It's beautiful. Love it unconditionally. <3