Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out scalable way to handle feature data #5

Open
soundanalogous opened this issue Jan 3, 2015 · 0 comments
Open

Figure out scalable way to handle feature data #5

soundanalogous opened this issue Jan 3, 2015 · 0 comments

Comments

@soundanalogous
Copy link
Member

feature.js is collection of data for all of the current Firmata features for the configurable firmata architecture. Example of "features" are DigitalInput, DigitalOutput, AnalogInput, I2C, OneWire, etc. This collection will grow and needs to be easy for Firmata feature developers to add data for their new features to. What is the best way to accomplish this? A flat file as it currently is? A separate module for each feature (or a file for core features and separate file for each contributed feature (likely device-specific features), a database or something else?

The collection of features will also be used to populate the firmata builder UI (a selection of features and options that the users chooses to generate the Arduino .ino file).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant