Francis Burton
2010-03-16 14:03:19 UTC
Hi,
I thought it might be neat to use run-time type information (RTTI) to
display and set properties of objects that serve as storage for data
and as a way of grouping the data logically (like records, except that
record types can't participate in RTTI). The display and setting would
be done via a property editor just the one in the IDE. I have looked
for a component that can do property editing at run-time, but haven't
found anything yet. Which leads me to think that either my idea is too
esoteric or there is a serious flaw with it that I haven't realized.
My intention is to use this mechanism/component to allow users to edit
properties of graphical "objects" (in addition to direct manipulation).
These entities wouldn't necessarily be encapsulated in the objects that
were edited by the property editor - but I suppose they could be.
Is this such a crazy idea? Has anyone implemented such a component?
Francis
I thought it might be neat to use run-time type information (RTTI) to
display and set properties of objects that serve as storage for data
and as a way of grouping the data logically (like records, except that
record types can't participate in RTTI). The display and setting would
be done via a property editor just the one in the IDE. I have looked
for a component that can do property editing at run-time, but haven't
found anything yet. Which leads me to think that either my idea is too
esoteric or there is a serious flaw with it that I haven't realized.
My intention is to use this mechanism/component to allow users to edit
properties of graphical "objects" (in addition to direct manipulation).
These entities wouldn't necessarily be encapsulated in the objects that
were edited by the property editor - but I suppose they could be.
Is this such a crazy idea? Has anyone implemented such a component?
Francis