> > *It doesn't get super heavy use, but it generally exposes new users to > some of the hardware features before they have to take things to the next > level. My hope is that it would provide some single point of documentation > on the Linux file interfaces for these peripherals that would be reasonable > to read. Unfortunately, not enough people in this community are interested > in patching JavaScript code to document the Linux interfaces, so the > out-of-box experience has remained a bit rough (though I'd argue still > better than it would be without it).* >
So here is the problem for me. I'm an experienced programmer of ~20 or so years. I do not know Nodejs well enough to just start ripping into your package and fix it. From my perspective, it's just as easy, and perhaps easier to just read the Nodejs documentation and create my own abstraction layer. *Anyway, I'm still motivated to enable all the peripherals with it. > octalbonescript is an interesting alternative, but they also haven't kept > up with kernel updates and broke some interfaces I wasn't interested in > breaking. The MRAA thing is hot to try right now, but it largely goes > against the whole strategy of utilizing kernel drivers and advancing the > state of Linux, so I'm not a big fan.* > > *Anyway, if you aren't a big fan, I'd suggest offering alternatives to help newbies get started or simply leave-it-be.* This is exactly my plan, eventually. I have a huge project of my own right now that includes creating a Nodejs back end, and I'm thinking an Angularjs front end for a project that is pretty much a web appliance that uses nearly every pin on the P8, and P9 headers. With this project though, I have a lot to learn myself. As I'm not really a web developer. Technically, I know I could do all of this in C, at least on the back end. But that does not exactly make much sense to me as Nodejs has a much better library infrastructure for this situation. So I've never even toggled a GPIO with Nodejs yet, and haven't even seen any code yet either. However, I do know the peripheral sysfs stuff, and Nodejs BCL well enough to know that it can be done, and that doing so would be fairly trivial for an experienced developer. All I have to do is read up on the various libraries I need to know, and I'll be set. So, when I do get around to writing code for this purpose. I will write up a blog post, and offer the information for all to see. On Mon, May 16, 2016 at 9:38 PM, Jason Kridner <[email protected]> wrote: > > On Sat, May 14, 2016 at 8:34 AM Jason Kridner <[email protected]> > wrote: > >> Robert's made a ton of improvements over the last several weeks/months >> and it makes some sense to try to update the promoted images. A GUI-less >> IoT image is now being produced to >> >> These are using a 4.4 Linux kernel. >> > > So far, feedback has been that these images are an improvement, but have > some issues to be resolved. To that end, I've mirrored them and added them > to > > http://beagleboard.org/latest-images > > After Maker Faire Bay Area, we can put a concerted effort into cleaning up > the remaining bugs. > > >> >> LXQT-4GB for BeagleBoard-X15: >> >> http://debian.beagleboard.org/images/bbx15-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz >> >> >> shat256sum: 69dc6b1daccc5fc0bb3050977d102706621ec0dd8bf14757f5ef0542e60ac72e >> >> LXQT-4GB for BeagleBone Black and compatibles: >> >> http://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz >> >> >> sha256sum: 28d67e877497fb9e52fe605f2cbefdbaedaff23e9fa82e9ed2076ae375aa777f >> >> IoT for BeagleBone Black and compatibles: >> >> http://debian.beagleboard.org/images/bone-debian-8.4-iot-armhf-2016-05-13-4gb.img.xz >> >> >> sha256sum: 22fbba21cf294a92528b8a973e838f3cac801ce0e7d180b260a583f4bb0d1318 >> >> There are associated bmap files in the directory for those using >> bmaptool. For others, I recommend using http://etcher.io. >> >> Reply with issues here or post to >> http://github.com/beagleboard/image-builder. >> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPk16RSwkhhAp1i3wcfxdBQ%3DZ_vOkZgV%2BYxcgbZfooBufA%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPk16RSwkhhAp1i3wcfxdBQ%3DZ_vOkZgV%2BYxcgbZfooBufA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqYdCD2h9bh4U8YrAsck2OFx8RqjOa1Nbb2_CH30-e%3DWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
