#thats why i asked for your planned
1 messages Β· Page 1 of 1 (latest)
The LCPF is built on top of CircuitPython, and I sometimes need to share details to provide relevant context - like why I'd prefer ADC on a StemmaQT/Qwiiic board, but #help-with-circuitpython isn't an appropriate venue for Q&A on my project. That said, I'll gladly answer any LCPF questions you have on my discord server. If you're interested, please take a look at the LCPF Developer's README first. If you're still interested after that, the Lumensalis contact page has info on our discord server.
Lumensalis Website
hey! thanks π ill have a read and come back to it tomorrow, when i sobered up a bit π
But a short answer is that the LCPF is just a layer on top of CircuitPython which, among other things, minimizes the need for users to know or care about pin assignments.
arg.... im reading it and ..... wel im curious to see what you will come up with ^.^
but things like:
-that code is (hopefully) easy to understand and modify
-most projects will simply start by copying and modifying an existing example
-itβs plausible that the majority of projects will be less than 100 lines of βcodeβ
that is how i learned it but arduino already provides that...i mean c++ is not that hard... and one should know what pin to connect thing to... otherwise it kinda feels like teaching people how to roof without telling them how a ladder works/how to get up there. id think you need a really big hardware support behind this?
You could maybe create a cool firmware for existing MCU like arduino but one still needs to look before plugging stuff in, not all ports have PWM for instance.
or maybe you planning on a shield?
but then again i have also not used the new block style programming yet. it might be great! im just a bit old-school
If you read the README before you sober up, you might actually be ready to jump right in. I'm not saying that you should go scarf down some "homemade" brownies or foraged mushroom salad before your first LCPF discussion, but... it is rather different.
i already reading it, before i join, thats where those questions came from π but i will not join yet. i wont be able to add anthing, just ask questions π
'i wont be able to add anthing, just ask questions' - asking questions IS adding something, so you'd have plenty to add!
i mean "providing a way to add complex interactive light, audio, and motion effects to DIY projects (tabletop terrain, Cosplay, stage props, etc)" kinda sounds like USB π and sure.... i guess ill join π if you think its ok π
FWIW the "Developer's README" isn't meant to provide a simple general overview of the LCPF - it's more a preemptive "warning" that things might be a bit twisted if you have any experience coding with traditional APIs and attempt to view the LCPF from that perspective. Bit of a square hole, dodecahedronal peg scenario
All are welcome
i joined and are pending. π
But so you plan on making shields?
I'm not planning on making any hardware - I just add support for existing things that "fit" the LCPF purpose. Currently the LCPF supports several D1 Mini shields from Terrain Tronics, and I'm planning to start supporting FeatherWing shields soon.