|
#101
|
|||
|
|||
|
SmartGWT Pro/EE 2.0 has been released. Download the evaluation here.
New client-side features are described here. |
|
#102
|
|||
|
|||
|
so, I download the EE Eval version, started up the embedded server, and opened the browser, found the IDE.. and bummer. the ONE thing I wanted to see is not in the components, dynamic data bound tree.
Sam |
|
#103
|
|||
|
|||
|
It's not particularly hard to find the complete running sample with source.
|
|
#104
|
|||
|
|||
|
Quote:
Quote:
DataSource.getBeanClassName() seems to be related. Is this the intended use of it? Where can I find an example of it? |
|
#105
|
|||
|
|||
|
The best place to look for an explanation of the Flyweight design pattern is probably the original "Gang of Four" Design Patterns book, and/or the many web sites recapitulating that content.
Due to the lack of Java reflection in GWT, to convert a Record into an instance of some custom bean, there's nothing you can do but retrieve each attribute via record.getAttribute() and call each setter method (eg setName()) manually. This is why we recommend the Flyweight pattern being used with the Record class. There is very very little business logic that can meaningfully run either client or server-side, and most of it is already captured in the Validator system. We see a lot of people get very excited by the idea of a single Bean class that exists both client and server side, and then spend a spectacular amount of effort trying to somehow separate out the server-side business logic that they naturally want to attach to the bean but which can't be added there if they want the bean to go through the GWT compiler. Two months of tricky Java dependency management later they have "solved" the problem and managed to factor a bean with 2 methods (yes only 2) so that they run either client or server. But another team that chose not to tilt at this particular windmill just made equivalent static methods, with no dependencies on a particular bean and which go through the GWT compiler with no issues, and never wasted those two months. |
|
#106
|
|||
|
|||
|
I see. Thank you for sharing this experience. One more question: what is the intended usage of DataSource.getBeanClassName() ?
|
|
#108
|
|||
|
|||
|
Hi,
it seems like the expiration for the Smart GWT EE is hard coded to Feb 16th or something around there, regardless of when the SDK was downloaded. cowper |
|
#109
|
|||
|
|||
|
Hi,
after the purchase of SmartGWT license PRO, i can't understand how to download the package of SmartGWT EE. I need to use only SmartGWT EE Pro license but, after regular payment, on your site there's only instructions to download SmartClient Pro (and not for SmartGWT). Please give me a feedback ASAP, because next week i will to show a software demo and actually it appears a message related the end of trial period (60 days). Thank you and excuse me for my bad english Mariella |
|
#110
|
|||
|
|||
|
SmartGWT EE 2.1 has been released
New server features:
New client-side features An overview of several major new client-side features, which are also available in SmartGWT LGPL, has been posted here: http://www.jroller.com/sjivan/entry/...t_2_1_released .. some key ones which were not mentioned:
The new evaluation is available here: http://smartclient.com/releases/smar...tgwtee-2.1.zip License holders will be receiving emails with links to download licensed versions shortly. |