cac-t-u-s / om-sharp Goto Github PK

• Library of functions and objects
• Editor

Implement

• as general controller
• as an object

... to use/create the maquette in a patch ...

input a maquette, just to visualize and select boxes.

• Separate tracks
• Show piano keys
• Add notes
• Edit notes

Store editor params persitantly in the box

A big project which could be split into several sub-issues, around the use of time markers in the sequencer editor:

• Markers from objects
• Global markers (on rulers)
• Snap
• Synchronization
• etc.

Implement a basic UNDO system

Sort of "echo-area"

• Use LW's in-built or make a new one...

A utility box which will allow to dispatch data according to type.
Could stand for current OM's 'typed-input' which is rarely used.

Try to propose, e.g. rounded rectangles etc.

Decide what to do and implement variables

Inside the maquette (with menu commands)
Between maquette and patches

Turn page or scroll while cursor moves (sound, data stream, maquette...)

Implement the object

The interface between our code and LW's API can be much simpler.

Finalize/check meta-programming in maquette and temporal boxes

• Self patch box
• Self maquette box

• Review / optimize current code
• Get rid of dependencies
• Buffering and zoom levels

Decide / implement a system for loading user code

Display the current view in the global structure
Implement in sequencer and data-stream editors

Define a command to make external abstract embedded in the containing patch.

Test and validate recursive graphical functions

More than #audio outs should be authorised and re-routable in SOUNDs

Implement the OMLoop and File-Box (OMLoop with file I/O) in the visual language

Handle functions / patches not found

Check all features

• Editing
• Compilation
• Internalize / externalize
  ...

Visualize the contents value of the boxes in the sequencer window

Implement the pictures:

• Picture API
• Picture object
• Picture editor
• Picture in BPF background
• Picture in patch backgraound

Define / implement a system for the docs, reference and tutorials

=> fix box movements etc.

• Edit menus
• File menus
• Open file : remember previous location etc.
• find source
• etc.

Work on better automatic alignment between boxes

Allow to deal with the properties / inspector widow with several items at a time.

Cases to work:

• play a collection of sounds
• play / stop in collections in general
• Close an editor while playing
• Sync play box and editor

(currently commented in midi-events.lisp)

Add an optional input to the input bow in order to implement the "default value" feature.

Redo the DI-boxes:

• button
• switch
• choice-list
• popo-up menu
• check-box

• Basic operations: cut / paste / insert silence / fade in-out
• Undo/redo
• Save / revert to file

Implement a preferences system and interface

Integrate the basic OM preferences:

• Default box/connections properties
• ...

Decide / implement a system for libraries / package management

• Compute / display sonagram on SOUND boxes and editor
• Implementing PARTIALS as a data-frames over the SOUND
• Export to score