Service without Icon or Window?

2010-06-15 Thread Lightning Duck
I need to make an application  that runs a bit as a 'service' if you will.  Not 
in the sense of running from the "Services" menu but something the tuns 
continually in the background with an Icon in the Dock or a Window of it's own, 
that monitors when files are added or removed from a directory

So basically I have two requirements

Monitor the contents of a directory

Run without visibility?

Can anyone send me to some pointers for how to do either, or both, of these 
tasks?

Thanks,
Jay
___

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/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: Service without Icon or Window?

2010-06-16 Thread Lightning Duck
Thanks, all, for the advice and the pointers


Take care,
Jay

On Jun 15, 2010, at 5:05 PM, Peter Ammon wrote:

> 
> On Jun 15, 2010, at 2:56 PM, Lightning Duck wrote:
> 
>> I need to make an application  that runs a bit as a 'service' if you will.  
>> Not in the sense of running from the "Services" menu but something the tuns 
>> continually in the background with an Icon in the Dock or a Window of it's 
>> own, that monitors when files are added or removed from a directory
>> 
>> So basically I have two requirements
>> 
>> Monitor the contents of a directory
>> 
>> Run without visibility?
>> 
>> Can anyone send me to some pointers for how to do either, or both, of these 
>> tasks?
> 
> It sounds like you want a launchd agent.  launchd can launch your program 
> when certain paths are modified, via the WatchPaths or QueueDirectories info 
> plist keys.
> 
> The advantage of this approach is that your process does not have to run 
> continuously in the background: it's launched on-demand, and can exit when 
> it's finished.
> 
> -Peter ___
> 
> 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/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/lightningduck%40me.com
> 
> This email sent to lightningd...@me.com

___

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/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


iPad widget question

2011-02-26 Thread Lightning Duck
Hello, I have an iPad widget question (hence the subject)

I need to make something like a 2D grid of icons where each icon is tappable.  
This seems like fairly obvious functionality but I don't see a widget that 
really supports that idea

Thanks

Take care,
Jay
___

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/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: iPad widget question

2011-02-26 Thread Lightning Duck
That was actually very helpful simply because I didn't know about 
NSCollectionView or NSMatrix


On Feb 26, 2011, at 7:12 PM, Dave DeLong wrote:

> I'd start with AQGridView:  https://github.com/AlanQuatermain/AQGridView
> 
> Cheers,
> 
> Dave
> 
> On Feb 26, 2011, at 7:10 PM, Lightning Duck wrote:
> 
>> Hello, I have an iPad widget question (hence the subject)
>> 
>> I need to make something like a 2D grid of icons where each icon is 
>> tappable.  This seems like fairly obvious functionality but I don't see a 
>> widget that really supports that idea
>> 
>> Thanks
>> 
>> Take care,
>> Jay

___

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/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: iPad widget question

2011-02-26 Thread Lightning Duck
And now I realize NSCollectionView is for Mac, not for iPad and the AQGridView 
works for the iPad

Thanks.

On Feb 26, 2011, at 7:14 PM, Gleb Dolgich wrote:

> Have a look at AQGridView: https://github.com/AlanQuatermain/AQGridView
> 
> -- 
> Gleb Dolgich
> PixelEspresso
> http://www.pixelespressoapps.com
> 
> 
> On 27 Feb 2011, at 03:10, Lightning Duck wrote:
> 
>> I need to make something like a 2D grid of icons where each icon is 
>> tappable.  This seems like fairly obvious functionality but I don't see a 
>> widget that really supports that idea
> 

___

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/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


SourceView example

2010-02-04 Thread Lightning Duck
I'm fairly new to Cocoa development (although I've been writing software for 
more than 15 years).

I'm working on an app for myself that needs a tree view so I'm looking through 
the SourceView example as a guide.

I'm curious why the use of BaseNode versus ChildNode and why the code uses one 
in some places and the other in other places?

Thanks,
Jay


___

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/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: Guidance on use of Application Support folder

2010-02-12 Thread Lightning Duck
What has confused me about this is why does CoreDate store it's data in the 
Application Support folder be default  then?

On Feb 12, 2010, at 9:27 AM, Stuart Malin wrote:

> I sorta would agree, Jens, and certainly many apps do put user-specific files 
> here, but the Apple docs specifically say this is NOT how the Application 
> Support folder should be used. 
> 
> ~~~
> 
> "A support file is any type of file that supports the application but is not 
> required for the application to run. Document templates and sample files are 
> simple examples of support files. However, you might store more 
> application-bound information, such as custom configurations or preset data 
> files for your application’s workspace. In these instances, the information 
> is intrinsically tied to a specific application (as opposed to the user’s 
> data) but is not essential for the application to run."
>   
> 
> 
> ~~~
> 
> In the "File System Overview", is this:
> 
> Table 1  Subdirectories of the Library directory
> Subdirectory
> Directory contents
> Application Support
> Contains application-specific data and support files such as third-party 
> plug-ins, helper applications, templates, and extra resources that are used 
> by the application but not required for it to operate. This directory should 
> never contain any kind of user data. By convention, all of these items should 
> be put in a subdirectory named after the application. For example, 
> third-party resources for the application MyApp would go in Application 
> Support/MyApp/. Note that required resources should go inside the application 
> bundle itself.
> 
>   
> 
> 
> Note the line: "This directory should never contain any kind of user data."
> 
> ~~~
> 
> There is some discussion of relevance here:
>   
> 
> On Feb 12, 2010, at 11:13 AM, Jens Alfke wrote:
> 
>> 
>> On Feb 12, 2010, at 8:05 AM, Stuart Malin wrote:
>> 
>>> I am building an app that needs to store per-user data that is not document 
>>> specific. I have created a folder under ~/Library for this, and am not 
>>> using ~/Library/Application Support.  Is there guidance from Apple on where 
>>> such per-user, non-document-specific data is supposed to be stored?
>> 
>> I would say that's what Application Support is for. There are apps that 
>> create their own direct subfolders of ~/Library, but I think that's messy.
>> 
>> —Jens
> 
> ___
> 
> 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/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/lightningduck%40me.com
> 
> This email sent to lightningd...@me.com

___

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/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com