Difference between revisions of "Sous-titre en temps réel d'un cours"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | ==Objectif== |
||
| − | =Preambule= |
||
| + | *réalisation d’une application de traduction semi-automatique |
||
| − | |||
| + | *IHM collaborative 2.0 pour faciliter la correction des mauvaises traductions |
||
| − | |||
| + | ==Les contraintes technologiques== |
||
| − | =Project presentation= |
||
| + | *google speech recognition API |
||
| − | |||
| + | *HTML5+ CSS + Javascript |
||
| − | |||
| + | ==Plan de travail== |
||
| − | = Team = |
||
| + | *découverte de google speech |
||
| − | |||
| + | *découverte de reveal.js |
||
| − | * Supervisors : Jérôme Maisonnasse |
||
| + | *scénarisation |
||
| − | |||
| + | ==Conseil== |
||
| − | * Members : BUI David / LECHEVALLIER Maxime / OUNISSI Sara |
||
| + | *ne pas laisser la créativité l’emporter sur l’atteinte d’un proto fonctionnel |
||
| − | |||
| − | * Departement : [http://www.polytech-grenoble.fr/ricm.html RICM 4], [[Polytech Grenoble]] |
||
| − | |||
| − | |||
| − | =Specifications= |
||
| − | |||
| − | |||
| − | =Links= |
||
| − | |||
| − | |||
| − | '''GitHub''' |
||
| − | |||
| − | |||
| − | |||
| − | '''Documents''' |
||
| − | |||
| − | |||
| − | |||
| − | = Progress of the project = |
||
| − | |||
| − | The project started January 11th, 2015. |
||
| − | |||
| − | == Week 1 (January 11th - January 17th) == |
||
| − | ''First interview with our tutor Jérôme. We've learned more about our project and what is expected for the next weeks'' |
||
| − | |||
| − | *Handling the project |
||
| − | *testing Google API Speech |
||
| − | *Making git repository |
||
| − | |||
| − | == Week 2 (January 18th - January 24th) == |
||
| − | |||
| − | *Going further into the tests of the API |
||
| − | *https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html |
||
| − | *There are multiples API : Google recognition and Web Speech API |
||
| − | |||
| − | == Week 3 (January 25th - January 31th) == |
||
| − | *Microphone works only when a virtual server is installed, we try with apache |
||
| − | *Learning JavaScript |
||
| − | *Learning HTML/CSS |
||
| − | |||
| − | |||
| − | == Week 4 (February 1st - February 7th) == |
||
| − | *Scrum |
||
| − | *Trello |
||
| − | |||
| − | == Week 5 (February 08th - February 14th) == |
||
| − | |||
| − | |||
| − | == Design patterns == |
||
| − | |||
| − | * Model-View-Controller (GoF) : This pattern is used to separate application's concerns. Our project is Web oriented program |
||
| − | * Singleton (GoF) : Ensure a class has only one instance, and provide a global point of access to it. |
||
| − | Example : a teacher is the only one who can launch slides |
||
| − | * Visitor (GoF) : Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates. |
||
| − | Example : students can edit the subtitles |
||
| − | * State (GoF) : Allow an object to alter its behavior when its internal state changes. The object will appear to change its class. |
||
| − | Example : Microphone detection |
||
| − | * Service Contract - Concurrent Contracts (SOA) : http://soapatterns.org/design_patterns/concurrent_contracts |
||
| − | |||
| − | |||
| − | |||
| − | == Project work == |
||
| − | |||
| − | Solving critical problems : the API is not working with ambient noise. When we are talking directly to the microphone the API is working fine. |
||
| − | |||
| − | Tests : |
||
| − | *Fast talking : Dead after 1 minute |
||
| − | *Slow talking (with interruptions) with music arround : Dead after 2 minutes |
||
| − | *Slow talking : Dead after 2 minutes |
||
| − | |||
| − | Meeting with Jérôme to have new directions after a quick demo of the app. |
||
| − | |||
| − | |||
| − | == Week 6 (February 15th - February 21st) == |
||
| − | |||
| − | Studying Socket.io, trying the demo chat, linking Reveal.js with socke.io |
||
| − | |||
| − | |||
| − | |||
| − | =Gallery= |
||
Latest revision as of 00:08, 7 March 2016
Objectif
- réalisation d’une application de traduction semi-automatique
- IHM collaborative 2.0 pour faciliter la correction des mauvaises traductions
Les contraintes technologiques
- google speech recognition API
- HTML5+ CSS + Javascript
Plan de travail
- découverte de google speech
- découverte de reveal.js
- scénarisation
Conseil
- ne pas laisser la créativité l’emporter sur l’atteinte d’un proto fonctionnel