Re: Future for Mac applications

2011-10-29 Thread Kyle Sluder
On Oct 29, 2011, at 6:04 PM, James Merkel  wrote:

> Kyle Sluder  wrote:
> 
>> We all know that Apple will not comment on future plans. It might not be a 
>> good idea to encourage rampant speculation on this list.
>> 
>> But as it stands right now, it's worth remembering that code signing and 
>> sandboxing are orthogonal technologies, and sandboxing clearly hasn't been 
>> nailed down yet.
> 
> Not sure why you're saying they are orthogonal. In order to sandbox an App 
> you need to sign it.

You're right, orthogonal is not the correct word. I should have said 
"complementary." Code signing exists to protect the integrity of the app 
bundle; sandboxing exists to protect the user from exploitation of an app's 
vulnerabilities.

> 
> One thing's for sure, whenever security people get involved with something, 
> stasis sets in.

The sandboxing engineers have been fairly responsive on devforums.apple.com, 
but those responses have lately devolved to "file a Radar describing how 
sandboxing is interfering with your app." Of course they can't comment on the 
November 1st MAS sandboxing deadline; that's still a giant question mark.

I'm under the inpression that the security folks developed app sandboxing in a 
relative vacuum and presented it to the App Store team who loved the benefits 
it brought. But then they announced it to the world and DTS informed them of 
how much of the Mac ecosystem it actually breaks.

We really need Apple to either reiterate the deadline or announce its delay. 
That announcement won't happen on this list, and the best way to influence that 
decision is to give solid reasons to the sandboxing engineers via Radar (with 
bug numbers posted to the dev forums) and possibly a followup email to your 
friendly DTS representative.

--Kyle Sluder
___

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: Future for Mac applications

2011-10-29 Thread James Merkel
Kyle Sluder  wrote:

> We all know that Apple will not comment on future plans. It might not be a 
> good idea to encourage rampant speculation on this list.
> 
> But as it stands right now, it's worth remembering that code signing and 
> sandboxing are orthogonal technologies, and sandboxing clearly hasn't been 
> nailed down yet.

Not sure why you're saying they are orthogonal. In order to sandbox an App you 
need to sign it.

One thing's for sure, whenever security people get involved with something, 
stasis sets in.

Jim Merkel
___

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: NSOutlineView drag and drop: how to prevent parent being dropped on one of its children

2011-10-29 Thread Koen van der Drift
Thanks Kyle, I'll try to apply that. In the meantime, I also found the 
AbstractView sample code which does something similar.  I'll see which one fits 
my code better.

- Koen.


On Oct 29, 2011, at 5:34 PM, Kyle Sluder wrote:

> On Sat, Oct 29, 2011 at 1:18 PM, Koen van der Drift
>  wrote:
>> I'm setting up drag and drop for my NSOutlineView and I want to prevent 
>> parents being dropped on one of their children. The parent and children are 
>> all of the Group entity. I understand I need to do this in the 
>> outlineView:validatedrop method. I think I need to create an NSFetchRequest 
>> with the NSPredictate to get all the children of the parent, but I don't 
>> know what the predicate should be.
> 
> If your outline view is set up such that children are descendant items
> of their parents, you don't even need to round-trip to the model
> layer. You could implement something like the following:
> 
> // Warning: typed in Mail, not guaranteed to work
> 
> - (NSDragOperation)outlineView:(NSOutlineView *)outlineView
> validateDrop:(id < NSDraggingInfo >)info proposedItem:(id)item
> proposedChildIndex:(NSInteger)index
> {
>  NSArray *draggingItems = ItemsFromDragInfo(info);
> 
>  NSMutableSet *parentTree = [[NSMutableSet alloc] init];
>  id parentItem = item;
>  while (parentItem) {
>[parentTree addObject:item];
>parentItem = [outlineView parentForItem:item];
>  }
> 
>  NSDragOperation op = NSDragOperationMove;
>  for (id item in draggingItems) {
>if ([parentTree containsobject:item]) {
>  op = NSDragOperationNone;
>  break;
>}
>  }
> 
>  [parentTree release];
>  return op;
> }
> 
> --Kyle Sluder

___

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: NSOutlineView drag and drop: how to prevent parent being dropped on one of its children

2011-10-29 Thread Kyle Sluder
On Sat, Oct 29, 2011 at 1:18 PM, Koen van der Drift
 wrote:
> I'm setting up drag and drop for my NSOutlineView and I want to prevent 
> parents being dropped on one of their children. The parent and children are 
> all of the Group entity. I understand I need to do this in the 
> outlineView:validatedrop method. I think I need to create an NSFetchRequest 
> with the NSPredictate to get all the children of the parent, but I don't know 
> what the predicate should be.

If your outline view is set up such that children are descendant items
of their parents, you don't even need to round-trip to the model
layer. You could implement something like the following:

// Warning: typed in Mail, not guaranteed to work

- (NSDragOperation)outlineView:(NSOutlineView *)outlineView
validateDrop:(id < NSDraggingInfo >)info proposedItem:(id)item
proposedChildIndex:(NSInteger)index
{
  NSArray *draggingItems = ItemsFromDragInfo(info);

  NSMutableSet *parentTree = [[NSMutableSet alloc] init];
  id parentItem = item;
  while (parentItem) {
[parentTree addObject:item];
parentItem = [outlineView parentForItem:item];
  }

  NSDragOperation op = NSDragOperationMove;
  for (id item in draggingItems) {
if ([parentTree containsobject:item]) {
  op = NSDragOperationNone;
  break;
}
  }

  [parentTree release];
  return op;
}

--Kyle Sluder
___

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


NSMetadataQuery - Just a warning.

2011-10-29 Thread Michael Monscheuer

Hi,

I just had a hard time with NSMetadataQuery and would like to share
the results.

NSMetadataQuery leaks one MDQuery for each change of the predicate.
Even deallocation of a NSMetadataQuery does not free the MDQuery objects 
that have been created internally to run the query.
Beyond the possibility of nasty crashes, this goes along with quite a 
strange side effect:
You can place 128 searches within your app before NSMedataQuery class 
will end up in no longer search for anything. Even newly created 
instances of NSMedataQuery will not start searching for the first time 
after this weird barrier has been reached.


You can simply reproduce this with Apple's spotlighter example.
For time saving reason, I replaced spotlighter's editable text field by 
NSSearchField and toggled its cell to search immediately 
(-setSendsSearchStringImmediately: set to YES).
Start to type in some search strings. After typing in 128 chars 
spotlighter will ignore further requests.


System: 10.7.2 (Lion), have not tried with 10.6.x yet.

A workaround is to call -stopQuery on NSMetadataQuery, before a new 
MDQuery will be created internally (change predicate, start searching) 
and in -dealloc of NSMetadataQuery to get rid of a possible running 
query that have not been explicitly stopped yet. I additionally placed a 
stop when NSMetadataQueryDidFinishGatheringNotification is received.
Doing all this causes the underlying MDQuery to be freed when no longer 
needed and before a new search will begin.

And this also magically removes the limit of 128 searches.

I am wondering if calling -stopQuery so often has any negative effect on 
internal caching (AFAIK result items may be shared among queries).


Yes, I will place a bug report asap.

Greetings from Germany,

MiMo
___

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


NSOutlineView drag and drop: how to prevent parent being dropped on one of its children

2011-10-29 Thread Koen van der Drift
Hi,

I'm setting up drag and drop for my NSOutlineView and I want to prevent parents 
being dropped on one of their children. The parent and children are all of the 
Group entity. I understand I need to do this in the outlineView:validatedrop 
method. I think I need to create an NSFetchRequest with the NSPredictate to get 
all the children of the parent, but I don't know what the predicate should be.

It should be recursively, so it should also get the children of children, if 
any.

Any suggestions?

Thanks,

- Koen.___

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


STL algorithms and NSEnumerator/NSFastEnumeration

2011-10-29 Thread Kelvin Chung
I have this Objective-C container which I want to use in an algorithm that only 
takes STL iterators.  Is there a generic adapter for NSEnumerator or 
id that will provide appropriate STL iterators?

Also, is there a way to tell the difference between two NSEnumerators (a la STL 
iterator difference)?  Is equality defined for NSEnumerators?  Is it possible 
to clone an NSEnumerator?

___

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: Future for Mac applications

2011-10-29 Thread Gregory Casamento
This subject came up about a year ago when Lion was first announced
 here was the reaction to it:

http://9to5mac.com/2010/04/25/jobs-mac-store-negative-ghostrider-593035053/

While Steve is now no longer with us.  I very much doubt that Apple would
shoot itself in the foot in this manner.

GC

On Sat, Oct 29, 2011 at 1:02 PM, Kyle Sluder  wrote:

> On Oct 29, 2011, at 9:31 AM, James Merkel  wrote:
>
> > As of November, all applications submitted to the App store must be
> sandboxed and signed.
> >
> > Not too difficult to forecast the future here. Will it be for an
> application to run on a Mac it will need to sandboxed and signed ?
>
> We all know that Apple will not comment on future plans. It might not be a
> good idea to encourage rampant speculation on this list.
>
> But as it stands right now, it's worth remembering that code signing and
> sandboxing are orthogonal technologies, and sandboxing clearly hasn't been
> nailed down yet.
>
> --Kyle Sluder___
>
> 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/greg_casamento%40yahoo.com
>
> This email sent to greg_casame...@yahoo.com
>



-- 
Gregory Casamento - GNUstep Lead/Principal Consultant, OLC, Inc.
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
___

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: Future for Mac applications

2011-10-29 Thread Kyle Sluder
On Oct 29, 2011, at 9:31 AM, James Merkel  wrote:

> As of November, all applications submitted to the App store must be sandboxed 
> and signed.
> 
> Not too difficult to forecast the future here. Will it be for an application 
> to run on a Mac it will need to sandboxed and signed ?

We all know that Apple will not comment on future plans. It might not be a good 
idea to encourage rampant speculation on this list.

But as it stands right now, it's worth remembering that code signing and 
sandboxing are orthogonal technologies, and sandboxing clearly hasn't been 
nailed down yet.

--Kyle Sluder___

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


Future for Mac applications

2011-10-29 Thread James Merkel
As of November, all applications submitted to the App store must be sandboxed 
and signed.

Not too difficult to forecast the future here. Will it be for an application to 
run on a Mac it will need to sandboxed and signed ?

Jim Merkel
___

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


CoreBluetooth framework

2011-10-29 Thread Luca Ciciriello
Hai List.
Is there someone knowing where I can find some line of sample code about 
CoreBluetooth framework?

Thanks in advance for any answer.

Luca.___

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: ALAssetsLibrary and iOS5

2011-10-29 Thread James Cicenia
Thanks... found the answer in the developer forum. The Library had to be 
initialized in AppDelegate (singleton).

thanks

On Oct 29, 2011, at 1:46 AM, Sandy McGuffog wrote:

> Just looking at the code, one issue that you might be running into is that 
> for ALAssetsLibrary under iOS 5, to quote from the Apple docs, "The lifetimes 
> of objects you get back from a library instance are tied to the lifetime of 
> the library instance." In this case, it's not at all clear to me that this 
> restriction is being met. There are a couple of threads on the Apple 
> developer forum discussing this.
> 
> Sandy
> 
> On Oct 27, 2011, at 6:36 PM, James Cicenia wrote:
> 
>> ALAssetsLibrary 
> 



smime.p7s
Description: S/MIME cryptographic signature
___

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: IKImageBrowserView spinning animation on the Cell

2011-10-29 Thread Tom Hohensee
Create a CALayer with the spinning effects. and use the following 
IKImageBrowser cell Core Animation layer method.  

- (CALayer *)layerForType:(NSString *)type

where NSString is a “Cell Layer Positions” type 
IKImageBrowserCellForegroundLayer.

For the spinning effects layer have a look at 
https://github.com/kelan/yrk-spinning-progress-indicator-layer.  You should be 
able to use the YPKSpinningProgressLayer classes for what you need.

Tom

On Oct 29, 2011, at 7:58 AM, XiaoGang Li wrote:

> IKImageBrowserCel

___

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


IKImageBrowserView spinning animation on the Cell

2011-10-29 Thread XiaoGang Li
Dear list,


I have an IKImageBrowserView based app which retrieves thumbnails from web
service, which is much like iPhoto app. I want to support progress
indicator animation in the placeholder layer of the IKImageBrowserCell.


Depends on the network speed, there will take a long time to download the
thumbnails, so I want to add a spinning progress indicator on each cell to
tell customers which thumbnail is being downloaded. After customer double
click one cell, the original image file also will be retrieved from web
service, there also has a requirement to draw a spinning progress indicator
animation on the cell to tell the customer the wanted one is being
downloaded.


My question is how to add a spinning progress indicator animation on the
placeholder layer? I have some basic knowledge using the core animation,
but no idea to address this kind of issue. Can anyone give me any
guidelines to push me on a right direction?


Best wishes,


XiaoGang
___

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