[Gsoc] Python export functionality for Turtle Blocks
Marion Zepf
marion.zepf at gmail.com
Wed Apr 24 10:43:03 EDT 2013
Hi Walter,
Thank you for the tips. I now have a development version of only
TurtleBlocks running in GNOME.
I've also had a brief look at tabasics.py and talogo.py. tabasics is very
easy to understand, but I'll probably take a little longer for talogo. Can
I ask you my beginner's questions while I go through it?
As for the purpose of the project, I was wondering where the generated code
is supposed to run. Is it supposed to be self-contained, so it can be run
on other machines that don't have TurtleBlocks installed, or is it supposed
to run only in connection with TurtleBlocks? If the latter is the case,
should people include the code via the tamyblock module and the
corresponding block, or do we also need conversion from python code back to
TurtleBlock internal code?
Thank you.
Marion
2013/4/21 Walter Bender <walter.bender at gmail.com>
>
>
>
> On Sun, Apr 21, 2013 at 8:07 AM, Marion Zepf <marion.zepf at gmail.com>wrote:
>
>> Hi,
>>
>> My name is Marion Zepf and I am interested in the project 'Python export
>> functionality for Turtle Blocks'. Python is my favorite programming
>> language and I often teach programming or other computer skills to my
>> friends and family. I think it is very important to teach programming to
>> children because it is a very important skill in today's world. Children
>> are also very keen on playing around with the programming language, which
>> is very important for learning new features of it. This is why I would
>> like to make the step from block-based programming to writing code easier
>> for them.
>>
>> My Background
>> I am a student of computational linguistics in my 6th semester. I taught
>> myself Python programming before I went to university. So, I have three
>> years of experience in writing Python programs of various kinds - from
>> simple command line utilities to GUI applications (using the pygame and
>> tkinter libraries) and code generators for Java code. I also have strong
>> competence in the object oriented programming paradigm. I am new to
>> Berkeley Logo, but I learn quickly, so I expect to acquire good Logo skills
>> in a few days.
>> This will be my first contribution to the open source community.
>> However, I am familiar with commonly used frameworks and tools like
>> version control software (svn, git), Eclipse IDE, and autotools.
>> I have made myself familiar with the TurtleArt Activity in Sugar On A
>> Stick as well as in the Debian package 'turtleart'.
>>
>> Before I start writing my project proposal, I have a few questions about
>> this project:
>> (1) Which git repositories/ branches should I clone? I have found a list
>> of repositories on
>> http://wiki.sugarlabs.org/go/Development_Team/Source_Code
>> but I am not sure which ones I need and how to fit them together.
>>
>
> You can try to get a Sugar environment running [1] or just clone Turtle
> Blocks itself [2] and run it in GNOME.
>
>
>> (2) I understand that TurtleArt is written in Python, but the code that
>> users generate by putting together the blocks is in a different, internal
>> language. Is there documentation available for the syntax and semantics of
>> this language?
>>
>
> Not much to help with there. There is an OK guide to creating blocks in
> tabasic.py. The internal parser is talogo.py
>
>>
>> Thank you.
>> Marion
>>
>> _______________________________________________
>> GSoC mailing list
>> GSoC at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/gsoc
>>
>>
> regards.
>
> -walter
>
> [1] http://sugarlabs.org/~buildbot/docs/build.html
> [2] git.sugarlabs.org/turtleart
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/gsoc/attachments/20130424/e9c5fc6c/attachment.html>
More information about the GSoC
mailing list