 | | Why NQC over Robolab?
|
|
Greetings All, I'm hoping that someone who is familiar with both NQC and Robolab can enlighten me. Specifically, with regard to the RCX, Scout, and microScout, what can you do in NQC that you cannot do in Robolab? Is it simply a matter of (...) (20 years ago, 6-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) I'm not very familiar with Robolab so I can't give you a direct comparison between the two. But I can say a few things about NQC that might help. With NQC you write programs in a more traditional style of programming (ala C, C++, C#, Java, (...) (20 years ago, 7-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
An IDE is an Integrated Development Environment. Basically a software suite sporting an editor with colorcoding, a built-in compiler and a debugger. Sometimes a complete reference is included too. Examples are MS Visual C++, or Borland Delphi. (...) (20 years ago, 7-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) Integrated Development Environments. Typically, an IDE consists of a compiler, a text editor, debugger, build system - all the tools a programmer needs rolled up into one huge tool. ---...--- Steve Baker ---...--- HomeEmail: (...) (20 years ago, 8-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
Hi, (...) Actually, I've only played with the Robolab demo version. First, Robolab is for working with the RCX. I saw no Scout or microscout support. The target of Robolab is the use in education, for example at schools. Robolab is related to (...) (20 years ago, 8-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) I'm actually quite familiar w/Robolab--it is NQC that I don't know much about. Robolab (2.5.x) supports The RCX, Scout, microscout, and the Control Lab Interface. It also supports the LEGO cam. I believe the demo is of a much earlier and buggy (...) (20 years ago, 8-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
What is the limitations of the demo version? It´s possible to get it downloaded somewhere? Patrick Levy "Michael Obenland" <obenland@t-online.de> escreveu na mensagem news:I8Ev9K.1DCJ@lugnet.com... (...) you (...) support. (...) Robolab (...) like (...) (20 years ago, 8-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) Robolab is an example of an IDE as well. Tom (20 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) The only version I can find is here: (URL) This version is crippled and makes Robolab seem extremely limited. I seem to remember a more complete demo of version 1.5 but I can't find it. Another option is "Robolab for LabVIEW" found here: (URL) (...) (20 years ago, 9-Dec-04, to lugnet.robotics, FTX)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) Here's a link to the "Robolab for LavVIEW" that Tom was talking about: (URL) is a ~50 MB download. This is version 2.5.2. You can download the patch (4 MB) to 2.5.3 here: (URL) tufts.edu site says that "Robolab for LabVIEW" has only been (...) (20 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) Sounds great. But I run the nqc compiler on Linux and have no COM... (...) Sometimes I dream of a BricxCC written in Java, running on Win, Linux or OSX with Control Lab and all kind of features... something like an Bricklipse... (...) Well... (...) (20 years ago, 9-Dec-04, to lugnet.robotics)
|
| |
| | Re: Why NQC over Robolab?
|
|
(...) Oops. Thanks for the correct link, John. (...) debugging the existing ones. That said, version 2.5.4 is excellent. The event bugs have been fixed as well as a ton of others. Also, more (not all) of the underlying code is unlocked. This allows (...) (20 years ago, 9-Dec-04, to lugnet.robotics)
|
