[gwt-contrib] Re: Flurry of Data binding threads

Thera are another project that implement data binding using reflection. http://code.google.com/p/gwt-model/ I think that the reflection way is the more clean solution. Regards. On Nov 18, 1:53 am, Rogerio <[EMAIL PROTECTED]> wrote: > Hello all, > > I have a few ideas/requirements for a GWT dat

[gwt-contrib] Re: Flurry of Data binding threads

Hello all, I have a few ideas/requirements for a GWT data binding API. Such a solution would hopefully allow for a reduction of literally tens of thousands of lines of Java code that we currently have to write and maintain for manual data management, in the large web app I currently help develop

[gwt-contrib] Re: Flurry of Data binding threads

On Mon, Nov 17, 2008 at 6:11 AM, Arthur Kalmenson <[EMAIL PROTECTED]>wrote: > > Hello Rahul, > > Here's some of the projects: > > gwt-data-binding: http://code.google.com/p/gwt-data-binding/ > gwt-validation : > http://code.google.com/p/gwt

[gwt-contrib] Re: Flurry of Data binding threads

Hello Rahul, Here's some of the projects: gwt-data-binding: http://code.google.com/p/gwt-data-binding/ gwt-validation: http://code.google.com/p/gwt-validation/ I'm working on visibility logic as we speak, I'll make a post when I get the chance. I am also wondering what the status of the GWT te

[gwt-contrib] Re: Flurry of Data binding threads

Hello Emily, > > *Metadata Systems, comprising Models and Controllers* > xforms, Ian's databinding system, Arthur's validation system, gwt team's > upcoming proposal for data management: Do you have links to the above resources please, where we could find more details/sources? Also, you mention

[gwt-contrib] Re: Flurry of Data binding threads

Absolutely. I think we may be vehemently agreeing with each other here. On Thu, Oct 9, 2008 at 5:45 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote: > That is true, as the answer "never" is certainly too simplistic. > > The point is that the primary use case of HasValue is not to bind data > object

[gwt-contrib] Re: Flurry of Data binding threads

That is true, as the answer "never" is certainly too simplistic. The point is that the primary use case of HasValue is not to bind data objects to widgets, but to allow widgets to provide an easy to use interface for other systems. As the data binder should not have to care what the physical wid

[gwt-contrib] Re: Flurry of Data binding threads

There may be cases where this is permissible. For example, a MapWidget might return LatLng objects, rather than having a Long and Lat field which are separately bound. In the context of OpenSocial or GData, I could see a common reusable widget for picking from your network that would naturally re

[gwt-contrib] Re: Flurry of Data binding threads

Would you normally have a UI widget as specific as a person picker? That seems like the model (a person) and the widget displaying the person might be a bit too closely bound, and we'd rather that binding took place using some sort of data binding solution. The reason for this distinction is to m

[gwt-contrib] Re: Flurry of Data binding threads

Going to stick my nose in here a bit: I certainly believe that this is all one ball of wax. I /know/ that the system that I've been working on can be used to modify the data. I know it breaks the JSR-303 paradigm so I've left it alone. The fundamental difference is that I'm expecting some outpu

[gwt-contrib] Re: Flurry of Data binding threads

To give you an idea of where I am coming from, here is my understanding of the world: *Metadata Systems, comprising Models and Controllers* xforms, Ian's databinding system, Arthur's validation system, gwt team's upcoming proposal for data management: All part of the larger metadata, binding, cod

[gwt-contrib] Re: Flurry of Data binding threads

There appears to be the following overlapping/complimentary items being worked on by various people: 1) compile time UI Template markup language proposal (status?) 2) JSR 303 Bean validation annotation stuff 3) HasData/HasValue consistent interface proposal for GWT widgets 4) Data Binding (variou

[gwt-contrib] Re: Flurry of Data binding threads

Sounds good to me, a solution that fits seamlessly with GWT would be very nice. Will you be posting a design document about it? Will this all tie into some form component for GWT? Will you include other useful features like visibility logic? Best regards, Arthur Kalmenson On Oct 8, 10:15 am, "R