On Apr 5, 2013, at 2:41 PM, Mark Munz unmar...@gmail.com wrote:
Btw.. the solution I used to prevent Services from bringing the app forward
is to have a background (LSUIElement) helper app that acts as the
NSServices provider. Depending on what you need to do, you could either
support the
Thanks, Uli! Indeed the thing to do is start with a regular Application project
and tweak it. Quite simple once you know how.
I wrote up what I learned here:
http://www.notesfromandy.com/2013/04/05/writing-a-service-bundle/
And here's the service I wrote. It copies a selector to the clipboard
.service was also designed to allow for dynamic services where an app could
write out just the info.plist in a bundle.service and the NSServices key
points to services offered by other apps. You could then have services
created by apps using a single entry point with different user data to take
I wrote CodingService a while ago
(http://the-void-software.com/codingservice/), and as far I can see from a
quick glance at the sources, all a .service is, is a faceless background
application (LSBackgroundOnly == true in Info.plist) where you change the
suffix in the build settings from .app
From: ag...@mac.com
Date: Wednesday, April 3, 2013
To: Kevin Callahan kc...@mac.com
Subject: Re: Providing a Service without activating an app
On Apr 2, 2013, at 4:43 PM, Kevin Callahan kc...@mac.com wrote: So,
basically, my solution was to minimize my app, do the service work
On Apr 2, 2013, at 4:43 PM, Kevin Callahan kc...@mac.com wrote:
So, basically, my solution was to minimize my app, do the service work,
then activate Xcode, then insert results.
Maybe there's a better way?
Thanks, Kevin! I think you may have mentioned dealing with this a while
On Apr 3, 2013, at 3:27 AM, Andy Lee ag...@mac.com wrote:
How did everybody else learn how to write a .service?
To answer my own question, I see now chapters on the subject in a couple of the
older books on my shelves.
--Andy
___
Cocoa-dev
I'm writing an app that provides an NSService. Is there a way to have the app
not activate when the service is invoked?
Alternatively -- where can I find good docs and/or sample code for creating a
standalone .service bundle?
--Andy
___
Cocoa-dev
On Apr 2, 2013, at 11:03 AM, Andy Lee ag...@mac.com wrote:
I'm writing an app that provides an NSService. Is there a way to have the app
not activate when the service is invoked?
Alternatively -- where can I find good docs and/or sample code for creating a
standalone .service bundle?
