Frank Schönheit - Sun Microsystems Germany wrote:
Hi Malte,
I disagree with doing "selected" enhancements in single css.awt interfaces.
...
If people agree on incompatible changes, I would prefer to clean up all
css.awt API and add missing get- methods.
I wouldn't start to do it "here and there" when somebody stumbles over
it. And the next change, and one change again, one more, ...
Somebody already started this with XWindow2 ....
exactly and the questions is why not. It's better to do simply start and
do it step by step than waiting on the big shot. And the argument with
the oneway calls is obsolete anyway.
Well, as I see it, we have two choices:
1. Add some little more ugliness by introducing XView2.
Hope that we'll find the time to do the "big cleanup". If so, XView2
will be dead then, and have added a little more to the
already-big-enough pile of legacy API.
2. Change XView now and here, not introducing new legacy API, not adding
to API ugliness, not waiting for some future redeemer giving us all
the resources to do the big cleanup.
At the cost of introducing a (minor, as I tried to outline)
incompatibility.
Well, yes, my wording was a little bit tendentious, but really, I prefer
2. over 1.
me too. The "big cleanup" should maybe end in a completely new toolkit
(at least from my perspective). We learned a lot since the beginning and
probably a new toolkit would result in a cleaner, more intuitive and
better to use APIs. Talk with people who try to implement new controls...
But as long as we see no clear signal to do it or as long as we don't
see a real investigation in this direction we should try to improve the
stuff we already have step by step.
Juergen
Ciao
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
