I found pure gwt developer guide, documentation and community forum is
quite helpful, for GXT, I try to learn but there is no any tutorial like
the stockwatch program, and no developer guide, the forum has poor
response..., so I really do not know how to start with GXT although its UI
is very
I would recommend to go with GWT for your requirement, for WSDL just go
with GWT-RPC and from RPC server/servlet connect to WSDL.
point here is there has been a continuous improvement/enhancement on GWT
since last 2 year.
Best regrads,
Saida.
On Wed, Oct 31, 2012 at 12:07 PM, tong123123
I've seen in the past many comments and different opinions about
Vaadin, GXT, SmartGWT and GWT-only apps. I think the fundamental
thing to remember here is resources.
If you work for a company where you can afford to have the designer/s,
a CSS savy person/s and the time to build and enhance more
Also, besides Joseph said (it is true in my case), there is a fundamental
difference and it is that vaadin, smartGWT, etc uses an architecture where
they depend on server side stuff. For example, all vaading Java code runs
in the serverside, and the webapp is rendered 100% on the serverside.
Smart GWT runs on the client.
2012/10/30 Sebastián Gurin sebastigu...@gmail.com
Also, besides Joseph said (it is true in my case), there is a fundamental
difference and it is that vaadin, smartGWT, etc uses an architecture where
they depend on server side stuff. For example, all vaading
It will be well worth your time to add the missing bits to GWT rather than
jump into SmartGWT. We just re-wrote the UI on an app due to SmartGWT
shortcomings and incompatibilities.
On Monday, October 29, 2012 5:47:08 AM UTC-4, kumar thatikonda wrote:
Hi All,
Can you please let me know
I said it before.
Nothing beats Flex on the Desktop anyway :)
2012/10/30 Jason Hobbs jason.ho...@shawinc.com
It will be well worth your time to add the missing bits to GWT rather than
jump into SmartGWT. We just re-wrote the UI on an app due to SmartGWT
shortcomings and incompatibilities.
On 29/10/2012 21:59, Benjamin Possolo wrote:
I recommend straight GWT for almost everything. The other frameworks just add
abstractions
on top of GWT that confuse things a lot more.
They are supposed to offer a bit more than some abstraction layers and nice
CSS...
For example, they offer
On Tuesday, October 30, 2012 5:30:56 PM UTC+1, PhiLho wrote:
On 29/10/2012 21:59, Benjamin Possolo wrote:
I recommend straight GWT for almost everything. The other frameworks
just add abstractions
on top of GWT that confuse things a lot more.
They are supposed to offer a bit more
Hi Kumar,
SmartGWT has an extensive subsystem for interacting directly with WSDL web
services from the browser. Some samples here:
http://www.smartclient.com/smartgwtee/showcase/#data_integration_server_wsdl_weather
This is all part of the free LGPL product, assuming you don't need a
Also smartgwt has a great forum support, where any Isomorphic stuff member
can make an idiot out of you. (my recent exp:
http://forums.smartclient.com/showthread.php?t=24112). To be honest, it's
not that way always, sometimes you get really good, fast and polite
support. It all depens on
Hello Валерий Остапенко,
You should probably go take a look at that thread again - looks like
you didn't see the last reply from Support. They cleared up your
misconception, which appears to be the reason you were getting so
frustrated, and why you were trying to say the docs were wrong when
Hi All,
Please let me know which one is better(GWT or SmartGWT) for developing a
web application considering the below scenario.
1. Will use only for developing the screens and client side validations.
2. Needs to communicate with server through wsdls.
3. Performance (initial screen loading
Hi All,
Can you please let me know which of the option( GWT or SmartGWT) is
better, considering the below scenario.
1. Will be used for designing screens and client-side validations.
2. Performance ( page loading , grid loading) should be good.
3. Need to communicate with server through
I recommend straight GWT for almost everything. The other frameworks just
add abstractions on top of GWT that confuse things a lot more.
Designing screens: UI Binder
Client-side validation: Editor framework + JSR303 validation using
HibernateValidator 4.0.2GA
Performance: AsyncProxy,
I agree with Benjamin. I would add though that if the standard widgets are
not a good fit for your requirements, then it is worth seriously looking at
Sencha GXT (Ext-GWT) as well.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view
Folks in my company were just asking me this the other day. If you want an
app that looks like the GXT or SmartGWT showcase, and absolutely nothing
more, then use them. But you'll have to bend to their paradigms and extend
their frameworks if you want more than they do. Further, these
17 matches
Mail list logo
