Skip to content

Abstraction Layer: Dot Definitions #41

@uber5001

Description

@uber5001

I think this needs to be cleaned up a lot in our code.

The idea is that a Dot represents an AudioNode, but a Dot is not an AudioNode. Our code should work with dot definitions, and those definitions should work with AudioNodes. Our application should not work with AudioNodes directly. This allows for the easy addition of custom nodes that are not defined in the Web Audio API spec itself, such as MIDI nodes and user-made nodes.

This layer is already partially defined ( and works! see pull #40 ), but not completed.

The only issue I have with this abstraction layer is that there will probably be functions in the definitions in nodes.js. My first instinct points out that if there are functions, then the definitions can't be JSON.stringify'd. But is that needed?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions