Hello!
I am wondering, if NSTask can be replaced with low-level fork/exec
calls. Looking through forums, i often met statements that launching a
process with "fork/exec" is not an "OS X way", especially if i am
using Cocoa framework (and i am using Cocoa!).
What i want to do - is to launch an appl
I know Cocoa has a project group that was building a Graphics API
called Drawkit but it's not been ported to iOS.
So I was wondering what people are using to build Pages like apps say
Freeform or other type of page layout apps.
Is there a new project I might have missed or is everyone just rolling
On 24 oct. 2010, at 19:03, eveningnick eveningnick wrote:
> Hello!
> I am wondering, if NSTask can be replaced with low-level fork/exec
> calls. Looking through forums, i often met statements that launching a
> process with "fork/exec" is not an "OS X way", especially if i am
> using Cocoa frame
Hello!
What operations does the "application launcher" (or launch services?
who's responsible for launching bundles) when i doubleclick on a
bundle? What happens when i open a terminal and go (CD) straight
through MyApp.app/Contents/MacOS and launch the binary? Is there some
source to read about th
>
> Are you sure about that?
No, but by reading all the topics of people, who tried to launch a
simple (non bundled) binary with it, i left that idea - according to
gossips Launch Services act like Finder's doubleclick - if you
doubleclick on a binary file, it just won't work. And unfortunately on
eveningnick wrote::
Basically this is the question about using fork in MacOS. But if there
are other ways to launch a process, i'd appreciate if someone shared
:)
Maybe setup a launchd plist specifying the target executable you want
to run, then ask launchd to run it by executing the 'laun
On 24 oct. 2010, at 19:56, eveningnick eveningnick wrote:
> Hello!
> What operations does the "application launcher" (or launch services?
> who's responsible for launching bundles) when i doubleclick on a
> bundle? What happens when i open a terminal and go (CD) straight
> through MyApp.app/Conten
On 24 Oct 2010, at 18:48, Thomas Clement wrote:
> On 24 oct. 2010, at 19:03, eveningnick eveningnick wrote:
>
>> Hello!
>> I am wondering, if NSTask can be replaced with low-level fork/exec
>> calls. Looking through forums, i often met statements that launching a
>> process with "fork/exec" is n
On 24 oct. 2010, at 20:03, eveningnick eveningnick wrote:
>
>> Not great but should work.
>> Better would be to use LaunchServices, if not possible I would use
>> SMJobSubmit() (ServicesManagement framework).
> Could you please explain why? What steps do i omit, if using fork/exec?
LaunchServi
On Oct 24, 2010, at 12:03 PM, eveningnick eveningnick wrote:
> I am wondering, if NSTask can be replaced with low-level fork/exec
> calls. Looking through forums, i often met statements that launching a
> process with "fork/exec" is not an "OS X way", especially if i am
> using Cocoa framework (a
Hi,
I am trying to upload a xml file to google my maps that follows the following
protocol:
http://code.google.com/apis/maps/documentation/mapsdata/developers_guide_protocol.html#uploading_xml
POST http://maps.google.com/maps/feeds/maps/userID/full
Content-type: application/atom+xml
Authorizat
Hello,
For PDFView, I used enterFullScreenMode:WithOptions:
After looking up some sample codes, I found out that what they used in
examples,
• From A View to A Movie
• From A View to A Picture
are different from what is explained in the document.
Anyway, I tried many options in
Hello,
I'm trying to understand why I'm getting thrown in to the debugger when using
NSError. I have three methods and I'm overloading them and trying to pass the
NSError along the way. What am I doing wrong?
Thanks,
tom
Code:
-(NSString *)getDataForType:(NSString *)aType error:(NSError **)er
On Oct 24, 2010, at 5:54 PM, Tom Jones wrote:
> I'm trying to understand why I'm getting thrown in to the debugger when using
> NSError. I have three methods and I'm overloading them and trying to pass the
> NSError along the way. What am I doing wrong?
> -(NSString *)getDataForType:(NSString *
On Sun, Oct 24, 2010 at 5:54 PM, Tom Jones wrote:
> -(NSString *)getDataForType:(NSString *)aType error:(NSError **)err
> {
> NSError *localErr = nil;
> NSString *result = [self getDataForType:aType separator:@"\t"
> excludeFields:nil error:&localErr];
> *err = *localErr;
> return res
On Oct 24, 2010, at 3:54 PM, Tom Jones wrote:
> Hello,
> I'm trying to understand why I'm getting thrown in to the debugger when using
> NSError. I have three methods and I'm overloading them and trying to pass the
> NSError along the way. What am I doing wrong?
>
> Thanks,
> tom
>
>
> Code:
On 2010 Oct 24, at 13:26, Philip Vallone wrote:
> I am not getting a response back, which indicates my post method is wrong.
I disagree. You probably are getting a response, but you're allowing it to
fall into the bit bucket on the floor.
What are logging there, although you have labelled it
Thanks Jerry.
Works perfect!
Regards,
Phil
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Up
Dave Carrigan wrote:
This is fine, although the code in the else is useless.
It won't be fine if err is nil. That's another Cocoa idiom: if the
NSError** is nil, then no NSError* is returned.
-- GG
___
Cocoa-dev mailing list (Cocoa-dev@lis
yes it will. i don't think the OP quite grasps pointer-to-pointers yet.
On Sun, Oct 24, 2010 at 9:21 PM, Greg Guerin wrote:
> Dave Carrigan wrote:
>
>> This is fine, although the code in the else is useless.
>
>
> It won't be fine if err is nil. That's another Cocoa idiom: if the
> NSError** is
The else will be fine, but the other half isn't because he isn't checking for
nil err, as Greg and others pointed out.
On Oct 24, 2010, at 7:46 PM, Stephen J. Butler wrote:
> yes it will. i don't think the OP quite grasps pointer-to-pointers yet.
>
> On Sun, Oct 24, 2010 at 9:21 PM, Greg Guerin
21 matches
Mail list logo
