date:20090322

Hi everyone:

I am wondering if there is some way to change another applications icon
programmatically.  The problem that I see if that every application's icon
name is different and I haven't found a way to read that application's icon
location or will just return a NSImage that is the icon.


Thanks for any help.


___

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: NSAppleScript - what is going on here?

2009-03-22 Thread Matt Neuburg

On Sat, 21 Mar 2009 12:38:11 -0500, Steve Cronin steve_cro...@mac.com
said:
Folks;

I'm trying to get a string value back from a simple AppleScript in
Cocoa:

NSDictionary *errorDict= nil;
NSAppleScript *appleScriptObject = [[NSAppleScript alloc]
initWithSource:theScript]; 
NSAppleEventDescriptor *eventDescriptor = [appleScriptObject
executeAndReturnError: errorDict];
[appleScriptObject release]; 
if (([eventDescriptor descriptorType])  (errorDict==nil)) {
 return [self stringFromAppleEventDescriptor:eventDescriptor];  //my
own method that checks descriptorType and returns stringValue
} else {
 NSLog(@%@,[errorDict objectForKey:@NSAppleScriptErrorMessage]);
 return nil;
}

The 'theScript' is a valid script that executes flawlessly in 'Script
Editor':
tell application Finder
 try
  comment of file (/Users/steve/ as POSIX file)
 on error
  return Error
 end try
end tell

The problem is that the above errors out @ [appleScriptObject
executeAndReturnError: errorDict];
The stack is shown below.

That's hard to answer because you're so obviously lying. You are not
reporting what you're really doing. What is theScript really? A string? Show
us the string. And clearly you are not really saying /Users/steve/, so
show us what you *are* saying.

Let me show you how to answer. Here is a *complete* valid chunk of *real*
Objective-C code:

NSString* theScript = @tell application \Finder\\n
@try\n
@set pp to \/Users/mattneub/Desktop/BrahmsHandel2.mus\\n
@comment of file (pp as POSIX file)\n
@on error\n
@return \Error\\n
@end try\n
@end tell\n;
NSDictionary *errorDict= nil;
NSAppleScript *appleScriptObject = [[NSAppleScript alloc]
initWithSource:theScript];
NSAppleEventDescriptor *eventDescriptor = [appleScriptObject
executeAndReturnError: errorDict];
[appleScriptObject release];
if (([eventDescriptor descriptorType])  (errorDict==nil)) {
NSLog(@%@, [eventDescriptor stringValue]);
} else {
NSLog(@%@,[errorDict objectForKey:@NSAppleScriptErrorMessage]);
}

I actually ran that code and it actually works (the finder comment from the
specified file appears in the log). Okay, now it's your turn. :) m.

-- 
matt neuburg, phd = m...@tidbits.com, http://www.tidbits.com/matt/
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings



___

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: NSAppleScript - what is going on here?

2009-03-22 Thread Steve Cronin


Matt;

I really take offense at your tone.  I was not lying.
I merely clipped out my personal details in order not to provide them  
to the world.
The 'theScript' IS a string - constructed in ObjC differently than you  
show but a string nonetheless.


Turns out the error was that an SDEF file had been renamed.

As Samuel Jackson said in Black Snake Moan --  Collar that dog!,
Steve

On Mar 22, 2009, at 12:05 PM, Matt Neuburg wrote:

On Sat, 21 Mar 2009 12:38:11 -0500, Steve Cronin  
steve_cro...@mac.com

said:

Folks;

I'm trying to get a string value back from a simple AppleScript in
Cocoa:

NSDictionary *errorDict= nil;
NSAppleScript *appleScriptObject = [[NSAppleScript alloc]
initWithSource:theScript];
NSAppleEventDescriptor *eventDescriptor = [appleScriptObject
executeAndReturnError: errorDict];
[appleScriptObject release];
if (([eventDescriptor descriptorType])  (errorDict==nil)) {
return [self stringFromAppleEventDescriptor:eventDescriptor];  //my
own method that checks descriptorType and returns stringValue
} else {
NSLog(@%@,[errorDict objectForKey:@NSAppleScriptErrorMessage]);
return nil;
}

The 'theScript' is a valid script that executes flawlessly in 'Script
Editor':
tell application Finder
try
comment of file (/Users/steve/ as POSIX file)
on error
return Error
end try
end tell

The problem is that the above errors out @ [appleScriptObject
executeAndReturnError: errorDict];
The stack is shown below.


That's hard to answer because you're so obviously lying. You are not
reporting what you're really doing. What is theScript really? A  
string? Show
us the string. And clearly you are not really saying /Users/ 
steve/, so

show us what you *are* saying.

Let me show you how to answer. Here is a *complete* valid chunk of  
*real*

Objective-C code:

   NSString* theScript = @tell application \Finder\\n
   @try\n
   @set pp to \/Users/mattneub/Desktop/BrahmsHandel2.mus\\n
   @comment of file (pp as POSIX file)\n
   @on error\n
   @return \Error\\n
   @end try\n
   @end tell\n;
   NSDictionary *errorDict= nil;
   NSAppleScript *appleScriptObject = [[NSAppleScript alloc]
initWithSource:theScript];
   NSAppleEventDescriptor *eventDescriptor = [appleScriptObject
executeAndReturnError: errorDict];
   [appleScriptObject release];
   if (([eventDescriptor descriptorType])  (errorDict==nil)) {
   NSLog(@%@, [eventDescriptor stringValue]);
   } else {
   NSLog(@%@,[errorDict  
objectForKey:@NSAppleScriptErrorMessage]);

   }

I actually ran that code and it actually works (the finder comment  
from the

specified file appears in the log). Okay, now it's your turn. :) m.

--
matt neuburg, phd = m...@tidbits.com, http://www.tidbits.com/matt/
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings





___

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: NSAppleScript - what is going on here?

2009-03-22 Thread Adam R. Maxwell


On Mar 21, 2009, at 10:38 AM, Steve Cronin wrote:

The 'theScript' is a valid script that executes flawlessly in  
'Script Editor':

tell application Finder
try
comment of file (/Users/steve/ as POSIX file)
on error
return Error
end try
end tell


It sounds like you've solved your problem, but I'd just note that if  
you're only getting Finder comments, MDItem is faster and simpler:


- (NSString *)commentForURL:(NSURL *)fileURL;
{
NSParameterAssert([fileURL isFileURL]);

MDItemRef mdItem = NULL;
CFStringRef path = (CFStringRef)[fileURL path];
NSString *theComment = nil;

if (path  (mdItem = MDItemCreate(CFGetAllocator(path), path))) {
theComment = (NSString *)MDItemCopyAttribute(mdItem,  
kMDItemFinderComment);

CFRelease(mdItem);
[theComment autorelease];
}
return theComment;
}





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: NSAppleScript - what is going on here?

2009-03-22 Thread Steve Cronin


Adam;

I'm an ObjC guy -- I generally avoid the C stuff if possible - 'cause  
I have to support my own code.


But your method seems like it will work not only as a replacement but  
actually a doorway to the full gamut of common metadata attributes -  
very nice!!


I know I should lose the resistance but there are only so many  
mountains one guy can climb...


Thanks for the very helpful note!
Steve

On Mar 22, 2009, at 12:43 PM, Adam R. Maxwell wrote:


On Mar 21, 2009, at 10:38 AM, Steve Cronin wrote:

The 'theScript' is a valid script that executes flawlessly in  
'Script Editor':

tell application Finder
try
comment of file (/Users/steve/ as POSIX file)
on error
return Error
end try
end tell


It sounds like you've solved your problem, but I'd just note that if  
you're only getting Finder comments, MDItem is faster and simpler:


- (NSString *)commentForURL:(NSURL *)fileURL;
{
   NSParameterAssert([fileURL isFileURL]);

   MDItemRef mdItem = NULL;
   CFStringRef path = (CFStringRef)[fileURL path];
   NSString *theComment = nil;

   if (path  (mdItem = MDItemCreate(CFGetAllocator(path), path))) {
   theComment = (NSString *)MDItemCopyAttribute(mdItem,  
kMDItemFinderComment);

   CFRelease(mdItem);
   [theComment autorelease];
   }
   return theComment;
}





___

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: Programmatically Change Icon


On Mar 22, 2009, at 12:27 PM, Pierce Freeman wrote:

I am wondering if there is some way to change another applications  
icon
programmatically.  The problem that I see if that every  
application's icon
name is different and I haven't found a way to read that  
application's icon

location or will just return a NSImage that is the icon.


Problems:

1 - Not all users are administrators of their computer, and so a user- 
space application may not be able to modify the application bundles in  
question. You'll need to authenticate/authorize the user to perform  
this change if the application is in the /Applications folder, or the  
user has no write permissions for the app bundles otherwise.


2 - Some applications may be digitally signed, in which case modifying  
the application bundles in question may at least cause disconcerting  
warnings for the user launching the modified applications, and at  
worst break the application(s).


3 - This may be technically in violation of the EULA of the  
applications in question. IANAL, but I certainly would look into this  
before trying it, especially with the very loosely-defined DMCA laws.


4 - All the above aside, make sure you have your users' express  
permission to perform this action ... it is a pretty big deal and I  
would personally not use any application that does this, and you can  
count on others feeling the same way, so make sure you ask in very  
clear, plain language.


  That said, to get the application's icon, you can do what the  
Finder does and use the app bundle's Info.plist and ask for the value  
for the CFBundleIconFile key. Then ask the application bundle for the  
resource with the returned name.


  See the documentation for the permissions issue and for how to work  
with the icon file format.


--
I.S.


___

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

How to get events in PDE auxiliary window?

2009-03-22 Thread Alexander Shmelev


Hello,

I have implemented cocoa PDE plugin. Auxiliary window appears when  
user clicks button on this PDE.
I can interact with all controls on this auxiliary window in all  
applications except Adobe Acrobat Reader.
When I select Print then open my cocoa PDE and click button then  
auxiliary window appears behind print dialog, and when I try to  
interact with controls on this window, I get only beeps.


How this can be fixed? How can I place auxiliary window above print  
dialog? And how I can forward events to controls on this window?


BR, Alexander 
___


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

how to say app using only my plug-in?

2009-03-22 Thread Carlo Gulliani

I finished project, which use Flash player plug-in. But if user has same 
plug-in (but old version), my application load his. I wanna that app use just 
my plug-ins from my folder (myapp.app/Contents/PlugIns/Flash Player.plugin) and 
doesn't use system's plug-in. how to do so?


  
___

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: Programmatically Change Icon

2009-03-22 Thread Uli Kusterer


On 22.03.2009, at 17:27, Pierce Freeman wrote:

 The problem that I see if that every application's icon
name is different and I haven't found a way to read that  
application's icon

location or will just return a NSImage that is the icon.


 Sure you can retrieve NSImages for application icons. Look at  
NSWorkspace's iconForFile: method and similar ones. Now, changing  
them, that's a different matter. This used to be able with Carbon's  
Icon Services APIs, though. There you were able to override an icon  
with one you provided, e.g. to animate the progress bar on a  
downloaded file icon. Might want to look into those. Last time I did  
that was on OS 9 though, so no guarantee whether that's still system- 
wide these days.


I am wondering if there is some way to change another applications  
icon

programmatically.



 What are you trying to do that you need to do this? Are you trying  
to change the dock icons of running applications, or what? For that,  
it might be a better idea to use Accessibility APIs or AppleScript (or  
maybe even CGWindow APIs work?) to determine the rectangle of the  
requisite dock tile, and then show your own, transparent window on top?


 Have you considered the repercussions of your changes on the  
developers of the other applications? Consider that, not only would  
you break any code signing on those apps, and any other checksums they  
may be using to make sure patches or incremental updates work, you  
could also trigger other sorts of tamper alerts, or through a bug  
damage the application whose icon you wanted to change.


 Trouble is, the user might not notice until they next launch that  
other app. And the people who would then have to deal with what your  
app caused are likely the ones who developed your 'victim' app. After  
all, many users won't understand that just changing an icon can damage  
an application, not to mention that some might have forgotten they  
used your application to change the icon.


 We used to get lots of bug reports from people who had used third- 
party tools to strip Intel code from their universal binary  
applications to save disk space. They'd done that a while ago, and  
when they used the migration assistant to move their apps to their new  
Intel Mac months later, some of them refused to work, and many of them  
were dog-slow because of issues with Rosetta they wouldn't even have  
had if they had just run the intel-native code we put in there.


 I'm not saying you shouldn't do that, but I just thought I'd make  
you aware of the backlash that applications that patch others in  
whatever way can cause. Talk to the guys from Unsanity if you want to  
know how even people who did a very good job of writing a robust  
patching engine got hissed at, I'm sure they have a few stories to  
tell...


 Oh, one more thing: If you really just want to change the icon, you  
may want to look into how Finder applies custom icons to folders.  
You'd still have to authenticate, but at least you'd be doing a  
modification that the user can do using the Finder, so it's something  
application developers can expect. I believe how it's basically done  
is creating a file with the name Icon\r (\r is 0x0D, i.e. a return  
character, not a newline as in \n or 0x0A) at the top level of the  
application package, next to the Contents folder, and set the  
kHasCustomIcon flag on the folder. The Icon\r-file contains an  
'icns' resource with ID -16455 containing the contents of a .icns file.


Cheers,
-- Uli Kusterer
The Witnesses of TeachText are everywhere...
http://www.zathras.de





___

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: NSAppleScript - what is going on here?

2009-03-22 Thread Kyle Sluder

On Sun, Mar 22, 2009 at 1:53 PM, Steve Cronin steve_cro...@mac.com wrote:
 I'm an ObjC guy -- I generally avoid the C stuff if possible - 'cause I have
 to support my own code.

You cannot reasonably expect to avoid C... there's a lot of
functionality Cocoa doesn't provide.  Launch Services for example.
You're only doing yourself a disservice by avoiding C APIs, which are
just as much part of Objective-C as the OO stuff -- ObjC is a strict
superset after all.

I bet that by avoiding C you actually create more work for yourself
than if you just went with C when appropriate.

--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: Programmatically Change Icon

Well, that's what I get for typing this when I was still half asleep.  I
meant to simply view instead of changing the icon.  Would there be any
problems (legally or otherwise) with doing this?  You seem to know about
these issues a lot better them myself...

I definitely agree with all the problems you outlined, and never wanted to
cause problems.  If you would  mind saying, though, how would changing the
Application's icon involve legal issues?  Since the users of the computers
do it all the time.  Also I agree that using an application that would
change them without the user's permission would be very disconcerting and I
would probably trash that application right away.


Thanks for your help.


On 3/22/09 10:55 AM, I. Savant idiotsavant2...@gmail.com wrote:

 On Mar 22, 2009, at 12:27 PM, Pierce Freeman wrote:
 
 I am wondering if there is some way to change another applications
 icon
 programmatically.  The problem that I see if that every
 application's icon
 name is different and I haven't found a way to read that
 application's icon
 location or will just return a NSImage that is the icon.
 
 Problems:
 
 1 - Not all users are administrators of their computer, and so a user-
 space application may not be able to modify the application bundles in
 question. You'll need to authenticate/authorize the user to perform
 this change if the application is in the /Applications folder, or the
 user has no write permissions for the app bundles otherwise.
 
 2 - Some applications may be digitally signed, in which case modifying
 the application bundles in question may at least cause disconcerting
 warnings for the user launching the modified applications, and at
 worst break the application(s).
 
 3 - This may be technically in violation of the EULA of the
 applications in question. IANAL, but I certainly would look into this
 before trying it, especially with the very loosely-defined DMCA laws.
 
 4 - All the above aside, make sure you have your users' express
 permission to perform this action ... it is a pretty big deal and I
 would personally not use any application that does this, and you can
 count on others feeling the same way, so make sure you ask in very
 clear, plain language.
 
That said, to get the application's icon, you can do what the
 Finder does and use the app bundle's Info.plist and ask for the value
 for the CFBundleIconFile key. Then ask the application bundle for the
 resource with the returned name.
 
See the documentation for the permissions issue and for how to work
 with the icon file format.
 
 --
 I.S.
 
 


___

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: how to say app using only my plug-in?

2009-03-22 Thread Benjamin Dobson



On 22 Mar 2009, at 18:34:46, Carlo Gulliani wrote:

I finished project, which use Flash player plug-in. But if user has  
same plug-in (but old version), my application load his. I wanna  
that app use just my plug-ins from my folder (myapp.app/Contents/ 
PlugIns/Flash Player.plugin) and doesn't use system's plug-in. how  
to do so?


I think you just install it in the user domain. Nothing wrong with  
helping users avoid up-to-date software. But please, warn them you're  
doing this.

___

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: Programmatically Change Icon


On Mar 22, 2009, at 3:45 PM, Pierce Freeman wrote:

Well, that's what I get for typing this when I was still half  
asleep.  I

meant to simply view instead of changing the icon.


  Heh - ... some way to change another applications icon ...   
Changing has all those issues attached. Viewing on the other hand is  
easy.


  As Uli mentioned, NSWorkspace should be all you need simply to get  
a copy of the icon. The bundle stuff is only necessary if you want to  
get at the file itself (say, to modify it :-)).



Would there be any problems (legally or otherwise) with doing this?   
You seem to know about these issues a lot better them myself...


  Best answer: I don't know for sure. Note the use of IANAL (I Am  
Not A Lawyer) and might be. :-)


  In the US, distributing software that modifies third-party software  
is uncomfortably close to the fence of a number of copyright laws and  
regulations. It's something any independent software business owner  
should be aware of. Again, this is from the perspective of a US  
citizen; it may be a non-issue for you, but you should definitely  
consult a lawyer before distributing such an application. That's all I  
meant to say.


  This discussion, however, is off-topic for cocoa-dev, so I'll leave  
it at that. I suggest the macsb group on Yahoo Groups.


--
I.S.

___

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: Programmatically Change Icon

Heh - ... some way to change another applications icon ...
 Changing has all those issues attached. Viewing on the other hand is
 easy.

My point exactly. ;)

As Uli mentioned, NSWorkspace should be all you need simply to get
 a copy of the icon. The bundle stuff is only necessary if you want to
 get at the file itself (say, to modify it :-)).

Would NSWorkspace also work if the app was not running, or only if it is?

Best answer: I don't know for sure. Note the use of IANAL (I Am
 Not A Lawyer) and might be. :-)
 
In the US, distributing software that modifies third-party software
 is uncomfortably close to the fence of a number of copyright laws and
 regulations. It's something any independent software business owner
 should be aware of. Again, this is from the perspective of a US
 citizen; it may be a non-issue for you, but you should definitely
 consult a lawyer before distributing such an application. That's all I
 meant to say.

While it doesn't have to do with me, it's good advice to know.  However, as
you said, I assume these problems aren't true with just showing the icon
(versus changing it).

This discussion, however, is off-topic for cocoa-dev, so I'll leave
 it at that. I suggest the macsb group on Yahoo Groups.

True, I'll look there if I have any more questions.


Thanks for all your help.


___

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: Programmatically Change Icon


On Mar 22, 2009, at 5:29 PM, Pierce Freeman wrote:

Would NSWorkspace also work if the app was not running, or only if  
it is?




  Slightly-challenging-answer: Try it and see.

  Non-smarmy-answer: Yes. So would the other, more complicated  
approach.



While it doesn't have to do with me, it's good advice to know.   
However, as
you said, I assume these problems aren't true with just showing the  
icon

(versus changing it).


  I would assume this as well ... there'd be a number of software  
companies in hot water otherwise. Especially OS vendors like Apple and  
Microsoft, since Finder and Windows Explorer both show other  
applications' icons. :-)


--
I.S.





___

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: Explicit release when using garbage collection with circular references

Hello David,

your  garbage collection approach is a bit naive, but not everything
is wrong, you can make a google search, it will point you good
resources anyway,

@implementation AppDelegate

- (void)sendSharedMessage:(NSString *)msg
{
   return [[[NSString alloc] initWithFormat:@ %@,msg] autorelease];
}

@end


@implementation MyObject

- (void)aMathod
{
id sharedController = [[NSApplication sharedApplication] delegate];

if ([[sharedController class]
instancesRespondToSelector:@selector(sendSharedMessage:)]) {
NSString aMsg = [[NSString alloc] initWithString:@hello];
 [sharedController performSelector:@selector(sendSharedMessage:)
withObject:aMsg];
[aMsg release];
   }

}

@end

 (sorry if there is synthax errors this is a live code)

this model will apply with/or without garbage collection, release
autorelease will be ignored in garbage collection env, avoid as far
is possible circular refs by a proper design.

On Sat, Mar 21, 2009 at 9:16 PM, Bill Bumgarner b...@mac.com wrote:
 On Mar 21, 2009, at 9:11 PM, David wrote:

 Is there any issue issuing explicit release when using garbage
 collection with Leopard and Obj-c 2.0?

 -release is ignored entirely.

 CFRelease() work as it always does, and balances CFRetain() nicely.

 But that isn't the issue.

 I've become aware that I have lots of memory not being freed within my
 application. I presume this is because its a tree structure with
 parent child pointers between the objects. If I drop the last
 reference to the tree, I presume the tree does not get garbage
 collected because each object has circular pointers between them, ie
 parent has references to children and each child has a reference to
 its parent. In this case, it seem that the appropriate course of
 action would be to call a specific method to forcibly release each
 node in the tree.
 Is this the proper approach?
 Should garbage collection somehow work anyway?

 That would be an incorrect presumption.  The garbage collector handles
 complexly connected, but not rooted, graphs just fine. Your sub-graphs --
 trees -- of objects that are no longer referenced by your rooted object
 graphs should be reaped without a problem.

 So, something else is going on.

 Have you used 'info gc-roots' to see what is causing the items within your
 tree to stick around?

 b.bum

 ___

 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/openspecies%40gmail.com

 This email sent to openspec...@gmail.com




-- 
-mmw
___

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: Programmatically Change Icon

Slightly-challenging-answer: Try it and see.
 
Non-smarmy-answer: Yes. So would the other, more complicated
 approach.

Lol, just wanted to make sure.

I would assume this as well ... there'd be a number of software
 companies in hot water otherwise. Especially OS vendors like Apple and
 Microsoft, since Finder and Windows Explorer both show other
 applications' icons. :-)

Yeah, this is more or less what I figured... Application icons are more or
less made to be viewed. ;)


___

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: Explicit release when using garbage collection with circular references

I changed my mind, when I was writting this

- (void)sendSharedMessage:(NSString *)msg
{
   NSString *print = [[[NSString alloc] initWithFormat:@ %@,msg] autorelease];

   NSLog(@ %@, print);
}

anyway it doesn't change the background


On Sun, Mar 22, 2009 at 2:47 PM, mm w openspec...@gmail.com wrote:
 Hello David,

 your  garbage collection approach is a bit naive, but not everything
 is wrong, you can make a google search, it will point you good
 resources anyway,

 @implementation AppDelegate

 - (void)sendSharedMessage:(NSString *)msg
 {
   return [[[NSString alloc] initWithFormat:@ %@,msg] autorelease];
 }

 @end


 @implementation MyObject

 - (void)aMathod
 {
    id sharedController = [[NSApplication sharedApplication] delegate];

    if ([[sharedController class]
 instancesRespondToSelector:@selector(sendSharedMessage:)]) {
        NSString aMsg = [[NSString alloc] initWithString:@hello];
         [sharedController performSelector:@selector(sendSharedMessage:)
 withObject:aMsg];
        [aMsg release];
   }

 }

 @end

  (sorry if there is synthax errors this is a live code)

 this model will apply with/or without garbage collection, release
 autorelease will be ignored in garbage collection env, avoid as far
 is possible circular refs by a proper design.

 On Sat, Mar 21, 2009 at 9:16 PM, Bill Bumgarner b...@mac.com wrote:
 On Mar 21, 2009, at 9:11 PM, David wrote:

 Is there any issue issuing explicit release when using garbage
 collection with Leopard and Obj-c 2.0?

 -release is ignored entirely.

 CFRelease() work as it always does, and balances CFRetain() nicely.

 But that isn't the issue.

 I've become aware that I have lots of memory not being freed within my
 application. I presume this is because its a tree structure with
 parent child pointers between the objects. If I drop the last
 reference to the tree, I presume the tree does not get garbage
 collected because each object has circular pointers between them, ie
 parent has references to children and each child has a reference to
 its parent. In this case, it seem that the appropriate course of
 action would be to call a specific method to forcibly release each
 node in the tree.
 Is this the proper approach?
 Should garbage collection somehow work anyway?

 That would be an incorrect presumption.  The garbage collector handles
 complexly connected, but not rooted, graphs just fine. Your sub-graphs --
 trees -- of objects that are no longer referenced by your rooted object
 graphs should be reaped without a problem.

 So, something else is going on.

 Have you used 'info gc-roots' to see what is causing the items within your
 tree to stick around?

 b.bum

 ___

 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/openspecies%40gmail.com

 This email sent to openspec...@gmail.com




 --
 -mmw




-- 
-mmw
___

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: Programmatically Change Icon

Slightly-challenging-answer: Try it and see.
 
Non-smarmy-answer: Yes. So would the other, more complicated
 approach.

Just tried it, and it works great... Thanks!  Just two questions so far:

1. How can I get different sizes of the icon, or are they just linked to the
size of the outlet?
2. If you link to a non-existent application, it still returns an image - Is
there some way to set it to return an error if this happens?


Thanks for all your help.


___

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: Programmatically Change Icon

On Mar 22, 2009, at 6:09 PM, Pierce Freeman wrote:

Slightly-challenging-answer: Try it and see.

Non-smarmy-answer: Yes. So would the other, more complicated
approach.

Just tried it, and it works great... Thanks! Just two questions so
far:

1. How can I get different sizes of the icon, or are they just
linked to the

size of the outlet?

I suggest some reading:

http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/nsimage_Class/Reference/Reference.html

http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaDrawingGuide/Images/Images.html

http://developer.apple.com/documentation/Cocoa/Conceptual/ImageView/ImageView.html

2. If you link to a non-existent application, it still returns an
image - Is

there some way to set it to return an error if this happens?

This is what I'd expect ... if an application has no custom icon,
it gets the standard, generic application icon. In this case, you'd
probably want to go with the get the app icon file name, then ask the
app bundle for the resource of that name route. This way, if there's
nothing set for the app icon key, you'll know there's no custom icon.
If so, you can just use the NSWorkspace call to get that custom icon.

--
I.S.

___

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: Explicit release when using garbage collection with circular references

2009-03-22 Thread David Melgar

I'm confused. Bill said that the garbage collection will correctly  
handle releasing these types of objects despite the circular  
references. Therefore it appears that no additional actions are  
required since I am using garbage collection.


What is your approach trying to solve?
I certainly don't follow your reply. Google for what?
Naive in what way?
Avoid circular refs by a proper design? Ok... what is proper?

Generally your message alludes to many things yet provides little  
information.


On Mar 22, 2009, at 5:53 PM, mm w wrote:


I changed my mind, when I was writting this

- (void)sendSharedMessage:(NSString *)msg
{
  NSString *print = [[[NSString alloc] initWithFormat:@ %@,msg]  
autorelease];


  NSLog(@ %@, print);
}

anyway it doesn't change the background


On Sun, Mar 22, 2009 at 2:47 PM, mm w openspec...@gmail.com wrote:

Hello David,

your  garbage collection approach is a bit naive, but not everything
is wrong, you can make a google search, it will point you good
resources anyway,

@implementation AppDelegate

- (void)sendSharedMessage:(NSString *)msg
{
  return [[[NSString alloc] initWithFormat:@ %@,msg] autorelease];
}

@end


@implementation MyObject

- (void)aMathod
{
   id sharedController = [[NSApplication sharedApplication]  
delegate];


   if ([[sharedController class]
instancesRespondToSelector:@selector(sendSharedMessage:)]) {
   NSString aMsg = [[NSString alloc] initWithString:@hello];
[sharedController  
performSelector:@selector(sendSharedMessage:)

withObject:aMsg];
   [aMsg release];
  }

}

@end

 (sorry if there is synthax errors this is a live code)

this model will apply with/or without garbage collection, release
autorelease will be ignored in garbage collection env, avoid as far
is possible circular refs by a proper design.

On Sat, Mar 21, 2009 at 9:16 PM, Bill Bumgarner b...@mac.com wrote:

On Mar 21, 2009, at 9:11 PM, David wrote:


Is there any issue issuing explicit release when using garbage
collection with Leopard and Obj-c 2.0?


-release is ignored entirely.

CFRelease() work as it always does, and balances CFRetain() nicely.

But that isn't the issue.

I've become aware that I have lots of memory not being freed  
within my

application. I presume this is because its a tree structure with
parent child pointers between the objects. If I drop the last
reference to the tree, I presume the tree does not get garbage
collected because each object has circular pointers between them,  
ie

parent has references to children and each child has a reference to
its parent. In this case, it seem that the appropriate course of
action would be to call a specific method to forcibly release each
node in the tree.
Is this the proper approach?
Should garbage collection somehow work anyway?


That would be an incorrect presumption.  The garbage collector  
handles
complexly connected, but not rooted, graphs just fine. Your sub- 
graphs --
trees -- of objects that are no longer referenced by your rooted  
object

graphs should be reaped without a problem.

So, something else is going on.

Have you used 'info gc-roots' to see what is causing the items  
within your

tree to stick around?

b.bum

___

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/openspecies%40gmail.com

This email sent to openspec...@gmail.com





--
-mmw





--
-mmw


___

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: Programmatically Change Icon

I suggest some reading:
 
 http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classe
 s/nsimage_Class/Reference/Reference.html
 
 http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaDrawingGuide/Im
 ages/Images.html
 
 http://developer.apple.com/documentation/Cocoa/Conceptual/ImageView/ImageView.
 html

Thanks for the links, I'll look them over when I get a chance.

This is what I'd expect ... if an application has no custom icon,
 it gets the standard, generic application icon. In this case, you'd
 probably want to go with the get the app icon file name, then ask the
 app bundle for the resource of that name route. This way, if there's
 nothing set for the app icon key, you'll know there's no custom icon.
 If so, you can just use the NSWorkspace call to get that custom icon.

I think I may just go this route, especially if it doesn't break any
copyright/patent/etc. Laws. ;)  But the odd thing is, if I set the path to a
file that I know doesn't exist (ex.
/Applications/soidaoidaiodsaoidiasoadsoidoiaadiosoaidiodaoidasoidaoidasoiado
iasdoidaoidadasoidiaosasidoosdiaiodsiodsa.app) it will still return some
weird page icon.


___

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: Explicit release when using garbage collection with circular references

Because I am like this I won't do the job for you, I will only point
you directions, that's it

Google garbage collection, it's naive to think that's a linear tree.

What Bill told you is right, and my comment is following his thought

Avoiding circular refs: in 95% of cases it can be avoided, by
refactoring his work,
taking a pen and a white paper... and think

Cheers!

On Sun, Mar 22, 2009 at 3:21 PM, David Melgar enki1...@gmail.com wrote:
 I'm confused. Bill said that the garbage collection will correctly handle
 releasing these types of objects despite the circular references. Therefore
 it appears that no additional actions are required since I am using garbage
 collection.

 What is your approach trying to solve?
 I certainly don't follow your reply. Google for what?
 Naive in what way?
 Avoid circular refs by a proper design? Ok... what is proper?

 Generally your message alludes to many things yet provides little
 information.

 On Mar 22, 2009, at 5:53 PM, mm w wrote:

 I changed my mind, when I was writting this

 - (void)sendSharedMessage:(NSString *)msg
 {
  NSString *print = [[[NSString alloc] initWithFormat:@ %@,msg]
 autorelease];

  NSLog(@ %@, print);
 }

 anyway it doesn't change the background


 On Sun, Mar 22, 2009 at 2:47 PM, mm w openspec...@gmail.com wrote:

 Hello David,

 your  garbage collection approach is a bit naive, but not everything
 is wrong, you can make a google search, it will point you good
 resources anyway,

 @implementation AppDelegate

 - (void)sendSharedMessage:(NSString *)msg
 {
  return [[[NSString alloc] initWithFormat:@ %@,msg] autorelease];
 }

 @end


 @implementation MyObject

 - (void)aMathod
 {
   id sharedController = [[NSApplication sharedApplication] delegate];

   if ([[sharedController class]
 instancesRespondToSelector:@selector(sendSharedMessage:)]) {
       NSString aMsg = [[NSString alloc] initWithString:@hello];
        [sharedController performSelector:@selector(sendSharedMessage:)
 withObject:aMsg];
       [aMsg release];
  }

 }

 @end

  (sorry if there is synthax errors this is a live code)

 this model will apply with/or without garbage collection, release
 autorelease will be ignored in garbage collection env, avoid as far
 is possible circular refs by a proper design.

 On Sat, Mar 21, 2009 at 9:16 PM, Bill Bumgarner b...@mac.com wrote:

 On Mar 21, 2009, at 9:11 PM, David wrote:

 Is there any issue issuing explicit release when using garbage
 collection with Leopard and Obj-c 2.0?

 -release is ignored entirely.

 CFRelease() work as it always does, and balances CFRetain() nicely.

 But that isn't the issue.

 I've become aware that I have lots of memory not being freed within my
 application. I presume this is because its a tree structure with
 parent child pointers between the objects. If I drop the last
 reference to the tree, I presume the tree does not get garbage
 collected because each object has circular pointers between them, ie
 parent has references to children and each child has a reference to
 its parent. In this case, it seem that the appropriate course of
 action would be to call a specific method to forcibly release each
 node in the tree.
 Is this the proper approach?
 Should garbage collection somehow work anyway?

 That would be an incorrect presumption.  The garbage collector handles
 complexly connected, but not rooted, graphs just fine. Your sub-graphs
 --
 trees -- of objects that are no longer referenced by your rooted object
 graphs should be reaped without a problem.

 So, something else is going on.

 Have you used 'info gc-roots' to see what is causing the items within
 your
 tree to stick around?

 b.bum

 ___

 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/openspecies%40gmail.com

 This email sent to openspec...@gmail.com




 --
 -mmw




 --
 -mmw





-- 
-mmw
___

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: NSAppleScript - what is going on here?

2009-03-22 Thread Jim Correia


On Mar 22, 2009, at 1:53 PM, Steve Cronin wrote:

I'm an ObjC guy -- I generally avoid the C stuff if possible -  
'cause I have to support my own code.


Objective-C is a superset of C. Avoiding the C stuff isn't really  
possible - it is a core part of the language.


As far as choice of API, I tend to be a pragmatist, choosing an  
appropriate tool for the task at hand, without artificial restrictions.


JIm
___

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: Programmatically Change Icon


On Mar 22, 2009, at 6:29 PM, Pierce Freeman wrote:


But the odd thing is, if I set the path to a
file that I know doesn't exist (ex.
/Applications/ 
soidaoidaiodsaoidiasoadsoidoiaadiosoaidiodaoidasoidaoidasoiado
iasdoidaoidadasoidiaosasidoosdiaiodsiodsa.app) it will still return  
some

weird page icon.


  Come to think of it, it's strange that you get an icon for a non- 
existent file, but if it *does* exist, I'd always expect some sort of  
icon. I've never run into this situation personally. Which specific  
method are you using? There are:


– iconForFile:
– iconForFileType:
– iconForFiles:

  Just curious.

  In your case, though, if you're going after applications, you'd  
presumably already have a list of app bundle paths, so it shouldn't be  
a problem, right?


--
I.S.




___

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: Explicit release when using garbage collection with circular references

2009-03-22 Thread Jean-Daniel Dupas



Le 22 mars 09 à 23:37, mm w a écrit :


Because I am like this I won't do the job for you, I will only point
you directions, that's it

Google garbage collection, it's naive to think that's a linear  
tree.


What Bill told you is right, and my comment is following his thought

Avoiding circular refs: in 95% of cases it can be avoided, by
refactoring his work,
taking a pen and a white paper... and think



I don't understand your point here.

Circular references have not to be avoid. They are not an error.

As previously mention, the garbage collector tracks root objects, and  
so it should properly deal with circular references.


In a reference counted world, they are valid too, as long as the who  
retain who policy is properly designed.


___

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: Explicit release when using garbage collection with circular references

2009-03-22 Thread Clark Cox

On Sun, Mar 22, 2009 at 3:37 PM, mm w openspec...@gmail.com wrote:
 Because I am like this I won't do the job for you, I will only point
 you directions, that's it

 Google garbage collection, it's naive to think that's a linear tree.

 What Bill told you is right, and my comment is following his thought

 Avoiding circular refs: in 95% of cases it can be avoided,

They can be avoided, but why? They are not an error under garbage
collection, and there is no reason to avoid them.

-- 
Clark S. Cox III
clarkc...@gmail.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

Re: Programmatically Change Icon

Come to think of it, it's strange that you get an icon for a non-
 existent file, but if it *does* exist, I'd always expect some sort of
 icon. I've never run into this situation personally. Which specific
 method are you using? There are:
 
  iconForFile:
  iconForFileType:
  iconForFiles:

I kind of figured that it was a bit odd.  I am using iconForFile and then
the path.

In your case, though, if you're going after applications, you'd
 presumably already have a list of app bundle paths, so it shouldn't be
 a problem, right?

Presumably, but if the user deleted the application it would be nice to
alert the user saying something instead of just showing some empty page
icon. ;)


___

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: Explicit release when using garbage collection with circular references

On Sun, Mar 22, 2009 at 3:54 PM, Jean-Daniel Dupas
devli...@shadowlab.org wrote:

 Le 22 mars 09 à 23:37, mm w a écrit :

 Because I am like this I won't do the job for you, I will only point
 you directions, that's it

 Google garbage collection, it's naive to think that's a linear tree.

 What Bill told you is right, and my comment is following his thought

 Avoiding circular refs: in 95% of cases it can be avoided, by
 refactoring his work,
 taking a pen and a white paper... and think


 I don't understand your point here.

 Circular references have not to be avoid. They are not an error.


yes that's true

 As previously mention, the garbage collector tracks root objects, and so it
 should properly deal with circular references.


yep right, my point was circular refs are bad

 In a reference counted world, they are valid too, as long as the who retain
 who policy is properly designed.



yep right, my point was circular refs are bad

-- 
-mmw
___

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: Explicit release when using garbage collection with circular references

maybe in your world, anyway there are a bunch of reasons to avoid circular refs
I let you discover it

Cheers!

On Sun, Mar 22, 2009 at 3:58 PM, Clark Cox clarkc...@gmail.com wrote:
 On Sun, Mar 22, 2009 at 3:37 PM, mm w openspec...@gmail.com wrote:
 Because I am like this I won't do the job for you, I will only point
 you directions, that's it

 Google garbage collection, it's naive to think that's a linear tree.

 What Bill told you is right, and my comment is following his thought

 Avoiding circular refs: in 95% of cases it can be avoided,

 They can be avoided, but why? They are not an error under garbage
 collection, and there is no reason to avoid them.

 --
 Clark S. Cox III
 clarkc...@gmail.com




-- 
-mmw
___

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: Explicit release when using garbage collection with circular references

2009-03-22 Thread Clark Cox

It's not very conducive to conversation to make claims, and then
refuse to back them up, and leave it at I let you discover it.

On Sun, Mar 22, 2009 at 4:19 PM, mm w openspec...@gmail.com wrote:
 maybe in your world, anyway there are a bunch of reasons to avoid circular 
 refs
 I let you discover it

 Cheers!

 On Sun, Mar 22, 2009 at 3:58 PM, Clark Cox clarkc...@gmail.com wrote:
 On Sun, Mar 22, 2009 at 3:37 PM, mm w openspec...@gmail.com wrote:
 Because I am like this I won't do the job for you, I will only point
 you directions, that's it

 Google garbage collection, it's naive to think that's a linear tree.

 What Bill told you is right, and my comment is following his thought

 Avoiding circular refs: in 95% of cases it can be avoided,

 They can be avoided, but why? They are not an error under garbage
 collection, and there is no reason to avoid them.

 --
 Clark S. Cox III
 clarkc...@gmail.com




 --
 -mmw




-- 
Clark S. Cox III
clarkc...@gmail.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

Re: MacRoman - UTF8 [solved]

2009-03-22 Thread Peter Duniho


On Mar 22, 2009, at 5:22 AM, Uli Kusterer wrote:


On 22.03.2009, at 12:22, Michael Ash wrote:

Just a general request for the list here: could we not add [solved]
to the topic when the problem is solved? It breaks threading and
causes confusion. Just stick it into the original thread. The act of
having solved the problem is not so significant that it needs to be
made evident the moment we read the subject


What mail app are you using? Apple Mail shows it just fine as part  
of the thread it was in. So do most other mail apps. There's a  
header in RFC822-style mail messages that indicates the thread, the  
subject doesn't even begin to figure into the equation.


It doesn't matter what email client someone _might_ be using.  The  
fact that not ALL email clients can deal with it is sufficient cause  
for concern.


Of particular note is Apple's own mail archive for the mailing list.   
Maybe they've fixed it recently, but a couple of years ago when I  
first started with Cocoa, I got very frustrated trying to read threads  
in the archive only to find that the one email message in which the  
solution was to be found, was not grouped with the rest of the thread  
(this is especially problematic when solved is prepended to the  
subject, as is so often the case).  The experience was much as if  
someone had torn the last page out of a gripping suspense novel.


I've gotten enough grief already for not being willing to play along  
with community philosophy here, so I've kept my mouth shut on this  
particular issue.  But I think Michael's a frequent enough contributor  
and has a high enough reputation that if he makes a suggestion, people  
ought to consider it seriously.  I will happily state my agreement  
with his suggestion, given that it's been a source of frustration to  
me since I started following this mailing list.


Please.  Stop mucking with the subject.  There really is very little  
benefit to adding the word solved to the subject, but there is  
definitely a significant drawback.  I have followed various community/ 
online electronic forums for nearly thirty years, and this is the only  
one I've run across in which there is this habit of adding solved to  
the subject.  No doubt it's not the only place where the behavior can  
be seen, but there's ample evidence that it's not helpful enough to  
gain traction as a widespread convention.  I'd just as soon see it  
disappear here too.


And my apologies to Michael if my statement of support for his request  
only hurts the chances of it being honored.  :)


Pete
___

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: Explicit release when using garbage collection with circular references

2009-03-22 Thread David Melgar


Some people do that to try and impress.
I'm not impressed.
No useful information.

On Mar 22, 2009, at 7:22 PM, Clark Cox wrote:


It's not very conducive to conversation to make claims, and then
refuse to back them up, and leave it at I let you discover it.

On Sun, Mar 22, 2009 at 4:19 PM, mm w openspec...@gmail.com wrote:
maybe in your world, anyway there are a bunch of reasons to avoid  
circular refs

I let you discover it

Cheers!

On Sun, Mar 22, 2009 at 3:58 PM, Clark Cox clarkc...@gmail.com  
wrote:

On Sun, Mar 22, 2009 at 3:37 PM, mm w openspec...@gmail.com wrote:
Because I am like this I won't do the job for you, I will only  
point

you directions, that's it

Google garbage collection, it's naive to think that's a  
linear tree.


What Bill told you is right, and my comment is following his  
thought


Avoiding circular refs: in 95% of cases it can be avoided,


They can be avoided, but why? They are not an error under garbage
collection, and there is no reason to avoid them.

--
Clark S. Cox III
clarkc...@gmail.com





--
-mmw





--
Clark S. Cox III
clarkc...@gmail.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

Re: Explicit release when using garbage collection with circular references

No but this point is on left-side of this subject, anyway,

here we can see one side effect at code design-level:

here we have some symptoms:

- a lack of visibility
- when you can be the owner : be the owner and control what is happening

direct effect you are screwing up the garbage collection system

a last comment:
when someone is hill, do you try to fix the symptoms or the reasons?

one rule: there is no circular refs in your design, it's the same for
people who are designing circuits: there is no bridge, there is no
circular refs allowed

if you start with those constraints in mind I can ensure you that you
won't fall in this kind of trap, and always be able to increase the
possibility of your application, circular refs are against every oop
design logic, when you face it, that's the result and the consequence
of a previous mistake,

sure sometimes for various reasons you will use a circular ref

it's not 100% rule, sometimes it's good to be evil!


Cheers!

On Sun, Mar 22, 2009 at 4:22 PM, Clark Cox clarkc...@gmail.com wrote:
 It's not very conducive to conversation to make claims, and then
 refuse to back them up, and leave it at I let you discover it.

 On Sun, Mar 22, 2009 at 4:19 PM, mm w openspec...@gmail.com wrote:
 maybe in your world, anyway there are a bunch of reasons to avoid circular 
 refs
 I let you discover it

 Cheers!

 On Sun, Mar 22, 2009 at 3:58 PM, Clark Cox clarkc...@gmail.com wrote:
 On Sun, Mar 22, 2009 at 3:37 PM, mm w openspec...@gmail.com wrote:
 Because I am like this I won't do the job for you, I will only point
 you directions, that's it

 Google garbage collection, it's naive to think that's a linear tree.

 What Bill told you is right, and my comment is following his thought

 Avoiding circular refs: in 95% of cases it can be avoided,

 They can be avoided, but why? They are not an error under garbage
 collection, and there is no reason to avoid them.

 --
 Clark S. Cox III
 clarkc...@gmail.com




 --
 -mmw




 --
 Clark S. Cox III
 clarkc...@gmail.com




-- 
-mmw
___

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: Explicit release when using garbage collection with circular references

On Sun, Mar 22, 2009 at 4:32 PM, David Melgar enki1...@gmail.com wrote:
 Some people do that to try and impress.
 I'm not impressed.
 No useful information.


it's not my point, i don't understand your feeling here, I am not
trying to impress anyone, I'm only give some points

 On Mar 22, 2009, at 7:22 PM, Clark Cox wrote:

 It's not very conducive to conversation to make claims, and then
 refuse to back them up, and leave it at I let you discover it.

 On Sun, Mar 22, 2009 at 4:19 PM, mm w openspec...@gmail.com wrote:

 maybe in your world, anyway there are a bunch of reasons to avoid
 circular refs
 I let you discover it

 Cheers!

 On Sun, Mar 22, 2009 at 3:58 PM, Clark Cox clarkc...@gmail.com wrote:

 On Sun, Mar 22, 2009 at 3:37 PM, mm w openspec...@gmail.com wrote:

 Because I am like this I won't do the job for you, I will only point
 you directions, that's it

 Google garbage collection, it's naive to think that's a linear
 tree.

 What Bill told you is right, and my comment is following his thought

 Avoiding circular refs: in 95% of cases it can be avoided,

 They can be avoided, but why? They are not an error under garbage
 collection, and there is no reason to avoid them.

 --
 Clark S. Cox III
 clarkc...@gmail.com




 --
 -mmw




 --
 Clark S. Cox III
 clarkc...@gmail.com





-- 
-mmw
___

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: Explicit release when using garbage collection with circular references

ref my previous email,

anyway there are other aspects and side effects due to the circular
refs, and one this is a memory issue, GC is now almost clever to
detect that's ObjectB reference is hold by a previous ObjectA ref to
Object0 our first reference, but it wasn't true at the beginning, and
I am pretty sure there are still some undiscovered effects

by adopting a proper design you will avoid this, here you can see a
bunch of unsolvable requests due to this kind of mistake, sure people
find patch on patch on patch and finish with a ton of lines to try to
correct the reasons,

see my previous comment on symptoms and consequences

Cheers!

On Sun, Mar 22, 2009 at 4:53 PM, mm w openspec...@gmail.com wrote:
 On Sun, Mar 22, 2009 at 4:32 PM, David Melgar enki1...@gmail.com wrote:
 Some people do that to try and impress.
 I'm not impressed.
 No useful information.


 it's not my point, i don't understand your feeling here, I am not
 trying to impress anyone, I'm only give some points

 On Mar 22, 2009, at 7:22 PM, Clark Cox wrote:

 It's not very conducive to conversation to make claims, and then
 refuse to back them up, and leave it at I let you discover it.

 On Sun, Mar 22, 2009 at 4:19 PM, mm w openspec...@gmail.com wrote:

 maybe in your world, anyway there are a bunch of reasons to avoid
 circular refs
 I let you discover it

 Cheers!

 On Sun, Mar 22, 2009 at 3:58 PM, Clark Cox clarkc...@gmail.com wrote:

 On Sun, Mar 22, 2009 at 3:37 PM, mm w openspec...@gmail.com wrote:

 Because I am like this I won't do the job for you, I will only point
 you directions, that's it

 Google garbage collection, it's naive to think that's a linear
 tree.

 What Bill told you is right, and my comment is following his thought

 Avoiding circular refs: in 95% of cases it can be avoided,

 They can be avoided, but why? They are not an error under garbage
 collection, and there is no reason to avoid them.

 --
 Clark S. Cox III
 clarkc...@gmail.com




 --
 -mmw




 --
 Clark S. Cox III
 clarkc...@gmail.com





 --
 -mmw




-- 
-mmw
___

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: Explicit release when using garbage collection with circular references