sorry it has been a while before replying to your last message, I have
been using the program a bit more to gather some more thoughts
firstly, these commands do not work on my Linux (Mandriva 2010);
wrapon
wrapoff
hide (but sh does)
show (but ss does)
inputwindow
on trying to use kTurtle I had these problems/frustrations;
the syntax for building procedures was not valid for my Linux - ie the
handbook shows these brackets [], but I have to use these {}
(however the screenshot examples in the handbook do show {} being
used)
a variable on my Linux needs $ before it, this is not mentioned in the
handbook
there is no mention of error messages or how to deal with them
I feel these discrepancies could frustrate a new user (a child for
example) and they could then dismiss the program at the first hurdle
possible developments;
a tutorial approach to learning the program's basics using simple
shapes eg lines, lines at an angle, draw triangle, square,then
progress to building procedures using the learn command, projects to
carry out that will teach the programming language in easy steps (the
handbook does do this, but not with enough simple illustrated steps,
maybe this would be good on a website or tutorials that can be
downloaded)
an easily accessible list of logo primitives, definition of use and
their abbreviations
ability to save and load procedures (at the moment a whole turtle file
has to be loaded containing all procedures needed for a partucular
session)
fill shapes with colour
ability to run commands consequentially as they are typed in, not
whole editor contents from beginning
guide on error codes for debugging
these are my initial thoughts, I am really pleased to have found a
good Logo version for Linux, as a teacher I have used Logo from its
manifestation on BBC computers back in the 1980s(!) with primary
school children, if you feel I could help with development of kTurtle
I would be happy to do so (I am not tecnically able, but experienced
in using programs and possibly devising projects and tutorials so that
others can use the program and learn the basics of logical thought,
planning, editing and testing)
best regards
Steve Redshaw
On 8 Dec, 04:31, cies <cies.bre...@gmail.com> wrote:
> On Fri, Dec 4, 2009 at 1:37 PM, steve_redshaw
>
great..
> firstly, these commands do not work on my Linux (Mandriva 2010);
>
> wrapon
> wrapoff
intended. we do not have wrapping anymore in kturtle starting with kde4.
> hide (but sh does) -> spritehide
> show (but ss does) -> spriteshow
> inputwindow -> ask
hmmm.. interesting. these commands have changed (see my arrows).
do you use the german handbook for kturtle? or do you use an old one?
please use a new kturtle and handbook.
> on trying to use kTurtle I had these problems/frustrations;
>
> the syntax for building procedures was not valid for my Linux - ie the
> handbook shows these brackets [], but I have to use these {}
> (however the screenshot examples in the handbook do show {} being
> used)
> a variable on my Linux needs $ before it, this is not mentioned in the
> handbook
you use a different manual than me im afraid.
please refer to this one:
http://docs.kde.org/stable/en/kdeedu/kturtle
http://docs.kde.org/stable/en/kdeedu/kturtle/commands.html
> there is no mention of error messages or how to deal with them
>
> I feel these discrepancies could frustrate a new user (a child for
> example) and they could then dismiss the program at the first hurdle
what would you suggest here? please elaborate...
> possible developments;
>
> a tutorial approach to learning the program's basics using simple
> shapes eg lines, lines at an angle, draw triangle, square,then
> progress to building procedures using the learn command, projects to
> carry out that will teach the programming language in easy steps (the
> handbook does do this, but not with enough simple illustrated steps,
> maybe this would be good on a website or tutorials that can be
> downloaded)
a tutorial would be a welcome addition. i doesnt have to be in the
handbook. anyone can publish this in any format :).
> an easily accessible list of logo primitives, definition of use and
> their abbreviations
see link mentioned earlier.
> ability to save and load procedures (at the moment a whole turtle file
> has to be loaded containing all procedures needed for a partucular
> session)
file -> save :)
> fill shapes with colour
impossible.
> ability to run commands consequentially as they are typed in, not
> whole editor contents from beginning
in the toolbar is a single command console. works much like you describe.
otherwise use the step-by-step run mode.
> guide on error codes for debugging
error codes are merely for reference of the developers.
> these are my initial thoughts, I am really pleased to have found a
> good Logo version for Linux, as a teacher I have used Logo from its
> manifestation on BBC computers back in the 1980s(!) with primary
> school children, if you feel I could help with development of kTurtle
> I would be happy to do so (I am not tecnically able, but experienced
> in using programs and possibly devising projects and tutorials so that
> others can use the program and learn the basics of logical thought,
> planning, editing and testing)
please do not call kturtle logo. we're not pretending to be logo any more :)
we're a educatinoal programming environment. (also on windows and mac)
im glad you like it!
kindly,
_cies.
i dont know. my kununtu does not suffer from this problem, maybe a
problem with mandriva.
> I have looked at the online manual from your link and it answers most of my
> problems and frustrations!!
good. im glad to hear.
> I cannot however get a later version through my
> software updater - as a fairly new Linux user I am still floundering with
> terminals and commands and building an application seems quite a challenge,
> however I have looked at the instructions and will try it out if this gives
> me the latest version
try some mandriva related sources. maybe raise this issue on a mailing
list ("old documentation for kturtle in m2010")
> should be able to contribute some simple projects too in the not too distant
> future
great!
> just to elaborate on the loading/saving of procedures (by this I mean
> commands defined by the user with the learn primitive);
>
> perhaps importing and exporting procedures would be a better term
>
> at the moment (if I understand things correctly), the program operates from
> one turtle script that is displayed in the editor, if a new script is loaded
> the program forgets any previous commands and procedures - it would be a
> useful feature I think if single procedures or groups of procedures could be
> imported into a session, they would not have to be displayed in the editor,
> but the commands (that the imported procedures had defined) would be
> available to use in the current session
>
> if a session was then saved it would perhaps then include the procedures
> that had been added or maybe link to the files containing the imported
> procedures
>
> also if procedures were able to be exported separate to the current session
> they could be used in other sessions without having to redefine them within
> the current session
>
> eg I have defined a procedure that draws a square, I export (save) this
> procedure (just the script with the instructions for drawing a square), in
> another session I need to draw a square (or several), so I import (load)
> that procedure and it is then available to me as a command that I can simply
> type in
i understand what you mean. but from my respective your suggestion
would need a lot of code added to kturtle.
what is the point? i having scripts that draw various things by
"learned" functions, and using copy/paste will do. we have decided
against an 'include' statement -- keeping it simple is most important.
doing things with a gui that have clear analogues in in programming
(with code) are not what we want either: we van to make programming
simple, but not to the extend that it becomes a clicking exercise. :)
kindly,
_cies.