prothero at earthednet.org
Sun Jun 19 11:43:01 EDT 2016
Richmond makes excellent points. I am an experienced programmer, but have often scratched my head (as a relative newby) about whether to call a livecode thingy an object, a control, or whatever.
For the future of livecode, it is vital that the dictionary, and other documentation and tutorials, somehow address issues that newbies face. I've been in groups developing a software system that is intended for wide adoption (digital library intended for educators, for example) and they study the user experience using videos and eye tracking to design the interface. Obviously, this is beyond the scope of the livecode team. But the point I want to make is that the input from folks like Richmond, who can directly observe (and more importantly, interpret) the challenges that new users experience, is extremely valuable.
So.... Thanks to Richmond for his input about the new by experience.
> On Jun 19, 2016, at 7:56 AM, Richmond <richmondmathewson at gmail.com> wrote:
> Or, put it another way:
> Maybe I'm just grasping for a consistent way to talk about things in Livecode
> to young children . . ..
>> On 19.06.2016 17:47, Richmond wrote:
>> "My goal" is to get young children interested in programming computers, and so that those
>> who have more than a passing interest generated by the classes can continue by themselves.
>> There are 3 things that have to be considered in "my goal":
>> 1. Those kids who continue rely fairly heavily on what they find in the Dictionary (which can be confusing).
>> 2. Those kids are neither native speakers of English (nor, frankly, does Bulgarian contain obvious cognates as do languages such as Vlaams, Nederlaans, Frisian, Platt-Deutsch or Doric Scots), nor is their standard of English at anywhere near a near-native like competence.
>> 3. While, with Primary-level children, an element of simplification has to take place, I have no
>> desire to dumb-down things to such an extent that those children who wish to to extend their skills
>> with Livecode (or other programming languages) are unable to owning to a mis-match between the way I have presented Livecode and what they find "out in the wild".
>>> On 19.06.2016 17:32, Mark Schonewille wrote:
>>> If your goal is to teach computer science, you really should stop calling controls objects, but if your goal is to teach LiveCode, perhaps it would be easier for them to use the word object for now.
>>> Kind regards,
>>> Mark Schonewille
>>> Share the clipboard of your computer over a local network with Clipboard Link http://clipboardlink.economy-x-talk.com
>>>> Op 19 jun. 2016 om 16:28 heeft Richmond <richmondmathewson at gmail.com> het volgende geschreven:
>>>> Should I stop using the word 'Object' for Buttons, Fields and so on while
>>>> teaching children, and make sure I refer to all of those things as 'Controls'; even if only
>>>> for the simple reason that the menus keep referring to 'Controls'?
>>>>> On 19.06.2016 10:19, Richmond wrote:
>>>>> I am currently teaching some children Livecode programming and ran into some difficulty
>>>>> on Friday when a child asked me why the menus were full of the word "Control"
>>>>> when I had been talking about "Objects".
>>>>> How about changing every use of the word "Control" to "Object"?
>>>>> Enhancement Request 17879
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode