Re: [gwt-contrib] Re: Porting gwt-i18n module to gwt3

2018-04-07 Thread Ahmad Bawaneh
I also one of those who replaced gwt-i18n with my own implementation which was a simple dictionary like, that loads the labels and messages at runtime, but in my case i didnt need more than plain simple text translation without parameters or anything else. with that said, one of the goals of

Re: [gwt-contrib] Re: Porting gwt-i18n module to gwt3

2018-04-07 Thread Thomas Broyer
On Saturday, April 7, 2018 at 3:03:39 PM UTC+2, Learner Evermore wrote: > > I think I18N is important. However, we never liked or used the GWT 2.x > style of it because it requires dev time knowledge of locales and > multiplies permutations (compile time). It was also inflexible another way >

[gwt-contrib] Re: Naming convention for ported GWT modules

2018-04-07 Thread Thomas Broyer
On Saturday, April 7, 2018 at 6:48:53 PM UTC+2, Jens wrote: > > > Fwiw, I can see zero reason why examples would be published to a Maven >> repo. > > > Well right, although quite a lot projects do so. But maybe just because > examples are part of a multi module project and they just deploy

[gwt-contrib] Re: Naming convention for ported GWT modules

2018-04-07 Thread Jens
> Fwiw, I can see zero reason why examples would be published to a Maven > repo. Well right, although quite a lot projects do so. But maybe just because examples are part of a multi module project and they just deploy everything to maven central. That would even be a stronger argument to

Re: [gwt-contrib] Re: Porting gwt-i18n module to gwt3

2018-04-07 Thread Learner Evermore
I think I18N is important. However, we never liked or used the GWT 2.x style of it because it requires dev time knowledge of locales and multiplies permutations (compile time). It was also inflexible another way - e.g. if a user wants to switch or update the language the code is reloaded as well

[gwt-contrib] Re: Porting gwt-i18n module to gwt3

2018-04-07 Thread Ahmad Bawaneh
a ported version of the gwt-cldr importer and gwt-cldr is now available on github https://github.com/vegegoku/gwt-i18n-cldr https://github.com/vegegoku/gwt-cldr-importer On Friday, January 5, 2018 at 7:33:48 PM UTC+2, Ahmad Bawaneh wrote: > > Dears > I am working on porting the *i18n* module,

[gwt-contrib] Re: Naming convention for ported GWT modules

2018-04-07 Thread Ahmad Bawaneh
Yes, you are right, now both the importer and the cldr repository are available on github The importer : https://github.com/vegegoku/gwt-cldr-importer The gwt-cldr https://github.com/vegegoku/gwt-i18n-cldr the cldr uses the *org.gwtproject.i18n *groupId and *gwt-cldr *as artifactId Your

[gwt-contrib] Re: Naming convention for ported GWT modules

2018-04-07 Thread Thomas Broyer
On Friday, April 6, 2018 at 6:16:50 PM UTC+2, Ahmad Bawaneh wrote: > > Hi > i am working on date pickers for domino-ui, mean while i found that in > order to support different locales in the date picker i need the > DateTimeFormat information for each locale, gwt in the other hand has a >