Maybe there is effectively going to be a fork? So if the interest was there
could be GWT 2.9 - GWT 2.123
I think that might represent the truth that there is one user base that
wants to build Java apps that happen to run in a browser vs users who are
working on products that need to squeeze
I'm puzzled as to what the disadvantages could be of GWT Widgets. They
are, after all, translated to efficient JavaScript and allow full use of
the browser. I can see that some developers might want to integrate with
JavaScript frameworks, but others, like me, start writing applications in
pure
I can see the logic of GWT 3.0. The browser has evolved a lot since GWT was
first designed. Back in those days every browser had significant quirks and
the lowest common denominator was very low. In 2015 there is less reason
for a big layer between domain code and the browser. I think the same
+1
I think the division of GWT-compiler and GWT-widgets is the right thing to
do. The web-platform is moving fast and to GWT has to adopt to stay
relevant.
Webcomponents have the potential to become the new widgets and the new
JSInterops will make it quite easy to consume webcomponents that are
If you just want to run java apps in the browser there are solutions out
thtere
Free: http://www.webswing.org
Paying: http://www.creamtec.com/products/ajaxswing/overview.html
Now if you want to run create webapps then it is another matter. For me the
web stack is a crazy platform. But still since
Hello Magallo
You can use a code like this:
*protected* *void* doGet(HttpServletRequest request, HttpServletResponse
response) *throws* ServletException, IOException {
response.setContentType("image/png");
*if*(request.getParameter("id") != *null*) {
*
On Monday, October 19, 2015 at 12:22:19 PM UTC+2, Jens wrote:
>
>
>> * Stick with 2.x and risk being left behind and the project becoming
>> neglected due to split effort.
>>
>
> You are not behind when using 2.x:
>
> GWT 2 = GWT 2.x Compiler + JsInterop + Elemental 1 + Elemental 2 when
>
Somehow people seem to forget that they don't have to migrate at all if its
not profitable. Just stay on GWT 2.8.x and only start new projects with new
technology. There will be plenty of companies that have huge apps that will
not be rewritten anytime soon (if at all) so IMHO GWT 2.8.x will
I'm trying to understand my options.
* Stick with 2.x and risk being left behind and the project becoming
neglected due to split effort.
* Try to migrate to 3.x and possibly throw away a big investment.
* Look to move to something other than GWT.
Obviously we will also be taking action to
>
>
> * Stick with 2.x and risk being left behind and the project becoming
> neglected due to split effort.
>
You are not behind when using 2.x:
GWT 2 = GWT 2.x Compiler + JsInterop + Elemental 1 + Elemental 2 when
released + all current GWT SDK code + all GWT libraries.
GWT 3 = J2CL +
Actually what makes sense for me in an after split era is
* compile with the newest GWT 3.5, 4, 5 to pick up new features
* link with legacy but compatible gwt-widgets until I can gradually get rid
of them - or not.
This way I can migrate step by step my application (widget per widget) and
stay
On Saturday, October 17, 2015 at 3:18:11 PM UTC+2, james0072 wrote:
>
> Did you use the viewport in the html?
>
> https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag
>
No, but the page you pointed to sounds like there could be a solution.
But if I add a viewport tag, what
12 matches
Mail list logo
