Jas Jas 1, 5 5 silver badges 16 16 bronze badges. To those trying to close this -- is it really subjective and argumentative? It it not a fair question to ask if GWT is suited to some problems better than others? Kirk - And to think I actually went an extra mile to make sure that question does not get closed How is this not subjective and argumentative?
Is the redeployment time a disadvantage? Yes, if you're using Java server-side. No, if you're using something else. No, if you're using JRebel. Is there a learning curve?
It's a very interesting topic to discuss, but this isn't the place for that. Igor, are you sure you are not being, mildly put hypocritical, given the wording of this question here actually answered by you : stackoverflow.
You ask a general question without giving out any info about your team what experience do they have? Web development? Show 4 more comments. Active Oldest Votes. I don't have to spend much time worrying about cross-browser support. Improve this answer. Kevin K 9, 2 2 gold badges 34 34 silver badges 59 59 bronze badges. Tony Tony 1 1 gold badge 4 4 silver badges 13 13 bronze badges. What you get of the box is:.
Our application issues only one request to the server on startup. On the negative side is that GWT and also Android have a poor design out of the box, but anyway if you apply your own look and feel you have to adapt the CSS. Alternatively you can use various component libraries for GWT which make it easy to apply proper styles and theming.
See the mission statement at:. But it should not be unmentioned that Google don't use GWT on many of their internal projects and that at the moment there are some rumors around about the future of GWT, see. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Learn more. When not to use Google Web Toolkit? Asked 10 years, 9 months ago. Active 6 years, 11 months ago. Viewed 33k times. Improve this question. Jas Jas 6, 1 1 gold badge 30 30 silver badges 46 46 bronze badges.
I thought GWT died. Aaron, really? I don't recommend GWT personally. The mindset it forces you into works for desktop applications, but will give you problems trying to think that way in HTML functions. I'm a fan of matching the coding paradigm to the problem at hand, and the abstraction gets in my way.
Which is why every time I started evaluating it, I decided not to use it. Jas Experience was couple years back; in it's infancy and it felt very raw at the time. Has it changed? At the end of the day it is a meat grinder for churning out JS; not that it is a bad thing but not somewhere I want to put my effort. Many of these frameworks are chosen due to lack of technology X knowledge or something thereof I am very knowledgeable in JS, wrote some pretty serious stuff there, however I am now running a very time-critical project and I cannot afford to have junior staff waste time because of errors induced by context-switching from say Java to JS.
So please, if you have some real world example of why GWT did not work for you, then please describe it, otherwise let's not waste each other's time with hypothetical and highly subjective-colored discussions.
Show 6 more comments. Active Oldest Votes. Union of problems, intersection of benefits Any languages is going to have it's own set of problems and benefits. Separation of concerns We all know that as the size of a project grows, having good separation of concerns is critical. GWT is a compiled framework that is written in Java. An Eclipse environment is typically used to generate GWT code. This is compared to the Jquery widgets that are rendered are more lightweight and tend to use more standard HTML.
For example, the Jquery ToggleButton uses a standard checkbox hidden behind the facade of a button. Assistive technology knows how to work with a standard checkbox. Because of that ARIA must be used to expose states and roles. ARIA is not as well supported yet by assistive technologies and browsers. This can be compensated by using an onKeyDown event. However, assistive technologies such as screen readers use virtual navigation modes where the enter and space bar are trapped and not sent through to the browser.
Instead the assistive technology must call the click event on the element — and it determines whether to send this event based on the HTML element type and whether ARIA is present. These factors make the process of getting solely ARIA based widgets to work with assistive technologies like screen readers complex.
There are accessible widgets that are provided directly in the toolkit, however, others only partially support accessibility, and still others require that the developer add in accessibility by extended the widget or by setting accessibility properties on the instance of a widget.
0コメント