Re: [LogoForum] Further development on MSWLogo

The message below is being cross-posted from LogoForum.

This is a fascinating thread- but I leave on a email vacation tomorrow!

Brian.
PLM- I wish I had found it myself I would look less stupid.  PLM was I
thought a variant of PL/1 but I was not up on IBM speak we used to think
that Atlas autocode would rule the earth and HBM was a latecomer- we
were patriotic in Manchester.
Wikipedia doesn't recognise PLM either- someone needs to write an entry.

The existance of PLM really helps to read the UCB code, I was being
polite about lack of comment statements- I understand the philosophy and
it works for core code.With my code I could make the same statement, but
with my younger students I need every assistance to to unerstand what
they meant.
It is the IO routines, and the Windows bits that I find more difficult
as logic 'as we know it' has to be abandonned when dealing with
Redmondware , I would need them if I nried to port them to X and
Linux/OS GUIs.

Daniel
8 bit does rule out East Asian languages which will need to be
addressed. However, half is better than nothing, from my point of view
everything I do should be acccessible in all EU states (including Poland
with their difficult s ). that also includes Russian and Greek.

Gene.
How also about a intelligent Logo that detects the language of the user
from the source code. A child that types LINKS90 will be recognised as
using German keywords, while one who types ESQUERDA90 will be using
Portuguese. (I like the idea of Logo self correcting elementary mistakes
DWIM)

David.
No, not just Western European- Eastern European is required. Dates and
times are very important- particular with youngsters the fourteens of
July is 14.07.2005 in English lessons, in exercise books so 'why must we
do it differently in Computing'. Another bugbear is where North American
spelling diverges from European English. I always have to say "BGCOLOR-
remember to include the deliberate spelling mistake". Both spellings of
the keyword should be acceptable for important primitives. The other
words that the English department has fought to teach is ' licence' the
noun and 'to license' the verb there are a couple of others with this
pattern, and finally 'internationalisation' jumps out of the page when
it is written with a 'z'.
All hard coded strings should be in a external table- it is an urban
myth that german words are necessarily longer- as Abk.s (Abkurzungen)
are perfectly akzeptabel (annehmbar).  I have forgotten the French
command set but believe it  they use AV for forward, AR for back, TD and
TG for  turn Right and Left, as LOGO commands are traditionnnally done
in uppercase accents are not a used. This will not apply in Polish,
where I suspect accents will be needed.
You dont translate the 700 page work of art, you allow each language to
default to the English doc, if no local translation is found. As I said
before, the first person to demand LOGO in a particular language  will
have to used LOGO in English first before (s)he could understand LOGO's
advantages- they are thus the idea person to  undertake the translation
of the fixed text strings and primitives and to apply to their
government for a grant to get it officially translated..

Control codes.
Howabout  Ctrl Y and Ctrl Z for Undo and Redo. Some folk may prefer
other keyboard bindings - its not an issue for me.
DWIM yes please, ideally I like to see fd100 changed on entering cr
giving a audible sound,  with experience users will automatically change
to the correct syntax, when they internalise the concept of a keyword
taking an argument/parameter.


If I can be of assistance in September, feel free to ask.
Clem


LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum

.

Relevant Pages
Loading