Re: chrome 53 styleSheet insertRule not working

[fenyoapa]

I solved it by not storing the sheet in a gwt JavaScriptObject field but 
always get it with a native js method: styleElement.sheet.


-- 
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: chrome 53 styleSheet insertRule not working

[fenyoapa]

<https://lh3.googleusercontent.com/-Y7rENNP-5_M/V9KNXG8zcTI/Bu4/8MZSvGya7x0rezwecQUSd507_HmW0EeHwCLcB/s1600/ff_sty_1.jpg>

<https://lh3.googleusercontent.com/-cEsfGqPe39U/V9KNorjMAhI/Bu8/mUNtpus0cwQpG0FBs1IVYybf2vlenHR5QCLcB/s1600/chrome_sty_1.jpg>

<https://lh3.googleusercontent.com/-Po31RfmdZNs/V9KNqten0SI/BvA/gKGC5Af_lvQp0rBK2KArzVsRNfJBDzS5wCLcB/s1600/chrome_sty_2.jpg>


it is just one example


2016. szeptember 9., péntek 11:55:34 UTC+2 időpontban Thomas Broyer a 
következőt írta:
>
> Works for me (from the devtools console, but still).
> 53.0.2785.101 (64-bit) on Ubuntu 16.04.
>
> On Friday, September 9, 2016 at 11:41:12 AM UTC+2, fenyoapa wrote:
>>
>> hi,
>> it is maybe not a gwt issue, but it is in a gwt app.
>> This code snippet worked for years:
>>
>>
>> *$doc.styleSheets[0].insertRule('.aclassname { color:red;}', 0);*
>> but now in chrome 53.0.2785.101 m (64-bit) not work (css rules not 
>> applied)
>> It is working in FF/IE too, and worked in chrome 52.
>>
>

-- 
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: chrome 53 styleSheet insertRule not working

[fenyoapa]

2016. szeptember 9., péntek 11:41:12 UTC+2 időpontban fenyoapa a következőt 
írta:
>
> hi,
> it is maybe not a gwt issue, but it is in a gwt app.
> This code snippet worked for years:
>
>
> *$doc.styleSheets[0].insertRule('.aclassname { color:red;}', 0);*
> but now in chrome 53.0.2785.101 m (64-bit) not work (css rules not applied)
> It is working in FF/IE too, and worked in chrome 52.
>

-- 
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.

chrome 53 styleSheet insertRule not working

[fenyoapa]

hi,
it is maybe not a gwt issue, but it is in a gwt app.
This code snippet worked for years:


*$doc.styleSheets[0].insertRule('.aclassname { color:red;}', 0);*
but now in chrome 53.0.2785.101 m (64-bit) not work (css rules not applied)
It is working in FF/IE too, and worked in chrome 52.

-- 
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: Are GWT widgets "heavy" ?

[fenyoapa]

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 5., kedd 19:20:36 UTC+2 időpontban Paul Stockley a következőt 
írta:
>
> 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 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 finished
>>
>> 2016. július 5., kedd 17:53:26 UTC+2 időpontban Jens a következőt írta:
>>>
>>> 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 FlowPanels do not provide real value. IF you are familiar with HTML and 
>>> CSS then you could use
>>>
>>> 
>>>   
>>> 
>>>click me 1
>>>click me 2
>>> 
>>> 
>>>click me 1
>>>click me 2
>>> 
>>>   
>>> 
>>>
>>> The above uses less DOM operations to build the UI and needs less memory 
>>> because there are fewer JavaScript objects pointing to DOM elements (= less 
>>> GWT widgets).
>>>
>>> Some side notes: 
>>>
>>>- When you build a large list of widgets as in your search result, 
>>>then do not append all the search result entries to a container in a 
>>>for-loop if that container is already attached to the DOM. This causes 
>>> the 
>>>browser to recalculate and repaint the page each time you append a 
>>> single 
>>>search item to the DOM. Instead detach the container, fill it with the 
>>>search results and then attach it again (or create a new container and 
>>>replace the old one).
>>>- Use pagination
>>>- If you can't use pagination for any reason, consider only render 
>>>the items that are visible. If you have 1000 search results but only 20 
>>> are 
>>>visible in the scroll panel, then only render 40 or so and render 
>>>additional entries when the user scrolls to them.
>>>- Only show the top 20 search results and add a "show more" button 
>>>or let users redefine their search until their desired result is in the 
>>> top 
>>>20.
>>>
>>>
>>> Basically if your list is so long that it starts to get slow then you 
>>> most likely have a general usability/UI problem because nobody will scroll 
>>> through such long lists anyways.
>>>
>>> -- J.
>>>
>>

-- 
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: Are GWT widgets "heavy" ?

[fenyoapa]

>
> "*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 finished

2016. július 5., kedd 17:53:26 UTC+2 időpontban Jens a következőt írta:
>
> 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 
> FlowPanels do not provide real value. IF you are familiar with HTML and CSS 
> then you could use
>
> 
>   
> 
>click me 1
>click me 2
> 
> 
>click me 1
>click me 2
> 
>   
> 
>
> The above uses less DOM operations to build the UI and needs less memory 
> because there are fewer JavaScript objects pointing to DOM elements (= less 
> GWT widgets).
>
> Some side notes: 
>
>- When you build a large list of widgets as in your search result, 
>then do not append all the search result entries to a container in a 
>for-loop if that container is already attached to the DOM. This causes the 
>browser to recalculate and repaint the page each time you append a single 
>search item to the DOM. Instead detach the container, fill it with the 
>search results and then attach it again (or create a new container and 
>replace the old one).
>- Use pagination
>- If you can't use pagination for any reason, consider only render the 
>items that are visible. If you have 1000 search results but only 20 are 
>visible in the scroll panel, then only render 40 or so and render 
>additional entries when the user scrolls to them.
>- Only show the top 20 search results and add a "show more" button or 
>let users redefine their search until their desired result is in the top 
> 20.
>
>
> Basically if your list is so long that it starts to get slow then you most 
> likely have a general usability/UI problem because nobody will scroll 
> through such long lists anyways.
>
> -- J.
>

-- 
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: GWT can not run on Tomcat

[fenyoapa]

>
> I'm running gwt under tomcat in MyEclipse. Maybe you did not set the 
> "output folder":
>


 

-- 
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: Petition for a standalone Chome installer allowing DevMode

[fenyoapa]

It is very needful, and not only on chrome but on latest FF.

-- 
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/d/optout.

Re: Code Splitting with Factory usage?

[fenyoapa]

Hi, here are two links you should read:
http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html
http://www.javabeat.net/2011/11/code-splitting-in-gwt/#

You are interested on this:

To obtain a compile report for your application, simply compile your 
application with the -compileReport option added. Your application should 
then have an output directory named compileReport. Open index.html in that 
directory to view a Compile Report for your application.

In the report you will see the answer to your question.

-F

2013. szeptember 23., hétfő 14:13:38 UTC+2 időpontban Ed a következőt írta:

 I have a global Factory class to create instances.
 I have a code split A and code split B that both use this Factory to 
 create instance A1 that is only used in A and instance B1 that is only used 
 in B.

 Will code for object  A1 also end up in split point B, and code for object 
 B1 als end up in split point A? Or is the GWT compiler smart enough to 
 detect it's usage and ensure that code A1 is only present in split point A, 
 and code B1 is only present in split point B?

 I think so, but got my doubts, as the Factory is shared  between both 
 split points, and it also shows up in the SOYC report.
 - Ed



-- 
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.

Re: RPC AsyncCallback freezes chrome

[fenyoapa]

Sorry I can't, It runs behind a VPN in a special environment and it is 
property of our customer..

2013. július 2., kedd 22:07:53 UTC+2 időpontban Ed a következőt írta:

 Can you please isolate your problem in a stand alone gwt app?
 If it then still occurs, could you please submit it as an gwt issue in the 
 issue tracker?
 Thanks.


-- 
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.

Re: RPC AsyncCallback freezes chrome

[fenyoapa]

Ok, then I don't understand what do you mean on isolate your problem in a 
stand alone gwt app. I can provide short code snippets (as I did above) 
but I can't provide a working gwt app with which the problem can be seen 
because of the points I wrote. Or, maybe I can package the whole app and 
send, but I guess you don't thought that. Can you please help me how to 
help you in order to you will be able to help me...

2013. július 6., szombat 14:31:42 UTC+2 időpontban Ed a következőt írta:

  Sorry I can't, It runs behind a VPN in a special environment and it is 
 property of our customer..
 Why not?
 I just make your own gwt app that shows the issue  (no client code, no 
 vpn).
 I don't understand what this has to do with vpn or customer code?



-- 
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.

RPC AsyncCallback freezes chrome

[fenyoapa]

Hi, I wrote this in the issue tracker but I was redirected to here.

Found in GWT Release (2.5.1, 2.5.0.rc1)

Encountered on OS / Browser (Win7, Google Chrome):


Detailed description:

Dear folks,

we have a complex and large gwt app with many rpc calls.
In Google Chrome, there are some rpc call that freezes the browser's thread, 
cpu runs at 13%, and the page does not respond anymore, only closing the page 
helps. It happens only in Chrome (not in Firefox), and only in production mode 
with compiled gwt code (it works well in dev mode). The rpc call initiated 
properly, the server responds some data (data from an Oracle db), but neither 
of onSuccess nor onFailure is called, but Chrome freezes.
In Network tab of Chrome I see the call with status code 200, but the 
Preview and the Response tabs are empty despite of the server sends back 
the data (I see it in a log).


Shortest code snippet which demonstrates issue (please indicate whereactual 
result differs from expected result):

MxServiceAsync svc = GWT.create(MxService.class);  //fine
svc.frameRPC(nb, new AsyncCallbackNucleusBean() {//fine
public void onFailure(Throwable t) {
t.printStackTrace();   //never called
}
public void onSuccess(NucleusBean result) {
System.out.println(result);//never called
}
});



Workaround if you have one: NONE


In Fiddler network monitor I can see the response (correct data) from the 
server (Apache Tomcat).

ANY help or advise is appreciated!

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.