Re: __defineGetter__

2007/4/3, Michael Platzer <[email protected]>:
>
> > The reason this doesn't work is that property inspection from macros
> > on HopObjects only supports collections and properties defined in
> > type.properties. Since first and last are not in type.properties, the
> > resolution failse. Let's think about this restriction.
> >
> Any more thoughts on this? I would say +1 for dropping this restriction.
> I never fully understood its purpose anyways.

I guess it just reflected the thinking of the time of HopObject as
cearly typed objects. I still am unsure whether having extra
properties on persistent HopObjects is good design.

I'd like to hear more opinions on this, specifically regarding
exposure of non-defined properties to skins.

hannes