Re: What are the changes done in gwt related to strict csp and how we can code to be in comliance with strict csp policies . #content securoty policy ...
On Thursday, September 21, 2017 at 9:34:01 PM UTC+2, Sahil Aggarwal wrote: > > What are the changes done in gwt related to strict csp and how we can code > to be in comliance with strict csp policies . #content securoty policy ... > > What are techniques or coding guildline for csp . > > Is gwt says that , it is csp compliance . https://gwt-review.googlesource.com/c/gwt/+/19323 should be the final step; but all changes to make GWT compatible with strict CSP are rather recent (in February and May this year), so you'll have to use HEAD-SNAPSHOT for now (or wait 'til 2.8.2 is released) -- 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: elemental.json confusion/error
On Thursday, September 21, 2017 at 11:29:31 AM UTC+2, Vassilis Virvilis wrote: > > Hi, > > On Wed, Sep 20, 2017 at 5:18 PM, Thomas Broyer wrote: > >> >> You might also want to have a look at elemental2-core: >> https://javadoc.io/doc/com.google.elemental2/elemental2-core/1.0.0-beta-1 >> (which BTW defines JSONType.parse(…)), but be careful as Elemental2 is >> entirely generated, and might change in the future as the generator evolves >> (also, Elemental 2 might require that you use the HEAD-SNAPSHOT of GWT) >> >> > Any timeframe on this? I mean on freezing the elemental2. > > I am asking because without this it is impossible to port other libraries > to jsinterop. jquery, datatables, d3 are the most important for me. > > Is the plan to generate everything from typescript files still exists? > Last I heard, Julien Dramaix is currently working on Elemental 2 (more accurately probably the jsinterop-generator and the closure externs). I don't know whether that means a 1.0.0 non-beta release is to be expected soon though. Also, Elemental 2 is a Google project, not a GWT one. (btw, you can probably start porting libraries to Elemental 2, they'll "just" have to be beta until Elemental 2 itself goes out of beta) -- 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
What are the changes done in gwt related to strict csp and how we can code to be in comliance with strict csp policies . #content securoty policy ...
What are the changes done in gwt related to strict csp and how we can code to be in comliance with strict csp policies . #content securoty policy ... What are techniques or coding guildline for csp . Is gwt says that , it is csp compliance . -- 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: elemental.json confusion/error
Hi, On Wed, Sep 20, 2017 at 5:18 PM, Thomas Broyer wrote: > > You might also want to have a look at elemental2-core: https:// > javadoc.io/doc/com.google.elemental2/elemental2-core/1.0.0-beta-1 (which > BTW defines JSONType.parse(…)), but be careful as Elemental2 is entirely > generated, and might change in the future as the generator evolves (also, > Elemental 2 might require that you use the HEAD-SNAPSHOT of GWT) > > Any timeframe on this? I mean on freezing the elemental2. I am asking because without this it is impossible to port other libraries to jsinterop. jquery, datatables, d3 are the most important for me. Is the plan to generate everything from typescript files still exists? Vassilis -- 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: elemental.json confusion/error
> > If you need to parse JSON with a known structure, use JsInterop to > describe that structure (as @JsType(isNative=true, > namespace=JsPackage.GLOBAL, name="*"), or name="Object" if you can't use > name="*"), and then either > com.google.gwt.core.client.JsonUtils.safeEval() with a > cast to your JsInterop interface/class, or JsInterop to call JSON.parse() > (as @JsMethod(namespace="JSON", name="parse") static native T > parseJson(String json)). > If you don't know the structure upfront, then use jsinterop-base's types > instead https://javadoc.io/doc/com.google.jsinterop/base/1.0.0-beta-2 > (JsPropertyMap mostly, and the Js helper class), and the same method for > parsing. You might also want to have a look at elemental2-core: > https://javadoc.io/doc/com.google.elemental2/elemental2-core/1.0.0-beta-1 > (which BTW defines JSONType.parse(…)), but be careful as Elemental2 is > entirely generated, and might change in the future as the generator evolves > (also, Elemental 2 might require that you use the HEAD-SNAPSHOT of GWT) > Thanks for that. I'll look into those solutions. > These are likely bugs, and they're unlikely to ever be fixed (unless maybe > someone provides the patch). > Would do that, but I don't know how those work :/ > The correct way is Json.instance(), one shouldn't ever use any "impl" > class. > That's totally correct. Didn't see it :) -- 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Problem compiling GWT code with Java9
Fwiw, I confirm that HEAD-SNAPSHOT works with Java 9: https://travis-ci.org/tbroyer/gwt-maven-plugin/jobs/277854932 On Wednesday, September 20, 2017 at 10:06:51 AM UTC+2, Thomas Broyer wrote: > > There have been some changes [1,2] to make it (at least partially) work > with a Java 9 VM; you can try HEAD-SNAPSHOT (from > https://oss.sonatype.org/content/repositories/google-snapshots/) until we > release 2.8.2 with the changes. > > [1] > https://github.com/gwtproject/gwt/commit/87f27659af55d7d549521405ef10889e8dfe3f3a > [2] > https://github.com/gwtproject/gwt/commit/5b7560c4bb6376e997981387e4f2feee1816e1dc > > On Wednesday, September 20, 2017 at 9:49:20 AM UTC+2, Pratik Parikh wrote: >> >> does anyone have an update on this sissu? I am running into the same >> problem, so an update would help. >> >> On Tuesday, June 13, 2017 at 12:08:29 PM UTC-4, James Nelson wrote: >>> >>> Hi. >>> >>> I am currently very busy this week, but can try to schedule a push to >>> maven central this weekend (I have other people waiting on it to use >>> various other tools I dabble in as well). >>> >>> Please remind me if I don't post links back here by next Monday. >>> >>> Worst case scenario, I can just upload jars to github and push a gist of >>> the pom I used, with some instructions on how to set the system properties >>> to make it work. >>> >>> I used the IDE to handle vm args, as standard maven plugins are less >>> amenable to hacking / debugging (though I'm sure it must be possible, I did >>> not have enough free time to get that far on it). >>> >>> I'll probably update to latest java 9 spec, since the module system has >>> undergone another iteration since I tried these hacks. >>> >>> Please keep in mind, however, that my fork has diverged from mainline >>> for quite a while, and does not undergo the same rigorous testing that you >>> might expect. >>> In particular, if you start using any of the other features I've added >>> (reflection, arbitrary magic method injection), it can break incremental >>> recompilations. >>> It's a known issue I'm avoiding looking at, since most of the 2.X stack >>> is going to go away, and I have to migrate all my magic into apt-generators >>> to run as a pre-gwtc stage. >>> >>> While I might be able to help you get something that works as a proof of >>> concept, I would urge you to hold off on using it in production, as I am >>> not (yet) ready to offer fulltime support. >>> A couple colleagues and I are playing with the idea of offering fulltime >>> support and maintenance of 2.X around mid-September (barring a funding >>> miracle for our current money-source). >>> >>> So, please take this caveats to heart; I can probably get you up and >>> compiling, but this should all be viewed as experimental and not-production >>> ready for a while yet. >>> >> -- 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
