Re: App opens in wrong language on some users' machines

2016-03-05 Thread Ken Thomases 
On Mar 5, 2016, at 3:32 PM, SevenBits  wrote:
> 
> Some users of my app have reported to me that, despite their Mac being set to 
> English, the program opens in German (it’s always German, never any other 
> language). I have never been able to reproduce this on any Mac I’ve tried on. 
> I’m not sure why the app would open in German. Has anyone here encountered an 
> issue like this before?
> 
> My Xcode project has a development language of English, and uses Base 
> localization. I’ve never received a bug report like this on any other 
> language, so my initial thought is that there must be something wrong with my 
> localization settings, but I don’t see anything out of place.
> 
> Anyone have any pointers of things to try first?

Have your affected users verify that the system language is exactly "English" 
and not a country-specific variant such as "English (U.K.)".  Or, if it is a 
country-specific variant, that plain "English" is also in the list below that.  
Ideally, they'd share a screenshot of the Language & Region pane of System 
Preferences.  Or the output of "defaults read -g AppleLanguages".

As a test, you could have them do "defaults write your.bundle.id.here 
AppleLanguages -array en" to see if that fixes it.  To restore things to normal 
(a.k.a. broken), they'd do "defaults delete your.bundle.id.here AppleLanguages".

Regards,
Ken


___

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

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

Re: App opens in wrong language on some users' machines

2016-03-05 Thread Quincey Morris 
On Mar 5, 2016, at 17:24 , Quincey Morris  
wrote:
> 
> the strings themselves are demonstrably different

Well, I take this back. The .strings *files* are demonstrably different.

Normally, the method for looking up localized strings (-[NSBundle 
localizedStringForKey:value:table:]) returns the key if the localized value 
doesn’t exist, but the keys in the IB-generated .strings files for the other 
localizations are *not* the English text from the base localization, but some 
random IB object IDs. That might explain why the rules are different: returning 
the key would be meaningless.

The only way to find out would be to submit a bug report with the question. In 
practical terms of getting a solution out to your users, I guess you just fix 
it using whatever means work right now.

___

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

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

Re: App opens in wrong language on some users' machines

2016-03-05 Thread Quincey Morris 
On Mar 5, 2016, at 15:21 , SevenBits  wrote:
> 
> I did not, mainly because I was under the assumption that you didn't need to 
> explicitly localize the app in its development language; you could provide 
> translations for specific languages, and if there wasn't a translation for 
> the user's language, then the development or Base language would be used. 
> That would seem to make sense and since it worked for me and the majority of 
> my users... well, I know we're not supposed to make assumptions, but what's a 
> "base language" for, if not to accomplish this behavior?


Here’s what I see in the documentation:

https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPInternational/InternationalizingYourUserInterface/InternationalizingYourUserInterface.html
Using Base Internationalization [Updated: 2015-09-16]

> Base internationalization separates user-facing strings from .storyboard and 
> .xib files. It relieves localizers of the need to modify .storyboard and .xib 
> files in Interface Builder. Instead, an app has just one set of .storyboard 
> and .xib files where strings are in the development language—the language 
> that you used to create the .storyboard and .xib files. These .storyboard and 
> .xib files are called the base internationalization. When you export 
> localizations, the development language strings are the source that is 
> translated into multiple languages. When you import localizations, Xcode 
> generates language-specific strings files for each .storyboard and .xib file. 
> The strings files don’t appear in the project navigator until you import 
> localizations or add languages.

(This is a fairly recently updated document, so it should be fairly technically 
correct, although it’s possible the the introductory material reflects an older 
implementation.)

The way I read this is that the contents of the base files are treated as 
English, your development language. Keep in mind, FWIW, that the XIB files are 
in the base localization. Only the corresponding strings files are in the other 
localizations, so there is an asymmetry between the base and other 
localizations.

But, according to your github repository, you have an en.lproj subdirectory *as 
well as* a base.lproj subdirectory. IOW, your project claims to have an 
*English* localization on top of the base localization. Logic says this 
localization would be use *instead of* the base localization on an English 
system. The languages are the same in this case, but the strings themselves are 
demonstrably different. Logic says that the nicely complete set of English 
strings in the base localization are ignored in favor of what’s in the en 
localization, which happens to be incomplete in this case. Apparently missing 
strings result in substitutions from a (random?) other localization.

Logic therefore says you should *either* remove the en localization, *or* you 
should complete the missing portions of the en localization. I don’t know what 
the considerations might be, one way or the other, but I think I’d probably 
choose the latter — generate the English XLIFF, fill in any missing bits, 
re-import. That’s because you might choose to send the English out to a 
documentation specialist in the future, for things like grammar and word usage, 
and what I’ve seen on the developer forums suggests that trying to customize 
the base localization via XLIFF doesn’t work.

___

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

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

Re: Starting out with storyboards (on Mac)

2016-03-05 Thread Luther Baker 
Thanks for posting those great references Bill!

Luther
On Sat, Mar 5, 2016 at 1:04 PM Bill Cheeseman  wrote:

>
> > On Mar 5, 2016, at 1:35 PM, Gary L. Wade 
> wrote:
> >
> > On Mar 2, 2016, at 11:20 AM, Bill Cheeseman  > wrote:
> >
> >> Broadening my horizons is *always* one of my purposes.
> >
> > Sounds like your book will be getting a sequel by the end of it? Swift
> Cocoa Recipes for Apple Platforms?
>
>
> No, my book writing days are over and done with. I do occasionally think
> about a blog for the little things I learn how to do every day. Something
> much less in-depth than "Friday Q&A" or the like, but still suitable for
> helping people find solutions via Google. "Vermont Snippets," maybe.
>
> But then I kick myself and wake up. These days, I just want to write good
> code, especially if it's doing something I've never done before.
>
> --
>
> Bill Cheeseman - wjcheese...@comcast.net
>
> ___
>
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/lutherbaker%40gmail.com
>
> This email sent to lutherba...@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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: App opens in wrong language on some users' machines

2016-03-05 Thread SevenBits 
On Saturday, March 5, 2016, Quincey Morris <
quinceymor...@rivergatesoftware.com> wrote:

> On Mar 5, 2016, at 14:41 , SevenBits  > wrote:
>
>
> On which Macs would this be the case? It hasn't happened on any of the
> ones that I've tried. Is there a documentation page anywhere detailing this?
>
>
> I don’t know. The specific piece of information that would answer this may
> be tucked away anywhere, or may not be in the documentation at all.
>

Wonderful.


>
> How did you do the non-English localizations? Did you export a LIFF file?
> Whatever you did for those languages, you need to do for English.
>

Yes, I used Xcode's built-in functionality to export an XLIFF file and sent
it to my translators. It was a pretty painless process, thankfully.


>  Most of the files in those other lproj directories look like they were
> created by IB, but IB never created those for English, so I have to assume
> you never *edited* the English resources (or imported from LIFF).
>

I did not, mainly because I was under the assumption that you didn't need
to explicitly localize the app in its development language; you could
provide translations for specific languages, and if there wasn't a
translation for the user's language, then the development or Base language
would be used. That would seem to make sense and since it worked for me and
the majority of my users... well, I know we're not supposed to make
assumptions, but what's a "base language" for, if not to accomplish this
behavior?
___

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

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

Re: App opens in wrong language on some users' machines

2016-03-05 Thread Quincey Morris 
On Mar 5, 2016, at 14:41 , SevenBits  wrote:
> 
> On which Macs would this be the case? It hasn't happened on any of the ones 
> that I've tried. Is there a documentation page anywhere detailing this?

I don’t know. The specific piece of information that would answer this may be 
tucked away anywhere, or may not be in the documentation at all.

How did you do the non-English localizations? Did you export a LIFF file? 
Whatever you did for those languages, you need to do for English. Most of the 
files in those other lproj directories look like they were created by IB, but 
IB never created those for English, so I have to assume you never *edited* the 
English resources (or imported from LIFF).

___

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

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

Re: App opens in wrong language on some users' machines

2016-03-05 Thread SevenBits 
On Saturday, March 5, 2016, Quincey Morris <
quinceymor...@rivergatesoftware.com> wrote:

> On Mar 5, 2016, at 13:32 , SevenBits  > wrote:
>
>
> Anyone have any pointers of things to try first?
>
>
> Looking in the project in github, I see that en.lproj is missing almost
> all of the files that the other localizations have.
>
> I think the problem is along the lines of the fact that the app *has* an
> ‘en’ localization, but hasn’t actually been localized for ‘en’, relying
> instead on the base localization. On some Macs, or in some OS X versions,
> the substitute for the invalid ‘en’ localization is the the first valid
> localization (de), rather than the development language.
>

Hmm, I did not know this.

On which Macs would this be the case? It hasn't happened on any of the ones
that I've tried. Is there a documentation page anywhere detailing 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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: App opens in wrong language on some users' machines

2016-03-05 Thread Alex Zavatone 

On Mar 5, 2016, at 5:05 PM, Quincey Morris 
 wrote:

>  en.lproj is missing almost all of the files that the other localizations 
> have.

Check to make sure that the files that are supposed to be in English have a 
check mark that they belong to the English localization.
___

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

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

Re: App opens in wrong language on some users' machines

2016-03-05 Thread Quincey Morris 
On Mar 5, 2016, at 13:32 , SevenBits  wrote:
> 
> Anyone have any pointers of things to try first?

Looking in the project in github, I see that en.lproj is missing almost all of 
the files that the other localizations have.

I think the problem is along the lines of the fact that the app *has* an ‘en’ 
localization, but hasn’t actually been localized for ‘en’, relying instead on 
the base localization. On some Macs, or in some OS X versions, the substitute 
for the invalid ‘en’ localization is the the first valid localization (de), 
rather than the development language.

___

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

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

App opens in wrong language on some users' machines

2016-03-05 Thread SevenBits 
Some users of my app have reported to me that, despite their Mac being set to 
English, the program opens in German (it’s always German, never any other 
language). I have never been able to reproduce this on any Mac I’ve tried on. 
I’m not sure why the app would open in German. Has anyone here encountered an 
issue like this before?

My Xcode project has a development language of English, and uses Base 
localization. I’ve never received a bug report like this on any other language, 
so my initial thought is that there must be something wrong with my 
localization settings, but I don’t see anything out of place.

Anyone have any pointers of things to try first?

P.S.: This is one of the many bug reports I’ve received on the issue: 
https://github.com/SevenBits/Mac-Linux-USB-Loader/issues/88


signature.asc
Description: Message signed with OpenPGP using GPGMail
___

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

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

Re: Starting out with storyboards (on Mac)

2016-03-05 Thread Bill Cheeseman 

> On Mar 5, 2016, at 1:35 PM, Gary L. Wade  wrote:
> 
> On Mar 2, 2016, at 11:20 AM, Bill Cheeseman  > wrote:
> 
>> Broadening my horizons is *always* one of my purposes.
> 
> Sounds like your book will be getting a sequel by the end of it? Swift Cocoa 
> Recipes for Apple Platforms?


No, my book writing days are over and done with. I do occasionally think about 
a blog for the little things I learn how to do every day. Something much less 
in-depth than "Friday Q&A" or the like, but still suitable for helping people 
find solutions via Google. "Vermont Snippets," maybe.

But then I kick myself and wake up. These days, I just want to write good code, 
especially if it's doing something I've never done before.

-- 

Bill Cheeseman - wjcheese...@comcast.net

___

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

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

Re: Starting out with storyboards (on Mac)

2016-03-05 Thread Gary L. Wade 
> On Mar 2, 2016, at 11:20 AM, Bill Cheeseman  wrote:
> 
> Broadening my horizons is *always* one of my purposes.

Sounds like your book will be getting a sequel by the end of it? Swift Cocoa 
Recipes for Apple Platforms?
--
Gary L. Wade (Sent from my iPad)
http://www.garywade.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: State Restoration thinks all my windows closes prior to quit

2016-03-05 Thread Quincey Morris 
On Mar 5, 2016, at 01:36 , Daryle Walker  wrote:
> 
> Default project Xcode 7 with OS X Cocoa app, with Storyboards but without 
> Core Data nor Documents. Somewhere I messed up and State Restoration stopped 
> working correctly. It somehow thinks when quit happens and any open windows 
> get automatically closed that those windows were user-closed instead and 
> therefore not restored.

Maybe I’m missing something, but I don’t see where you set the restoration 
class on the windows you create. Note that when you have a NSDocument-based 
app, NSDocumentController takes care of this for you. Without the restoration 
class, there’s no state restoration.

___

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

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

Re: State Restoration thinks all my windows closes prior to quit

2016-03-05 Thread Bill Cheeseman 

> On Mar 5, 2016, at 4:36 AM, Daryle Walker  wrote:
> 
> Default project Xcode 7 with OS X Cocoa app, with Storyboards but without 
> Core Data nor Documents. Somewhere I messed up and State Restoration stopped 
> working correctly. It somehow thinks when quit happens and any open windows 
> get automatically closed that those windows were user-closed instead and 
> therefore not restored. I was having problems before with windows hanging 
> around in the wrong position, so I must have fried a setting somewhere or 
> made some other bad assumption.

Did you implement the applicationShouldTerminateAfterLastWindowClosed(_:) 
delegate method, returning true? If you do that, and if the user (or some other 
cause, such as an AppleScript script) does close the last window, then Cocoa's 
state restoration mechanism (interface persistence, or the "Resume" feature) 
does not save the window's last state (position, size, etc.) because the window 
was no longer open when termination time arrives.

I work around this by not implementing that delegate method, and instead 
implement the windowShouldClose(_:) delegate method in my main window 
controller like this:

func windowShouldClose(sender: AnyObject) -> Bool {   
if window != nil {
NSApplication.sharedApplication().performSelector("terminate:", 
withObject: self, afterDelay: 0.0)
return false // keep main window open until "terminate:" selector 
is performed in next iteration of run loop
}
return true
}

-- 

Bill Cheeseman - wjcheese...@comcast.net

___

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

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

Re: Starting out with storyboards (on Mac)

2016-03-05 Thread Bill Cheeseman 

> On Mar 5, 2016, at 4:26 AM, Daryle Walker  wrote:
> 
> What sites did you find via web-search? The ones I found weren’t that great.


The OS X storyboard websites I found helpful include those listed below. The 
first few are general overviews, and the rest are more narrowly focused on 
specific storyboard techniques.

The Brimelow video tutorial is a very good introduction and overview.

The Ray Wenderlich tutorial is essential to understand how to use container 
views with OS X storyboards. This is what broke the storyboard logjam for me. I 
had been struggling to use the new split view controllers and tab view 
controllers with nib files and getting nowhere. I'm still convinced they can be 
used with nib files, but I never figured out how. They are really, really easy 
to use with storyboards, which convinced me that storyboards are the way to go 
in OS X from now on.

I also like the fact that, in El Capitan, storyboards can be broken up into 
pieces, using transition segues to get from storyboard file to storyboard file. 
Now I can create smaller storyboards that are divided into topical units in 
much the way that I have done with nib files in the past, without losing the 
great storyboard benefit of segues.

WWDC 2014 "Storyboards and Controllers on OS X (Session 212) 


Lee Brimelow, "Using Storyboards for OS X" 


Ray Wenderlich, "OS X View Controllers Tutorial" 


Xamarin, "Working with Storyboards" 


Apple Technical Q&A QA1871 (2016-02-18) 


IconMaster, "Transitioning between view controllers in the same window, with 
Swift - Mac" 


Scott Sherwood, "Storyboards and Nibs: When To Use Which, and How to Mix" 


Mike Abdullah, "Storyboards on the Mac" 


Stack Overflow, "How to work with Storyboard Unwind Segue in Mac OS X" 


Stack Overflow, "Initializing another window using storyboard for OS X" 


Me and Mark Publishing, "Connecting Menu Items to IBActions in a Mac 
Storyboard" 


Nick Kuh, "How to Modally Present Windows as Sheets in OS X" 


-- 

Bill Cheeseman - wjcheese...@comcast.net

___

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

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

State Restoration thinks all my windows closes prior to quit

2016-03-05 Thread Daryle Walker 
Default project Xcode 7 with OS X Cocoa app, with Storyboards but without Core 
Data nor Documents. Somewhere I messed up and State Restoration stopped working 
correctly. It somehow thinks when quit happens and any open windows get 
automatically closed that those windows were user-closed instead and therefore 
not restored. I was having problems before with windows hanging around in the 
wrong position, so I must have fried a setting somewhere or made some other bad 
assumption.

//===
private func createWindow(sender: AnyObject?) -> Bool {
guard let controller = 
self.mainStoryboard.instantiateControllerWithIdentifier(Names.mainWindowControllerID)
 as? NSWindowController, window = controller.window else {
return false
}

let notificationCenter = NSNotificationCenter.defaultCenter()
let observer = 
notificationCenter.addObserverForName(NSWindowWillCloseNotification, object: 
window, queue: NSOperationQueue.mainQueue()) { [unowned self] note in
guard let window = note.object as? NSWindow, controller = 
window.windowController else {
return
}
self.windowControllers.remove(controller)
if let observer = self.observers.removeValueForKey(controller) {
notificationCenter.removeObserver(observer)
}
}
self.observers[controller] = observer
self.windowControllers.insert(controller)
controller.showWindow(sender)
return true
}
//===

The “applicationOpenUntitledFile:” and “newDocument:” methods call this method. 
The “windowControllers” property is a Set and “observers” 
is a [NSWindowController: AnyObject]. The set retains the window controllers 
(the system will release them and close their windows otherwise) and the 
dictionary lets me release the observers later. Am I messing something up in 
that code so the window is aborted (instead of fully closing) to death and 
messing up the restore state?

I have modified the window-controller and/or window parts of the main 
storyboard, but I don’t see where anything could have gone wrong there.

— 
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT 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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: Starting out with storyboards (on Mac)

2016-03-05 Thread Daryle Walker 
> On Mar 2, 2016, at 2:20 PM, Bill Cheeseman  wrote:
> 
> I started playing with OS X storyboards a few weeks ago. It took more time 
> than it should to figure them out because the documentation is inadequate, 
> but Google searches led me to lots of helpful third-party articles. At this 
> point, they are working well for me. I think they are better than pure nib 
> files, mostly because they include all the familiar nib stuff but add 
> additional features such as presentation segues and good use of view 
> controllers. The net effect is less code, better organized code, and more 
> understandable code.
> 
> A 15-year old product of mine is due for a complete rewrite anyway, so I am 
> taking this as an opportunity to rewrite it from scratch with storyboards, in 
> Swift of course, and with a complete refactoring into smaller classes with 
> heavy use of NSViewController, container views and other new stuff.
> 
> Broadening my horizons is *always* one of my purposes.

What sites did you find via web-search? The ones I found weren’t that great.

— 
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT 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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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