On Sunday, August 11, 2013 12:02:24 PM UTC+2, Nuno Godinho de Matos wrote: > > It runs the DevMode main class, ture. > But I am quite certain mvn gwt:run is fueling me the compiled javascript. > The project compilation time is huge for making the gecko_1_3 and safari > permutations (since I am testing in both chrome and firefox). > What would be the point of compiling all that java into javascript if the > gwt:run would later not use the compiled javascript. >
It depends on your Maven build. Generally, gwt:compile is attached to the prepare-package phase so that it doesn't run when you only need to compile/process-classes like gwt:run does. > Moreover, if in the module user.agent property I take away the compilation > for gecko, when I load the page with firefox I get alarms that there is no > compiled javascript for my user agent. > If you don't have the ?gwt.codesvr= in your URL then yes it's possible that you're running the compiled JS code served by the DevMode embedded HTTP server. If you want to run in prod mode, better use "mvn jetty:run" though. What i am going to check out first is weather or not the dead weight of the > cell table is not related to the DOM structure of my GWT components tree. > Such as, for example, laying the table within the bootstrap grid model. > Potentially, each of these nested page components that are being used for > layout or whatever else, are all like the cell table implementation crowing > up the application with mouseover, mouseout events. You put the mouse on > top of a cell table row, and there goes a mouse over buble up to kingdom > come. > > I am considering that It is possible that this drag on performance has to > do with a "by default spamming" of dom events. Events running from the > bottom of the DOM tree up to the very top element, all bubbling and lagging > up. > So what I am going to try out this time, is to dump the cell table outside > the overall page layout, so that there aren't any OnWhatever events to > buble up to. > > Let's see if that is is the problem. > And if that is indeed the problem, Christ!, you do have to be ever careful > with most of the gwt components you use cause they just booby trap the html > elements with events you did not even know where being played out for you. > One thing that might help, if you don't need it, is to setSkipRowHoverStyleUpdate(true) and possibly setSkipRowHoverCheck(true) and/or setSkipRowHoverFloatElementCheck(true) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
