On 20.06.2016 19:58, Mark Waddingham wrote:
On 2016-06-20 16:38, Richmond wrote:
Thank you very much indeed for the comprehensive reply.
I shall deal with the children's confusion by using neither 'object'
or 'control' and
just refer to buttons, fields and so on.
I know this is dodging the
On 2016-06-20 14:48, David Bovill wrote:
Great post Mark. I'm going to keep that for my notes!
I've too tangentially related questions - mainly with regard to what it
is
better to do with widgets and with script. You say "the ability to be
able
to package up a group of controls as a black-box
On 2016-06-20 16:38, Richmond wrote:
Thank you very much indeed for the comprehensive reply.
I shall deal with the children's confusion by using neither 'object'
or 'control' and
just refer to buttons, fields and so on.
I know this is dodging the issue; but I can see no other way round it
at
Mark,
Thanks for this fantastic explanation of controls and objects and lots more.
I’m happy to learn that what I’ve always thought I understood is not far off
from reality. :) The definig of audioclips and videoclips as objects, not
controls, within the stack tree, cleared up one point of
Your students might be "the opposite of tech-savvy", but they are
neither in the 8-14 age range, nor
native Bulgarian speakers (unless there is something you're not telling
us about Utah).
R.
On 20.06.2016 18:33, Devin Asay wrote:
Yes, that’s true no doubt. But I think part of the reason it
Yes, that’s true no doubt. But I think part of the reason it hasn’t been a
confusion is because I start out by defining what an “object” is (it could just
as well be a doohickey), then asserting that control doohickies are a subset of
all doohickies, and then sticking with the same terminology
Thank you very much indeed for the comprehensive reply.
I shall deal with the children's confusion by using neither 'object' or
'control' and
just refer to buttons, fields and so on.
I know this is dodging the issue; but I can see no other way round it at
the moment.
Richmond.
On
I would like to think that there is a significant difference, Devin,
between your University
students and my small children.
The children I teach actually believe that 'objects' are things that
exist inside a computer,
rather than metaphorical abstractions drawn on a screen because we
cannot
Great post Mark. I'm going to keep that for my notes!
I've too tangentially related questions - mainly with regard to what it is
better to do with widgets and with script. You say "the ability to be able
to package up a group of controls as a black-box just like a widget would
be entirely
On 2016-06-19 09: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".
Well?
How about changing every use of the word
On 19/06/2016 15:28, Richmond wrote:
So:
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'?
All controls are
This is an interesting discussion, but I’ll admit it has never been a source of
confusion for me or my students. I announce on day 1: “Everything in LiveCode
is an object.” And then: “Controls are objects that can be placed on cards to
create a user interface.” Going forward I usually refer to
“I object!”, he protested.
“Control yourself!”, she replied.
Later they agreed, “It was just one of those things.”
Jim Lambert
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
On 19.06.2016 19:56, FlexibleLearning.com wrote:
To me the terms "control" and "object" are synonymous.
They may be synonymous to you; but all they do is cause confusion in the
"tiny minds" of 9 - 14 year old children who haven't heard about Piaget's
Formal Operational Stage, nor reached it.
To me the terms "control" and "object" are synonymous. When someone talks of
"controls" I immediately assume they come from a C+ background, whereas if
they refer to "objects" I feel more at home. On the other hand, "the number
of controls" is standard syntax and "the number of objects" throws an
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,
Or, put it another way:
Maybe I'm just grasping for a consistent way to talk about things in
Livecode
to young children . . ..
Richmond.
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
"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
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
Economy-x-Talk
Http://economy-x-talk.com
Share the
So:
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'?
Richmond.
On 19.06.2016 10:19, Richmond wrote:
I am
Mark Schonewille wrote:
In my book, I consistently distinguish objects and controls. This means
that I almost always talk about controls and very rarely about objects,
because it isn't really necessary to use objects in the LiveCode
scripting language
Sounds like a good approach, since as you
Richmond wrote:
> So there is no question of 'reserved words'; there is a simple case
> of a state of BAD confusion that needs to be sorted out, 2 words
> being used for one thing, or, rather one set of things:
>
> either:
>
> 1. Dump the word 'object' and only use 'control', or
>
> 2. Dump the
Well said, Mark!
Best, Jerry
On Jun 19, 2016, 7:23 AM -0500, Mark
Schonewille, wrote:
> Hi Richmond,
>
> The LiveCode documentation consistently talks about objects, where this
> should be controls. The scripting language, however, mixes up the two
> concepts
Hi Richmond,
The LiveCode documentation consistently talks about objects, where this
should be controls. The scripting language, however, mixes up the two
concepts completely.
An object is a collection of properties and instructions defined by a
programming syntax (where one shouldn't limit
trols"
I doubt the team would think this very important.
Craig Newman
-Original Message-
From: Richmond <richmondmathew...@gmail.com>
To: How to use LiveCode <use-livecode@lists.runrev.com>
Sent: Sun, Jun 19, 2016 6:44 am
Subject: Re: Control? Object?
If 'Object' is a
If 'Object' is a reserved word, then why is the Dictionary "we all know
and love" full of 'objects':
errorObject
focusedObject
menuObject
objectSelectionEnded
objectSelectionStarted
selectedObjectChanged
selectedObject
selectedObjects
selObj
selObjs ?
Looking up 'focusedObject' one can read:
I have the same issue :)
I started a long time ago to name handlers with the concept of "object"
rather than "control" - it was more intuitive. The word "object" has
associations for the new user which makes it easier to grasp the related
concepts of "property" and so forth. Livecode is rooted in
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".
Well?
How about changing every use of the word "Control" to "Object"?
Enhancement
28 matches
Mail list logo