ev3dev / ev3dev-lang

(deprecated) language bindings for ev3dev sensors, motors, LEDs, etc.
GNU General Public License v2.0
56 stars 39 forks source link

PiStorms platform devices #115

Open dlech opened 9 years ago

dlech commented 9 years ago

This is what PiStorms is looking like now.

B stands for "Bank", so you might want to translate pistorms:BX to PistormsBankX in the code gen.

jabrena commented 9 years ago

It sounds nice! I hope to receive a unit in some weeks. I will help in the testing process.

ddemidov commented 9 years ago

B stands for "Bank", so you might want to translate pistorms:BX to PistormsBankX in the code gen.

I did not understand this part. Do you mean user-friendly name for the port should be PistormsBankX?

dlech commented 9 years ago

Yes, that is what I mean. Just a suggestion.

ddemidov commented 9 years ago

@dlech, we can do that, or we can stick to INPUT_X, OUTPUT_X on all platforms. The latter would make scripts more portable between platforms. What do you think?

dlech commented 9 years ago

I think that sounds good. I would like the same program to run on any platform without having to make any changes.

WasabiFan commented 8 years ago

What's the conclusion on this? Were the PiStorms devices added to Python (if so, what was done there)? If not, I think we need to have a discussion on the platform differences and standardization.

As I understand it, there are three platforms that we need to support as of now (correct me if I'm wrong):

So, I think we need to get this standardized spec-wise so that adding more platforms (I think there was talk of the Beaglebone) isn't going to break anything.

For the port names, @ddemidov How do you think we can implement the ability to use the same OUTBUT_X constants? In my case at least, I declare them as export var OUTPUT_A = 'outA', so they are used directly as strings. Did you already find a way to implement this on your end?