We use a build.gradle file similar to the following for most of our
GWT client projects:
(Note: We use './gradlew :gwts' to run SDM and './gradlew :build
:farmRun' to run a local http server)
apply plugin: 'java'
apply plugin: 'war'
apply plugin: 'gwt'
I imported the project from svn, then eclipse created a new gradle project.
It seems like gradle recognize this project as a normal java project.
I have only src and war directories in the repository, so no files in the
root dir.
In the src there are numerous gwt modules directories, and in the
Use Maven or Gradle to configure the project and let Eclipse import it as a
Maven or Gradle project.
On Tue, Jul 28, 2020 at 11:42 AM mb user wrote:
> Hi,
>
> After a storage crash, I had to reinstall my development computer.
>
> Now I have eclipse 4.16 and a gwt 2.8.1 project source imported
Hi,
After a storage crash, I had to reinstall my development computer.
Now I have eclipse 4.16 and a gwt 2.8.1 project source imported from svn.
This project was built with the eclipse gwt plugin, but I cannot install it
to eclipse 4.16.
What is the recommended way to achieve compile and
When I looked at this 6 years ago (in relation to MGWT, which is dead
although we still use it in legacy products) Pointer events were the way to
go and are supported on all browsers now as far as I am aware.
There was talk of a single touch/pointer API system in GWT similar to what
MGWT did
Maybe you can Google for : JS surface touch events
Or something like that. But for JS. Maybe that can point you in the right
direction.
Op maandag 27 juli 2020 om 22:02:20 UTC+2 schreef m.conr...@gmail.com:
> you will need to check and see what event is actually generated for the
> windows 10
