Projets-2016-2017-GrenobloisFute: Difference between revisions

From air
Jump to navigation Jump to search
No edit summary
No edit summary
Line 29: Line 29:
**Setting up environnement.
**Setting up environnement.
**Contacting OsmAnb by email to get more information.
**Contacting OsmAnb by email to get more information.



==''Week 4 (January 30th - February 5th)''==
==''Week 4 (January 30th - February 5th)''==
*Finally manage build on both computer.
*Reflexion about the libraries available in JAVA to carry the parser JSON.org, JACKSON
*Begin to look at source code and where and how pluggin is implemented (with help of previous group on this project)
*Viewing text when activating the plugin (detection where to write the plugin code)


==''Week 5 (February 6th - February 12th)''==
==''Week 5 (February 6th - February 12th)''==
*Begin to work on the Parser.
*Choice of the library : JACKSON
*First implementation with add of a fake pluggin based on the skiMapPluggin (and then remplacing the information and understanding how it works at the same time)
*Realization of an application in stand-alone
*Resolving merge issue.
*Link to SkiMapPlugin to test
*Goal : direct link to our plugin

===Design pattern===
* Adapter : Using data / external applications : métromobilités & OSMand data
* Memento : Restoration of the application if we remove the plugin
* Observer : To change its state, the map must be informed of the change of traffic data
* MVC : model view controller architecture to separate the representation of the map and data


==''Week 6 (February 27st - March 5th)''==
==''Week 6 (February 27st - March 5th)''==
*First implementation of a fake traficLayer based on paringPointLayer in goals of use it on our pluggin.
*Beginning of parser adaptation for the project
*Try tu use renderer but doesn't works.
*Bug resolution to redirect to our plugin
*CI jenkins installation on private server and configuration.


==''Week 7 (March 6th - March 12th)''==
==''Week 7 (March 6th - March 12th)''==
*Bug rezolution: the link to the plugin is effective
*Bug resolution on the renderer.
*We now can change the color of a route

Revision as of 13:15, 6 March 2017

Project presentation

Team

  • Supervisor : Nicolas Palix
  • Members : GUERRY Lucas/ VIAL-GRELIER Aymeric
  • Department : RICM4

Links

Progress of the project

Week 1 (January 9th - January 15th)

Choice of the subject

Week 2 (January 16th - January 22th)

  • Research of the source code on GitHub because the project of the previous students isn't up to date.
  • Fork of the git project
  • Try building application on both computer.

Week 3 (January 23th - January 29th)

  • The project doesn't build on one on the two computers so trying to understand why :
    • Downloading differents JDK and SDK
    • Reading documentation of OsmAnd
    • Setting up environnement.
    • Contacting OsmAnb by email to get more information.

Week 4 (January 30th - February 5th)

  • Finally manage build on both computer.
  • Begin to look at source code and where and how pluggin is implemented (with help of previous group on this project)

Week 5 (February 6th - February 12th)

  • Begin to work on the Parser.
  • First implementation with add of a fake pluggin based on the skiMapPluggin (and then remplacing the information and understanding how it works at the same time)
  • Resolving merge issue.

Week 6 (February 27st - March 5th)

  • First implementation of a fake traficLayer based on paringPointLayer in goals of use it on our pluggin.
  • Try tu use renderer but doesn't works.
  • CI jenkins installation on private server and configuration.

Week 7 (March 6th - March 12th)

  • Bug resolution on the renderer.