Re: How to do Save As... in Lion

2011-09-18 Thread Kyle Sluder 
On Sep 18, 2011, at 9:59 PM, Graham Cox  wrote:

> Save As is used for saving as a different format - not just in many apps, but 
> by default if you have NSDocument set up just so. I'm not sure how that 
> behaviour is handled with Lion's autosave enabled, but in 10.6 and earlier, 
> Save As automatically adds a format menu if your document supports multiple 
> formats.

I would argue encoding is not a format. But I agree the Save panel is the 
correct place to put the Encoding selector, *unless* the encoding is an 
integral part of the document (for example, an HTML editor) in which case the 
encoding should be settable in an inspector instead of or in addition to the 
Save panel.

--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: How to do Save As... in Lion

2011-09-18 Thread Graham Cox 
Save As is used for saving as a different format - not just in many apps, but 
by default if you have NSDocument set up just so. I'm not sure how that 
behaviour is handled with Lion's autosave enabled, but in 10.6 and earlier, 
Save As automatically adds a format menu if your document supports multiple 
formats.

Saving As a different format does imply saving as a different file - because 
the extensions are different even if the name is otherwise the same.

TextEdit is something of an aberration in fact.

--Graham


On 19/09/2011, at 2:53 PM, Ron Hunsinger wrote:

> That's not what I would expect as a user. "Save as..." means "Save as a 
> different file". I wouldn't expect to use it to "Save in the same file in a 
> different format", any more than I would use it to "Save in the same file 
> with different content."
> 
> Look at how TextEdit handles letting the user choose a file format, with its 
> "Make Plain Text / Make Rich Text" menu commands.

___

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 do Save As... in Lion

2011-09-18 Thread Ron Hunsinger 

On Sep 18, 2011, at 9:33 PM, Gerriet M. Denkmann wrote:
> Peviously if a user wanted a specific encoding, Save As... was the only 
> choice (with choosing the original filename).

That's not what I would expect as a user. "Save as..." means "Save as a 
different file". I wouldn't expect to use it to "Save in the same file in a 
different format", any more than I would use it to "Save in the same file with 
different content."

Look at how TextEdit handles letting the user choose a file format, with its 
"Make Plain Text / Make Rich Text" menu commands.

-Ron Hunsinger

___

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 do Save As... in Lion

2011-09-18 Thread Gerriet M. Denkmann 

On 19 Sep 2011, at 02:02, Quincey Morris wrote:

> On Sep 18, 2011, at 03:05 , Gerriet M. Denkmann wrote:
> 
>> No, this is not what I really want.
> 
> Yet that is what you asked about. :)
> 
>> Think of a file which contains Englisch text, and which has been saved as 
>> Ascii or Mac Roman.
>> Now I enter some Chinese characters and it has to be saved in Utf-8 or 
>> Simplified Chinese (Mac) etc.
>> But it should NOT be saved under a new name. Saved in place with version 
>> working as well.
> 
> Well, how did this work before (pre-Lion), when the user issued a Save? You 
> detected that the current file encoding was inadequate and changed the Save 
> to a Save As?

The previous version just used Utf-8 when the current encoding was not good 
enough.
But now I have decided to give uses a choice of applicable encodings.

Peviously if a user wanted a specific encoding, Save As... was the only choice 
(with choosing the original filename).

Kind regards,

Gerriet.


___

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: Launching an app with extended rights

2011-09-18 Thread Kyle Sluder 
On Sun, Sep 18, 2011 at 6:16 PM, Tito Ciuro  wrote:
> I just downloaded SMJobBless. Thanks for the info Kyle.

SMJobBless is a function in SerivceManagement.framework.

Confusingly, there is also a sample project named SMJobBless.

Hopefully you have not confused the two. You can study the sample code
to learn how to use the API function. But you don't need to copy the
sample code into your project or anything.

--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: Launching an app with extended rights

2011-09-18 Thread Tito Ciuro 
I just downloaded SMJobBless. Thanks for the info Kyle.

Regards,

-- Tito

On Sep 18, 2011, at 4:25 PM, Kyle Sluder wrote:

> The modern way is to use SMJobBless. ;-)
> 
> Apple is discouraging people from using AuthorizationExecuteWithPrivileges 
> directly. Your scenario sounds like the perfect use case for launchd.
> 
> --Kyle Sluder
> (Sent from the road)
> 
> On Sep 18, 2011, at 2:27 PM, Tito Ciuro  wrote:
> 
>> Hi Kyle,
>> 
>> This is exactly what I've done, except that I'm not using SMJobBless.
>> 
>> -- Tito
>> 
>> On Sep 18, 2011, at 2:08 PM, Kyle Sluder wrote:
>> 
>>> The modern way to do this is to split the server portion into a separate 
>>> process and use SMJobBless to submit it as a privileged launchd task.
>>> 
>>> --Kyle Sluder
>>> (Sent from the road)
>>> 
>>> On Sep 18, 2011, at 9:05 AM, Tito Ciuro  wrote:
>>> 
 Hello,
 
 When my app launches, I'd like it to listen to port 80 or 443. To do that, 
 I believe I need to use Security Framework Authorization API to obtain 
 extended rights. A potential solution is to split the app's executable int 
 two parts:
 
 1) one executable, the main one that first gets launched, obtains extended 
 rights.
 2) the app itself, which is the embedded web server.
 
 When the user double clicks the app, it would execute (1) with:
 
 SFAuthorization *authorization = [SFAuthorization authorization];
 BOOL result = [authorization obtainWithRights:NULL
 
 flags:kAuthorizationFlagExtendRights
   environment:NULL
  authorizedRights:NULL
 error:&error];
 
 and then use NSTask to launch (2) via:
 
 + (NSString *)stringByLaunchingPath:(NSString *)processPath
 withArguments:(NSArray *)arguments
 authorization:(SFAuthorization *)authorization
 error:(NSError **)error;
 
 Is this approach the way to go, or is there an easier/better/safer way do 
 to that?
 
 Thank you,
 
 -- Tito
 ___
 
 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/kyle.sluder%40gmail.com
 
 This email sent to kyle.slu...@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

Canceling text-completion

2011-09-18 Thread Shane Stanley 
I'm sure I'm missing something simple...

I'm using text-completion in a text view. It's generally working as I want, but 
I can't figure out how, programmatically, to do the equivalent of hitting the 
esc key to cancel it (which I want to do if the user does something like tries 
to save, etc). Any clues?

-- 
Shane Stanley 
'AppleScriptObjC Explored' 

___

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: Launching an app with extended rights

2011-09-18 Thread Kyle Sluder 
The modern way is to use SMJobBless. ;-)

Apple is discouraging people from using AuthorizationExecuteWithPrivileges 
directly. Your scenario sounds like the perfect use case for launchd.

--Kyle Sluder
(Sent from the road)

On Sep 18, 2011, at 2:27 PM, Tito Ciuro  wrote:

> Hi Kyle,
> 
> This is exactly what I've done, except that I'm not using SMJobBless.
> 
> -- Tito
> 
> On Sep 18, 2011, at 2:08 PM, Kyle Sluder wrote:
> 
>> The modern way to do this is to split the server portion into a separate 
>> process and use SMJobBless to submit it as a privileged launchd task.
>> 
>> --Kyle Sluder
>> (Sent from the road)
>> 
>> On Sep 18, 2011, at 9:05 AM, Tito Ciuro  wrote:
>> 
>>> Hello,
>>> 
>>> When my app launches, I'd like it to listen to port 80 or 443. To do that, 
>>> I believe I need to use Security Framework Authorization API to obtain 
>>> extended rights. A potential solution is to split the app's executable int 
>>> two parts:
>>> 
>>> 1) one executable, the main one that first gets launched, obtains extended 
>>> rights.
>>> 2) the app itself, which is the embedded web server.
>>> 
>>> When the user double clicks the app, it would execute (1) with:
>>> 
>>>  SFAuthorization *authorization = [SFAuthorization authorization];
>>>  BOOL result = [authorization obtainWithRights:NULL
>>>  
>>> flags:kAuthorizationFlagExtendRights
>>>environment:NULL
>>>   authorizedRights:NULL
>>>  error:&error];
>>> 
>>> and then use NSTask to launch (2) via:
>>> 
>>> + (NSString *)stringByLaunchingPath:(NSString *)processPath
>>>  withArguments:(NSArray *)arguments
>>>  authorization:(SFAuthorization *)authorization
>>>  error:(NSError **)error;
>>> 
>>> Is this approach the way to go, or is there an easier/better/safer way do 
>>> to that?
>>> 
>>> Thank you,
>>> 
>>> -- Tito
>>> ___
>>> 
>>> 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/kyle.sluder%40gmail.com
>>> 
>>> This email sent to kyle.slu...@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: Launching an app with extended rights

2011-09-18 Thread Tito Ciuro 
Hi Kyle,

This is exactly what I've done, except that I'm not using SMJobBless.

-- Tito

On Sep 18, 2011, at 2:08 PM, Kyle Sluder wrote:

> The modern way to do this is to split the server portion into a separate 
> process and use SMJobBless to submit it as a privileged launchd task.
> 
> --Kyle Sluder
> (Sent from the road)
> 
> On Sep 18, 2011, at 9:05 AM, Tito Ciuro  wrote:
> 
>> Hello,
>> 
>> When my app launches, I'd like it to listen to port 80 or 443. To do that, I 
>> believe I need to use Security Framework Authorization API to obtain 
>> extended rights. A potential solution is to split the app's executable int 
>> two parts:
>> 
>> 1) one executable, the main one that first gets launched, obtains extended 
>> rights.
>> 2) the app itself, which is the embedded web server.
>> 
>> When the user double clicks the app, it would execute (1) with:
>> 
>>   SFAuthorization *authorization = [SFAuthorization authorization];
>>   BOOL result = [authorization obtainWithRights:NULL
>>   
>> flags:kAuthorizationFlagExtendRights
>> environment:NULL
>>authorizedRights:NULL
>>   error:&error];
>> 
>> and then use NSTask to launch (2) via:
>> 
>> + (NSString *)stringByLaunchingPath:(NSString *)processPath
>>   withArguments:(NSArray *)arguments
>>   authorization:(SFAuthorization *)authorization
>>   error:(NSError **)error;
>> 
>> Is this approach the way to go, or is there an easier/better/safer way do to 
>> that?
>> 
>> Thank you,
>> 
>> -- Tito
>> ___
>> 
>> 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/kyle.sluder%40gmail.com
>> 
>> This email sent to kyle.slu...@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: Launching an app with extended rights

2011-09-18 Thread Kyle Sluder 
The modern way to do this is to split the server portion into a separate 
process and use SMJobBless to submit it as a privileged launchd task.

--Kyle Sluder
(Sent from the road)

On Sep 18, 2011, at 9:05 AM, Tito Ciuro  wrote:

> Hello,
> 
> When my app launches, I'd like it to listen to port 80 or 443. To do that, I 
> believe I need to use Security Framework Authorization API to obtain extended 
> rights. A potential solution is to split the app's executable int two parts:
> 
> 1) one executable, the main one that first gets launched, obtains extended 
> rights.
> 2) the app itself, which is the embedded web server.
> 
> When the user double clicks the app, it would execute (1) with:
> 
>SFAuthorization *authorization = [SFAuthorization authorization];
>BOOL result = [authorization obtainWithRights:NULL
>
> flags:kAuthorizationFlagExtendRights
>  environment:NULL
> authorizedRights:NULL
>error:&error];
> 
> and then use NSTask to launch (2) via:
> 
> + (NSString *)stringByLaunchingPath:(NSString *)processPath
>withArguments:(NSArray *)arguments
>authorization:(SFAuthorization *)authorization
>error:(NSError **)error;
> 
> Is this approach the way to go, or is there an easier/better/safer way do to 
> that?
> 
> Thank you,
> 
> -- Tito
> ___
> 
> 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/kyle.sluder%40gmail.com
> 
> This email sent to kyle.slu...@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

Looking for Tab framework

2011-09-18 Thread Todd Freese 
I am looking for recommendations for a open source framework to create small 
tabs. I have looked at PSMTabBarControl and Chromium Tabs. Just wondering if 
there are any others out there?

Todd Freese
The Filmworkers Club

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__
___

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

[SOLVED] Re: Launching an app with extended rights

2011-09-18 Thread Tito Ciuro 
Hi Nick,

Thank so much for the heads up. Works fine!

Thanks for the help,

-- Tito

On Sep 18, 2011, at 10:13 AM, Nick Zitzmann wrote:

> 
> On Sep 18, 2011, at 10:05 AM, Tito Ciuro wrote:
> 
>> Hello,
>> 
>> When my app launches, I'd like it to listen to port 80 or 443. To do that, I 
>> believe I need to use Security Framework Authorization API to obtain 
>> extended rights. A potential solution is to split the app's executable int 
>> two parts:
>> 
>> 1) one executable, the main one that first gets launched, obtains extended 
>> rights.
>> 2) the app itself, which is the embedded web server.
>> 
>> When the user double clicks the app, it would execute (1) with:
>> 
>>   SFAuthorization *authorization = [SFAuthorization authorization];
>>   BOOL result = [authorization obtainWithRights:NULL
>>   
>> flags:kAuthorizationFlagExtendRights
>> environment:NULL
>>authorizedRights:NULL
>>   error:&error];
> 
> You need to obtain the system.privilege.admin right if you want to launch a 
> task with root privileges. You should also use the 
> kAuthorizationFlagInteractionAllowed and kAuthorizationFlagPreAuthorize flags 
> as well.
> 
>> and then use NSTask to launch (2) via:
>> 
>> + (NSString *)stringByLaunchingPath:(NSString *)processPath
>>  withArguments:(NSArray *)arguments
>>  authorization:(SFAuthorization *)authorization
>>  error:(NSError **)error;
>> 
>> Is this approach the way to go, or is there an easier/better/safer way do to 
>> that?
> 
> You must use AuthorizationExecuteWithPrivileges() to launch a task with 
> privileges; you cannot do that with NSTask.
> 
> Nick Zitzmann
> 
> 
> 
> 

___

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 do Save As... in Lion

2011-09-18 Thread Quincey Morris 
On Sep 18, 2011, at 03:05 , Gerriet M. Denkmann wrote:

> No, this is not what I really want.

Yet that is what you asked about. :)

> Think of a file which contains Englisch text, and which has been saved as 
> Ascii or Mac Roman.
> Now I enter some Chinese characters and it has to be saved in Utf-8 or 
> Simplified Chinese (Mac) etc.
> But it should NOT be saved under a new name. Saved in place with version 
> working as well.

Well, how did this work before (pre-Lion), when the user issued a Save? You 
detected that the current file encoding was inadequate and changed the Save to 
a Save As?


___

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: Launching an app with extended rights

2011-09-18 Thread Nick Zitzmann 

On Sep 18, 2011, at 10:05 AM, Tito Ciuro wrote:

> Hello,
> 
> When my app launches, I'd like it to listen to port 80 or 443. To do that, I 
> believe I need to use Security Framework Authorization API to obtain extended 
> rights. A potential solution is to split the app's executable int two parts:
> 
> 1) one executable, the main one that first gets launched, obtains extended 
> rights.
> 2) the app itself, which is the embedded web server.
> 
> When the user double clicks the app, it would execute (1) with:
> 
>SFAuthorization *authorization = [SFAuthorization authorization];
>BOOL result = [authorization obtainWithRights:NULL
>
> flags:kAuthorizationFlagExtendRights
>  environment:NULL
> authorizedRights:NULL
>error:&error];

You need to obtain the system.privilege.admin right if you want to launch a 
task with root privileges. You should also use the 
kAuthorizationFlagInteractionAllowed and kAuthorizationFlagPreAuthorize flags 
as well.

> and then use NSTask to launch (2) via:
> 
> + (NSString *)stringByLaunchingPath:(NSString *)processPath
>   withArguments:(NSArray *)arguments
>   authorization:(SFAuthorization *)authorization
>   error:(NSError **)error;
> 
> Is this approach the way to go, or is there an easier/better/safer way do to 
> that?

You must use AuthorizationExecuteWithPrivileges() to launch a task with 
privileges; you cannot do that with NSTask.

Nick Zitzmann




___

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

Launching an app with extended rights

2011-09-18 Thread Tito Ciuro 
Hello,

When my app launches, I'd like it to listen to port 80 or 443. To do that, I 
believe I need to use Security Framework Authorization API to obtain extended 
rights. A potential solution is to split the app's executable int two parts:

1) one executable, the main one that first gets launched, obtains extended 
rights.
2) the app itself, which is the embedded web server.

When the user double clicks the app, it would execute (1) with:

SFAuthorization *authorization = [SFAuthorization authorization];
BOOL result = [authorization obtainWithRights:NULL
flags:kAuthorizationFlagExtendRights
  environment:NULL
 authorizedRights:NULL
error:&error];

and then use NSTask to launch (2) via:

+ (NSString *)stringByLaunchingPath:(NSString *)processPath
withArguments:(NSArray *)arguments
authorization:(SFAuthorization *)authorization
error:(NSError **)error;

Is this approach the way to go, or is there an easier/better/safer way do to 
that?

Thank you,

-- Tito
___

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 do Save As... in Lion

2011-09-18 Thread Gerriet M. Denkmann 

On 18 Sep 2011, at 10:13, Quincey Morris wrote:

> On Sep 17, 2011, at 19:59 , Gerriet M. Denkmann wrote:
> 
>> My app had (before Lion) a Menu Item Save As... which brought up a save 
>> panel with a SavePanelAccessory, which contained a PopUpButton with all 
>> available stringEncodings.
>> 
>> In Lion there is only Save... (which also shows my SavePanelAccessory) for 
>> new documents.
>> But after this, there is only Save a Version, which does NOT show a save 
>> panel (and thus no SavePanelAccessory).
>> 
>> How should I implement the old pre-Lion feature of setting the 
>> stringEncoding?
> 
> The Lion way is via Duplicate. This creates a new document, and when you save 
> it the save panel will be displayed.

No, this is not what I really want.

Think of a file which contains Englisch text, and which has been saved as Ascii 
or Mac Roman.
Now I enter some Chinese characters and it has to be saved in Utf-8 or 
Simplified Chinese (Mac) etc.
But it should NOT be saved under a new name. Saved in place with version 
working as well.

Currently I have implemented File → Set Encoding... which works quite nicely.


Kind regards,

Gerriet.




___

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