I really like this solution and you are right that the KISS method
applies here. I guess I have been violating the KISS edict because I
was assuming that the kids' printouts should completely reflect a
working program from start to finish. It's always better to use
myblocks or other techniques to make the programs easier to manage on
screen but there really is no need to compromise the program purely to
My only suggestion would be to have the kids make use of the NXT-G
commenting tool as much as possible. In addition to documenting program
flow for the printout, the comments also help the kids easily find
critical areas when coding.
( i.e. leave base , turn toward model , start tracking with light
sensor, activate model, return home. )
Thanks for the tip
3rd year coach
Tracie Short wrote:
> I know this was addressed earlier this week or last but our team has
> just gotten around to that part of preparation. This is our first
> using the NXT so we were worried about how to do this as well. Here
> is what we discovered worked easily for us:
> We simply highlighted about 8 or 9 blocks of a mission and went to the
> edit button, copied and then pasted the blocks into a Publisher
> document. I would imagine it would also work with Word but we liked
> Publisher as we could easily move the blocks around on the page and
> title them with Mission names.
> Hope that helps anyone else out there that may be trying to figure out
> a way to do it easily!! We really stick to the whole KISS mentality!!!
> Best of Luck to all teams who compete this weekend!!!
> Tracie Short
> Gifted Resource Teacher
> Ni River Middle School
> (540) 785-3990
To UNSUBSCRIBE or CHANGE YOUR SETTINGS, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list".
If you want to join the VADCFLL-ADMIN-L mailing list - to which FLL administrative announcements will be distributed - visit https://listserv.jmu.edu/archives/vadcfll-admin-l.html and select "Join or leave the list".