Re: CSS Variables and GSS

Reviving an old thread ... 

I need to use CSS variables to override some styling in bootstrap in one of my screens. 

But it seems that the CSS variable support in closure stylesheets was never finished (and closure stylesheets seems dead)

Should we assume that CssResources and GSS are deprecated and stop using them? Many JS UI components start using CSS variables to allow for customisations.

What are my options? Go for something external to style my GWT application? But then I lose the benefits of the obfuscation and optimisations that are done by GWT.

On Monday, September 11, 2017 at 4:49:15 PM UTC+2 max.d...@corussoft.de wrote:

Thx for the reply. https://github.com/google/closure-stylesheets/pull/121/commits/7c99519b6726a2bcdb9458d4dc352e8722f50178 

It seems there are at least some contribution in this regard :)

Am Montag, 11. September 2017 15:29:19 UTC+2 schrieb Jens:

GWT itself uses a version of Google Closure Stylesheets library internally to support CSS 3 features. GWT updates this library from time to time to support more CSS 3 features and it looks like CSS variables are not yet available in Google Closure Stylesheets: https://github.com/google/closure-stylesheets/pull/121

For now you have to stick with closure stylesheets variables: https://github.com/google/closure-stylesheets#variables

-- J.

--
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/111978d4-5dc3-4966-adcf-e379bcba6b78n%40googlegroups.com.

Re: Announcement for the GWT 2.12 release

> I think, updating client and server to Java 17 might be enough. Spring Boot 3 at least requires Java 17. If someone is willing to use Java 21 on the server, it is possible by updating it. @Craig: What do you think?

Agreed.  PR:  https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/21

Cheers.

On Monday 4 November 2024 at 10:11:55 pm UTC+11 Frank Hossfeld wrote:

I think, updating client and server to Java 17 might be enough. Spring Boot 3 at least requires Java 17. If someone is willing to use Java 21 on the server, it is possible by updating it. @Craig: What do you think?

Craig Mitchell schrieb am Sonntag, 3. November 2024 um 10:24:03 UTC+1:

Woohoo!  Upgrade went flawlessly.  Thank you to all involved!

@Frank  The work done in this PR https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/8 can be either removed, or maybe we want to upgrade the server to Java 21, and the client to Java 17.

On Saturday 2 November 2024 at 3:41:37 am UTC+11 Frank Hossfeld wrote:

Fyi, gwt-maven-springboot-archetype have been updated (version 2024.11.1) with GWT 2.12 and Spring Boot 3.3.5



Thomas Broyer schrieb am Donnerstag, 31. Oktober 2024 um 23:19:37 UTC+1:

Fyi, gwt-maven-archetypes have been updated (version 2024.10.31) with GWT 2.12 (and Maven plugins each updated to their latest version)

On Tuesday, October 29, 2024 at 3:22:14 PM UTC+1 Colin Alworth wrote:

GWT 2.12 is here!

Highlights:

• Added support for Java 12-17 language features, including text blocks, instanceof pattern matching, records, and switch expressions.
• Minimum Java version 11 is required to run any dev tools, though the server code should continue to function with Java 8 for this release. Later versions may no longer support Java 8. Tested to run on Java 11-23.
  
• Added support for sourcemaps to include the contents of the sources files.
• Enabled sourcemaps by default in all browsers
• Fix CSP issues in linkers and dev mode, provide CSP workarounds for GWT-RPC payloads

See https://github.com/gwtproject/gwt/releases/tag/2.12.0 or https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_0 for the complete release notes.

This was a shorter release cycle than we've done in the past, and we're taking steps to simplify some of the processes we use, while still ensuring that projects can continue to update with a minimum of friction. Thanks to our testers, reviewers, committers in this release! A short list of the names that helped bring us this release: Ahmad Bawaneh, Michael S., Dmitrii Tikhomirov, Zbynek Konecny, Paul Kintner, George Paret, Daniel Portmann, Frank Hossfeld, Joan Pablo Gardella, Jens Nehlmeier, Thomas Broyer,

Join us on the issue tracker or at our OpenCollective page to help make future releases.possible.

 

--
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/58bc08f2-49fe-4a19-848e-6e6e6069b183n%40googlegroups.com.

Re: Announcement for the GWT 2.12 release

Thanks!

Op maandag 4 november 2024 om 12:11:55 UTC+1 schreef Frank Hossfeld:

I think, updating client and server to Java 17 might be enough. Spring Boot 3 at least requires Java 17. If someone is willing to use Java 21 on the server, it is possible by updating it. @Craig: What do you think?

Craig Mitchell schrieb am Sonntag, 3. November 2024 um 10:24:03 UTC+1:

Woohoo!  Upgrade went flawlessly.  Thank you to all involved!

@Frank  The work done in this PR https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/8 can be either removed, or maybe we want to upgrade the server to Java 21, and the client to Java 17.

On Saturday 2 November 2024 at 3:41:37 am UTC+11 Frank Hossfeld wrote:

Fyi, gwt-maven-springboot-archetype have been updated (version 2024.11.1) with GWT 2.12 and Spring Boot 3.3.5



Thomas Broyer schrieb am Donnerstag, 31. Oktober 2024 um 23:19:37 UTC+1:

Fyi, gwt-maven-archetypes have been updated (version 2024.10.31) with GWT 2.12 (and Maven plugins each updated to their latest version)

On Tuesday, October 29, 2024 at 3:22:14 PM UTC+1 Colin Alworth wrote:

GWT 2.12 is here!

Highlights:

• Added support for Java 12-17 language features, including text blocks, instanceof pattern matching, records, and switch expressions.
• Minimum Java version 11 is required to run any dev tools, though the server code should continue to function with Java 8 for this release. Later versions may no longer support Java 8. Tested to run on Java 11-23.
  
• Added support for sourcemaps to include the contents of the sources files.
• Enabled sourcemaps by default in all browsers
• Fix CSP issues in linkers and dev mode, provide CSP workarounds for GWT-RPC payloads

See https://github.com/gwtproject/gwt/releases/tag/2.12.0 or https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_0 for the complete release notes.

This was a shorter release cycle than we've done in the past, and we're taking steps to simplify some of the processes we use, while still ensuring that projects can continue to update with a minimum of friction. Thanks to our testers, reviewers, committers in this release! A short list of the names that helped bring us this release: Ahmad Bawaneh, Michael S., Dmitrii Tikhomirov, Zbynek Konecny, Paul Kintner, George Paret, Daniel Portmann, Frank Hossfeld, Joan Pablo Gardella, Jens Nehlmeier, Thomas Broyer,

Join us on the issue tracker or at our OpenCollective page to help make future releases.possible.

 

--
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/95299e3f-6ef1-4411-9b35-0fc139b94089n%40googlegroups.com.

Re: Announcement for the GWT 2.12 release

I think, updating client and server to Java 17 might be enough. Spring Boot 3 at least requires Java 17. If someone is willing to use Java 21 on the server, it is possible by updating it. @Craig: What do you think?

Craig Mitchell schrieb am Sonntag, 3. November 2024 um 10:24:03 UTC+1:

Woohoo!  Upgrade went flawlessly.  Thank you to all involved!

@Frank  The work done in this PR https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/8 can be either removed, or maybe we want to upgrade the server to Java 21, and the client to Java 17.

On Saturday 2 November 2024 at 3:41:37 am UTC+11 Frank Hossfeld wrote:

Fyi, gwt-maven-springboot-archetype have been updated (version 2024.11.1) with GWT 2.12 and Spring Boot 3.3.5



Thomas Broyer schrieb am Donnerstag, 31. Oktober 2024 um 23:19:37 UTC+1:

Fyi, gwt-maven-archetypes have been updated (version 2024.10.31) with GWT 2.12 (and Maven plugins each updated to their latest version)

On Tuesday, October 29, 2024 at 3:22:14 PM UTC+1 Colin Alworth wrote:

GWT 2.12 is here!

Highlights:

• Added support for Java 12-17 language features, including text blocks, instanceof pattern matching, records, and switch expressions.
• Minimum Java version 11 is required to run any dev tools, though the server code should continue to function with Java 8 for this release. Later versions may no longer support Java 8. Tested to run on Java 11-23.
  
• Added support for sourcemaps to include the contents of the sources files.
• Enabled sourcemaps by default in all browsers
• Fix CSP issues in linkers and dev mode, provide CSP workarounds for GWT-RPC payloads

See https://github.com/gwtproject/gwt/releases/tag/2.12.0 or https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_0 for the complete release notes.

This was a shorter release cycle than we've done in the past, and we're taking steps to simplify some of the processes we use, while still ensuring that projects can continue to update with a minimum of friction. Thanks to our testers, reviewers, committers in this release! A short list of the names that helped bring us this release: Ahmad Bawaneh, Michael S., Dmitrii Tikhomirov, Zbynek Konecny, Paul Kintner, George Paret, Daniel Portmann, Frank Hossfeld, Joan Pablo Gardella, Jens Nehlmeier, Thomas Broyer,

Join us on the issue tracker or at our OpenCollective page to help make future releases.possible.

 

--
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/6b0aeebb-5a36-48b3-9486-cd95120cda30n%40googlegroups.com.

Re: Announcement for the GWT 2.12 release

Great work to the team, congrats!

Lofi

Colin Alworth schrieb am Dienstag, 29. Oktober 2024 um 15:22:14 UTC+1:

GWT 2.12 is here!

Highlights:

• Added support for Java 12-17 language features, including text blocks, instanceof pattern matching, records, and switch expressions.
• Minimum Java version 11 is required to run any dev tools, though the server code should continue to function with Java 8 for this release. Later versions may no longer support Java 8. Tested to run on Java 11-23.
  
• Added support for sourcemaps to include the contents of the sources files.
• Enabled sourcemaps by default in all browsers
• Fix CSP issues in linkers and dev mode, provide CSP workarounds for GWT-RPC payloads

See https://github.com/gwtproject/gwt/releases/tag/2.12.0 or https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_0 for the complete release notes.

This was a shorter release cycle than we've done in the past, and we're taking steps to simplify some of the processes we use, while still ensuring that projects can continue to update with a minimum of friction. Thanks to our testers, reviewers, committers in this release! A short list of the names that helped bring us this release: Ahmad Bawaneh, Michael S., Dmitrii Tikhomirov, Zbynek Konecny, Paul Kintner, George Paret, Daniel Portmann, Frank Hossfeld, Joan Pablo Gardella, Jens Nehlmeier, Thomas Broyer,

Join us on the issue tracker or at our OpenCollective page to help make future releases.possible.

 

--
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/f6a6f4ab-d3d1-45d3-866c-2c943657171an%40googlegroups.com.

Re: Announcement for the GWT 2.12 release

Woohoo!  Upgrade went flawlessly.  Thank you to all involved!

@Frank  The work done in this PR https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/8 can be either removed, or maybe we want to upgrade the server to Java 21, and the client to Java 17.

On Saturday 2 November 2024 at 3:41:37 am UTC+11 Frank Hossfeld wrote:

Fyi, gwt-maven-springboot-archetype have been updated (version 2024.11.1) with GWT 2.12 and Spring Boot 3.3.5



Thomas Broyer schrieb am Donnerstag, 31. Oktober 2024 um 23:19:37 UTC+1:

Fyi, gwt-maven-archetypes have been updated (version 2024.10.31) with GWT 2.12 (and Maven plugins each updated to their latest version)

On Tuesday, October 29, 2024 at 3:22:14 PM UTC+1 Colin Alworth wrote:

GWT 2.12 is here!

Highlights:

• Added support for Java 12-17 language features, including text blocks, instanceof pattern matching, records, and switch expressions.
• Minimum Java version 11 is required to run any dev tools, though the server code should continue to function with Java 8 for this release. Later versions may no longer support Java 8. Tested to run on Java 11-23.
  
• Added support for sourcemaps to include the contents of the sources files.
• Enabled sourcemaps by default in all browsers
• Fix CSP issues in linkers and dev mode, provide CSP workarounds for GWT-RPC payloads

See https://github.com/gwtproject/gwt/releases/tag/2.12.0 or https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_0 for the complete release notes.

This was a shorter release cycle than we've done in the past, and we're taking steps to simplify some of the processes we use, while still ensuring that projects can continue to update with a minimum of friction. Thanks to our testers, reviewers, committers in this release! A short list of the names that helped bring us this release: Ahmad Bawaneh, Michael S., Dmitrii Tikhomirov, Zbynek Konecny, Paul Kintner, George Paret, Daniel Portmann, Frank Hossfeld, Joan Pablo Gardella, Jens Nehlmeier, Thomas Broyer,

Join us on the issue tracker or at our OpenCollective page to help make future releases.possible.

 

--
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/d8bd24da-71dc-473c-a70b-6d6dc07d9fc9n%40googlegroups.com.

Re: Error : No project found - Running GWT in client mode only

I do a similar thing with the resources with my Springboot based app:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>3.3.1</version>
<executions>
<execution>
<id>copy-resources</id>
<phase>generate-resources</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>${basedir}/target/${project.build.finalName}/</outputDirectory>
<resources>
<resource>
<directory>${basedir}/src/main/resources/public/</directory>
<includes>
<include>**/*.*</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>

This was all auto configured for me by:  https://github.com/NaluKit/gwt-maven-springboot-archetype

Cheers.

On Friday 1 November 2024 at 7:08:08 am UTC+11 Mukeya Kassindye wrote:

Hi Craig,

Just a heads up.
I finally managed to get all the files right. The package of the module responsible for generating the js file was war instead of gwt-app.
I changed this and referenced it as a war type in my main pom.xml file. Then I was able to get the no cache js files while running mvn package.

Now I have another challenge, I think it is for another topic. All my files are in the same war directory. I would like to have the html and css files in a separate folder from the generated js ones.

As I am running a standalone GWT app, and using the default GWT public path for static files, they all come under the same folder. I tried to use Maven WAR Plugin and copy-resources, but no luck.

Any ways, thanks

Mnamo Jumatano, 30 Oktoba 2024 saa 10:25:21 UTC-3 Mukeya Kassindye aliandika:

Hi craig thanks for your perspective.

Wildfly is going to be the server that is going to host the GWT compiled javascript/html etc. as I am going to use the errai framework.

When I run maven install, it does generate the war file and perfectly deploy to Wildfly (only with the index.html and css file. no js file). 

however I can't run gwt:devmode or gwt:codeserver. I have a project not found error and I don't have the "app.nocache.js" file generated either.

My guess is I am not doing something right with my gwt-maven-plugin configuration plugin, either on my client pom.xml file or my main project.xml file.

Any advice?

Mnamo Jumatano, 16 Oktoba 2024 saa 04:54:44 UTC-3 Craig Mitchell aliandika:

>  I am trying to set up a project where I want to use the GWT app on the client side only that is going to interact with another remote server.

Which server is going to host the GWT compiled JavaScript / HTML / ...?

1. If you'll have your own server, just leave the architecture as is, and write your calls to the external server in the the client.

2. If you need to host it on the external server, again, just leave the  architecture as is, as you can just copy the compiled GWT code across when you are ready to deploy.  But, if this is the situation, it's a bit crazy to not just make the external server a GWT app.

On Tuesday 15 October 2024 at 4:54:10 am UTC+11 Mukeya Kassindye wrote:

I am trying to set up a project where I want to use the GWT app on the client side only that is going to interact with another remote server.

However, before I implement the CORS option, I just want to run the client only part by eliminating all the server side code and deleting their corresponding module.

The GWT project is generated with the Tbroyer archetypes modular web-app.

This is what I did so far :

- copied the webapp folder from the web-project-server/src/main to web-project-client/src/main

- deleted the web-project-server and web-project-shared folders.

- updated the web-project-client's packaging from gwt-app to war

- kept the main pom packaging to "pom" because, soon the client's project is going to  have another modules(maven).

- deleted all reference to the two modules in the main pom.xml file.

So, if I run mvn clean install I can see that a war file is generated that can be deployed let's say to a Jboss/ wildfly server app.

However, from the main folder where the main pom.xml file is, I have an error of No project found if I run mvn gwt:codeserver -pl *-client -am

is there any other tweak I should consider on both poms xml file?

Notice that, if the packaging is kept to gwt-app in the client module, codeserver/devmode runs without a problem but I will have no reference the webapp files (index.html, css) because they won't be referenced.

Please advise.

this the content of my main pom.xml file : 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

  <modelVersion>4.0.0</modelVersion>

  <groupId>com.example</groupId>

  <artifactId>web-app</artifactId>

  <version>HEAD-SNAPSHOT</version>

  <packaging>pom</packaging>

  <properties>

    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

  </properties>

  <dependencyManagement>

    <dependencies>

      <dependency>

        <groupId>org.gwtproject</groupId>

        <artifactId>gwt</artifactId>

        <version>2.11.0</version>

        <type>pom</type>

        <scope>import</scope>

      </dependency>

    </dependencies>

  </dependencyManagement>

  <build>

    <plugins>

      <plugin>

        <groupId>net.ltgt.gwt.maven</groupId>

        <artifactId>gwt-maven-plugin</artifactId>

        <inherited>false</inherited>

        <configuration>

          <moduleName>com.example.WebAppClient</moduleName>

          <launcherDir>${project.build.directory}/gwt/launcherDir</launcherDir>

          <!-- To be able to use gwt:devmode (useful on Windows where Ctrl+C won't kill gwt:codeserver)-->

          <warDir>${project.build.directory}/gwt/launcherDir</warDir>

          <devmodeArgs>

            <arg>-noserver</arg>

            <arg>-startupUrl</arg>

            <arg>app/index.html</arg>

          </devmodeArgs>

        </configuration>

      </plugin>

    </plugins>

    <pluginManagement>

      <plugins>

        <plugin>

          <groupId>org.apache.maven.plugins</groupId>

          <artifactId>maven-compiler-plugin</artifactId>

          <version>3.12.1</version>

          <configuration>

            <release>11</release>

          </configuration>

        </plugin>

        <plugin>

          <groupId>org.apache.maven.plugins</groupId>

          <artifactId>maven-resources-plugin</artifactId>

          <version>3.3.1</version>

        </plugin>

        <plugin>

          <groupId>org.apache.maven.plugins</groupId>

          <artifactId>maven-surefire-plugin</artifactId>

          <version>3.2.5</version>

        </plugin>

        <plugin>

          <groupId>org.apache.maven.plugins</groupId>

          <artifactId>maven-war-plugin</artifactId>

          <version>3.4.0</version>

        </plugin>

        <plugin>

          <groupId>org.eclipse.jetty</groupId>

          <artifactId>jetty-maven-plugin</artifactId>

          <version>11.0.19</version>

        </plugin>

        <plugin>

          <groupId>net.ltgt.gwt.maven</groupId>

          <artifactId>gwt-maven-plugin</artifactId>

          <version>1.1.0</version>

          <extensions>true</extensions>

          <configuration>

            <sourceLevel>11</sourceLevel>

            <failOnError>true</failOnError>

          </configuration>

        </plugin>

      </plugins>

    </pluginManagement>

  </build>

  <modules>

    <module>web-app-client</module>

  </modules>

</project>

and this is the content of my client module pom.xml file : 

<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

  <modelVersion>4.0.0</modelVersion>

  <parent>

    <groupId>com.example</groupId>

    <artifactId>web-app</artifactId>

    <version>HEAD-SNAPSHOT</version>

  </parent>

  <artifactId>web-app-client</artifactId>

  <!-- <packaging>gwt-app</packaging> -->

  <packaging>war</packaging>

  <dependencies>

    <dependency>

      <groupId>org.gwtproject</groupId>

      <artifactId>gwt-user</artifactId>

    </dependency>

    <dependency>

      <groupId>org.gwtproject</groupId>

      <artifactId>gwt-dev</artifactId>

    </dependency>

  </dependencies>

  <build>

    <plugins>

      <plugin>

        <groupId>net.ltgt.gwt.maven</groupId>

        <artifactId>gwt-maven-plugin</artifactId>

        <configuration>

          <moduleName>com.example.WebAppClient</moduleName>

          <moduleShortName>app</moduleShortName>

        </configuration>

      </plugin>

    </plugins>

  </build>

</project>

what am i missing?

--
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/a48ebba3-f082-47e5-9c4e-e0ae23a1e30en%40googlegroups.com.