On Wed, Apr 8, 2009 at 11:01 AM, Marcel Weiher wrote:
> Heck, Google does it with Chrome, so
> it must be good, right? ;-)
If they continue this in Chrome for the Mac, I expect it will go
nowhere. Chrome's adoption consists largely of, and is entirely due
to, technically-savvy early adopters. T
On Apr 5, 2009, at 14:59 , Andrew Farmer wrote:
On 05 Apr 09, at 08:17, Michael Ash wrote:
On Sun, Apr 5, 2009 at 9:33 AM, Kirk Kerekes
wrote:
[Use a separate process instead of a separate thread]
I recommend avoiding this if possible. Processes are a somewhat
scarce
resource on OS X (
David:
Thanks for all your help, it's almost working... Just one more question:
Question: I am attempting to "turn" the object returned into a NSDictionary,
but it doesn't seem like something that can be turned into a NSDictionary.
Am I doing something wrong here? The file is a plist file.
Si
> 1. Is there any concern of thread safety using this class?
> 2. How can I pass NSFileHandle the file URL of my files?
> 3. How could I create a method that will take the contents of the file and
> do something with them?
1. No. NSFIleHandle takes care of creating a separate thread for you,
and n
On 05 Apr 09, at 08:17, Michael Ash wrote:
On Sun, Apr 5, 2009 at 9:33 AM, Kirk Kerekes wrote:
Along with threads and various asynchronous techniques already
mentioned,
you should also consider creating a separate UI-less "foundation
tool" to
perform your lengthy task, controlled with NSTask
Dear Kirk:
While I probably won't be using that in my current project, it sounds like a
good idea and I will probably look into it if I ever have a need...
On 4/5/09 6:33 AM, "Kirk Kerekes" wrote:
> Along with threads and various asynchronous techniques already
> mentioned, you should also con
David:
Thanks for your help, this seems like a class that will be perfect for what
I am doing! Just a few questions:
1. Is there any concern of thread safety using this class?
2. How can I pass NSFileHandle the file URL of my files?
3. How could I create a method that will take the contents of t
Stuart:
That sounds like it could work, however, pointed out by someone else - I
think NSFileHandle's readToEndOfFileInBackgroundAndNotify could work better
as I am dealing with reading files.
On 4/4/09 8:45 PM, "Stuart Malin" wrote:
>
> On Apr 4, 2009, at 5:36 PM, Pierce Freeman wrote:
>
>>
Michael Ash wrote:
Processes are a somewhat scarce
resource on OS X (only 266 per user by default, looks like)
That's a raisable (soft) limit. The hard limit is higher. See man
setrlimit.
In bash, the command 'ulimit -Sa' lists the soft limits, and 'ulimit -
Ha' lists the hard ones.
On Sun, Apr 5, 2009 at 9:33 AM, Kirk Kerekes wrote:
> Along with threads and various asynchronous techniques already mentioned,
> you should also consider creating a separate UI-less "foundation tool" to
> perform your lengthy task, controlled with NSTask in your main app. This
> yields all of the
> Yeah, it really helped! I am trying to get the contents of the files in a
> certain directory, so I think that I could probably get away with using a
> timer.
In this case, the reason your task is taking several seconds to
complete is most likely attributed to the sheer time it takes the read
t
On Apr 4, 2009, at 5:36 PM, Pierce Freeman wrote:
And, if you are 10.5 only, there's also NSObject's
performSelectorInBackground:withObject:
Is this a timer or a thread creator? I don't believe it has inputs
for the
time, or could it just do it automatically? Also, is there some way
I c
> And, if you are 10.5 only, there's also NSObject's
> performSelectorInBackground:withObject:
Is this a timer or a thread creator? I don't believe it has inputs for the
time, or could it just do it automatically? Also, is there some way I can
make this work with a function already created?
__
On Apr 4, 2009, at 5:07 PM, Andrew Farmer wrote:
On 04 Apr 09, at 19:35, Pierce Freeman wrote:
Yeah, it really helped! I am trying to get the contents of the
files in a
certain directory, so I think that I could probably get away with
using a
timer. I assume you mean NSTimer for the timer, t
On 04 Apr 09, at 19:35, Pierce Freeman wrote:
Yeah, it really helped! I am trying to get the contents of the
files in a
certain directory, so I think that I could probably get away with
using a
timer. I assume you mean NSTimer for the timer, though there could be
another class that I am tot
Hey Dave:
Yeah, it really helped! I am trying to get the contents of the files in a
certain directory, so I think that I could probably get away with using a
timer. I assume you mean NSTimer for the timer, though there could be
another class that I am totally missing. ;) In addition, if you are
> I am getting the beachball of death when I try to run an action that takes
> over a few seconds to complete. Given, the beachball goes away after the
> task is completed - But for lengthy tasks, why can't I just allow the user
> to go along with their work instead of having them wait with the be
Hey Ryan:
I have heard of threads before, but am just looking into them now to see if
they will work.
On 4/4/09 6:40 PM, "Ryan Joseph" wrote:
> Are you aware of threading or run loops? There is no problem here, you must
> share the processor with OS X. Read about those concepts and come back l
John:
Good idea, I¹ll look into threads and hopefully it will work.
On 4/4/09 6:37 PM, "john chen" wrote:
> You can try to do that task in another thread.
>
> John
>
> On Sat, Apr 4, 2009 at 8:08 PM, Pierce Freeman
> wrote:
>> Hi everyone:
>>
>> I am getting the beachball of death when I t
Are you aware of threading or run loops? There is no problem here, you
must share the processor with OS X. Read about those concepts and come
back later with questions. ;)
On Apr 5, 2009, at 8:08 AM, Pierce Freeman wrote:
Hi everyone:
I am getting the beachball of death when I try to run a
You can try to do that task in another thread.
John
On Sat, Apr 4, 2009 at 8:08 PM, Pierce Freeman
wrote:
> Hi everyone:
>
> I am getting the beachball of death when I try to run an action that takes
> over a few seconds to complete. Given, the beachball goes away after the
> task is completed -
Hi everyone:
I am getting the beachball of death when I try to run an action that takes
over a few seconds to complete. Given, the beachball goes away after the
task is completed - But for lengthy tasks, why can't I just allow the user
to go along with their work instead of having them wait with
22 matches
Mail list logo
