undocumented commands

8 views
Skip to first unread message

pam

unread,
Jun 7, 2009, 4:05:58 PM6/7/09
to KTurtle; an educational programming environment
how to find out the meaning of undocumented commands found in
logokeywords file?
(in, spritepress, spritechange,...)
i'm using KTurtle 0.6.

cies

unread,
Jun 8, 2009, 1:47:49 PM6/8/09
to kdeedu-...@googlegroups.com
i would say it is better not to use these commands.

to be honest i wouldnt know if they actually do something (in 0.6).


currently we're working towards a 1.0 release, from 1.0 we do not want
to change the language (except maybe for 2.0).
part of that is to make a language specification in terms of a
unittest suite -- im currently working on that. this will make sure
the language is stable, consistent over different releases.


hope it answers your question.

thanks for your feedback and for using kturtle!

_cies.

pam

unread,
Jun 8, 2009, 5:09:09 PM6/8/09
to KTurtle; an educational programming environment
thanks cies,
for the quick response.
Just for background information: which programming language do you use
for kturtle?
And: are the sources available?

BR pam

P.S.: my little son (13) is "playing" with the turtle - and he enjoys
it!
I hope this will enforce his interrests in programming computers...

P.P.S.: I tried to use the shortcut "sc" with an additional number -
and this turned the turtle.
next I read the manual, but I found no hint on this command.
The translation file showed an existing command.
Further I tried to copy & past a part of code from the handbook
section Commands: "in = inputwindow "What is you age?"
This didn't work because in can not be used as a variable - it seems
to be a token (it's also syntax highlighted in green).
This is the story behind my initial question... ;-)


On Jun 8, 7:47 pm, cies <cies.bre...@gmail.com> wrote:
> i would say it is better not to use these commands.
>
> to be honest i wouldnt know if they actually do something (in 0.6).
>
> currently we're working towards a 1.0 release, from 1.0 we do not want
> to change the language (except maybe for 2.0).
> part of that is to make a language specification in terms of a
> unittest suite -- im currently working on that. this will make sure
> the language is stable, consistent over different releases.
>
> hope it answers your question.
>
> thanks for your feedback and for using kturtle!
>
> _cies.
>

cies

unread,
Jun 8, 2009, 10:25:28 PM6/8/09
to kdeedu-...@googlegroups.com
> Just for background information: which programming language do you use
> for kturtle?

kturtle is written in C++, some of the C++ code is generated by some
Ruby scripts.


> And: are the sources available?

naturally.. KTurtle is "Free Software" under the definition of the
fsf.org. the license is GPL, which sais i have to provide the
sourcecodes. i happily comply :)

here you can browse the code:
http://websvn.kde.org/trunk/KDE/kdeedu/kturtle

have a look at the techbase.kde.org for more info on doing things with
that code.


> P.S.: my little son (13) is "playing" with the turtle - and he enjoys
> it!
> I hope this will enforce his interrests in programming computers...

wow.. good to hear :)

> P.P.S.: I tried to use the shortcut "sc" with an additional number -
> and this turned the turtle.
> next I read the manual, but I found no hint on this command.
> The translation file showed an existing command.
> Further I tried to copy & past a part of code from the handbook
> section Commands: "in = inputwindow "What is you age?"
> This didn't work because in can not be used as a variable - it seems
> to be a token (it's also syntax highlighted in green).
> This is the story behind my initial question... ;-)

i just tested this with the latest version of kturtle. the commands
and the syntax slightly changed for the version that ships with kde4.
but the inputwindow works as expected, and when a number is given it
is casted into a number variabel (not a string).



thanks for the feedback!
_c.
Reply all
Reply to author
Forward
0 new messages