Alex, it took a few engineer-days for us to declare in JsInterop what we need
from HTML API (in a really big project including DOM, events, WebGL, input,
network).
There is no blocker of using it today, if u want of course.
"Official" Google public annotations is useful to make a "standard"
https://gwt-review.googlesource.com/#/c/17180/
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
I do not completely understand which problems do you have, but we dont have any
issues working with SDM with modules I described above.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from
> On 12 Oct 2016, at 10:29, Luca Morettoni wrote:
>
> Hi all, currently my application is using a single module for the GWT code,
> but I’d like to split it in some submodules to better organize the code.
> Everything is under maven and I organised the main project layout
A while back -bindAddress 0.0.0.0 was changed in GWT 2.8 to use the actual
IP address instead of a local hostname to work better when operating in an
environment where the local hostname isn't recognized by the client
(specifically, things like windows tablets don't seem to recognize the mac
GWT Eclipse Plugin (V3)
Issue: https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/274
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
What would you think of adding a bindAddress replacement to the
template.nocache.js file. __bindAddress__ instead of
$window.location.hostname?
Example Source - Used for testing Hack
> On 12 Oct 2016, at 19:05, Kirill Prazdnikov wrote:
>
> As far as I know you need only one GWT maven module that builds the app.
> The rest modules are just regular (platform independent) modules
> (jar) and the gwt-app module depends on it.
>
> So for the client app u
As far as I know you need only one GWT maven module that builds the app.
The rest modules are just regular (platform independent) modules
(jar) and the gwt-app module depends on it.
So for the client app u have 2: main GWT module (A) with GWT specific code and
GWT dependencies and a plain jar
As far as I know you need only one GWT maven module that builds the app.
The rest modules are just regular (platform independent) modules
(jar) and the gwt-app module depends on it.
So for the client app u have 2: main GWT module (A) with GWT specific code and
GWT dependencies and a plain jar
> On 12 Oct 2016, at 10:29, Luca Morettoni wrote:
>
> Hi all, currently my application is using a single module for the GWT code,
> but I’d like to split it in some submodules to better organize the code.
> Everything is under maven and I organised the main project layout
Hi all, currently my application is using a single module for the GWT code, but
I’d like to split it in some submodules to better organize the code.
Everything is under maven and I organised the main project layout using Thomas
Broyer gwt-maven-archetypes [1], so now I have a main maven project
I have the same problem. Any news?
On Wednesday, April 20, 2016 at 10:04:40 PM UTC+3, Farrukh Shakil wrote:
>
> My GWT+Maven setup stopped working after upgrading to 2.7. I am running
> both GWT+MAVEN (gwt:run) and GWT+MAVEN+Eclipse (as google web application)
> using built in jetty and
13 matches
Mail list logo