you can use Worker.isSupported property to check if workers are
available - i presume that attempting to export a release build ios app
(with workers) will trigger a compiler error while its a beta option.
On 08/11/2013 20:18, Mark Fuqua wrote:
If I write the application using 'workers', will I have to change it for IOS
or will it just be ignored?
Forgive me if this is an ignorant question, I have not done anything with
'workers' to date.
Mark
-----Original Message-----
From: Lee Burrows [mailto:[email protected]]
Sent: Friday, November 08, 2013 2:51 PM
To: [email protected]
Subject: Re: SQLite query vs. Filtering ArrayCollection
My mistake - i thought android was a release feature and ios a beta :(
from air3.9 release notes...
"We haven't forgotten about iOS! Look for news on iOS workers in an upcoming
release (NOTE: this feature will undergo an extended beta period.)"
On 08/11/2013 19:44, Mark Fuqua wrote:
Hmmm...well that's not good. Any other way to keep things working on
the front end?
Is there any indication of when it might be added for IOS?
Mark
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
OmPrakash Muppirala
Sent: Friday, November 08, 2013 2:26 PM
To: [email protected]
Subject: Re: SQLite query vs. Filtering ArrayCollection
On Fri, Nov 8, 2013 at 11:16 AM, Mark Fuqua <[email protected]> wrote:
Thanks Lee...I'm going to try the SQLite way...seems cleaner somehow.
As to workers, I have never used them, but need to with RemoteObject
calls in this same application. I want to do the RemoteObject calls
in the background to avoid having the UI freeze up. Hoping I can find
a good tutorial somewhere...though it is a pretty new topic.
Am I correct in thinking that handing the communication with remote
data over to 'workers' will keep my interface from stalling?
You had mentioned that this is for a mobile app. Do keep in mind that
workers is available only for Android at this point in AIR 3.9 [1]
Thanks,
Om
[1] http://forums.adobe.com/message/5745066
Mark
-----Original Message-----
From: Lee Burrows [mailto:[email protected]]
Sent: Friday, November 08, 2013 2:03 PM
To: [email protected]
Subject: Re: SQLite query vs. Filtering ArrayCollection
i dont think there's a simple answer - it depends on the amount of
data you are dealing with, whether the database is indexed etc. i
would say, the more data to deal with, the more likely that a SQL
call would be quicker (and probably with a lower memory footprint).
to confuse matters, a third option would be to use workers to handle
the filtering in the background.
On 08/11/2013 18:30, Mark Fuqua wrote:
I have a mobile application which gets its data from a SQLite database.
Query results are really fast.
Right now, the application hits the database and converts the result
into an ArrayCollection. I need to allow for filtering the
ArrayCollection.seems like it might be just a quick to hit the
database again with filtering criteria rather than using the
built-in filtering function of the ArrayCollection. Is it
substantially quicker to use a filter function rather than hit the
SQLite database again and loading the result into the same
ArrayCollection?
Mark Fuqua
[email protected]
2301 Mount Carmel Road
Parkton, MD 21120
(410) 215-7356
www.availdata.com
--
Lee Burrows
ActionScripter
--
Lee Burrows
ActionScripter
--
Lee Burrows
ActionScripter
