Difference between revisions of "Calico Boo"
From IPRE Wiki
Doug Blank (Talk | contribs) |
Doug Blank (Talk | contribs) |
||
Line 1: | Line 1: | ||
− | Calico (so far) uses | + | Calico (so far) uses a standard, if not older, version of Boo, so any regular Boo program should work without issue. |
− | + | ||
− | + | ||
To use a Calico module, one needs to import it (which brings the module's items into the current namespace, unlike Python which keeps the names in the Myro module namespace). Also, one must provide all of the arguments for each parameter. For example: | To use a Calico module, one needs to import it (which brings the module's items into the current namespace, unlike Python which keeps the names in the Myro module namespace). Also, one must provide all of the arguments for each parameter. For example: | ||
Line 10: | Line 8: | ||
= Introduction to Boo = | = Introduction to Boo = | ||
− | + | For an introduction to Boo, please see: | |
http://jbryankelly.files.wordpress.com/2012/07/thinksciboorev2_hb.pdf | http://jbryankelly.files.wordpress.com/2012/07/thinksciboorev2_hb.pdf |
Latest revision as of 10:26, 19 April 2014
Calico (so far) uses a standard, if not older, version of Boo, so any regular Boo program should work without issue.
To use a Calico module, one needs to import it (which brings the module's items into the current namespace, unlike Python which keeps the names in the Myro module namespace). Also, one must provide all of the arguments for each parameter. For example:
boo---> import Myro boo---> init("COM5", 38400)
Introduction to Boo
For an introduction to Boo, please see:
http://jbryankelly.files.wordpress.com/2012/07/thinksciboorev2_hb.pdf