Week 2 Team Meeting Minutes

Tuesday, 8 May 2018, 2pm

• We discussed this morning’s team building workshop

  • Attended Team Building Workshop Today and won a prize for group exercise.

• Last weekend, Lorenzo created a proof of concept that contained the structure for building all the parts:

  • An HTML and Typescript frontend based on the Angular framework that displays inside a webview in VS Code
  • A backend that runs Python code in an interpreter and sends the output to the frontend
  • Common types, shared as a node package between the backend and frontend, to streamline the interface between the two parts of code
  • Marco contributed a bare-bones Python interpreter that supports running code and reading stdout.

• Everyone got the project to build and run successfully today, and spent some time understanding the structure.

• We wrote a list of tasks to do for a first milestone version. We created Github issues for all of the points below:

   * export to jupyter and excel: select cards with a "select cards" button, then export with another button
   * implement interpreter/card types: plain text, html, images...
   * pop-up detail view
   * title inferring algorithm
   * frontend: card styling
   * frontend: changing the card title
   * frontend: collapse-expand code
   * frontend: delete/expand buttons
   * frontend: rearrange cards
   * installing and running jupyter automatically
   * loading extension when python files are open
   * displaying a "Show output pane" button
   * sending code on ALT-Enter: also on single line
   * adding R support
   * custom markdown cards
   * integrate inline command in interpreter for matplotlib
   * show run status of a python script in the status bar
   * filtering cards based on a search query
   * optimising memory usage (destroying cards when hidden)
     saving state
   * frontend: syntax highlighting of input code
   * import python packages before anything executes
  

Project management

• We set up a protected master branch, and agreed to use git to organise our workflow
• We will keep track of features and contributions via Github issues
• New features will be worked on in separate branches
• We will carry out code reviews before adding features to the main branch

Next steps

• We split out tasks to do over the next few days by assigning ourselves github issues
• Meanwhile, Rajan will be creating a survey for academics and the first draft of the leaflet

Next meeting: Tuesday 15th May