[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: AW: [riena-dev] Ridgets
|
Scott,
Yes there are examples of using validations and conversions in
riena.example.client and I believe there are also JUnit tests in
riena.tests. However its quite early and we are currently have a
discussion about how to implement validations and conversions (as you
see in this other thread in riena-dev). So it might that a complete
implementation will take some more time.
I am not sure that I am understanding the point of your questions
about in general.
We decided to introduce Ridgets into Riena for a number of reasons
that we already wrote about that we believe it supplies great value
for enterprise smart client applications. Some of the concepts are
already known in Eclipse like databinding (and we of course use them)
and there are others like Marker support that we couldnt find any
implementation in Eclipse.
Is your point that you see no value in Ridgets and wouldnt use it ?
Is your point that we shouldnt been allowed to have a concept like
Ridgets ?
Maybe you can help me to understand what you dont like about
Ridgets......
With easy access to databinding I meant nothing more than an easy
access to the existing databinding that is used interenally. But thats
not the only added value of Ridgets.
christian
Am 17.06.2008 um 20:35 schrieb Scott Lewis:
Hi Christian,
Christian Campo wrote:
Hi Scott,
1) as carsten wrote, Ridgets are an abstraction from the Widget of
the used UI-Toolkit and they offer additional functionality like
marker support and they offer easy access to databinding as well as
support for validation of widgets and conversion (from widget to
model). so its just way more than databinding by itself
I don't understand this. What exactly do you mean by 'validation
and conversion (from widget to model)'? Is there a use case or
code example/test that shows the value of this?
And what is meant by 'easy access to databinding'? A new API for
databinding? Changes to databinding?
2) They are part of Riena because they are part of the different
"process-orientiented user-interface" as noted here http://www.eclipse.org/proposals/riena/
This part of things seems to me to be more closely related to the
JWT project than it is the stated primary purpose of Riena
(transparent RPC).
Scott
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
