We have a new employee and his first task is to make new programming language bindings and to document the low-level TCP/IP communication (so it is in theory possible to use every programming language)

 

The remaining question is of course: Which programming langauge should we support first? What should have the highest priority?

I would focus on documenting the communication protocol. That way the entire community can start writing their own bindings in any language they want.

The communication protocol will be documented. It is important that the language bindings are generated using our generation config files etc., otherwise every api change and new product will be a huge pain in the ass.

Are your C#-Bindings CLR-compliant? If so they should work for Visual Basic .NET out of the box (as for any other CLR-compliant language). Or what do you mean by "Visual Basic"?

 

BR

Jan

At 1st is there a XML dokumenation in the last C# bindings? In English and German please. For Visual Studio is a code documentation a very nice feature.

-

Back 2 Topic: A "graphical language" like:

http://greyscalegorilla.com/blog/2011/11/intro-to-xpresso-in-cinema-4d/

or in the real robots project:

http://web.archive.org/web/20021216102124/http://www.realrobots.co.uk/magazine.html

Some people like the idea of the Bricks but they nerver learn a programming Language. So for this target group were a (German: Klikitiebunti Programmieroberfläche) a graphical programming interface the best way.

 

@AuronX

Yes, you should be able to use the .dll of the C# Bindings in VB.net. But there is currently no documenation on how to do this and no sample code etc.

Hi,

Could you make brickd usb driver documentation too when you'll have time ?

Thanks.

The protocol we speak on USB is practically the same that we speak over TCP/IP. So i think we can do that in one go!