Re: [flexcoders] callLater in a non UI actionscript component (pseudo-threading)
Alex thanks for the tip. I saw your post about pseudo-threading: http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html Then I found this project doing it: http://code.google.com/p/async-threading/downloads/list Do you know that project? Should I use that? Thanks so much! Baz On Wed, Oct 7, 2009 at 9:35 PM, Alex Harui aha...@adobe.com wrote: Calllater is just using enterFrame and render events. If you have any Flex code in the app, you can use Application.application.callLater Alex Harui Flex SDK Developer Adobe Systems Inc. http://www.adobe.com/ Blog: http://blogs.adobe.com/aharui *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On Behalf Of *Baz *Sent:* Wednesday, October 07, 2009 2:32 PM *To:* flexcoders@yahoogroups.com *Subject:* [flexcoders] callLater in a non UI actionscript component (pseudo-threading) I currently have an expensive process that I am pseudo-threading by processing part of it, then using callLater to process the rest. This lets me update the view after each batch is processed, giving the user feedback during the process. Also, it gives the user a window to 'interrupt' the process and change some parameters so that it continues processing the rest of the data with those new paramaters. I would like to move this batch pseudo-threading functionality to my service layer (an AS component) but callLater is a UIComponent function. Is there a way to get similar functionality in a NON-UIComponent component? Is there a better way of going about this? Thank you!
RE: [flexcoders] callLater in a non UI actionscript component (pseudo-threading)
Don't know anything about the google code. Give it a try and see. Alex Harui Flex SDK Developer Adobe Systems Inc.http://www.adobe.com/ Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Baz Sent: Friday, October 09, 2009 8:56 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] callLater in a non UI actionscript component (pseudo-threading) Alex thanks for the tip. I saw your post about pseudo-threading: http://blogs.adobe.com/aharui/2008/01/threads_in_actionscript_3.html Then I found this project doing it: http://code.google.com/p/async-threading/downloads/list Do you know that project? Should I use that? Thanks so much! Baz On Wed, Oct 7, 2009 at 9:35 PM, Alex Harui aha...@adobe.commailto:aha...@adobe.com wrote: Calllater is just using enterFrame and render events. If you have any Flex code in the app, you can use Application.application.callLater Alex Harui Flex SDK Developer Adobe Systems Inc.http://www.adobe.com/ Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com] On Behalf Of Baz Sent: Wednesday, October 07, 2009 2:32 PM To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com Subject: [flexcoders] callLater in a non UI actionscript component (pseudo-threading) I currently have an expensive process that I am pseudo-threading by processing part of it, then using callLater to process the rest. This lets me update the view after each batch is processed, giving the user feedback during the process. Also, it gives the user a window to 'interrupt' the process and change some parameters so that it continues processing the rest of the data with those new paramaters. I would like to move this batch pseudo-threading functionality to my service layer (an AS component) but callLater is a UIComponent function. Is there a way to get similar functionality in a NON-UIComponent component? Is there a better way of going about this? Thank you!
[flexcoders] callLater in a non UI actionscript component (pseudo-threading)
I currently have an expensive process that I am pseudo-threading by processing part of it, then using callLater to process the rest. This lets me update the view after each batch is processed, giving the user feedback during the process. Also, it gives the user a window to 'interrupt' the process and change some parameters so that it continues processing the rest of the data with those new paramaters. I would like to move this batch pseudo-threading functionality to my service layer (an AS component) but callLater is a UIComponent function. Is there a way to get similar functionality in a NON-UIComponent component? Is there a better way of going about this? Thank you!
RE: [flexcoders] callLater in a non UI actionscript component (pseudo-threading)
Calllater is just using enterFrame and render events. If you have any Flex code in the app, you can use Application.application.callLater Alex Harui Flex SDK Developer Adobe Systems Inc.http://www.adobe.com/ Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Baz Sent: Wednesday, October 07, 2009 2:32 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] callLater in a non UI actionscript component (pseudo-threading) I currently have an expensive process that I am pseudo-threading by processing part of it, then using callLater to process the rest. This lets me update the view after each batch is processed, giving the user feedback during the process. Also, it gives the user a window to 'interrupt' the process and change some parameters so that it continues processing the rest of the data with those new paramaters. I would like to move this batch pseudo-threading functionality to my service layer (an AS component) but callLater is a UIComponent function. Is there a way to get similar functionality in a NON-UIComponent component? Is there a better way of going about this? Thank you!
