Well I am not willing to just give this as an answer, because I don't
feel it is a $100 answer... In fact I don't feel it is a $100
question... You might consider lowering your price to something around
$20... Just my opinion tho... :)
I have never worked with nqc before, but I am a computer scientist,
and here are my thoughts on this type of thing: Becomming proficient
in any 1 programming language in ~24h is possible if you already know
3 or 4 programming languages that are similar. In other words if you
know C really well and maybe C++ or something else (perl, pascal,
whatever), then getting nqc down shouldn't take very long at all... If
your programming expirence is at the "Well I have modified some source
code before" level then getting nqc may take longer than 24h... But
still possible... :)
I would start with the "Not Quite C" home page:
http://www.baumfamily.org/nqc/
Read the faq, and get the programmers guide, from this page:
"nqc information"
http://www.baumfamily.org/nqc/doc/index.html
Then I would checkout the mini-lessons, which don't seem to be too
informative, but rather illustrate traps that a newcomer might fall
into:
"Mini-lessons"
http://www.baumfamily.org/nqc/lessons/index.html
Then download the nqc compiler from this page:
"nqc current version"
http://www.baumfamily.org/nqc/release/index.html
I am not sure what platform you are running, but they only support Mac
and Windows, in binary form, they do have the source available if you
are a linux man, but that might be a lot of work compiling the
compiler... :)
I would then recommend getting some of the sample code from this page:
"nqc samples"
http://www.baumfamily.org/nqc/samples/index.html
And open it up in a text editor and try and figure it out... I suggest
the bumpseeker.nqc, because it is pretty short, and it tells you what
components you need in the robot. Then I would just go from there,
through other samples, until you get an understanding of what will do
what. At that point it will be time to start writing your own nqc
programs...
Hope this helps
--jld |
