Alberto,
I will also say that I think you did a great job of promoting GWTCon and my
comments should only be taken in terms of visibility of people who might
not be entrenched in the community so steeply as we all are. Someone new
coming into GWT, what does the message, brand and presence say
On Friday, October 16, 2015 at 1:07:49 PM UTC+2, Alberto Mancini wrote:
>
>
>>
>>> There is no promotion on the main GWT site of the only currently
>>> scheduled GWT conference and the normally already scheduled GWT.create
>>> conference, there is no chatter about.
>>>
>>
>> Conference
On Friday, October 16, 2015 at 2:15:22 AM UTC+2, JonL wrote:
>
> There is no clear status of the next release or when it can be expected or
> what are the blockers on the Contributor forum here.
>
This is not
exact: https://groups.google.com/d/topic/gwt-steering/uv_WsmNkti0/discussion
(*not*
On Thursday, October 15, 2015 at 9:25:40 PM UTC+2, bendg25 wrote:
>
> Can you ditch the embedded Jetty server please.
>
Hmm, no. But it'd be interesting to know the reason for that request.
For example, a classpath conflict is generally not a valid reason, because
the part of GWT that includes
>
>
>
>> There is no promotion on the main GWT site of the only currently
>> scheduled GWT conference and the normally already scheduled GWT.create
>> conference, there is no chatter about.
>>
>
> Conference organizers are probably the ones who should promote their
> conference; GWT core
Is there a guide somewhere of migration path to 3.0 per feature?
I've been trying to follow these threads but I'm still not sure on the
future of things like RequestFactory and Editor. They heavily depend on
GWT.create and the latter depends on Widgets, are they really going away?
We have a
Some very dubious statements about the comparison with GWT at the end of
that page.
On Wednesday, September 30, 2015 at 4:49:41 PM UTC+1, Kirill Prazdnikov
wrote:
>
> Looks like http://teavm.org/ is one that can replace GWT.
>
> среда, 30 сентября 2015 г., 11:54:51 UTC+3 пользователь Vladislav
"classpath conflict is generally not a valid reason, because the part of
GWT that includes Jetty is not concerned about the server side of the
applications"
Unless you run [Super]DevMode, which runs both in a single JVM, then it is
a pain.
There are other libs which are bundled in GWT jars,
Hi,
my GWT app shows wrong on iPad/Safari. It is displayed extremely zoomed so
that you only see a small section and have to scroll a lot.
When thinking about the code, I don't know where to start. The app works
good in IE, FF and Chrome.
Are there any things you have to pay attention when
On Friday, October 16, 2015 at 3:25:04 PM UTC+2, Luis Fernando Planella
Gonzalez wrote:
>
> "classpath conflict is generally not a valid reason, because the part of
> GWT that includes Jetty is not concerned about the server side of the
> applications"
> Unless you run [Super]DevMode, which
I think nobody has such information yet; not even Google who are pushing
for the change. They do have many apps that use widgets and RPC today
(example: Google Groups, the exact app I'm typing this message into) and
will need to come up with a migration path for those apps too.
On Friday,
Thanks for the link Thomas! I knew something along this line must exist.
However, it appears that the GWT Steering google group is not listed on
the GWT Resources page, so it is kind of hidden from view and I was unaware
it existed.
I made a suggested edit and pull request to have it added
12 matches
Mail list logo
