[gwt-contrib] GWT as OSGI plug-ins

Hi, I am new here and i am not sure if this is the right place for this, but i have made a new design model using the MVP model to simulate OSGI plug-ins for client side GWT code, and i was able to deploy my work inside and OSGI container - i used KARAF. i was able to write my application as a

[gwt-contrib] Re: GWT as OSGI plug-ins

Thank you very much for directions. On Monday, November 9, 2015 at 1:49:18 AM UTC+2, Jens wrote: > > Usually people publish their library/framework on Github along with some > examples/demos and then post it on gwt-users [1] and on G+ [2]. > > -- J > > > [1]

[gwt-contrib] Re: GWT as OSGI plug-ins

, at the end all modules/project are combined and compiled as one unit at run-time. so i think a merge in the future between what i did and what u did could be awesome. On Monday, November 9, 2015 at 4:00:27 AM UTC+2, Cristian Rinaldi wrote: > > Hey Ahmad Bawaneh, > > Currently I'm working

[gwt-contrib] Re: GWT as OSGI plug-ins

once i add my work to github ill post it here. On Sunday, November 8, 2015 at 10:47:37 PM UTC+2, Ahmad Bawaneh wrote: > > Hi, > I am new here and i am not sure if this is the right place for this, but i > have made a new design model using the MVP model to simulate OSGI plug-ins

[gwt-contrib] Re: GWT as OSGI plug-ins

Thank you very much for directing me. On Monday, November 9, 2015 at 1:49:18 AM UTC+2, Jens wrote: > > Usually people publish their library/framework on Github along with some > examples/demos and then post it on gwt-users [1] and on G+ [2]. > > -- J > > > [1]

[gwt-contrib] JsInterop with separate GWT module compilation

Hi All, is there any sample for using JsInterop to make communication between GWT module compiled each on its own? i think this will be a good idea to start implementing client side plugins and modularity. -- You received this message because you are subscribed to the Google Groups "GWT

[gwt-contrib] Re: Last call for GWT 2.8.2 patches, and testers needed!

I would like to test too On Tuesday, October 3, 2017 at 1:28:48 PM UTC+3, Colin Alworth wrote: > > As you can see from https://github.com/gwtproject/gwt/milestone/18, GWT > 2.8.2 is almost ready to go! This release is important to get out for > several reasons: > > * Supports running the

[gwt-contrib] Re: Which API for a future, modern JSON library?

Hi I have been working on an adaptation of gwt-jackson that uses APT instead of generators https://github.com/vegegoku/gwt-jackson-apt now i have plans to support using the same API for both client side and server side and want to consider the JsXxxx types as supported types for

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

Dears I am working on porting the *i18n* module, so far all i did is extract the module and the tests into and external repository and make the tests pass, not real change to the code have been yet. but the *i18n* module is an important module and is being used by so many gwt application so

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

wrong on that. Reusing that .properties format for localized files and > BundleName_locale.properties file name format seems like an express design > goal to me, no matter what other changes happen along the way. > > On Friday, January 5, 2018 at 11:33:48 AM UTC-6, Ahmad Bawaneh wrote: >> >> Dea

[gwt-contrib] Re: Which API for a future, modern JSON library?

I am glad to announce the latest jackson-apt that provide support for using the same mapper instance on both client side and server side, finally you can annotate the type in the shared module and generate a mapper into the shared module and use it in both client code and server code, sample

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

, January 5, 2018 at 7:33:48 PM UTC+2, Ahmad Bawaneh wrote: > > Dears > I am working on porting the *i18n* module, so far all i did is extract > the module and the tests into and external repository and make the tests > pass, not real change to the code have been yet. but th

[gwt-contrib] Updating GWT CLDR data from v25 to v32

Dears I have been working on updating the CLDR data from cldr version 25 to cldr version 32, the generation of the new data have been done successfully and all gwt test cases pass. i would like to make a pull request for both the cldr tools and gwt but first i need to discuss the part related

[gwt-contrib] Re: Updating GWT CLDR data from v25 to v32

Sorry i forgot to link my work to this issue https://github.com/gwtproject/gwt/issues/9557 On Friday, February 2, 2018 at 9:47:59 PM UTC+2, Ahmad Bawaneh wrote: > > Dears > I have been working on updating the CLDR data from cldr version 25 to cldr > version 32, the generation of

[gwt-contrib] Re: Migrating and update gwt-user.jar modules to github.com/gwtproject

Hi the gwt-timer module now is gwt3/j2cl ready i would like to move the module into gwtproject repository but i dont have permissions. the module can be found here for your kind review and approval. https://github.com/vegegoku/gwt-timer Thanks On Friday, January 12, 2018 at 11:58:32 PM UTC+2,

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

knowledge currently presented with generators. so if you have any point/note/suggestion to add i will appreciate that. Thanks On Friday, January 5, 2018 at 7:33:48 PM UTC+2, Ahmad Bawaneh wrote: > > Dears > I am working on porting the *i18n* module, so far all i did is extract >

[gwt-contrib] Re: Updating GWT CLDR data from v25 to v32

s pushed to tools? If not, are we comfortable >> just using the standard CLDR 32 release, so we can fix the out-of-date >> timezones that currently plague GWT? >> >> On Friday, February 2, 2018 at 1:51:18 PM UTC-6, Ahmad Bawaneh wrote: >>> >>> Sorry i forgot

[gwt-contrib] Re: Updating GWT CLDR data from v25 to v32

The update for the latest CLDR data is now on gerrit for review https://gwt-review.googlesource.com/c/gwt/+/20600 On Friday, February 2, 2018 at 9:47:59 PM UTC+2, Ahmad Bawaneh wrote: > > Dears > I have been working on updating the CLDR data from cldr version 25 to cldr >

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

kind review is really appreciated specially for the grade build scripts as i am new to gradle. Thanks On Saturday, April 7, 2018 at 12:34:11 PM UTC+3, Thomas Broyer wrote: > > > > On Friday, April 6, 2018 at 6:16:50 PM UTC+2, Ahmad Bawaneh wrote: >> >> Hi >> i am work

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

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 *i18

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

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

IMO more as > an "experimentation" exploring what can be done than a definitive answer to > how is *should* be done now. > > On Saturday, April 7, 2018 at 8:39:32 PM UTC+2, Ahmad Bawaneh wrote: >> >> I also one of those who replaced gwt-i18n with my own implementation >&g

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

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 decent support for datetime format informtion, so instead of adding my own

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

OK then, this means that gwt-timer should use *org.gtwproject* as group id and *gwt-timer* as artifact id. On Saturday, March 24, 2018 at 11:30:10 AM UTC+2, Mincong Huang wrote: > > Hi, > > I'd like to have a clarification about the naming convention for ported > GWT modules. Because I'm

[gwt-contrib] Re: How can I contribute to GWT?

, 2018 at 10:39:00 AM UTC+1, Ahmad Bawaneh wrote: >> >> Nice to see people asking about this, i went through this before you and >> now i do my small part of contributions because i love GWT i want it to be >> better and i want to help the amazing developer who maint

[gwt-contrib] Re: How can I contribute to GWT?

Nice to see people asking about this, i went through this before you and now i do my small part of contributions because i love GWT i want it to be better and i want to help the amazing developer who maintain and provide us with such stable wonderful library. I was a GWT nop even though i used

[gwt-contrib] Re: Updating GWT CLDR data from v25 to v32

rtant, can you weigh in on how we will >> evaluate the jar before it gets pushed to tools? If not, are we comfortable >> just using the standard CLDR 32 release, so we can fix the out-of-date >> timezones that currently plague GWT? >> >> On Friday, February 2, 2018 a

[gwt-contrib] Re: Updating GWT CLDR data from v25 to v32

, so I have prepared a follow-up patch which will update gwt ICU4J version to 63.1 from the current 50.1.1 the git hub issue for this change is here https://github.com/gwtproject/gwt/issues/8703 On Friday, February 2, 2018 at 9:47:59 PM UTC+2, Ahmad Bawaneh wrote: > > Dears > I ha

[gwt-contrib] Re: Updating GWT CLDR data from v25 to v32

Hi With the PR for the tools being already merged https://github.com/gwtproject/tools/pull/16 I am looking for review and approval on the gwt PR https://gwt-review.googlesource.com/c/gwt/+/21421 Thanks. On Friday, February 2, 2018 at 9:47:59 PM UTC+2, Ahmad Bawaneh wrote: > > Dears &g

[gwt-contrib] GWT 3.0 ready editors porting completed

Hi i would like to announce that i have completed the gwt-editors porting to annotation processor, and now is GWT 3.0 ready. the work was started by both Colin Alworth and Frank Hossfeld thanks for them both for the great work

Re: [gwt-contrib] GWT 3.0 ready editors porting completed

I already made it work with domino-ui <https://github.com/DominoKit/domino-ui>, in domino-ui j2cl-public branch On Friday, November 16, 2018 at 5:46:39 PM UTC+2, Michael Joyner wrote: > > Can this be used with any UI kit? > > On 11/16/18 10:32 AM, Ahmad Bawaneh wrote: >

[gwt-contrib] Template for porting GWT modules

Hi For maven we have a template for ported GWT modules to GWT 3.0 here https://github.com/Vertispan/some-gwt-module It would be realy helpful for gradle experts to provide a template for gradle in order to be consistence. Thanks -- You received this message because you are subscribed to the

[gwt-contrib] What tool generates TimeZoneConstants.properties?

Anyone know what is generating TimeZoneConstants.properties, it says it is generated from CLDR version 25 .. but i cant find any thing that generates this gile in gwt code nor in gwt-tools code, was it generated externally? -- You received this message because you are subscribed to the Google

Re: [gwt-contrib] Re: What tool generates TimeZoneConstants.properties?

ic commentary. >> >> -- >> Colin Alworth >> co...@colinalworth.com >> >> >> >> On Fri, Dec 7, 2018, at 8:32 AM, Thomas Broyer wrote: >> >> >> >> On Friday, December 7, 2018 at 1:54:09 PM UTC+1, Ahmad Bawaneh wrote: &

[gwt-contrib] Re: Template for porting GWT modules

yer wrote: > > Setting a reminder for tomorrow. I'll see what I can do this weekend. > > On Friday, December 7, 2018 at 12:39:52 PM UTC+1, Ahmad Bawaneh wrote: >> >> Hi >> >> For maven we have a template for ported GWT modules to GWT 3.0 here >> https://git

Re: [gwt-contrib] GWT 3.0 ready editors porting completed

This will be very appreciated On Tuesday, November 20, 2018 at 9:45:12 PM UTC+2, ManfredTremmel wrote: > > Thanks a lot. I've planed to start porting gwt-bean-validators on X-Mass > hollyday, this will help a lot. > > Am Freitag, 16. November 2018, 07:32:21 CET schrieb Ahmad B

Re: [gwt-contrib] GWT 3.0 ready editors porting completed

s J2CL ready > or a version requires J2CL tool to the compilation? > > S. > > On Friday, November 16, 2018 at 5:06:46 PM UTC+1, Ahmad Bawaneh wrote: >> >> I already made it work with domino-ui >> <https://github.com/DominoKit/domino-ui>, in domino-ui j2cl-publi

[gwt-contrib] GWT number constants generator ?!!

Dears I am trying to figure out a way to generate and update GWT number constants, looking around i could not find the tool that generates those number constants properties files, they are being generated using an external tool that is not present in the GWT repo. Now since i could not find

[gwt-contrib] Re: Time to require JDK 8?

I also agree to the upgrade and reduce the burden from supporting older java versions, Java is moving faster now and brings new features that are also good to have in GWT world, so focus in supporting those feature rather than supporting very old java versions. On Thursday, April 25, 2019 at

Re: [gwt-contrib] GWT number constants generator ?!!

e = False > for ch in simple_pattern: > if ch == '\'': > in_quote = not in_quote > elif ch == ';' and not in_quote: > global_pattern += ur' \u00a4\u00a4' > global_pattern += ch > global_pattern += ur' \u00a4\u00a4' > return global_pattern