| |
I've written a document summarizing all the options available for Linux that is
available here:
http://linuxdoc.org/HOWTO/mini/Lego/
This ignores Spirit.OCX and RoboLab, since they are windows only, but to the
best of my knowledge covers every other programming interface that is available
for the RCX, including links to their homepages and descriptions of what "type"
of interface to the lego they provide. Hope that helps, and I'm still actively
maintaining the HOWTO, so if anyone has other suggestions or things that I've
missed, please let me know. Good luck!
Luis
P.S. Ob. plug: if you want the best available docs on three of those options
(legOS, NQC, and pbForth) you may want to look into Extreme Mindstorms at
http://www.amazon.com/exec/obidos/ASIN/1893115844/tieguyorg
If the Dutch like it, it must be good :)
In lugnet.robotics.rcx, Ben Erwin writes:
>
> I can only speak from experience about programming languages that use the
> standard firmware, since that's all I've used.
>
> *Spirit.OCX (I've used VB and J++): The worst way to program in the standard
> firmware. non-intuitive syntax (even if you replace the numbers with
> variable
> names). lot's of ugly periods hanging around. I only learned/used this
> when I
> was making VB programs for all of the robots in my book and putting them
> onto
> the CD-ROM. Other than that I never use it. I'm sure some of the GUI
> interfaces that people have made for use with the Spirit are pretty good,
> but I
> haven't checked them out for more than a minute each.
>
> *RCX Code: Graphical. OCX dependency. The easiest way to write a
> quick-and-dirty sequential, simple-multitasking, and simple looping kinds of
> programs. Not good for much else. Good for kids with low motor
> skills/attention span. No variables (yet) besides a simple counter.
>
> *NQC: There are some things that you can do with NQC that you can't do with
> ROBOLAB (I'm not sure exactly what - maybe someone else can elaborate).
> Good
> if you're already used to C. I first learned NQC when I translated all of
> Dave's programs for his first book into ROBOLAB for his CD-ROM (check 'em
> out,
> I included jpg's too). It took me a week, and it wasn't a pleasant
> experience
> because I find ROBOLAB much more intuitive.
>
> *ROBOLAB: Graphical, like a flowchart. Written in LabVIEW. No OCX
> dependency.
> The best standard firmware solution in my _biased_ opinion. There are
> things
> that you can do with ROBOLAB that you can't do with NQC (in an
> out-of-the-box
> sense): Internet Communication, Graphing, Calculations on Data, Turn
> programs
> into Web pages, etc. Very intuitive.
>
> For non-standard-firmware languages, there is YBL (yellow brick logo) from
> the
> media lab, legOS, pbForth, ... ??
|
|
Message is in Reply To:
 | | Re: Programming Languages
|
| I can only speak from experience about programming languages that use the standard firmware, since that's all I've used. *Spirit.OCX (I've used VB and J++): The worst way to program in the standard firmware. non-intuitive syntax (even if you (...) (24 years ago, 14-Feb-01, to lugnet.robotics.rcx)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
