Difference between revisions of "RICM4 2017 2018 - Dashboard"

From air
Jump to navigation Jump to search
Line 1: Line 1:
 
=Presentation=
 
=Presentation=
   
The aim of [https://air.imag.fr/index.php/Dashboard_pour_gestionnaire_de_t%C3%A2ches DashBoard] is to develop a single page application. It will allow OAR's users and managers to use the technology more comfortably.
+
The aim of [https://air.imag.fr/index.php/Dashboard_pour_gestionnaire_de_t%C3%A2ches DashBoard] is to update a single page application already existing. It allows OAR's users and managers to use the technology more comfortably. Unfortunatly the 5th version of Angular made it impossible to use because technologies incompatibilities.
   
 
=Contraints=
 
=Contraints=
Line 34: Line 34:
 
Work done
 
Work done
 
* Creation of the Git deposit
 
* Creation of the Git deposit
* Decision on the general outline of our spa
+
* Decision on the general outline of our SPA
 
* Start the template
 
* Start the template
 
To do for next week
 
To do for next week
Line 62: Line 62:
 
To do for next week
 
To do for next week
 
* Try to use the API with some commands
 
* Try to use the API with some commands
 
==Week 6 : 05/02/18==
 
Work done
 
* Do the steps given by the supervisor to use the API with SB-Admin-BS4-Angular-5
 
* Start to talk about the presentation
 
To do for next week
 
* Prepare the presentation
 

Revision as of 20:18, 5 April 2018

Presentation

The aim of DashBoard is to update a single page application already existing. It allows OAR's users and managers to use the technology more comfortably. Unfortunatly the 5th version of Angular made it impossible to use because technologies incompatibilities.

Contraints

  • SB Admin Angular5 based
  • Single-page application
  • Restful service

Team

Students:

  • BELGUENDOUZ Sekina : Developer
  • LARNICOL Titouan : Project leader

Supervisor :

  • RICHARD Olivier

Progress

Week 0 : 15/01/18

  • Projects' choice

Week 1 : 22/01/18

Work done

  • Read the documentation.
  • Get familiar with the technological constraints.

Week 2 : 29/01/18

Work done

  • Read the documentation.
  • Get familiar with the technological constraints.

Week 3 : 05/02/18

Work done

  • Creation of the Git deposit
  • Decision on the general outline of our SPA
  • Start the template

To do for next week

  • Finish the outline of the wed application

Week 4 : 12/02/18

Work done

  • Work on the template
  • Look at the usage of the API
  • Download OAR docker

To do for next week

  • Finish roughly the template
  • Try to use the API with some commands

Week 5 : 19/02/18

Work done

  • Work on the outline
  • Try to solve the problem related to the API

To do for next week

  • Finish roughly the template
  • Try to use the API with some commands

Week 6 : 26/02/18

Work done

  • Finish roughly the template
  • Solve the problem related to the API with the supervisor

To do for next week

  • Try to use the API with some commands