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

Implement

• as general controller
• as an object

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

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

Check all features

• Editing
• Compilation
• Internalize / externalize
  ...

• Library of functions and objects
• Editor

Finalize/check meta-programming in maquette and temporal boxes

• Self patch box
• Self maquette box

Visualize the contents value of the boxes in the sequencer window

Sort of "echo-area"

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

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

Store editor params persitantly in the box

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

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.

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

=> fix box movements etc.

input a maquette, just to visualize and select boxes.

Decide what to do and implement variables

Implement the object

Handle functions / patches not found

Implement the pictures:

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

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

Decide / implement a system for libraries / package management

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

Cases to work:

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

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

(currently commented in midi-events.lisp)

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

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

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

Redo the DI-boxes:

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

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

Work on better automatic alignment between boxes

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

Test and validate recursive graphical functions

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

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

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

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

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

Decide / implement a system for loading user code

Implement a basic UNDO system

Implement a preferences system and interface

Integrate the basic OM preferences:

• Default box/connections properties
• ...