No registered users in community xowiki
in last 10 minutes
in last 10 minutes
Re: [Xotcl] NX nested objects
From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Sat, 22 Jan 2011 10:22:55 +0100
Technically, "slot" is a child object, which is not easy to
hide from the
application developer (otherwise, slot handling will break).
An option
could be to store the slot objects at a different place, but
this would
involve more complications on renaming, cleanup, etc. Not sure,
we can address that before our release in the not to far future.
Using "info lookup method|methods|..." is used for obtaining
information about the closure of local and inherited items from
the standpoint of an object. Questions like "what methods
can i call?", "where is the method defined, i am calling?", etc.
So hiding "slot" on "info children" and showing it on "...
lookup ..."
is not an option.
"info children" has already an option "-type" that can be
used to filter
the result. Is this an option for you?
-gustaf neumann
On 21.01.11 23:52, Victor Mayevski wrote:
> Hello Gustaf,
>
> After adding attributes to an object, and creating nested objects
> within it, I need to list those nested objects. When I do [myobject
> info children], "::myobject::slot" is listed among other nested
> objects that I created. Since my code did not specifically create the
> "slot" object (it is an artifact of creating attributes), it seems
> that it should not be listed along with my scripted objects, perhaps
> [myobject info lookup children] is a better place to list the "slot"
> object?
>
> Thanks,
>
> Victor
Date: Sat, 22 Jan 2011 10:22:55 +0100
Technically, "slot" is a child object, which is not easy to
hide from the
application developer (otherwise, slot handling will break).
An option
could be to store the slot objects at a different place, but
this would
involve more complications on renaming, cleanup, etc. Not sure,
we can address that before our release in the not to far future.
Using "info lookup method|methods|..." is used for obtaining
information about the closure of local and inherited items from
the standpoint of an object. Questions like "what methods
can i call?", "where is the method defined, i am calling?", etc.
So hiding "slot" on "info children" and showing it on "...
lookup ..."
is not an option.
"info children" has already an option "-type" that can be
used to filter
the result. Is this an option for you?
-gustaf neumann
On 21.01.11 23:52, Victor Mayevski wrote:
> Hello Gustaf,
>
> After adding attributes to an object, and creating nested objects
> within it, I need to list those nested objects. When I do [myobject
> info children], "::myobject::slot" is listed among other nested
> objects that I created. Since my code did not specifically create the
> "slot" object (it is an artifact of creating attributes), it seems
> that it should not be listed along with my scripted objects, perhaps
> [myobject info lookup children] is a better place to list the "slot"
> object?
>
> Thanks,
>
> Victor