David Lechner
David Lechner
I like the inversion idea. Makes things a bit simpler. If you published the autogen stuff on npm then you wouldn't even have to add ev3dev-lang as a submodule. It...
As far as the LEGO-specific drivers are concerned, the `9-ev3dev` is what matters.
PowerSupply: See #131. There is no need to use platform-specific names or even have platform-specific names in the spec. Then it is totally future-proof and one less thing to worry...
Does the sensor show up in BrickMan under Device Browser? Also it would be better if the bug report was filed in the ev3dev-lang-python repository. https://github.com/ev3dev/ev3dev-lang-python/issues
OK, so not a driver issue. More python people will see your issue if you post it at: https://github.com/ev3dev/ev3dev-lang-python/issues
> I'd call it simply ev3dev if you don't mind\ If you are writing a library that adheres to the ev3dev-lang spec, you should use the namespace (and package name)...
There are some tips on submodules in #30.
Unfortunately, the "arm" in CoreCLR is "armhf" in Debian, so no CoreCLR for the EV3 (which is "armel" in Debian). The latest mono from Xamarin works though.
Something like [this](https://www.adafruit.com/products/63) and [this](https://www.adafruit.com/products/1328) may be more in your price range if you need to leave the EV3 on for long periods of time. Also, I would suggest using...
`mono-complete` is getting hung up for me. It installs a bunch of desktop packages that we don't need on EV3 anyway. I did successfully make an image that has `mono-runtime`...