| |
In lugnet.robotics, Brian Davis wrote:
>
> It's not there. Conclusions may now be drawn :).
>
> Nor has anybody come along and made a reasonable "graphic description language"
> that translates a chunk of NXT-G into something like C or pseudocode.
Obviously, NI is so confident they've reached their design goal: that every 9
year old should be able to program in NXT-G without calling tech support.
In my classes, 9 and 10 year olds blow through such a low level of expectation
within an hour of two of completing Tribot or Spike. Then what?
IMO, any ambitious program could use a print to text option to help in
debugging. I therefore conclude that NI suffers from myopia or that they haven't
been paid enough for it.
|
|
Message has 1 Reply:
 | | Re: NXT-G print to text?
|
| (...) <grin>. I said "conclusions may now be drawn", not "all conclusions are equally likely to be correct". You seem to be assuming that NI is stupid or overconfident. I'm pretty sure that's not the case. When there's something I don't understand (...) (16 years ago, 19-Jul-08, to lugnet.robotics)
|
Message is in Reply To:
| | Re: NXT-G print to text?
|
| (...) I agree, which is why I suggested using NXT-G's print option - it will allow you to check "show hidden structures" or somesuch that will show you all the hidden structures in tabbed view mode. (...) Well, let me put it this way. A text version (...) (16 years ago, 18-Jul-08, to lugnet.robotics)
|
13 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
