[gwt-contrib] Elemental2-1.1.0 released

Hi, We released and pushed to maven central a new version of Elemental2 today: Elemental2-1.1.0. Please refer to the github page for an explanation on how to use it. Summary of fixes/improvements included in this release: - Elemental2 have been generated

Re: [gwt-contrib] Re: Happy to announce general access for J2CL!

I need to fix https://github.com/google/elemental2/issues/68 first I hope to find some time today or tomorrow to make elemental2 repo compliant with the opensource version of j2cl. On Thu, Nov 29, 2018 at 9:34 AM John Huss wrote: > Is there an example bazel WORKSPACE and BUILD file that pulls in

Re: [gwt-contrib] Update on J2CL

10:06 AM Konstantin Solomatov < > konstantin.soloma...@gmail.com> wrote: > >> Are there any updates on J2CL? A lot of time has passed. >> >> On Friday, June 15, 2018 at 3:54:08 AM UTC-4, Julien Dramaix wrote: >>> >>> > 2. J2CL itself is build wit

Re: [gwt-contrib] Update on J2CL

> 2. J2CL itself is build with Bazel (for the reasons you mentioned). This would not matter much, *as long as you could push the J2CL artifacts to Maven Central in an automated (Bazel) pipeline*. *Can Bazel do that*? Yes it can. We are already building jsinterop-base and Elemental2 with Bazel and

Re: [gwt-contrib] Update on J2CL

> I fail to understand why the prerequisite of using bazel was enforced Bazel is enforced if you want to contribute to J2CL not if you want to use it. As Goktug mentioned in his post, J2CL has been built for our internal users first. So it's natural to first integrate it with Bazel as we use it in

Re: [gwt-contrib] Re: The elusive J2CL

I changed the permission settings. You should now be able to apply for membership at https://groups.google.com/forum/#!forum/j2cl-external -Julien On Fri, Jun 1, 2018 at 1:50 PM Alberto Mancini wrote: > Hello Goktug, > thanks a lot for the opportunity. > Actually seems that the address j2cl-ext

Re: [gwt-contrib] Elemental2 1.0 release date

I planned to spend some time on that this quarter but keep in mind it always depends on our internal priorities and workload. On Tue, Apr 3, 2018 at 8:20 AM Paul Stockley wrote: > Any idea when Elemental2 1.0.0 will be released? The RC1 has been out > there for a while now. > > -- > You received

[gwt-contrib] Release candidate of Elemental2 and JsInterop-base.

Hi, I've released the first release candidate of Elemental2 and jsinterop-base today. As usual, elemental2 is split into small jar files: Jar file artifact-id GWT module elemental2-core.jar

[gwt-contrib] Re: Elemental2:1.0.0-beta-3 released

Correction of my previous email: Elemental2:1.0.0-beta-3 is working with the current version of GWT. You don't need to use the HEAD_SNAPSHOT release of GWT. Sorry for the confusion. -Julien On Tue, Dec 5, 2017 at 9:54 AM Julien Dramaix wrote: > I've released a Elemental2

Re: [gwt-contrib] Re: Elemental2:1.0.0-beta-2 released

So I think Thomas is right. One of our change in this new release was to rename toString() method on some objects to avoid confusion with java.lang.Object methods. That broke Elemental with J2CL because java.lang.Object is a JsType in J2CL and we need to lift up some jsinterop restriction to allows

[gwt-contrib] Elemental2:1.0.0-beta-3 released

.0-beta-3 > > > Julien, if you do happen to release an updated beta to solve this, perhaps > also update jsinterop-annotations to 1.0.2, the version that was released > with GWT 2.8.2. > > > > On Wednesday, November 22, 2017 at 7:13:29 PM UTC-6, Julien Dramaix wrote: &g

Re: [gwt-contrib] Re: Elemental2:1.0.0-beta-2 released

happen to release an updated beta to solve this, perhaps > also update jsinterop-annotations to 1.0.2, the version that was released > with GWT 2.8.2. > > > > On Wednesday, November 22, 2017 at 7:13:29 PM UTC-6, Julien Dramaix wrote: >> >> The beta version of Elemental2 usin

[gwt-contrib] Elemental2:1.0.0-beta-2 released

The beta version of Elemental2 using the JsInterop specification has been released on Sonatype today and is available on Maven central. This release should be the last beta release and I expect to release the first RC in few weeks. This release introduces -- among others: - a better granularity

Re: [gwt-contrib] jsinterop-base github repository and new beta release

I'll create a new release of elemental2 next week. Stay tuned. On Friday, November 10, 2017 at 6:13:31 PM UTC-8, Peter Donald wrote: > > Great work - thanks! > > Is this compatible with the last release of elemental2? (IIRC it > was 1.0.0-beta-1) > > On Sat, Nov 11,

[gwt-contrib] jsinterop-base github repository and new beta release

Dear contributors, We've just created a new github repository containing the source code of jsinterop-base: https://github.com/google/jsinterop-base We've also released a new beta version of the library: jsinterop-base:1.0.0-beta-3

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

Roberto is working on a patch needed for Elemental2 (lifting jsinterop restrictions up for native method overloads). I let Roberto give more info on the patch and eta. Julien On Tue, Oct 3, 2017 at 9:12 AM Thomas Broyer wrote: > > > On Tuesday, October 3, 2017 at 12:28:48 PM UTC+2, Colin Alwort

Re: [gwt-contrib] Re: Elemental2 source code on github

I've enabled the issue tab. On Tue, May 30, 2017 at 11:04 PM Daniel Harezlak wrote: > Hi, it looks like issues are disabled for the > https://github.com/google/elemental2 project. > > > On Saturday, May 20, 2017 at 12:34:09 AM UTC+2, Julien Dramaix wrote: > >>

[gwt-contrib] Elemental2 source code on github

The source code of Elemental2 is now available on github: https://github.com/google/elemental2 Please refer to the project README for more information about how to use it. If you have any questions/issues, feel free to open a bug in the github project. Important note: Elemental2 is in beta state

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

I forgot to mention: as a workaround, you can create your own JsFunction callback and cast it to Function: @JsFunction interface MyJsFunction { void onInvoke(); default Function asFunction() { return (Function) this; } } On Tue, May 9, 2017 at 9:37 AM Julien Dramaix wrote: >

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

> I believe it's due to how they're declared in the Closure externs: onreadystatechange and onerror: https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403 vs all the other callbacks: https://github.com/google/closure-compiler/b

Re: [gwt-contrib] auto generation of jsinterop from .d.ts

t 6:52:57 PM UTC-5, Julien Dramaix wrote: > >> We are working internally on a jsinterop generator that can take closure >> extern files and d.ts files as input. >> For the time being only the closure part works fine and we use it to >> generate elemental. We are in the proc

Re: [gwt-contrib] auto generation of jsinterop from .d.ts

We are working internally on a jsinterop generator that can take closure extern files and d.ts files as input. For the time being only the closure part works fine and we use it to generate elemental. We are in the process to opensource it. The d.ts part was an experiment and doesn't work (yet) with

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

good catch! It's a bug in GWT. Roberto is fixing it and will propose a patch for that. On Thu, Apr 6, 2017 at 3:17 PM Jens wrote: > Hmm, I have just built gwt head from source and used the above jars but > SDM tells me: > > Errors in jsinterop/base/Js.java > [ERROR] Line 56: JsProperty 'v

[gwt-contrib] Elemental2 and JsInterop base beta releases available.

; or use the following Maven dependency: com.google.jsinterop base 1.0.0-beta-1 Don’t hesitate to report any bugs, issues, concerns you have on this mailing list. Important note: They are beta releases and future updates (up until the final release) may break code! -Julien -- Ju

Re: [gwt-contrib] Re: Experimental release of Elemental2

me methods rather than fields - > uibinder, cssresource, editors all made assumptions about turning dot > notation into getters (and in the case of editors, setters), and did not > support fields at all as far as I'm aware. This is true of most (though not > all) codegen tools I'

Re: [gwt-contrib] Re: Experimental release of Elemental2

ing that elemental2 was being generated from TypeScript > definitions. If that's true, is there any chance we could get a look at the > generator code too? > > > On Thursday, June 30, 2016 at 1:23:51 AM UTC+1, Julien Dramaix wrote: >> >> A new experimental versi

Re: [gwt-contrib] GSS Resource is Default

We took the decision to set 'CssResource.enableGss' to false to provide a smooth transition/migration to GWT 2.8. If we set the value of the property to true, applications that don't migrate to GSS will stop to compile and that could slow down the migration to GWT 2.8 On Mon, Aug 15, 2016 at 7:05

Re: [gwt-contrib] Experimental release of Elemental2

> > - The API's do not use set/get/is as was the case in the old Elemental. So > how can I now detect that a property is readOnly ? > > > We can probably make it final but if we know it is readonly but I think we are not sure when the field is readonly. Julien? a property flagged as @Const could b

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

The release note is now available on the web site: http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_RC1 - Julien On Fri, Jul 29, 2016 at 11:19 AM Jens wrote: > You should file a bug on the maven plugin issue tracker > https://github.com/gwt-maven-plugin/gwt-maven-plugin > > -- J

Re: [gwt-contrib] Re: Experimental release of Elemental2

This is a bug :) That should be void and not object. On Mon, Jul 4, 2016 at 9:05 PM Jens wrote: > > > - often method signature defines Object as return type while I am pretty >> sure something more concrete would be more appropriate. >> >> if a method "getFoo" can return different types "string

Re: [gwt-contrib] Re: Experimental release of Elemental2

> - only doubles while int would make sense here and there we are aware of that. That should be solved before the first release > - no use of generics and enums generics are used (look at NativeArray ot HtmlCollection). Enums not yet > - no packages. Would be nice to have things like dom, crypto,

Re: [gwt-contrib] Re: Experimental release of Elemental2

> So I guess this is also the reason for why e.g. Int32Array returns double instead of int? yes we just have the information that it's a number, so we convert that to double. We should be able to improve the number conversion before the final release. > Right now, as HTMLCanvasElement.getContext(S

[gwt-contrib] Re: Experimental release of Elemental2

aParseException: > > inconsistent module metadata found. Descriptor: > com.google.gwt:elemental-experimental:2016-06-29 Errors: bad module name: > expected='elemental2-experimental' found='elemental-experimental' > bad version: expected='16-06-30'

[gwt-contrib] Re: Experimental release of Elemental2

yep it's planned On Sunday, July 3, 2016 at 3:13:17 AM UTC+2, Paul Stockley wrote: > > Would it be possible to break the project into a few packages? It would > make it easier to find things. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group.

Re: [gwt-contrib] Re: Experimental release of Elemental2

yes, we are thinking about that. We would like also to add a feature checking system. AFAIC, I think this kind of wrapper code should be part of a separate library using elemental. I would like that elemental stays "close to the metal". But we don't have decided anything yet now. On Saturday,

Re: [gwt-contrib] Re: Experimental release of Elemental2

h simple example how to start using > it. > Regards, > Matic > > On Thursday, June 30, 2016 at 2:23:51 AM UTC+2, Julien Dramaix wrote: >> >> A new experimental version of Elemental2 using the new JsInterop >> specification has been pushed on Sonatype today. >>

[gwt-contrib] Experimental release of Elemental2

A new experimental version of Elemental2 using the new JsInterop specification has been pushed on Sonatype today. You can try it by downloading the jar file

[gwt-contrib] GWT 2.8 RC1 release notes.

Dear contributors, we've started a pull request on github for the GWT 2.8RC1 release note: https://github.com/gwtproject/gwt-site/pull/181 Please review and comment if something is missing. Julien, On behalf of the GWT team. -- You received this message because you are subscribed to the Googl

Re: [gwt-contrib] Re: Elemental2 - What's the big secret?

Elemental is not secret, it is not ready yet... Stay tuned, in few days we should push an experimental version of elemental using JsInterop new specification. - Julien On Thu, Jun 16, 2016 at 1:13 PM Leif Åstrand wrote: > Elemental 2 is a completely new project that is being developed internal

Re: [gwt-contrib] Re: GWT 2.8.0-beta1 available for testing

is completed. > > Juan > > On 7 December 2015 at 11:15, István Horváth wrote: > >> ok, i have PR for this, i hope it fits Google's needs. >> >> 2015. december 7., hétfő 15:47:50 UTC+1 időpontban Julien Dramaix a >> következőt írta: >>> &

Re: [gwt-contrib] Re: GWT 2.8.0-beta1 available for testing

Feel free to fill a patch for that :) On Mon, Dec 7, 2015 at 2:28 PM István Horváth wrote: > it would nice to have if you update the release notes page with exact > dates on all of the version on both the links and the linked details too. > > http://www.gwtproject.org/release-notes.html > > > 20

Re: [gwt-contrib] GWT Maven Samples update for GWT 2.8

GSS is not turned on by default because we want that people migrate to GWT 2.8 without being blocked by the GSS migration. As I said in my previous mail, the compiler is smart enough to choose the right resource file (if both are provided) depending wether GSS is enabled or not. If you find a .css

Re: [gwt-contrib] Samples .css issue?

If you provide both the .css and .gss versions of a file. The GssResourceGenerator is smart enough to use the gss version of the file when gss is enabled even if you specify the css version in the @Source annotation. GSS is still disabled by default, so we have to keep the backward compatibility.

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

>>> >>>> And this for me sums up GWTs main issues going forward. The benefit >>>> before was that existing Java devs could use GWT to work on all the layers >>>> of an application. GWT 3 will force (not a bad thing) Java devs to use >>>> JavaScr

Re: [gwt-contrib] Re: Elemental 2?

. Do you know if Elemental2 will be at all > backwards compatible with Elemental1? I was trying to decide on whether to > use the Elemental1 interfaces for something I'm working on. > > On Fri, Nov 20, 2015 at 9:32 AM 'Julien Dramaix' via GWT Contributors < >

Re: [gwt-contrib] Re: Elemental 2?

Yes I'm currently working on Elemental2 and other intersting stuffs around JsInterop. It's a bit to early to communicate something right now. But you can expect to have more news in one or two months. Julien On Thu, Nov 19, 2015 at 7:04 PM Goktug Gokdogan wrote: > We have been actively working

Re: [gwt-contrib] Re: New JsInterop document

ic shared fields in JsType native interfaces, I think if we >> support static methods we should support static fields as well, or is there >> i any reason to prevent it ?. >> >> On Tue, Nov 10, 2015 at 6:11 PM, Manuel Carrasco Moñino < >> man...@apache.org> wr

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

Thomas gets it all correct. I just want to add one thing: If you are happy with the current GWT stack (uibinder + widget ...), stay with it. As I mentioned during the key notes, the GWT 2.8 will be a long maintenance release and you have now everything you need to do a great web app. Don't try to

Re: [gwt-contrib] Re: New JsInterop document

Method overloading works in native JsType JsType(isNative=true) On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino wrote: > Seems that method overloading is not working anymore with JS_RC mode, it > was working in JS mode though: > > Example: > >boolean validate() >boolean validate(S

Re: [gwt-contrib] Re: New JsInterop document

Create a native JsType (isNative=true) named Promise with namespace set to GLOBAL and define both constructors. It should work. @JsType(isNative = true, namespace = JsPackage.GLOBAL) public class Promise { public Promise(PromiseFn fn){}; } On Mon, Nov 9, 2015 at 2:57 PM Cristian Rinaldi wr

Re: [gwt-contrib] Re: Cannot build GWT anymore locally

it has been updated but the new version is not deployed yet... On Mon, Nov 2, 2015 at 11:49 AM Lars wrote: > Thank your for this information. > We should update this link ( > http://www.gwtproject.org/makinggwtbetter.html#workingoncode) to share > this with all :-) > > -- > You received this mes

Re: [gwt-contrib] Submit an issue destination on Google Code

Done. Julien On Sat, Jul 18, 2015 at 12:52 AM Brandon Donnelson wrote: > Would you like to change the submit an issue link target on Google Code? > > https://code.google.com/p/google-web-toolkit/ > > Thanks, > Brandon > > -- > You received this message because you are subscribed to the Google G

Re: [gwt-contrib] Re: Stop calling it GWT 3.0

> CssResources and such might be a bit more work... we were planning to move to GssResources ... will those remain ? probably not... CssResources will continue to work, the generator can be adapted to use APT api instead of GWT generators. > Widgets ... by switching to GQuery we can avoid widgets

[gwt-contrib] GSS and GWT 2.8

Dear GWT lovers, It has been decided not to turn GSS on by default in GWT 2.8 in order make the migration to the new GWT release simpler and smoother for everyone and let people migrate at their own timeline. You will still have to use the configuration property CssResource.enableGss to enable GS

[gwt-contrib] Errors during GWTTestCase and uibinder

Hi Everyone, Since yesterday, I'm not able to start any GWTTestCase using uibinder, I've got the error below. An idea ? Unexpected exception occurred while parsing HTML snippet org.xml.sax.SAXNotRecognizedException: Feature ' http://cyberneko.org/html/features/scanner/allow-selfclosing-tags' is

Re: [gwt-contrib] Re: GWT Meetup 2015

uld have some new docs, > videos and plugin preview ready to go too. > > Have a good day, > Brandon Donnelson > +Follow Me <https://plus.google.com/u/0/111739836936169749229/posts> > > On Thu, May 7, 2015 at 5:05 AM, Julien Dramaix > wrote: > >> It would be

Re: [gwt-contrib] Re: GWT Meetup 2015

It would be nice to have a status about the Eclipse plugin indeed. IIRC, sessions are recorded so people will be able to watch your session afterwards. On Thu, May 7, 2015 at 7:34 AM Brandon Donnelson wrote: > If folks are interested I could talk about the Eclipse plugin... thoughts? > > -- > Y

Re: [gwt-contrib] Re: Upcoming overhaul to JsInterop annotations in preparation towards v1.0 release

I'm really more in favor of the second options because (in addition to Jens' arguments): - it's more readable to have several meaningful annotations than one with several parameters. And I think it's more Javaish. simple example : @JsIgnore vs @Js(ignore=true) - IMO, the option 1 won't be simpler t

Re: [gwt-contrib] JsInterop retrofit

Hi all, Finally, did you made a decision ? I like very much the *native methods* approach for its simplicity and a test library like PowerMock seems to be able to mock native methods. But Ray seems to have some concerns about using class instead of Interface. So what was the selected approach

Re: [gwt-contrib] JsInterop Questions

FYI, I've tested this morning with the last night's build and now it works fine with sdm. On Wed, Apr 1, 2015 at 9:10 PM Julien Dramaix wrote: > > > If you have JsExport on a class in the first compilation, it works fine > right? > Nope I doesn't work. Even in the

Re: [gwt-contrib] JsInterop Questions

we were suspecting exporting might not be working properly w/ > SDM. We need to write some incremental compilation test to make sure this > works properly before 2.8. > > > On Wed, Apr 1, 2015 at 5:27 AM, Julien Dramaix > wrote: > >> Thanks Goktug ! >> >> That wo

Re: [gwt-contrib] JsInterop Questions

2:07 AM 'Goktug Gokdogan' via GWT Contributors < google-web-toolkit-contributors@googlegroups.com> wrote: > On Tue, Mar 31, 2015 at 2:30 PM, Julien Dramaix > wrote: > >> Dear GWT lovers, >> >> I've finally started to play with JsInterop in GW

[gwt-contrib] JsInterop Questions

Dear GWT lovers, I've finally started to play with JsInterop in GWT 2.7 and mainly I'm trying to use JsInterop in order to write polymer components. So far, I have two questions: 1. I'm using super dev mode and so I'm obliged to use the CrossSiteIframeLinker. As the javascript code generated by

Re: [gwt-contrib] Re: Snapshot repo?

Couldn't we configure sonatype to keep at least the last snapshot even if we don't update the repository (because the build failed) ? On Thu, Mar 19, 2015 at 5:45 PM 'Roberto Lublinerman' via GWT Contributors < google-web-toolkit-contributors@googlegroups.com> wrote: > We are looking into it an

Re: [gwt-contrib] Re: GWT 2.8: Turn GSS on by default

Sorry for my late reply. I'm OK to not remove the code of the old css completely. I will propose another patch for that. > That will the make the upgrade unnecessarily harder I just want to mention that the upgrade can be "hard" because UiBinder's inner style will use GSS by default. And the only

[gwt-contrib] GWT 2.8: Turn GSS on by default

Dear GWT aficionados, It has been decided to make GSS default in GWT 2.8. I think there are two ways to do that: 1. Simply change the configuration property *CssResource.enableGss* to true by default. *Pros*: People can easily disable GSS by changing the config property *Cons*: People can easily

Re: [gwt-contrib] GSS Custom Functions

Hi Jeffrey, Indeed this is a functionality we have to add (I've talked about that in my presentation about GSS at gwt.create) for GWT 2.8. But it's not a good idea to give the possibility to developers to change the behavior of GwtGssFunctionMapProvider by extending it and giving their own imple

Re: [gwt-contrib] Stop Leeeeroy please stop

i.e. any open change that has no Verified label and no negative Code-Review label, and is no older than one week. On Thu, Oct 9, 2014 at 9:42 AM, Julien Dramaix wrote: > Does someone know why Jenkins is posting the same message every 1h30 ? > > Looks at this patch : https://gwt-review.

Re: [gwt-contrib] Documentation sources

git checkout gwt-new-site On Wed Feb 11 2015 at 8:47:39 PM Nicolas Weeger wrote: > Hello. > > > I've updated my gwt-site repository from googlesource to github, but when > running the site locally I don't have the same look as the one on the > gwtproject.org site. > > > I've compiled the GWT cod

Re: [gwt-contrib] Where do I find my password for gerrit?

gt; >>>> I've contributed before, so everything is setup. I just need the >>>> password (Is this not possible?). >>>> >>>> It's a bit too much to ask Windows users to install cygwin, I'll setup >>>> a vm if it's not p

Re: [gwt-contrib] Where do I find my password for gerrit?

Richard, You could find interesting information on how to contribute by reading the documents we've written for the "contributor workshop" at gwtcreate this year: Preparation step for the workshop: http://goo.gl/F4pk0V Workshop slides: https://docs.google.com/presentation/d/11W6b4JCKB3N1-EuaGRORyL

Re: [gwt-contrib] A little change on two http.client.Request modifiers

Hi Danilo, The best is to propose the change by submitting a CL in gerrit and start the discussion there. Julien On Mon Feb 09 2015 at 12:37:01 PM Danilo Reinert wrote: > Currently I'm using the http.client.Request class without the > RequestBuilder for a project I'm working on, and I need to

Re: [gwt-contrib] Re: two errors in master

Jakob, It seems that the dependency to the guava-16.0.1-rebased.jar is missing. You can add it manually, it is located in tools/lib/guava/guava-16.0.1/ On Sat Jan 31 2015 at 9:09:55 AM Jakob Jarosch wrote: > Hi, > I've the same problems compiling the source of gwt. > > With the following steps

Re: [gwt-contrib] Re: GWT 2.8 SnapShot "Unexpected internal compiler error" in SDM after switching to GSS

I don't know if it will solve your problem but the configurationProperty CssResource.legacy is not needed anymore: So remove: On Sat Jan 31 2015 at 12:14:40 AM confile wrote: > It compiles perfectly with GWT 2.7 and GSS. So the problem must be in the > GWT 2.8SnapShot. > > -- > You received th

[gwt-contrib] Documentation site on github

Dear GWT Community, In order to increase the number of contributions on the GWT documentation, we've decided to move the documentation on Github and accept pull requests. We have also spent time to convert all the documentation in markdown syntax. In addition to that, each documentation page has

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

r 2014 23:40:08 UTC+2 schrieb Julien Dramaix: > >> Just to summarize: >> - GSS will be available in GWT 2.7 >> - GSS will use the CssResource interface and your file needs to end with >> the .gss extension >> - GSS will not be enabled by default. To enable it: add &g

Re: [gwt-contrib] Re: Official Gradle plugin

something in > Java. > > On Wed, Dec 10, 2014 at 12:21 PM, Julien Dramaix > wrote: > >> We have a steering committee meeting tonight and this point is on the >> agenda. So you could expect to get feedback very soon. >> >> >> On Wed Dec 10 2014 at 12:55:

Re: [gwt-contrib] Re: Official Gradle plugin

We have a steering committee meeting tonight and this point is on the agenda. So you could expect to get feedback very soon. On Wed Dec 10 2014 at 12:55:41 AM Jens wrote: > Ping. > > Would be great to get some feedback. Currently, the lack of a decision > regarding a new build tool for GWT and t

Re: [gwt-contrib] Website documentation question

I have a big patch (done by Jason Lemay from Arcbees by the way) that I have to push for review converting every files using markdown syntax. And indeed we use html syntax for the header: ## Related frameworks I will push this change in a few weeks but if you want to propose a patch for anything e

Re: [gwt-contrib] Not able to run any GWTTestCase

t; >> This looks awfully a class path issue. Did you ant clean before building? >> >> On Fri, Nov 14, 2014 at 3:06 AM, Julien Dramaix > > wrote: >> >>> I've updated my master branch (of the GWT-core project) the with the

Re: [gwt-contrib] Not able to run any GWTTestCase

and the gwt jar files (user and dev) are there. Am I missing something for the tests ? On Fri Nov 14 2014 at 1:12:02 PM 'Daniel Kurka' via GWT Contributors < google-web-toolkit-contributors@googlegroups.com> wrote: > Deleted all unit caches? > On Nov 14, 2014 1:10 PM, "

Re: [gwt-contrib] Not able to run any GWTTestCase

that area yesterday, can > you try reverting that one? > > On Friday, November 14, 2014, Julien Dramaix > wrote: > >> I've updated my master branch (of the GWT-core project) the with the >> remote and now I'm not able to run any GWT test

[gwt-contrib] Not able to run any GWTTestCase

I've updated my master branch (of the GWT-core project) the with the remote and now I'm not able to run any GWT test cases included in the project. I receive first this error: java.lang.NoSuchFieldError: VOID at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORe

Re: [gwt-contrib] Build gwtproject?

that out shortly. > > > On Wednesday, November 12, 2014 12:06:17 PM UTC-8, Julien Dramaix wrote: > >> yep sure, every improvement is welcome ! >> >> On Wed Nov 12 2014 at 4:41:32 PM Brandon Donnelson >> wrote: >> >>> I did an uploader rewrite a while

Re: [gwt-contrib] Build gwtproject?

Wednesday, November 12, 2014 6:47:12 AM UTC-8, Julien Dramaix wrote: > >> Yes we have to modify the gwt-site-uploader to uplaod the .dtd files. I >> will try to spent some time on that tonight. >> >> On Wed Nov 12 2014 at 3:32:58 PM Thomas Broyer wrote: >> >>>

Re: [gwt-contrib] Build gwtproject?

Yes we have to modify the gwt-site-uploader to uplaod the .dtd files. I will try to spent some time on that tonight. On Wed Nov 12 2014 at 3:32:58 PM Thomas Broyer wrote: > > > On Wednesday, November 12, 2014 11:38:44 AM UTC+1, Jens wrote: >> >> I'm not seeing the http://www.gwtproject.org/docty

Re: [gwt-contrib] 2.7RC1 compiles fine but recompile returns errors

Koen, Could you give us more information about the error (2) ? Does your BaseAdminCssResource use a .css or a .gss file ? Did you enable GSS ? Did you enable the auto conversion ? Could you paste the css line related with the warning message (line 75) ? Thanks, Julien On Friday, November 7,

Re: [gwt-contrib] Cell widgets and GSS

nsition right now they can easily use the converter with these > files and convert them to gss themselves. > I think we want to make that transition once GSS is default (or about to > be default) inside of Google as a testing ground. > > -Daniel > > On Thu, Oct 30, 2014 at 3:51 P

Re: [gwt-contrib] Cell widgets and GSS

n. > We can probably ship the gss files but I think it is optional at this > point. > > On Wed, Oct 29, 2014 at 5:50 AM, Julien Dramaix > wrote: > >> Now that GSS will be shipped in GWT 2.7 as an experimental feature, I'm >> wondering if we shouldn't provid

[gwt-contrib] Cell widgets and GSS

Now that GSS will be shipped in GWT 2.7 as an experimental feature, I'm wondering if we shouldn't provide GSS files for all existing CssResource interfaces present in GWT. The idea is to keep the associated .css files and use them by default but also to provide GSS files in order that people can us

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

tures. > > On Friday, October 24, 2014 4:37:18 AM UTC-4, Thomas Broyer wrote: >> >> >> >> On Thursday, October 23, 2014 11:40:08 PM UTC+2, Julien Dramaix wrote: >>> >>> Just to summarize: >>> - GSS will be available in GWT 2.7 >>>

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

isions). >>> >>> Given that we cannot get rid of the CSS generator in 2.7 and if you >>> think everything would be fine with css/gss mixed together (e.g. with >>> prefixes), I'm totally fine with kicking in-memory conversion out and it is >>> definitely not

Re: [gwt-contrib] Change packaging for GSS

https://gwt-review.googlesource.com/9810 On Sun, Oct 19, 2014 at 12:47 AM, Julien Dramaix wrote: > I will work on that tomorrow > On Oct 18, 2014 8:10 PM, "'Daniel Kurka' via GWT Contributors" < > google-web-toolkit-contributors@googlegroups.com> wrote: > &

Re: [gwt-contrib] Change packaging for GSS

I will work on that tomorrow On Oct 18, 2014 8:10 PM, "'Daniel Kurka' via GWT Contributors" < google-web-toolkit-contributors@googlegroups.com> wrote: > Hi all, > > apparently we ended up packaging gss into gwt-dev instead of gwt-user: > https://gwt-review.googlesource.com/#/c/9803/ > > @Thomas, @

Re: [gwt-contrib] Build gwtproject?

Hi Brandon I will do that this week end ! Just ping me monday if it doesn't work. Julien On Fri, Oct 17, 2014 at 4:34 AM, Brandon Donnelson wrote: > Could gwtproject site be built? > > I'm looking for access to these: > http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd > > Thanks, > Bran

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

e lib > should write the style that both compiles with css and gss or if it is not > feasible then it should extract the resource to a file and follow the two > file approach described above. > > > On Mon, Oct 6, 2014 at 12:54 PM, Julien Dramaix > wrote: > >> > Hmm but s

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

> Hmm but still a bit of work if a library has lots of inline styles and wants to use GSS stuff. If you want to use GSS in all of your inline styles, you have first to convert them to GSS and it will take more time than simply adding an attribute that say that this inline style is using GSS. The p

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

In fact, my question is stupid... If third party library want to use GSS, they just have to use file with .gss extension. For inline UiBinder styles, we can add an attribute useGss="true". On Mon, Oct 6, 2014 at 8:41 PM, Jens wrote: > Oh I forgot to mention that we had decided to use only the

Re: [gwt-contrib] Re: Code for GSS support (GssResource) pushed. Please review.

Oh I forgot to mention that we had decided to use only the CssResource interface and not create a new GssResource interface. And we use the extension of the file in order to know if the file has to be converted or not. On Oct 6, 2014 8:24 PM, "Jens" wrote: > Now I think we should allow the inver

[gwt-contrib] Code for GSS support (GssResource) pushed. Please review.

Hi, I've pushed the code for the so called GssResource. The code has been split in two patches: - The first one contains the code for the converter. The converter can be used in order to convert the existing css files to a GSS compatible file. - The second one contains the code for the generator

  1   2   >