I had mentioned something about simplifying the property dialogs for
shapes a while back. Most shapes have a number of properties of a limited
number of types. If we knew the types and names of the properties of an
object, we coult create the properties dialog for it. Now to simplify
things further, when the apply button is pressed, all the object needs to
know is the new values of its properties.
This could be implemented by getting each object to implement the
following methods:
list_props -- list the names and types of all the properties of this
type of object. This would fit in the ObjectTypeOps structure, as it
is not tied to a particular instance of the object.
get_props -- get the current values of a number of named properties.
set_props -- set the current values of a number of named properties.
This would be enough to build the properties dialog, and would be a lot
simpler to implement. It could probably also be used to implement the
defaults dialog. Of course, the old methods should remain and take
precedence over these new methods (I don't think we will be able to
automatically generate the UML class object's property sheet).
This also has the benefit of being able to select a number of shapes and
getting a dialog of the intersection of their properties. This could also
be used with grouped objects.
Another use would be for programatically manipulating a diagram (ie.
scripting).
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Sat, 30 Oct 1999, Cyrille Chepelov (home) wrote:
> The next steps would be to add a property manager 'layer', in order to
> make persistency and most of dialogbox work automatic, and a way to
> encapsulate the binary-defined objects into XML-defined ones (including
> various fun stuff on properties) (see my previous message)
>
> Comments ?
>
> -- Cyrille
>
> ------------------------------------------------------------------
> Oh, my god ! I'm trapped into a V90 modem ! GPG ID: A879BEF8
>
>
