Re: [qooxdoo-devel] qooxdoo: your script is running too slowly.....
> The demos are in the demobrowser, e.g., here: > http://demo.qooxdoo.org/devel/demobrowser/#virtual~List.html And running within the demobrowser, there is a "JS Code" button in the top right corner to view the source code, in case you missed it. T. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo: your script is running too slowly.....
On Fri, Nov 12, 2010 at 14:31, Ken MacDonald wrote: > Thanks, T & Tino, for the tips and links on timeouts. The virtual List you > mention sounds interesting, but the demo link below only shows the demo but > no code, and I didn't see it in the API. Is there a code link available? > qx.ui.virtual.* is still bleeding-edge code. I'm not sure whether it's ready for production use, nor if the API is considered stable or whether the API could change at any time. Martin is working on it as he as time, I believe, and some people are using it out in the wild. It'd be great to get more users of it for experience sake; just be forewarned. That whole set of widgets will be a huge win for qooxdoo once it's completed. Maybe Martin can comment on the API stability. The demos are in the demobrowser, e.g., here: http://demo.qooxdoo.org/devel/demobrowser/#virtual~List.html Derrell -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo: your script is running too slowly.....
Thanks, T & Tino, for the tips and links on timeouts. The virtual List you
mention sounds interesting, but the demo link below only shows the demo but
no code, and I didn't see it in the API. Is there a code link available?
Ken
On Fri, Nov 12, 2010 at 12:36 PM, Tino Butz wrote:
> Hi,
>
> Thomas is right. You should process only some ListItems and than add an
> timeout, e.g.:
>
> window.setTimeout(function() {
> goOnProcessing(currentIndex);
> },0);
>
> IE shows a long running script warning, when too much statements were
> executed. You can find more information on this subject in the following
> article:
>
>
> http://www.nczonline.net/blog/2009/01/05/what-determines-that-a-script-is-long-running/
>
> I would recommend that you use a virtual list and only render the items in
> the current viewport:
>
>
> http://demo.qooxdoo.org/current/demobrowser/demo/virtual/List.html?qx.theme=qx.theme.Modern
>
> Best regards,
> Tino
>
>
>
>
> http://www.nczonline.net/blog/2009/01/05/what-determines-that-a-script-is-long-running/
>
> Am 12.11.2010 um 18:15 schrieb thron7:
>
> > i know there are people with much more ie experience on the list. but to
> > me it sounds like incremental update and giving some breath to the
> > browser through setTimeout-style programming could be the cure.
> >
> > i recommend you to the Progressive widget in the framework. run this in
> > your ie and see how it feels:
> >
> >
> http://demo.qooxdoo.org/current/demobrowser/index.html#progressive~ProgressiveLoader.html
> >
> > t.
> >
> > On 11/12/2010 05:53 PM, Ken MacDonald wrote:
> >> We have to support IE for customers, and frequently we get this
> >> complaint box where IE thinks the .js is probably caught in an endless
> >> loop and asks the user if they want to kill the script or continue.
> >> Well, we're aren't stuck, it's just that IE's js engine is about 8-10x
> >> slower than Firefox. I'm looking for some way to reduce or eliminate
> >> this. Suggestions welcome!
> >>
> >> In one particularly bothersome case, we do a big DB query and then
> >> process a display out of the results. The query comes back within a
> >> second or so, then IE takes about 20 seconds to render the display of
> >> the info (Firefox - 2 seconds). The display contains on average 20 Lists
> >> arranged in a Grid, a couple labels and buttons, and perhaps 900
> >> ListItems divided between the Lists.
> >>
> >> A couple of things I've considered:
> >> 1) Use Tables instead of Lists for the display - anyone have a feel for
> >> whether the rendering would go more quickly?
> >>
> >> 2) Is there any way to let good ol' IE know that we are still alive,
> >> maybe some kind of signal that I could fire every 50 ListItems or so?
> >>
> >> 3) Similar to 2, is there a way to force the page to display, perhaps
> >> after each List is filled - maybe that would convince IE that we haven't
> >> died on it? (Actually, the Lists are all "collapsed" until they are are
> >> filled, then I make them visible - if I made them visible through the
> >> whole process, would that help?)
> >>
> >> 4) Once this thing is rendered and displayed, if I hit the IE 'refresh'
> >> button, I get the "script running slowly" prompt again! Apparently the
> >> page teardown and garbage collection is too slow for it as well. I have
> >> no idea how to fix that.
> >>
> >> Thanks for any ideas!
> >> Ken
> >>
> >>
> >>
> >>
> --
> >> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> >> Simplifying enterprise desktop deployment and management using
> >> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> >> client virtualization framework. Read more!
> >> http://p.sf.net/sfu/dell-eql-dev2dev
> >>
> >>
> >>
> >> ___
> >> qooxdoo-devel mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> >
> >
> --
> > Centralized Desktop Delivery: Dell and VMware Reference Architecture
> > Simplifying enterprise desktop deployment and management using
> > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> > client virtualization framework. Read more!
> > http://p.sf.net/sfu/dell-eql-dev2dev
> > ___
> > qooxdoo-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
>
> --
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
Re: [qooxdoo-devel] qooxdoo: your script is running too slowly.....
Hi,
Thomas is right. You should process only some ListItems and than add an
timeout, e.g.:
window.setTimeout(function() {
goOnProcessing(currentIndex);
},0);
IE shows a long running script warning, when too much statements were executed.
You can find more information on this subject in the following article:
http://www.nczonline.net/blog/2009/01/05/what-determines-that-a-script-is-long-running/
I would recommend that you use a virtual list and only render the items in the
current viewport:
http://demo.qooxdoo.org/current/demobrowser/demo/virtual/List.html?qx.theme=qx.theme.Modern
Best regards,
Tino
http://www.nczonline.net/blog/2009/01/05/what-determines-that-a-script-is-long-running/
Am 12.11.2010 um 18:15 schrieb thron7:
> i know there are people with much more ie experience on the list. but to
> me it sounds like incremental update and giving some breath to the
> browser through setTimeout-style programming could be the cure.
>
> i recommend you to the Progressive widget in the framework. run this in
> your ie and see how it feels:
>
> http://demo.qooxdoo.org/current/demobrowser/index.html#progressive~ProgressiveLoader.html
>
> t.
>
> On 11/12/2010 05:53 PM, Ken MacDonald wrote:
>> We have to support IE for customers, and frequently we get this
>> complaint box where IE thinks the .js is probably caught in an endless
>> loop and asks the user if they want to kill the script or continue.
>> Well, we're aren't stuck, it's just that IE's js engine is about 8-10x
>> slower than Firefox. I'm looking for some way to reduce or eliminate
>> this. Suggestions welcome!
>>
>> In one particularly bothersome case, we do a big DB query and then
>> process a display out of the results. The query comes back within a
>> second or so, then IE takes about 20 seconds to render the display of
>> the info (Firefox - 2 seconds). The display contains on average 20 Lists
>> arranged in a Grid, a couple labels and buttons, and perhaps 900
>> ListItems divided between the Lists.
>>
>> A couple of things I've considered:
>> 1) Use Tables instead of Lists for the display - anyone have a feel for
>> whether the rendering would go more quickly?
>>
>> 2) Is there any way to let good ol' IE know that we are still alive,
>> maybe some kind of signal that I could fire every 50 ListItems or so?
>>
>> 3) Similar to 2, is there a way to force the page to display, perhaps
>> after each List is filled - maybe that would convince IE that we haven't
>> died on it? (Actually, the Lists are all "collapsed" until they are are
>> filled, then I make them visible - if I made them visible through the
>> whole process, would that help?)
>>
>> 4) Once this thing is rendered and displayed, if I hit the IE 'refresh'
>> button, I get the "script running slowly" prompt again! Apparently the
>> page teardown and garbage collection is too slow for it as well. I have
>> no idea how to fix that.
>>
>> Thanks for any ideas!
>> Ken
>>
>>
>>
>> --
>> Centralized Desktop Delivery: Dell and VMware Reference Architecture
>> Simplifying enterprise desktop deployment and management using
>> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
>> client virtualization framework. Read more!
>> http://p.sf.net/sfu/dell-eql-dev2dev
>>
>>
>>
>> ___
>> qooxdoo-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> --
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
> http://p.sf.net/sfu/dell-eql-dev2dev
> ___
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo: your script is running too slowly.....
i know there are people with much more ie experience on the list. but to me it sounds like incremental update and giving some breath to the browser through setTimeout-style programming could be the cure. i recommend you to the Progressive widget in the framework. run this in your ie and see how it feels: http://demo.qooxdoo.org/current/demobrowser/index.html#progressive~ProgressiveLoader.html t. On 11/12/2010 05:53 PM, Ken MacDonald wrote: > We have to support IE for customers, and frequently we get this > complaint box where IE thinks the .js is probably caught in an endless > loop and asks the user if they want to kill the script or continue. > Well, we're aren't stuck, it's just that IE's js engine is about 8-10x > slower than Firefox. I'm looking for some way to reduce or eliminate > this. Suggestions welcome! > > In one particularly bothersome case, we do a big DB query and then > process a display out of the results. The query comes back within a > second or so, then IE takes about 20 seconds to render the display of > the info (Firefox - 2 seconds). The display contains on average 20 Lists > arranged in a Grid, a couple labels and buttons, and perhaps 900 > ListItems divided between the Lists. > > A couple of things I've considered: > 1) Use Tables instead of Lists for the display - anyone have a feel for > whether the rendering would go more quickly? > > 2) Is there any way to let good ol' IE know that we are still alive, > maybe some kind of signal that I could fire every 50 ListItems or so? > > 3) Similar to 2, is there a way to force the page to display, perhaps > after each List is filled - maybe that would convince IE that we haven't > died on it? (Actually, the Lists are all "collapsed" until they are are > filled, then I make them visible - if I made them visible through the > whole process, would that help?) > > 4) Once this thing is rendered and displayed, if I hit the IE 'refresh' > button, I get the "script running slowly" prompt again! Apparently the > page teardown and garbage collection is too slow for it as well. I have > no idea how to fix that. > > Thanks for any ideas! > Ken > > > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > > > > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
