Re: Screen stays disabled
Is this a modal popup? I guess you’d have to debug why PopUpManager doesn’t remove the modal window. On 6/25/15, 10:33 AM, mark goldin markzolo...@gmail.com wrote: I have a large ADG that takes almost the whole screen. It runs within a module that is fired from a top menu. I am opening a popup (TitleWindow) over the grid. The whole screen becomes disabled. After closing the popup it gets enabled. No code is needed for that kind of functionality. The popup logic can update the server in a way that an event that is triggered t get data will not return any data. At this point I am setting up grid's dataProvider to null and the grid loses all data. So far, so good. A problem is that the screen never become enabled. What would I need to look into to figure it out? Thanks for the help.
A script has executed for longer than ....
I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
In Flex 3, mx.core.Application.application from anywhere should give you access to the Application and thus its stage. In Flex 4, use FlexGlobals.topLevelApplication. -Alex On 6/25/15, 10:59 AM, mark goldin markzolo...@gmail.com wrote: Alex, I need to use it from a command class that does not have systemManager or its stages. How do I go about it? On Thu, Jun 25, 2015 at 11:34 AM Javier Guerrero García javi...@gmail.com wrote: More on that: http://www.jamesward.com/2008/11/21/drunk-on-software-episode-3-performan ce-pitfalls-of-flexs-arraycollection/ On Thu, Jun 25, 2015 at 6:29 PM, Javier Guerrero García javi...@gmail.com wrote: Hi Mark: A long shot here: are you sure that, while you are processing the XML, you're NOT triggering constant UI updates on each operation? For instance: if after processing each XML item, you are adding the final result to an ArrayCollection, and you have some rendering component bound to that ArrayCollection, that could cause a total repaint of the item renderers FOR EACH XML ITEM processed, hence causing the timeout. Something similar happened to me a while ago, and after noticing and solving it, I can say that 60 seconds are more than enough to process a few hundreds of thousand XML items, and unless your XML is REALLY huge that should be enough :) If that applies, the obvious workaround is: 1. Do all your updates and additions on a new ArrayCollection (not on the one bound to the component's dataProvider), and then just swap the dataProvider of the component to point to the newly populated ArrayCollection instead 2. Or call thefunctionthatdisabledautoupdates in advance (don't remember the exact name right now) on the bound arraycollection before starting processing your XML, modify/update your arraycollection items, and then enabling it afterwards. P.S. myCollection.disableAutoUpdate(); , that was it :) http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf668 d2-7fe7.html P.P.S. If none of that applies would some kind of pagination on the UI solve it? On Thu, Jun 25, 2015 at 3:52 PM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
On 6/25/15, 8:17 AM, mark goldin markzolo...@gmail.com wrote: In the threadCompleteHandler function? threadCompleteHandler is called when your callback function returns false. The callback function is a function you pass into PseudoThread. -Alex On Thu, Jun 25, 2015 at 10:03 AM Alex Harui aha...@adobe.com wrote: In the callback function. The callback function would probably process some node and update variables so when it gets called again it knows to process a different node. On 6/25/15, 7:46 AM, mark goldin markzolo...@gmail.com wrote: I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: Insallation de Flex SDK Installer 3.1 dans ubuntu 12.04
The installer isn’t supported on Linux. But yes, the sources for 3.1 assumed yoolab which seems to no longer be functional. The sources for 3.2 are being propagated to the mirrors right now and have a temporary replacement for yoolab. -Alex On 6/25/15, 8:17 AM, Frédéric THOMAS webdoubl...@hotmail.com wrote: Hi, I assumed you want to build the Apache Flex Installer from the sources on Linux. /path/to/apache/flex/sdk refers to a local installation of the Flex SDK as /path/to/air/sdk refers to a local installation of the Adobe AIR SDK. You can download the Flex SDK binary kit from http://flex.apache.org/download-binaries.html The Adobe SDK from http://www.adobe.com/devnet/air/air-sdk-download.html Frédéric THOMAS Date: Thu, 25 Jun 2015 14:45:39 + Subject: Insallation de Flex SDK Installer 3.1 dans ubuntu 12.04 From: azz.d...@gmail.com To: users@flex.apache.org Bonjour, J'ai essayé d'installer Flex SDK Installer 3.1 dans ma machine ubuntu mais le problème est que le serveur projects.yoolab.org est offline. Donc j'ai pas pu exécuté la commande ant [-DFLEX_HOME=/path/to/apache/flex/sdk] [-DAIR_HOME=/path/to/air/sdk] Merci.
RE: A script has executed for longer than ....
In the threadCompleteHandler function? Worker and Pseudo-Worker are low level API from which you can certainly achieve your goal, if you prefer to use an easier Thread like API, you can download an compile https://github.com/doublefx/easyWorker Using it, I would probably create a Thread lib containing only the classes an functions you need, instantiate it at application / module startup or even create a pool of Threads and use it whenever you will receive your data. Frédéric THOMAS From: markzolo...@gmail.com Date: Thu, 25 Jun 2015 15:17:43 + Subject: Re: A script has executed for longer than To: users@flex.apache.org In the threadCompleteHandler function? On Thu, Jun 25, 2015 at 10:03 AM Alex Harui aha...@adobe.com wrote: In the callback function. The callback function would probably process some node and update variables so when it gets called again it knows to process a different node. On 6/25/15, 7:46 AM, mark goldin markzolo...@gmail.com wrote: I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
Can I implement workers if I use Flex 3 with 4.13 SDK? On Thu, Jun 25, 2015 at 10:29 AM Frédéric THOMAS webdoubl...@hotmail.com wrote: In the threadCompleteHandler function? Worker and Pseudo-Worker are low level API from which you can certainly achieve your goal, if you prefer to use an easier Thread like API, you can download an compile https://github.com/doublefx/easyWorker Using it, I would probably create a Thread lib containing only the classes an functions you need, instantiate it at application / module startup or even create a pool of Threads and use it whenever you will receive your data. Frédéric THOMAS From: markzolo...@gmail.com Date: Thu, 25 Jun 2015 15:17:43 + Subject: Re: A script has executed for longer than To: users@flex.apache.org In the threadCompleteHandler function? On Thu, Jun 25, 2015 at 10:03 AM Alex Harui aha...@adobe.com wrote: In the callback function. The callback function would probably process some node and update variables so when it gets called again it knows to process a different node. On 6/25/15, 7:46 AM, mark goldin markzolo...@gmail.com wrote: I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Insallation de Flex SDK Installer 3.1 dans ubuntu 12.04
Bonjour, J'ai essayé d'installer Flex SDK Installer 3.1 dans ma machine ubuntu mais le problème est que le serveur projects.yoolab.org est offline. Donc j'ai pas pu exécuté la commande ant [-DFLEX_HOME=/path/to/apache/flex/sdk] [-DAIR_HOME=/path/to/air/sdk] Merci.
Re: A script has executed for longer than ....
I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
You can also use AS3 Workers. Thanks, Om On Jun 25, 2015 7:46 AM, mark goldin markzolo...@gmail.com wrote: I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
RE: A script has executed for longer than ....
Can I implement workers if I use Flex 3 with 4.13 SDK? If you want to use https://github.com/doublefx/easyWorker, the minimum is Apache Flex 4.13.0 FP 11.5 AIR 3.5, for Flex 3, I guess yes too as the only added class was in core IIRC Frédéric THOMAS From: markzolo...@gmail.com Date: Thu, 25 Jun 2015 15:35:59 + Subject: Re: A script has executed for longer than To: users@flex.apache.org Can I implement workers if I use Flex 3 with 4.13 SDK? On Thu, Jun 25, 2015 at 10:29 AM Frédéric THOMAS webdoubl...@hotmail.com wrote: In the threadCompleteHandler function? Worker and Pseudo-Worker are low level API from which you can certainly achieve your goal, if you prefer to use an easier Thread like API, you can download an compile https://github.com/doublefx/easyWorker Using it, I would probably create a Thread lib containing only the classes an functions you need, instantiate it at application / module startup or even create a pool of Threads and use it whenever you will receive your data. Frédéric THOMAS From: markzolo...@gmail.com Date: Thu, 25 Jun 2015 15:17:43 + Subject: Re: A script has executed for longer than To: users@flex.apache.org In the threadCompleteHandler function? On Thu, Jun 25, 2015 at 10:03 AM Alex Harui aha...@adobe.com wrote: In the callback function. The callback function would probably process some node and update variables so when it gets called again it knows to process a different node. On 6/25/15, 7:46 AM, mark goldin markzolo...@gmail.com wrote: I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
RE: Insallation de Flex SDK Installer 3.1 dans ubuntu 12.04
Hi, I assumed you want to build the Apache Flex Installer from the sources on Linux. /path/to/apache/flex/sdk refers to a local installation of the Flex SDK as /path/to/air/sdk refers to a local installation of the Adobe AIR SDK. You can download the Flex SDK binary kit from http://flex.apache.org/download-binaries.html The Adobe SDK from http://www.adobe.com/devnet/air/air-sdk-download.html Frédéric THOMAS Date: Thu, 25 Jun 2015 14:45:39 + Subject: Insallation de Flex SDK Installer 3.1 dans ubuntu 12.04 From: azz.d...@gmail.com To: users@flex.apache.org Bonjour, J'ai essayé d'installer Flex SDK Installer 3.1 dans ma machine ubuntu mais le problème est que le serveur projects.yoolab.org est offline. Donc j'ai pas pu exécuté la commande ant [-DFLEX_HOME=/path/to/apache/flex/sdk] [-DAIR_HOME=/path/to/air/sdk] Merci.
Re: A script has executed for longer than ....
In the threadCompleteHandler function? On Thu, Jun 25, 2015 at 10:03 AM Alex Harui aha...@adobe.com wrote: In the callback function. The callback function would probably process some node and update variables so when it gets called again it knows to process a different node. On 6/25/15, 7:46 AM, mark goldin markzolo...@gmail.com wrote: I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
In the callback function. The callback function would probably process some node and update variables so when it gets called again it knows to process a different node. On 6/25/15, 7:46 AM, mark goldin markzolo...@gmail.com wrote: I see. Alex, I am looking into the article you have provided. Just a quick question. Where do I put my code to process xml? Because you code is rendering screen I am not sure how to adapt your code to my needs. On Thu, Jun 25, 2015 at 9:33 AM Alex Harui aha...@adobe.com wrote: That sounds like pseudo-threading. You would have to break it up in one frame, handle chunks in separate frames, and assemble in the last frame. With pseudo-threading, you don’t have to break it up and lose parenting and re-assemble, you just keep some state around, and process chunks in each frame. -Alex On 6/25/15, 7:20 AM, mark goldin markzolo...@gmail.com wrote: What if I break xml into pieces for separate processing and then put them together into one final xml? On Thu, Jun 25, 2015 at 9:12 AM Alex Harui aha...@adobe.com wrote: Well, xml is terribly slow. If you can server-side process it into something else (RemoteObject/AMF to ValueObjects is considered to be the fastest, ObjectProxy is also slow, JSON might be fast) then you might be able to process all of the data in 60 seconds in ActionScript. However, if one of your customers happens to be running a virus scan or some other heavy job at the same time, you might find it exceeds 60 seconds anyway. Workers or Pseudo-threading [1] might help you. Also having the server do the processing and send you the results. -Alex [1] http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html On 6/25/15, 6:52 AM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
Hi Mark: A long shot here: are you sure that, while you are processing the XML, you're NOT triggering constant UI updates on each operation? For instance: if after processing each XML item, you are adding the final result to an ArrayCollection, and you have some rendering component bound to that ArrayCollection, that could cause a total repaint of the item renderers FOR EACH XML ITEM processed, hence causing the timeout. Something similar happened to me a while ago, and after noticing and solving it, I can say that 60 seconds are more than enough to process a few hundreds of thousand XML items, and unless your XML is REALLY huge that should be enough :) If that applies, the obvious workaround is: 1. Do all your updates and additions on a new ArrayCollection (not on the one bound to the component's dataProvider), and then just swap the dataProvider of the component to point to the newly populated ArrayCollection instead 2. Or call thefunctionthatdisabledautoupdates in advance (don't remember the exact name right now) on the bound arraycollection before starting processing your XML, modify/update your arraycollection items, and then enabling it afterwards. P.S. myCollection.disableAutoUpdate(); , that was it :) http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf668d2-7fe7.html P.P.S. If none of that applies would some kind of pagination on the UI solve it? On Thu, Jun 25, 2015 at 3:52 PM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Screen stays disabled
I have a large ADG that takes almost the whole screen. It runs within a module that is fired from a top menu. I am opening a popup (TitleWindow) over the grid. The whole screen becomes disabled. After closing the popup it gets enabled. No code is needed for that kind of functionality. The popup logic can update the server in a way that an event that is triggered t get data will not return any data. At this point I am setting up grid's dataProvider to null and the grid loses all data. So far, so good. A problem is that the screen never become enabled. What would I need to look into to figure it out? Thanks for the help.
Re: A script has executed for longer than ....
More on that: http://www.jamesward.com/2008/11/21/drunk-on-software-episode-3-performance-pitfalls-of-flexs-arraycollection/ On Thu, Jun 25, 2015 at 6:29 PM, Javier Guerrero García javi...@gmail.com wrote: Hi Mark: A long shot here: are you sure that, while you are processing the XML, you're NOT triggering constant UI updates on each operation? For instance: if after processing each XML item, you are adding the final result to an ArrayCollection, and you have some rendering component bound to that ArrayCollection, that could cause a total repaint of the item renderers FOR EACH XML ITEM processed, hence causing the timeout. Something similar happened to me a while ago, and after noticing and solving it, I can say that 60 seconds are more than enough to process a few hundreds of thousand XML items, and unless your XML is REALLY huge that should be enough :) If that applies, the obvious workaround is: 1. Do all your updates and additions on a new ArrayCollection (not on the one bound to the component's dataProvider), and then just swap the dataProvider of the component to point to the newly populated ArrayCollection instead 2. Or call thefunctionthatdisabledautoupdates in advance (don't remember the exact name right now) on the bound arraycollection before starting processing your XML, modify/update your arraycollection items, and then enabling it afterwards. P.S. myCollection.disableAutoUpdate(); , that was it :) http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf668d2-7fe7.html P.P.S. If none of that applies would some kind of pagination on the UI solve it? On Thu, Jun 25, 2015 at 3:52 PM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
Re: A script has executed for longer than ....
Alex, I need to use it from a command class that does not have systemManager or its stages. How do I go about it? On Thu, Jun 25, 2015 at 11:34 AM Javier Guerrero García javi...@gmail.com wrote: More on that: http://www.jamesward.com/2008/11/21/drunk-on-software-episode-3-performance-pitfalls-of-flexs-arraycollection/ On Thu, Jun 25, 2015 at 6:29 PM, Javier Guerrero García javi...@gmail.com wrote: Hi Mark: A long shot here: are you sure that, while you are processing the XML, you're NOT triggering constant UI updates on each operation? For instance: if after processing each XML item, you are adding the final result to an ArrayCollection, and you have some rendering component bound to that ArrayCollection, that could cause a total repaint of the item renderers FOR EACH XML ITEM processed, hence causing the timeout. Something similar happened to me a while ago, and after noticing and solving it, I can say that 60 seconds are more than enough to process a few hundreds of thousand XML items, and unless your XML is REALLY huge that should be enough :) If that applies, the obvious workaround is: 1. Do all your updates and additions on a new ArrayCollection (not on the one bound to the component's dataProvider), and then just swap the dataProvider of the component to point to the newly populated ArrayCollection instead 2. Or call thefunctionthatdisabledautoupdates in advance (don't remember the exact name right now) on the bound arraycollection before starting processing your XML, modify/update your arraycollection items, and then enabling it afterwards. P.S. myCollection.disableAutoUpdate(); , that was it :) http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf668d2-7fe7.html P.P.S. If none of that applies would some kind of pagination on the UI solve it? On Thu, Jun 25, 2015 at 3:52 PM, mark goldin markzolo...@gmail.com wrote: I have a large xml data that UI needs to process. I am getting the above message about timing out. Not sure I can break my function into smaller pieces. Any other idea? Thanks
