Re: Strategies for dealing with large number of languages?

['Alexander Bertram' via GWT Users]

Thanks!
This is all very helpful. 

Following on what Collin suggested, I took a look at what the effect would 
be of collapsing all the permutations.

I found that collapsing all 23 languages into a single permutation would 
increase the gzipped initial download of our application from 443k to 633k, 
which is not a good tradeoff for us as many our users are working in areas 
with poor or limited connectivity. But there is a probably room to group 
2-3 languages together to reduce the number of permutations in the 
short-term.

Also, I did some experimenting with virtual machines, and for what it's 
worth, moving from n1-highmem-32 to c3d-standard-8 cut our build time in 
half, and is much much cheaper. The C3D, which is based on AMD's Genoa 
processor seems to do better than the corresponding Intel-based C3 (and is 
cheaper).

However, long-term, it sounds like using side-loaded dictionaries are both 
feasable and much more practical. We'll start investigating how we can make 
the change this year.

Thanks again, and all the best for 2024.

Alex


 
 

On Thursday, January 4, 2024 at 2:16:24 PM UTC+1 Leon Pennings wrote:

> All,
>
> Same as Ralph, we've always been using a custom Translator class (since 
> 2009/2010 or so).
> so for instance .setText(Translator.translate("Submit"))
>
> The Translator loads all labels and puts them in mem based on the language 
> preference of the user. So only 1 set of language labels in mem.
> Works like a charm and never had a problem.
> The translations are on the server side in the db so that a superuser can 
> manage translations.
>
> rg,
>
> Leon.
>
> Op donderdag 4 januari 2024 om 09:55:26 UTC+1 schreef Ralph Fiergolla:
>
> Hi! 
> Since a big part of our string content comes from database records anyway, 
> we decided to go without any static texts but use dynamic labels. Initial 
> concerns about performance and memory footprint have proven to be 
> unfounded. That is, despite working in the context of European Institutions 
> we go with a single static language and avoid the compile time performance 
> bottleneck of having a large number of permutations. 
> Cheers,
> Ralph 
>
> On Thursday, January 4, 2024 at 1:29:08 AM UTC+1 Alexander Bertram wrote:
>
> Hi there,
> We have been using GWT to build our product for a very long time. 
> Recently, we've faced a new challenge as we've steadily been increasing the 
> number of supported translations of the application to support a global 
> audience. We're up to 24 languages, and could conceivably hit 40 in the 
> coming year.
>
> With all of these languages, come more permutations! We've stripped away 
> browser-specific permutations, but we do have a mobile version of the app, 
> which means that we have 2 x 24 permutations = 48.
>
> So far, we've addressed this problem by increasing the size of the VM that 
> builds the app, but even with 16 vCPUs it takes 10-12 minutes to build the 
> app. I'm experimenting with increasing to 32 vCPUs, but so far I can't get 
> the build time to drop linearly.
>
> Anyone else out there using alternate strategies? Is it worth trying to 
> create some sort of distributed cache from the intermediate files the 
> compiler writes out? Load translations dynamically at runtime instead? Or 
> just through more hardware at it :-)
>
> Just curious to hear what others are doing?
>
> Best,
> Alex
>
>

-- 
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/6cdd1d45-7f03-4ed0-88b9-f878cec84e09n%40googlegroups.com.

Re: DominoKit has a new home

['Frank Hossfeld' via GWT Users]

Great work!

Mamta Bansal schrieb am Freitag, 3. November 2023 um 14:25:48 UTC+1:

> Congratulations to the whole team, great work 
>
> On Fri, Nov 3, 2023, 09:06 Andrea Stocchero  wrote:
>
>> well done guys!
>>
>> Il giorno mercoledì 1 novembre 2023 alle 18:31:31 UTC+1 
>> lofid...@gmail.com ha scritto:
>>
>>> Great work! Congrats!
>>>
>>> Vegegoku schrieb am Dienstag, 31. Oktober 2023 um 09:41:19 UTC+1:
>>>
 Exciting news — https://dominokit.com is live! Our new platform stands 
 as a beacon of inclusion, unifying detailed documentation in one 
 centralized location to empower and educate. We invite you to explore this 
 collective reservoir of knowledge, designed to support and inspire. Please 
 help us spread the word by sharing this resource with your network and 
 beyond. Together, we can create a vast community of shared wisdom and 
 resources.

>>> -- 
>> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/74c23d48-1d9b-47f9-b77d-d4e313ba9a96n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/8bcd4fd7-64b3-46f4-bdb8-ebe499c9b59bn%40googlegroups.com.

Re: gwt-maven-springboot-archetype updated ...

['Frank Hossfeld' via GWT Users]

The plugin uses the same input (except for the artifactId) as Thomas 
Broyer's gwt-maven-archetype. 

> One small error, the top level pom.xml has 3 blank lines between every 
XML line.  Just like this:  
https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/clean-modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/pom.xml
  
Easy to fix up, so only a very minor error.

Yeah, that is something annoying. But, no chance to fix it. It seams, it is 
a bug inside the maven 
archetype: https://issues.apache.org/jira/browse/ARCHETYPE-584. Think, we 
have to wait until this one gets fixed.

Craig Mitchell schrieb am Samstag, 6. Januar 2024 um 02:13:46 UTC+1:

Thank you!  I was struggling to get Springboot to work with GWT, and this 
did it beautifully!

One thing I messed up:

> Define value for property 'package' teamdrift: : jar

I thought it meant how did I want to package the output, as I need an 
executable jar, not a war.  But it meant what did I want my Java package to 
be.  lol.

One small error, the top level pom.xml has 3 blank lines between every XML 
line.  Just like this:  
https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/clean-modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/pom.xml
  
Easy to fix up, so only a very minor error.

Thank you for making this awesome tool!

On Tuesday 2 January 2024 at 8:46:30 pm UTC+11 Frank Hossfeld wrote:

Happy new year! I just released a new version of the 
https://github.com/NaluKit/gwt-maven-springboot-archetype. The 
clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) 
with GWT 2.10.0 multi module project. Happy coding!

-- 
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/7ec2d4c3-22b1-4e70-98ea-fcff81e14042n%40googlegroups.com.