Re: Issue: Group by week to Date field in ListGrid.

[Mayur Laniya]

Thanks, Jens for your reply, I can understand now.

On Sun, 8 Aug 2021 at 19:01, Jens  wrote:

> 11.07.2021 is a sunday. There are different week numbering systems in the
> world which have different first day of week definition. For example in the
> EU the first day of the week is monday while in the US / Canada it is
> sunday. That is reflected in locales and thus you are seeing that
> behaviour.
>
> See: https://en.wikipedia.org/wiki/Week#Other_Week_Numbering_Systems
>
> In GWT you can see locale settings here (see property firstDayOfTheWeek
> which contains an index of the content of property weekdays):
>
> Generic German (Monday):
> https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/i18n/client/constants/DateTimeConstantsImpl_de.properties
> Generic English (Sunday):
> https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/i18n/client/constants/DateTimeConstantsImpl_en.properties
> English - Great Britain (Monday):
> https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/i18n/client/constants/DateTimeConstantsImpl_en_GB.properties
>
> So with locales it is important to pick the right country as well if
> possible instead of just the language.
>
> -- J.
>
> mk.l...@gmail.com schrieb am Samstag, 7. August 2021 um 19:50:38 UTC+2:
>
>> Hi There,
>>
>> I have faced an issue with the List grid grouping column when column type
>> is Date and group by week.
>>
>> In the german locale, I used  dd.mm. format mask and
>> In the English locale, I used mm/dd/ format mask.
>>
>> Issue:
>> I set German locale grouping by week works fine but, When I set English
>> locale with the same data set I get different output.
>>
>> Example: I got issue in date is 11.07.2021 (dd.mm.)
>> 12th July - 2021 comes in week number 27.
>>
>> In German locale is come in week 27 that perfect but same record in
>> English locale it shows me in week number 28. How?
>>
>> I attached a screenshot for both data in both locales.
>>
>> Please help me and guide me on what should I need to configure for that.
>>
>> Thanks.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/sQCZMHbN5hc/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/60563850-75e2-4c30-9228-231b1c29a12fn%40googlegroups.com
> 
> .
>


-- 
*Thanks & Regards,*
* Mayur Laniya*

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CAKxbzvJZ1yhhhOLiRGg7jVsTLcz%3DEoVs%3DzWx4juvMCZ6LsEBvA%40mail.gmail.com.

Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)

[Vassilis Virvilis]

>
> So maybe it is possible for you to skip GWT compilation while building the
> *.war directory to save some minutes.


In my case this is a huge understatement. In superdevmode the compilation
is nearly instant (1-2secs maybe less)  instead of 90sec of the full
compile.

I don't know how it behaves in really big codebases that take several
minutes to compile but I bet it would make a big difference.

So follow Jens' advice and try to setup superdevmode for development. For
production you still need the final compilation step.

The other solution is to use code splitting
http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html but a) I
have never done it and b) certainly looks more invasing.
-- 
Vassilis Virvilis

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CAKbOjEw7tKKzS2oniP8S7%2BN4qV%2B5AK%2BRa0gbQgzBQ0GJki7fnw%40mail.gmail.com.

Re: Issue: Group by week to Date field in ListGrid.

[Jens]

11.07.2021 is a sunday. There are different week numbering systems in the 
world which have different first day of week definition. For example in the 
EU the first day of the week is monday while in the US / Canada it is 
sunday. That is reflected in locales and thus you are seeing that 
behaviour. 

See: https://en.wikipedia.org/wiki/Week#Other_Week_Numbering_Systems

In GWT you can see locale settings here (see property firstDayOfTheWeek 
which contains an index of the content of property weekdays):

Generic German 
(Monday): 
https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/i18n/client/constants/DateTimeConstantsImpl_de.properties
Generic English 
(Sunday): 
https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/i18n/client/constants/DateTimeConstantsImpl_en.properties
English - Great Britain 
(Monday): 
https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/i18n/client/constants/DateTimeConstantsImpl_en_GB.properties

So with locales it is important to pick the right country as well if 
possible instead of just the language.

-- J.

mk.l...@gmail.com schrieb am Samstag, 7. August 2021 um 19:50:38 UTC+2:

> Hi There,
>
> I have faced an issue with the List grid grouping column when column type 
> is Date and group by week.
>
> In the german locale, I used  dd.mm. format mask and
> In the English locale, I used mm/dd/ format mask.
>
> Issue:
> I set German locale grouping by week works fine but, When I set English 
> locale with the same data set I get different output.
>
> Example: I got issue in date is 11.07.2021 (dd.mm.)
> 12th July - 2021 comes in week number 27.
>
> In German locale is come in week 27 that perfect but same record in 
> English locale it shows me in week number 28. How?
>
> I attached a screenshot for both data in both locales.
>
> Please help me and guide me on what should I need to configure for that.
>
> Thanks.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/60563850-75e2-4c30-9228-231b1c29a12fn%40googlegroups.com.

Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)

[Jens]

When you start SuperDevMode it will generate some minimalistic output that 
should be stored in the (exploded) war directory produced by your eclipse 
plugin. That output basically is a special index.html file for development 
(which loads resources from SuperDevMode server instead of your war) and 
all files that your GWT app has defined as public resources (by default 
directories named "public" on the root of your GWT module).

In order to place that output into your exploded war directory you would 
use the SuperDevMode parameter "-launcherDir", e.g. 
"-launcherDir 
\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\".
 
For a learning experience you could also point launcherDir to some tmp 
directory first and see what it actually generates.

Given you are using Maven to launch things, you should look up how to start 
SuperDevMode with the GWT Maven plugin you are using. For example I know 
this one: https://tbroyer.github.io/gwt-maven-plugin/ which uses 
gwt:codeserver to start SuperDevMode and also lets you configure the 
launcherDir parameter.

When using SuperDevMode you do not need to GWT compile your app during the 
build of your *.war file/directory. SuperDevMode will do an initial, 
unoptimised compile and then will only compile incrementally any source 
changes. So maybe it is possible for you to skip GWT compilation while 
building the *.war directory to save some minutes.

-- J.

mmo schrieb am Freitag, 6. August 2021 um 17:05:55 UTC+2:

> I am (trying to) upgrade our GWT-based legacy application to use newer 
> Hibernate, Spring and other library versions. After some (substantial) 
> pull-ups this works mostly fine by now when deploying a fully generated and 
> packaged .war file, but building this thing always takes forever and day 
> (the infamous permutations and other steps...).
>
> Since the Jetty that's built into the GWT plugin has issues with newer 
> (multi-release) .jar files (see my different discussion) I had to switch 
> deployment of the application to Tomcat (which is our target server anyway) 
> also for development. 
>
> To speed up the development cycle I am thus trying to get this thing also 
> to run as unpacked file using Eclipse's Tomcat "server bridge". This plugin 
> deploys a web application to a temporary directory in the eclipse workspace 
> and then starts Tomcat passing it the proper settings using VM options 
> like: 
> -Dcatalina.base="\.metadata\.plugins\org.eclipse.wst.server.core\tmp0"
>  
> -Dcatalina.home="C:\Program Files\Apache Software Foundation\Tomcat 8.5" 
> -Dwtp.deploy="\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps"
> .
>
> With that the application begins to start up, I get to the point where I 
> login and get the initial index.html page but as soon as some GWT-generated 
> Java-script has to be loaded things stall. As I had to learn the entire GWT 
> generated code which - as I found out - gets compiled into directories 
> named like C
> :\Users\\AppData\Local\Temp\gwt-codeserver-8682038074388630768.tmp\.WebWar\compile-1\war\
>  is 
> *not* copied over or linked into the wtpwebapps directory.
>
> I experimented a bit and if one creates a Junction (a kind of soft-link in 
> Windows) in the wtpwebapps\   directory pointing to that 
> generated GWT code then  the application indeed starts loading the UI. 
> However, at some point it invariably dies with a popup that it couldn't 
> load the application from Super Dev Mode Server at http://localhost:9876. 
> So there are (at least) two things missing: the GWT code has to be hooked 
> or copied into the generated server configuration and apparently there must 
> also be a Dev Server available. At this point - since I don't understand 
> this (Super) Dev Mode well enough - I decided to ask in this forum:
>
> Has anyone got this working so that one can deploy a GWT application to a 
> local Tomcat instance without first having to pack everything up and deploy 
> as a .war file, so that one can essentially continue to run and debug as 
> one used to using Jetty before using the maven goals gwt:run or gwt:debug? 
>
> Is that described or documented anywhere? Or would some kind soul mind to 
> share his/her knowledge on how to get this working? 
> It doesn't have to be for Eclipse - IntelliJ would be ok as well. The 
> point is that it should not require the lengthy build-package-deploy cycle 
> because a cycle-time of >10 minutes is just unbearable for development. 
>
> Any suggestions welcome!
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/9a5dbff2-b606-4b04-9e07-1989d9cb1765n%40googlegroups.com.

Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06

[Craig Mitchell]

>  client side in Chrome or Edge

Yep, I can still do this.  And when I want to step into code, I often do 
just use the Chrome debugger (as the SDBG plugin was a bit of hit and miss 
when inspecting variable, etc.).

However, it's very convient to get the Chrome console right in Eclipse.  
You can instantly see if anything is going wrong.  That's the main reason 
it'd be great to get the SDBG plugin working again.

I guess I could try to fix SDBG myself.  Looks like this is the problem:

https://github.com/sdbg/sdbg/blob/master/com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/internal/webkit/protocol/WebkitPage.java#L109

I'll post a message in https://groups.google.com/g/sdbg first, and hope 
someone that knows something about the plugin responds.  :-)

On Sunday, 8 August 2021 at 4:38:53 pm UTC+10 ralph.f...@gmail.com wrote:

> Stopped using Eclipse plug-ins just recently when going to JDK11. Am using 
> Maven Jetty plugin to run code server and host the application. 
>
> It was a bit cumbersome to set up (steep Maven learning curve!) but was 
> worth it in the end: onboard a new developer in no time (if Maven is 
> already configured). 
>
> Server side debugging in Eclipse (or whatever is your preferred IDE), 
> client side in Chrome or Edge. 
>
>
> Craig Mitchell  schrieb am So. 8. Aug. 2021 um 
> 08:25:
>
>> Tried a fresh Eclipse install, and also tried installing the GWT plugin 
>> without the Chrome debugger, and then adding the SDBG manually from here 
>> https://sdbg.github.io/ with no luck.
>>
>> Looks like the SDBG died somewhere between my old 2018-12 Eclipse, and 
>> 2021-06 Eclipse.
>>
>> Looking at the error:  javax/xml/bind/Datatypeconverter not found, it 
>> sounds like it's because Eclipse can no longer run on Java 8 (I'm running 
>> it on Java 11).
>>
>> Does anyone have Chrome debug in Eclipse still working?  Or are there any 
>> other plugins that we can use?
>>
>> On Saturday, 7 August 2021 at 2:46:30 pm UTC+10 Craig Mitchell wrote:
>>
>>> I just did a fresh install on a new PC, and the GWT plugin worked fine 
>>> with Eclipse 2021-06.
>>>
>>> The only issue I have is when I launch Chrome from Eclipse, Chrome opens 
>>> fine, however, I get this error:
>>> [image: error.png]
>>> and I can't debug the browser in Eclipse.  Debugging still works fine in 
>>> Chrome.
>>>
>>>
>>> On Thursday, 17 June 2021 at 3:22:34 am UTC+10 Jim Douglas wrote:
>>>
 I just updated my Eclipse development environment from 2021-03 to 
 2021-06. The installed GWT Eclipse Plugin (which hasn't been updated since 
 2017) no longer shows up in the menu bar, and it logs a bunch of errors. 
 Is 
 anyone (Brandon?) still maintaining it?


 http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html

   GWT Eclipse Plugin 3.0.0.201710131939 
 com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse 
 Plugin


 org.osgi.framework.BundleException: Could not resolve module: 
 com.gwtplugins.gdt.eclipse.core [3649]
   Unresolved requirement: Require-Bundle: 
 com.gwtplugins.gdt.eclipse.platform
 -> Bundle-SymbolicName: com.gwtplugins.gdt.eclipse.platform; 
 bundle-version="3.0.0.201710131939"; singleton:="true"
com.gwtplugins.gdt.eclipse.platform [3651]
  No resolution report for the bundle.  Bundle was not resolved 
 because of a uses constraint violation.
   org.apache.felix.resolver.reason.ReasonException: Uses constraint 
 violation. Unable to resolve resource com.gwtplugins.gdt.eclipse.platform 
 [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939"; 
 osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"] 
 because it is exposed to package 'javax.servlet' from resources 
 javax.servlet [osgi.identity; type="osgi.bundle"; 
 version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"] and 
 jakarta.servlet-api [osgi.identity; type="osgi.bundle"; 
 version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"] via two 
 dependency chains.

 Chain 1:
   com.gwtplugins.gdt.eclipse.platform [osgi.identity; 
 type="osgi.bundle"; version:Version="3.0.0.201710131939"; 
 osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
 require: (osgi.wiring.bundle=javax.servlet)
  |
 provide: osgi.wiring.bundle: javax.servlet
   javax.servlet [osgi.identity; type="osgi.bundle"; 
 version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"]

 Chain 2:
   com.gwtplugins.gdt.eclipse.platform [osgi.identity; 
 type="osgi.bundle"; version:Version="3.0.0.201710131939"; 
 osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
 require: (osgi.wiring.bundle=org.eclipse.jetty.servlet)
  |
 provide: osgi.wiring.bundle; bundle-version:Version="10.0.5"; 
 osgi.wiring.bundle="org.ec