Hi Les,

You can certainly use property change events on your widgets.

On the client side, the underlying widget is a Swing widget and you can
listen to property changes on it and pass on events to the server side if
you wish or handle it on the client side itself. When passing events to the
server side be mindful of the traffic generated.

However, remember that on a ULC Widget, properties are changed in the
Presentation logic of your server side ULC application and in the next
client initiated roundtrip these properties are uploaded to the client side
half object.

I hope this helps.

Thanks and regards,

Janak

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Les Thomas
Sent: Saturday, June 24, 2006 4:31 AM
To: [EMAIL PROTECTED]
Cc: 'Les Thomas'
Subject: [ULC-developer] PropertyChange Events and PropertyChangeSupport


Are there any known issues and/or drawback implementing widgets which make
heavy use of java beans (property change events and property change support)
for changing state, text, etc. Swing uses this under the covers, so I assume
that it is okay to use in ULC, but I didn't see anything in the
documentation (good or bad either way).

Thanks,

Les

_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer

Reply via email to