RE: [platform-swt-dev] Re: FW: SWT History and Design Decisions ( WAS: [

[Scott Stanchfield <scott@xxxxxxxxxxxx>]

Joe mentioned it briefly, but I think it really needs to be abstracted a
tad. The JavaBean event model is one implementation of Observer, and SWT
uses a slightly different one.

And I'd like to see a bit more "smarts" available, esp when it comes to
validation. The Beans spec just plain missed when it comes to
constrained properties. Interesting concept, but I think it falls flat
on its face in practice. I'd like to see some extensions to BeanInfo
that would help specify property value constraints, which a builder
could use to pick "smarter" fields (masked fields in 1.4, for example)
and/or attach validations to perform the constraint checks.

Of course there are other things to work on there...

Should we start a page at the Eclipse Wiki to capture BeanInfo, mark 2?
It could be the start of a new JSR... Sounds like we've got some folks
who could really think the problem through well, and I'm happy to play
with design ideas in my builder to see what happens. Heck, I'm dealing
with BeanInfo anyway, so I'm a good chunk of the way there ;)  You
should see what I'm having to do for property editors... (I'm sure Joe's
well aware, heh heh heh ;)

-- Scott

> -----Original Message-----
> From: platform-swt-dev-admin@xxxxxxxxxxx
> [mailto:platform-swt-dev-admin@xxxxxxxxxxx]On Behalf Of Bob Foster
> Sent: Friday, January 24, 2003 8:35 AM
> To: platform-swt-dev@xxxxxxxxxxx
> Subject: Re: [platform-swt-dev] Re: FW: SWT History and
> Design Decisions
> ( WAS: [platform-swt-dev] AWT Toolkit using SWT (was: From Swing to
> SWT))
>
>
> I agree with Joe.
>
> Let's not forget that the info that can be got must include
> event listeners.
>
> Bob