[Sugar-devel] [IAEP] Lego WeDo + TurtleArt - Screenshot & Code!

[Sean DALY]

Hi Ian,

I have purchased a Wedo kit and installed the latest version of Turtle
Blocks-107, just one question: you mention a "usb" folder but at the
link below I only saw a "udev" folder, is that the one you mean?

Also is the best way to copy these files with the command line? Do I
need to set any permissions?

thanks

Sean


On Thu, Mar 10, 2011 at 3:19 AM, Ian Daniher <it.daniher at gmail.com> wrote:
> Hi All!
> I'm writing with good news. I successfully have integrated the Lego WeDo
> with TurtleArt.
> Here's a screenshot: http://itdnhr.com/static/WeDoScreen.png
> The code needed can be found in my git repo
> at https://github.com/itdaniher/WeDoMore/.
> TurtleArt specific files can be found
> at https://github.com/itdaniher/WeDoMore/tree/master/TurtleArt.
> The svg files go in the "icons" folder.
> The "usb" folder goes in the root of the TurtleArt directory.
> The file "wedo_plugin.py" goes in the plugins folder in the TurtleArt
> directory.
> The folder "WeDoMore" goes in the root of the TurtleArt directory.
> This project is not ready for primetime yet. The only semipolished code is
> the actual Python WeDoMore library. Anything and everything in my repo that
> is related to turtleart should be considered 'alpha,' that is, may cause
> your computer to spontaneously burst into flames. That being said, it works
> perfectly for me, and I could definitely use testers.
> If you feel like giving it a go, and if you find any bugs, please report
> them at https://github.com/itdaniher/WeDoMore/issues.
> Best wishes and many thanks,
> --
> Ian
> On Wed, Mar 9, 2011 at 13:17, Martin Langhoff <martin.langhoff at gmail.com>
> wrote:
>>
>> Hi Ian!
>>
>> great to have you around! I am interested in your work with WeDo, both
>> the python plugin, and the TA integration.
>>
>> For the NXT integration, the parts are
>>
>> 1 - an rpm that has the udev rules
>> 2 - an rpm with nxt_python (python library, some utilities)
>> 3 - a TA plugin
>>
>> In your case, we'll probably want to use the same model for packaging.
>> The rpm with the udev rules already has rules for wedo. Once your
>> library code is ready for release, let me know and I'll look into
>> making an rpm.
>>
>> For the TA plugin it may be a good idea to share notes with Emiliano
>> -- he's doing the NXT stuff. The TA plugin will probably be shipped
>> with TA once ready.
>>
>> If you can keep those tiers separate, it will be a big win. Have you
>> seen the nxt_python library API? If yours is reasonably close you
>> might save some effort.
>>
>>
>>
>> m
>> --
>>  martin.langhoff at gmail.com
>>  martin at laptop.org -- Software Architect - OLPC
>>  - ask interesting questions
>>  - don't get distracted with shiny stuff  - working code first
>>  - http://wiki.laptop.org/go/User:Martinlanghoff
>
>
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>