tomduncalf/tomduncalf_juce_web_ui

Issues

• Add team ID to bundle ID to prevent collisions

  #21 opened 4 years ago by tomduncalf
  0

• Always run callbacks on the message thread?

  #5 opened 4 years ago by tomduncalf
  0

• Examples of using svg, canvas, webGL for rendering components

  #16 opened 4 years ago by tomduncalf
  0

• Measure memory usage

  #19 opened 4 years ago by tomduncalf
  0

• Better logging (hide chatty logs)

  #18 opened 4 years ago by tomduncalf
  0

• Performance testing harness

  #17 opened 4 years ago by tomduncalf
  0

• Use direct browser callbacks

  #15 opened 4 years ago by tomduncalf
  0

• Run release React build in release mode

  #14 opened 4 years ago by tomduncalf
  0

• Decide on module name

  #13 opened 4 years ago by tomduncalf
  0

• Documentation

  #1 opened 4 years ago by tomduncalf
  0

• Tutorial

  #2 opened 4 years ago by tomduncalf
  0

• Code review C++

  #12 opened 4 years ago by tomduncalf
  0

• Allow the web UI to be run in the browser for easier development (maybe using a snapshot of the parameter value tree?)

  #11 opened 4 years ago by tomduncalf
  0

• Proper typing of "choice" components

  #10 opened 4 years ago by tomduncalf
  0

• Use the parameter metadata sent across from JUCE to set min, max, etc. on components

  #9 opened 4 years ago by tomduncalf
  0

• Cross-platform support

  #8 opened 4 years ago by tomduncalf
  0

• JUCE should queue messages before JS is ready

  #7 opened 4 years ago by tomduncalf
  0

• Send begin/end paramter change gesture messages

  #6 opened 4 years ago by tomduncalf
  0

• Modularise supporting TypeScript code into an npm package

  #4 opened 4 years ago by tomduncalf
  0

• Add console.log hook so you can see errors in Xcode

  #3 opened 4 years ago by tomduncalf
  0