1. 24 May, 2017 2 commits
  2. 23 May, 2017 5 commits
  3. 22 May, 2017 1 commit
  4. 19 May, 2017 1 commit
    • Tom JORQUERA's avatar
      client: Add first version of robot behavior · d6ae25ef
      Tom JORQUERA authored
      Implement first version of robot behavior. Currently, the robot listen for new
      participants and, when a participant connect, start speech recognition.
      The results of speech recognition are displayed in the console.
      The robot requires the `start()` method to be called to begin. This method is
      automatically called by the runner after loading all the modules.
  5. 18 May, 2017 2 commits
  6. 17 May, 2017 1 commit
    • samy's avatar
      Fix callback tests and replace test descriptions · 780b67b6
      samy authored
      Replace test descriptions 'should not call callback with actual status' with 'should not call callback with incorrect value of status'
      Replace test description 'should not call callback with actual final' with 'should not call callback when final value is incorrect'
      Replace 'toHaveBeenCalledWith' with 'toHaveBeenCalled()' to test that the callback has not been called at all
  7. 16 May, 2017 8 commits
  8. 15 May, 2017 1 commit
  9. 11 May, 2017 2 commits
  10. 10 May, 2017 4 commits
  11. 09 May, 2017 8 commits
  12. 05 May, 2017 5 commits
    • Tom JORQUERA's avatar
      Uses `controller.loadAll` to load the client resources · 43a5f415
      Tom JORQUERA authored
      We now use the function defined in `lib/controller` to load the resources to
      inject into the client.
      The order of the "modules" to be loaded is defined as follow:
      - controller
      - lib
      - robot
      Each module corresponds to a specific folder in the `client` folder.
    • Tom JORQUERA's avatar
      Add `lib/controller` · 7a26dd36
      Tom JORQUERA authored
      This module allow to load all the files that must be injected into the client.
    • Tom JORQUERA's avatar
      Add skeletons for client modules · 10d984d0
      Tom JORQUERA authored
      We define three modules to be injected in the client:
      - controller: in charge of exposing the hubl.in functions as a unified API
      - lib: containing various libraries to be used by the robot
      - robot: containing the behavior of the robot itself
      Currently these modules only contain the base skeleton.
    • Tom JORQUERA's avatar
      Runner now take a list of source files to inject · 6d9b93bb
      Tom JORQUERA authored
      Instead of a single controller file, `runner.run` now takes a list of source
      files that will be injected in the passed order.
    • Tom JORQUERA's avatar
      Move and clean robot client controller · 184de96b
      Tom JORQUERA authored
      - `robotClientController.js` moved to `client/controller/controller.js`
      - `controller` renamed to `robotController`
      - changed some `var` to `const`
      - updated path to controller in `app.js`