Re: Are GWT widgets "heavy" ?

Thanks for the detailed reply! I'll try out something that will first show the result list with up to 100 or so results and when the user scrolls to the bottom of the list I will append more to the list. On Tuesday, 5 July 2016 18:53:26 UTC+3, Jens wrote: > > I wouldn't call them heavy but I

Re: Are GWT widgets "heavy" ?

Yes, but in this case the element has to be attached to get the correct size, right? So he can't detach-loop-reattach if sizes are important while looping. Or two loops are necessary? btw , here is a list of reflow triggers: https://gist.github.com/paulirish/5d52fb081b3570c81e3a 2016. július

Re: Cascading GWT Application ?

Hi again Pierre, In my experience, having to manage two or more separate GWT applications can be really cumbersome. I'd recommend it only in cases where you have explicitly two or more independent products. In cases where you allow the user to switch from one app to other, or you have a large

Re: Are GWT widgets "heavy" ?

If you make any calls that retrieve the size of an element then this will cause a re-flow even within a javascript block. On Tuesday, July 5, 2016 at 12:36:38 PM UTC-4, fenyoapa wrote: > > "*This causes the browser to recalculate and repaint the page each time >> you append a single search item

Re: Are GWT widgets "heavy" ?

> > "*This causes the browser to recalculate and repaint the page each time > you append a single search item to the DOM*" I think this is true only if he uses some async method that allow the browser to repaint. If not, then the repaint occures only once, when the search results loop

Re: Failed to load resource: xxx.cache.js

On top of that, GWT 2.7 explicitly sets a "modified time" on the nocache.js that doesn't actually reflects neither the time you compiled the project nor the latest modified time of the files used for the compilation (it sets it to the modified time of the gwt.xml file). If you package your app

Re: Failed to load resource: xxx.cache.js

There is a bug in GWT 2.7 for the no cache file having the wrong timestamp and being cached when it shouldn't as a result. We haven't seen this bug when using GWT 2.8-beta1. On Tue, Jul 5, 2016 at 11:58 AM, Jens wrote: > Most likely a caching problem in your browser

Re: Failed to load resource: xxx.cache.js

Most likely a caching problem in your browser (your .nocache.js file is probably cached by the browser and asks for an old permutation). *.cache.* and *.nocache.* must have correct HTTP caching headers. http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching --

Failed to load resource: xxx.cache.js

/Hi! I have upgraded to GWT 2.7 and after compiling a module and deploying it to Tomcat (in Eclipse Neon w Google Plugin v3.9.2), the browser just shows a blank page. And the Console goes: C266D1B0DFB2D9284591DE5B07B0FF9A.cache.js Failed to load resource: the server responded with a status of

Re: Cascading GWT Application ?

> I'm asking myself, is maven can help me ? > No. Most likely something is wrong with your general approach. Check your browsers DevTools if all

Re: Are GWT widgets "heavy" ?

I wouldn't call them heavy but I would not use a widget in cases I don't need events, e.g. taking a UiBinder example: click me 1 click me 2 click me 1 click me 2 In the above you are only interested in events for your labels and all the

Re: What is happening to GWT??? - quarterly or semi-annual releases would be nice!

We vote for quarterly or twice year releases. It doesn't matter if they are feature complete, only that progress is being made and all these other projects like GwtMaterial use them. Nothing like being told when asking about an issue that (to paraphrase) "You are using gwt 2.8, only gwt 2.7 is

gwt material and uibinder + gradle

two dimes: We find Gradle much easier to work with than Maven here at my shop. Especially for "loosely coupled" project dependency setup. We never could get Maven to simply reference other projects arbitrarily. We find Maven is too strict in specifying how projects are connected up with each

Are GWT widgets "heavy" ?

Hello, I've read in a few places that GWT widgets are "heavy" or "expensive". But some of these claims are almost ten years old. With GWT 2.7 and modern web browsers are GWT widgets still considered "expensive"? Our application has long lists of search results which are created using GWT

Re: Cascading GWT Application ?

I'm asking myself, is maven can help me ? -- 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,

Re: GWT and spring security integration,DelegatingFilterProxy has a dead loop

On Tuesday, July 5, 2016 at 1:25:39 PM UTC+3, Alex Luya wrote: > > Does this mean if add added blow to web.xml: > > > > springSecurityFilterChain > > org.springframework.web.filter.DelegatingFilterProxy > > > springSecurityFilterChain > /dp_web/service/* > > > > I must use

Re: GWT and spring security integration,DelegatingFilterProxy has a dead loop

Does this mean if add added blow to web.xml: springSecurityFilterChain org.springframework.web.filter.DelegatingFilterProxy springSecurityFilterChain /dp_web/service/* I must use to configure something in applicationContext.xml? In my case,I removed above stuff from

Cascading GWT Application ?

Hey. My question is simple : is this possible of calling a gwt application into another gwt application. My sample case is simplest as hell, but I can't figure it out what is the best solution to do it : I Would like 3 differents GWT project to deploy them independently : - A first app doing

Re: GWT and spring security integration,DelegatingFilterProxy has a dead loop

On Tuesday, July 5, 2016 at 6:02:38 AM UTC+3, Alex Luya wrote: > > and blow to applicationContext.xml: > > class="org.springframework.web.filter.DelegatingFilterProxy"/> > > > I think this causes recursion. Try to remove this bean declarion. Spring security should internally create bean with