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

Separate all effects as a second platform independent library. #479

Open
hetii opened this Issue Aug 18, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@hetii

hetii commented Aug 18, 2017

Hello :)
I have some idea to separate all effects as separate project written in C.
It should be written totally as a platform independent code and linked as a library for project like FastLED or any other one.

By that way people could commit their effects and all different projects use such "led layout language" at the end.

Let me know what do you think about this idea.

@hetii hetii changed the title from Separate all effects as a second project. to Separate all effects as a second platform independent library. Aug 18, 2017

@focalintent

This comment has been minimized.

Show comment
Hide comment
@focalintent

focalintent Aug 18, 2017

Member

Sounds like a fantastic project idea! Let me know when you starting working on it and set up a repo for it, and we'll be happy to link to it. (Note that something like this is way outside the scope of what we've got planned for FastLED - I do have a private library that I use for effects building, but it's very unstable, and regularly gets thrown away and rewritten - but it turns out that while it's pretty straight forward to have a library that allows you to address/set LEDs, the needs and desires of people building led projects and doing animations and such are wildly different enough that having a single pattern/effect library that would be usable by everyone in the ways they need it would be quite a complex undertaking - even as my projects evolve from project to project, I find the effects library code i've tried writing in the past isn't applicable to a new project, hence it getting thrown away and rewritten).

Member

focalintent commented Aug 18, 2017

Sounds like a fantastic project idea! Let me know when you starting working on it and set up a repo for it, and we'll be happy to link to it. (Note that something like this is way outside the scope of what we've got planned for FastLED - I do have a private library that I use for effects building, but it's very unstable, and regularly gets thrown away and rewritten - but it turns out that while it's pretty straight forward to have a library that allows you to address/set LEDs, the needs and desires of people building led projects and doing animations and such are wildly different enough that having a single pattern/effect library that would be usable by everyone in the ways they need it would be quite a complex undertaking - even as my projects evolve from project to project, I find the effects library code i've tried writing in the past isn't applicable to a new project, hence it getting thrown away and rewritten).

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