Hi, > this is the demo behavior or vaadin behavior which every widget will > need to retrieve some data from server?
It depends, as is often the case... Vaadin is "server-driven", so most components communicate with the server _at some point_. But: - There is the concept of immediateness: e.g. if you have a bunch of non-immediate textfields, nothing will be sent until you press the "save" button (that would obviously be immediate). Almost all of the demos are immediate and provide some extra feedback, for the sake of the demo, so it will almost always send some extra stuff back and forth. Otherwise, if the state was just pushed to the server but nothing changed, only a short acknowledgement message will be returned. - You _can_ make customized client-side composites and components that communicate with each other but not with the server - this is done in plain GWT. But the main benefit with Vaadin is the server integration, so usually you would only do this if you have some very specific needs. I hope this cleared things up a little. I would recommend trying it out to see what I'm actually talking about; a small example with some buttons and textfields is really easy to make, especially with eclipse and the vaadin plugin. Anyway, questions are always welcome. Best Regards, Marc -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
