Re: PROP_TYPE_LIST declaration

[Lars Clausen <lrclause cs uiuc edu>]

On Fri, 11 Apr 2003, Cyrille Chepelov wrote:
> Le Fri, Apr 11, 2003, Ã 01:24:52PM -0400, ashalper cox net a Ãcrit:
> > > Note that if your list is static, you may want to use PROP_TYPE_ENUM.
> > > I think it's prettier and easier to deal with (though I may end up
> > > changing the PROP_TYPE_LIST widget (or even removing it -- there's not
> > > much difference between the two, all PROP_TYPE_LIST seems to have
> > > going for it is that it uses GPtrArray)).
> >
> > It's dynamic.  Functionally quite similar to attributes in the UML
> > (although I know the UML objects still probably don't make use of
> > StdProp yet).  Should I avoid PROP_TYPE_LIST if you're considering
> > removing it?
>
> Hmmm; IIRC, I wrote PROP_TYPE_LIST, with the specific intent of using it
> as a foundation to rewriting the UML Class with it. Of course, I never
> got around to doing it, and that code has never been really tested.

So it's intended to be modifiable by the user, a la the UML things?  Adding
new lines and such isn't hard, and it could include the 'editing' widgets
(the ones under the list widget in UML) like frames do, but we'll need a
function that can convert between the string representation and the widget
representation.  Especially since I'd like the string representations to
eventually be editable directly in the diagram.

-Lars

-- 
Lars Clausen (http://shasta.cs.uiuc.edu/~lrclause)| HÃrdgrim of Numenor
"I do not agree with a word that you say, but I   |----------------------------
will defend to the death your right to say it."   | Where are we going, and
    --Evelyn Beatrice Hall paraphrasing Voltaire  | what's with the handbasket?