3 steps to closely approximate what you want.
1) In IB, turn off column headers for the table.
2) Add this delegate method to the delegate object for the table:
- (BOOL)tableView:(NSTableView *)tableView isGroupRow:(NSInteger)row
{
return row == 0; // the first row of the table will be
On May 20, 2008, at 10:50 PM, Steve Weller wrote:
However you slice it and whatever your personal experience, I
believe that what we are experiencing with the docs are the early
symptoms of massive scaling of the problem vs. insufficient scaling
of the resources to tackle it. If anyone
On May 20, 2008, at 9:52 PM, Peter Duniho wrote:
Each language varies a bit, of course. But in the other popular
languages that I know reasonably well -- C++, C#, Java -- a subclass
does not have the ability to touch any part of the base
implementation that is not specifically exposed by
On May 21, 2008, at 12:49 AM, Jeff LaMarche wrote:
This is really a fascinating discussion and, unfortunately, a time
consuming one =)
I can't help but feel that we have two identifiable camps forming,
and I'm not sure I like that. Though a range of opinions have been
stated, it seems
Hi, I finally solved the issue.
I was using the CGContextShowTextAtPoint and
CGAffineTransformMakeRotation to draw it correctly. Due to some
problem (I created :P ) the previous state of the context was stored
and then the rotations where concatenated, so the text was fliping in
each redraw.
Now
Have searched the archive and Googled for the solution to this, was
hoping someone could point me in the right direction. I have an
NSTextView which allows me to drag movies and audio into it, and they
display and play perfectly. After saving and reloading the data,
however, the media only shows
On May 21, 2008, at 12:01 AM, j o a r wrote:
On May 20, 2008, at 9:52 PM, Peter Duniho wrote:
The goal is not for every language to mimic C++/C#/Java.
I never said that was the goal.
Different languages serves different purposes and there is no
single best language.
I agree. So?
[...]
First off: all well said! +1
...a few comments though. (Will this thread ever gonna stop? ;) )
First, how much are you paying for the documentation? How much did
you pay for the IDE? I mean, I'd love everything to be perfect for
everybody, but let's be realistic here. Apple doesn't derive
On Wed, May 21, 2008 at 8:49 AM, Peter Duniho [EMAIL PROTECTED] wrote:
And again: it's not that I'm on a crusade to have Objective-C changed, or to
have Cocoa made fully accessible via some other language. I just want
people to have some empathy for what at least some of us go through upon
On May 21, 2008, at 12:49 AM, Peter Duniho wrote:
I have already acknowledged that opinions vary. You, being among
the regular contributors to this mailing list, I fully expect to
think that Objective-C find a pragmatic sweet spot. Anything else
would surprise me.
There are a lot of
Maybe all the messages of this list should bring one header that says not
ask about iphone please.. Dont worry i made the same mistake.
We are not allowed to talk in public about the iphone apisyet..Is
called DNA
2008/5/21 Vijay Malhan [EMAIL PROTECTED]:
Hi,
I'm planning to write a
http://www.cocoabuilder.com/archive/message/cocoa/2008/5/15/206811
--
I.S.
On May 21, 2008, at 7:12 AM, Vijay Malhan wrote:
Hi,
I'm planning to write a framework on iPhone, just similar to any
other Cocoa
framework on Mac OSX.
But so far I'm unable to find any reference on this in
We are not allowed to talk in public about the iphone
apisyet..Is
called DNA
Well, no, it's called NDA, which stands for non-disclosure
agreement. It's that pesky legal contract you agreed to in order to
gain access to the iPhone SDK that says DO NOT TALK ABOUT THE SDK
UNTIL IT IS
I have a vague memory that I can swoop up my own .plist in my main
bundle into an NSDictionary with one call, but I can't seem to find
that call right now.
I've looked at the NSBundle and NSDictionary api's to no avail.
Can someone her please spark my memory?
Thanks,
Allan
We are not allowed to talk in public about the iphone apisyet..Is
called DNA
Well, no, it's called NDA, which stands for non-disclosure agreement.
It's that pesky legal contract you agreed to in order to gain access to the
iPhone SDK that says DO NOT TALK ABOUT THE SDK UNTIL IT IS
Which as we all know, and probably all do, simply click through
without a second thought or glance.
I think if this ever comes to court a precedent will be set that
basically makes all on-screen presented contracts with an OK button
null and void, since there is absolutely no feedback in
On May 21, 2008, at 3:06 AM, Scott Anguish wrote:
I'm not sure that how much is being 'paid' for the documentation is
a valid metric.
I believe (not speaking for the company of course) that both of
these areas are viewed as investments.
No, you're right, it's not a good metric, and I
Is there a way to tell NSWorkspace only to launch a specific version
of an application (matched against CFBundleVersion in Info.plist)?
Thanks,
Ray
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or
On May 21, 2008, at 4:31 AM, Torsten Curdt wrote:
Well, they are free to open source XCode and have other people help.
Look at Eclipse.
You can suggest it to them, but I wouldn't hold your breath. :)
Probably shouldn't open up that argument in this thread.
Paying for documentation is a
On May 21, 2008, at 7:42 AM, Allan Greenier wrote:
I have a vague memory that I can swoop up my own .plist in my main
bundle into an NSDictionary with one call, but I can't seem to find
that call right now.
I've looked at the NSBundle and NSDictionary api's to no avail.
Can someone her
Well, they are free to open source XCode and have other people
help. Look at Eclipse.
You can suggest it to them, but I wouldn't hold your breath. :)
Probably shouldn't open up that argument in this thread.
No ...I don't hold my breath :)
I think even for the documentation user generated
I think face-to-face is an important part to overcome the
obstacles. And this will become easier the more popular it gets.
Amen. I can't tell you how much I sometimes hate having moved away
from the SF Bay Area where there are many Cocoa Programmers, and
there are NSCoder nights, and
from Foundation import NSBundle
print NSBundle.mainBundle().infoDictionary()
Ronald
On Wednesday, May 21, 2008, at 01:42PM, Allan Greenier [EMAIL PROTECTED]
wrote:
I have a vague memory that I can swoop up my own .plist in my main
bundle into an NSDictionary with one call, but I can't seem
On 2008/05/21, at 13:59, Jean-Daniel Dupas wrote:
I think face-to-face is an important part to overcome the
obstacles. And this will become easier the more popular it gets.
Amen. I can't tell you how much I sometimes hate having moved away
from the SF Bay Area where there are many
As I remember it, about 20% of DECs revenue stream came from
documentation, not software or hardware.
The English Department of my university produced a steady stream of
technical writers who went to DEC.
As you might imagine I come from a FORTRAN background followed by
procedural Pascal.
Hi,
My app has to create the resource fork of a file and then write raw
bytes picked up from the disk to it.
Is there any support in cocoa for this.
For writing to the data fork I'm creating the file with NSFileManager
and then writing using write().
Is there any similar mechanism for
Am 20.05.2008 um 21:26 schrieb Matt Long:
It's included for 10.5. I don't think you want Image Capture for
your app, though as this API is mainly for downloading images from
the camera after a photo shoot. I don't believe there is any
mechanism for causing the picture to be taken (from a
I kinda got the idea that Mr. Sanz was being sarcastic...After all, this
topic keeps coming up and coming up and coming up...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of I. Savant
Sent: Wednesday, May 21, 2008 6:24 AM
To: Bruno Sanz
Cc:
I remembered that one. :-)
I want to load my own .plist - myFile.plist
into a dictionary.
On May 21, 2008, at 9:01 AM, Ronald Oussoren wrote:
from Foundation import NSBundle
print NSBundle.mainBundle().infoDictionary()
Ronald
On Wednesday, May 21, 2008, at 01:42PM, Allan Greenier [EMAIL
It' absolutely annoying that paste is disabled in NSSecureTextField.
From the docs it sounds like that really is on purpose.
It overrides many aspects of text editing to prevent passing of the
object’s value out by mechanisms available to the user (namely,
through Cut, Copy, and Paste
On 21 May 2008, at 15:31, Torsten Curdt wrote:
So it also disabled passing values IN ...not just OUT. Why?
Any idea on how to enable paste in NSSecureTextFields?
From a security point of it makes some sense to prevent pasting. You
don't really want people keeping plain text versions of
Scott,
Thank you for taking time to reply. You must be getting pretty tired
of all this. Worse, this is not a documentation issue, it's an Apple
issue.
On May 20, 2008, at 11:51 PM, Scott Anguish wrote:
[helpful pointers and other parts snipped]
Ultimately, learning is a very
On Wed, May 21, 2008 at 7:24 PM, I. Savant [EMAIL PROTECTED] wrote:
We are not allowed to talk in public about the iphone apisyet..Is
called DNA
Well, no, it's called NDA, which stands for non-disclosure agreement.
It's that pesky legal contract you agreed to in order to gain access to
My point remains - you agreed to something. Whether you read it
fully or not (and until successfully challenged in court probably
several times), it is binding. Apple's sandbox, apple's rules.
--
I.S.
___
Cocoa-dev mailing list
On Wed, May 21, 2008 at 9:31 AM, Torsten Curdt [EMAIL PROTECTED] wrote:
It' absolutely annoying that paste is disabled in NSSecureTextField. From
the docs it sounds like that really is on purpose.
Perhaps to prevent scripted brute force attacks, continuously (and
rapidly) pasting attempts
I agreed to similar contracts every time I've installed Mac OS X and
Xcode and nobody ever got annoyed when I talked about *those* in a
public forum.
If you're referring to to the EULA, none of those forbid you to
publicly discuss the technology, ie, they're not non-disclosure
agreements.
On May 21, 2008, at 9:45 AM, Steve Weller wrote:
Don't you see how different the learning experience is for 100,000
iPhone developers in 2008 vs. a few hundred Next developers twenty
years ago? And the differences in motivation? And background? And
sponsorship?
Scott, you *are* doing
On Wednesday, May 21, 2008, at 03:24PM, Allan Greenier [EMAIL PROTECTED]
wrote:
I remembered that one. :-)
I want to load my own .plist - myFile.plist
into a dictionary.
NSDictionary has an 'dictionaryWithContentsOfFile:' method that read a plist
file, and NSBundle has methods for getting the
On May 21, 2008, at 15:45, Matt Gough wrote:
On 21 May 2008, at 15:31, Torsten Curdt wrote:
So it also disabled passing values IN ...not just OUT. Why?
Any idea on how to enable paste in NSSecureTextFields?
From a security point of it makes some sense to prevent pasting. You
don't
On May 21, 2008, at 15:49, I. Savant wrote:
On Wed, May 21, 2008 at 9:31 AM, Torsten Curdt [EMAIL PROTECTED]
wrote:
It' absolutely annoying that paste is disabled in
NSSecureTextField. From
the docs it sounds like that really is on purpose.
Perhaps to prevent scripted brute force
On 21 May 2008, at 16:05, Torsten Curdt wrote:
From a security point of it makes some sense to prevent pasting.
You don't really want people keeping plain text versions of their
passwords around. Also, whatever was pasted would be left on the
clipboard. That would be very easy for someone
denial of anything. Lowering the barriers to entry doesn't necessarily
serve them or their consumers better, it serves new developers who see
the iPhone as an opportunity but, obviously, there is no shortage of
people wanting to take advantage of that opportunity, so I'm not sure
Good
On 21 May 2008, at 16:06, Torsten Curdt wrote:
If the script can paste into the box and hit the OK button I
assume it could also simulate key strokes ...no?
No, Its my understanding that the NSSecureTextField is very particular
about how it will get its input. i.e You can't use the
I would like to know if anyone on the list would be willing to share some
information on training they may have taken at The Big Nerd Ranch.
I would be interested to hear their perspective on the material content,
classroom atmosphere, accomodations and overall value of their experience.
Thank
If the script can paste into the box and hit the OK button I assume
it could also simulate key strokes ...no?
A good point. :-)
--
I.S.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments
Savant,Right, coming back to that, my actual question to the forum was that
If I can write my own framework and deploy it on an iPhone. I was not
discussing about any of the API so far, so I was not violating any
agreement/contract.
I got my answer from the SDK Agreement itself (Section 3.2.2-
Savant,Right, coming back to that, my actual question to the forum was that
If I can write my own framework and deploy it on an iPhone. I was not
discussing about any of the API so far, so I was not violating any
agreement/contract.
I got my answer from the SDK Agreement itself (Section 3.2.2-
Greetings:
What is the preferred way to programmatically schedule a SEND/FAX event,
(preferably via Cocoa)? I could supply the necessary parameters data,
perhaps stored in User Defaults or a flat file.
1) The event must be able to fire regardless of parent application (parent
app.
On May 21, 2008, at 9:46 AM, Michael Ash wrote:
I agreed to similar contracts every time I've installed Mac OS X and
Xcode and nobody ever got annoyed when I talked about *those* in a
public forum.
You agreed, not agreed. Checking the box is legally binding. It
doesn't matter if you've
On 21 May '08, at 6:31 AM, Torsten Curdt wrote:
It' absolutely annoying that paste is disabled in NSSecureTextField.
From the docs it sounds like that really is on purpose.
That seems inconsistent, since other password fields in the user
interface are pasteable, like the password
On 20 May '08, at 9:16 PM, Vitaly Ovchinnikov wrote:
Anyway, should I forget about Tiger? I want to release my app this
summer and I don't think that it is a good idea to drop support of the
previous OS.
Some apps are Leopard-only, usually because they require new APIs
(like Core
On May 21, 2008, at 8:46 AM, Michael Ash wrote:
On Wed, May 21, 2008 at 7:24 PM, I. Savant
[EMAIL PROTECTED] wrote:
We are not allowed to talk in public about the iphone
apisyet..Is
called DNA
Well, no, it's called NDA, which stands for non-disclosure
agreement.
It's that pesky
On May 21, 2008, at 16:44, Jens Alfke wrote:
On 21 May '08, at 6:31 AM, Torsten Curdt wrote:
It' absolutely annoying that paste is disabled in
NSSecureTextField. From the docs it sounds like that really is on
purpose.
That seems inconsistent, since other password fields in the user
Hello Everyone:
I decided that it was time for a play period this morning so I set a
task for myself; to place a combo box on a dialog and
populate it with the names of ten cities--no more than that. I just
wanted to see if my understanding of the language had
progressed enough to do so.
I
I have a class that extends NSWindowController. I instantiate and call
it like this
MyWindowController *controller = [[MyWindowController alloc] init];
[controller test:@test];
The NIB has the textField connected. Here is the (simplified)
implementation of the controller.
- (id) init
Am 21.05.2008 um 15:34 schrieb Nick Rogers [EMAIL PROTECTED]:
Hi,
My app has to create the resource fork of a file and then write raw
bytes picked up from the disk to it.
Unless these raw bytes actually contain a valid Resource Manager
structure this would be a bad idea. Yes it is possible
Am 21.05.2008 um 15:12 Uhr schrieb Joseph Ayers:
I'll cite one example. I've been spending two weeks trying to get a
table to reloadData to a multi column NSTableView that
I created programmatically. Creating the table view was
straightforward. Getting it to populate is yet another matter.
You probably want to use a NSArrayController and bind the combo box to
that.
When you hit the buttons you change the array through the controller.
HTH
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or
I keep thinking that all the energy spent on the list discussing the
iPhone and how we're not supposed to be discussing the iPhone could
be better spent drafting some sort of joint letter to Apple
stockholders explaining that iPhone developers' inability discuss and
jointly figure out the
Sorry, forgot to cc the group on this.
:// Jake
-- Forwarded message --
From: Jake Carter [EMAIL PROTECTED]
Date: Wed, May 21, 2008 at 9:14 AM
Subject: Re: Trying to understand -- please help...
To: john darnell [EMAIL PROTECTED]
Ok, I'm somewhat of a beginner myself, but
You are not retaining the autoreleased array in your constructor. You
are over-riding the first initialization of your array(which is a
leak) while you are initializing with arrayWithObjects: call.
You can remove this line completely
cityArray = [[NSArray alloc] init];
and do a retain on
What you're doing here is allocating an empty array, and then setting the
pointer of your instance variable to a new array, created with the
arrayWithObjects message. An array returned by this message is
autoreleased, so at the end of your init method, it's being released. All
these type of
On May 21, 2008, at 12:05 PM, john darnell wrote:
- (id) init
{
cityArray = [[NSArray alloc] init];
NSString *c0 = @New York; //Ten NSString objects created here
...
NSString *c9 = @Virginia Beach;
cityArray = [NSArray arrayWithObjects: c0, ...c9, nil];
return self;
}
Here's
Okay, thanks to all of you who sent in messages similar to Jake's
message. Your pinpointing of my problems was spot on. I fixed the
errors, re-ran the code and the problem went away.
Take care,
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jake
Also, since the initializer methods of the superclasses aren't invoked
automatically for you, you should code your initializers using a
pattern along the lines of:
- init
{
if (self = [super init]) {
// ... initialization statements for the instance
variables of
Well
Something like this is standard :
- (id)init
{
if (!(self = [super init]))
return nil;
cityArray = [[NSArray alloc] initWithObjects:
@New York
...,
nil];
return self;
}
would
I don't know the answer to that question myself. Maybe it was because I was
running it in the debugger...
R,
John
-Original Message-
From: Gérard Iglesias [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 11:35 AM
To: Hank Heijink (Mailinglists)
Cc: john darnell;
Once again..
Discussion of the iPhone SDK on this list violates the Non-Disclosure
Agreement.
Do not discuss this here.
Scott
moderator
On May 21, 2008, at 7:12 AM, Vijay Malhan wrote:
Hi,
I'm planning to write a framework on iPhone, just similar to any
other Cocoa
framework on Mac
Be patient, the official discutable iPhone SDK is annonced for the
next month (probably a couple of weeks now).
The time your letter reaches Apple, it will no longer be under NDA.
Le 21 mai 08 à 18:18, Ilan Volow a écrit :
I keep thinking that all the energy spent on the list discussing the
The line of code [NSArray arrayWithObjects: c0, ...c9, nil]; produces
an array all right - but as you have used a class initializer, it
will auto release
when you return from the method where it was created.
Any initialiser with a + in front of it returns an autoreleased
object
-
The debate on what is or isn't a legally binding EULA isn't
appropriate for this list.
Unfortunately, this is getting out of hand.
Everyone, please stop contributing to this thread.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
with an empty NSArray (not very useful, since you can't add items to
an NSArray). Then, you leak that allocated memory by setting cityArray
to an autoreleased NSArray
In fact it is not leaking, it is just creating an object for nothing, it will
be released by the autorelease pool, than no
On Wed, May 21, 2008 at 9:49 AM, Gérard Iglesias
[EMAIL PROTECTED] wrote:
with an empty NSArray (not very useful, since you can't add items to
an NSArray). Then, you leak that allocated memory by setting cityArray
to an autoreleased NSArray
In fact it is not leaking, it is just creating an
Sorry for the caps, not sure how else to try and get everyone's
attention.
This thread has been interesting and useful. In order to continue to
keep it so (if there is even anything left to be said) please keep in
mind the following.
- Don't debate the languages involved. Objective-C is
On Wed, May 21, 2008 at 9:47 AM, Peter Hudson [EMAIL PROTECTED] wrote:
The line of code [NSArray arrayWithObjects: c0, ...c9, nil]; produces
an array all right - but as you have used a class initializer, it will auto
release when you return from the method where it was created.
They are
On May 21, 2008, at 9:49 AM, Gérard Iglesias wrote:
with an empty NSArray (not very useful, since you can't add items to
an NSArray). Then, you leak that allocated memory by setting
cityArray
to an autoreleased NSArray
In fact it is not leaking, it is just creating an object for
nothing,
Are you on Leopard?
This behavior should not be there on Tiger.
I faced similar problem on Leopard with NSTableView. It seems in
Leopard, nib is loaded, with lazy-loading kind of approach. The
controls are not initialized until the window, on which the controls
are hosted, is not
On May 21, 2008, at 12:49 PM, Gérard Iglesias wrote:
with an empty NSArray (not very useful, since you can't add items to
an NSArray). Then, you leak that allocated memory by setting
cityArray
to an autoreleased NSArray
In fact it is not leaking, it is just creating an object for
On May 21, 2008, at 19:21, Vijay Malhan wrote:
Are you on Leopard?
Yepp!
This behavior should not be there on Tiger.
I faced similar problem on Leopard with NSTableView. It seems in
Leopard, nib is loaded, with lazy-loading kind of approach. The
controls are not initialized until the
On May 21, 2008, at 12:52 AM, Peter Duniho wrote:
Cocoa restrains class extension _much_ less than any of these other
languages, and in turn has a _much_ higher degree of hazard.
I think you're overestimating the hazard. Or, at least, the risk that
it can be encountered accidentally.
Thank you.
It's up to you what OS you want to support, a trade-off between
development/testing time and market size.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
On May 21, 2008, at 1:42 AM, Hamish Allan wrote:
I'm getting lost as to whether your main objection is about Apple not
providing anything other than Objective-C / Cocoa to develop apps on
the Mac, or whether it's just that you think their documentation could
be improved.
Sorry, that's fair.
You probably want to use a NSArrayController and bind the combo box to that.
When you hit the buttons you change the array through the controller.
Folks please don't point someone at things like NSArrayController when
they are just getting started. Using controller layer / bindings can
make a
On Wed, May 21, 2008 at 12:47 PM, Peter Hudson [EMAIL PROTECTED] wrote:
The line of code [NSArray arrayWithObjects: c0, ...c9, nil]; produces
an array all right - but as you have used a class initializer, it will auto
release
when you return from the method where it was created.
No,
You also want to add a dealloc method to your class that releases
cityArray, something like:
- (void)dealloc
{
[cityArray release];
[super dealloc];
}
-- Ilan
On May 21, 2008, at 12:05 PM, john darnell wrote:
Hello Everyone:
I decided that it was time for a play period
On Wed, May 21, 2008 at 10:11 AM, Gérard Iglesias
[EMAIL PROTECTED] wrote:
Or am I missing something ?
Yes :)
You are misreading what he typed I inlined what he typed with the code...
- (id) init
{
// First, you allocate and initialize the cityArray with an empty
NSArray (not very useful,
...actually with this new lazy loading feature code like this
- (IBAction) showPreferences:(id)sender
{
if (!preferencesController) {
preferencesController = [[PreferencesController alloc] init];
}
[preferencesController showWindow:self];
}
could probably just go away and
But the problem is still open for discussion. Is there any differences
in sequence of events occurring while loading of Nib between Tiger and
Leopard platforms?
All UI-elements should be initialized by the time call reaches -
(void)awakeFromNib. This is ensured to happen on Mac OS X 10.4.
Any initialiser with a + in front of it returns an autoreleased object
ACK! NO! A *method* with a + is a class method, whether it
returns an autoreleased object or nothing at all. Class methods that
return autoreleased objects are for convenience, but not all of them
do. Consider
Consider +(void)initialize ... also, *none* of them are
initializers by implication because they're class methods.
Sorry, these two sentences seem to be contradictory. Let me clarify:
+initialize is used to initialize the *class*. No class methods are
*instance* initializers or have anything
On Wed, May 21, 2008 at 7:11 AM, [EMAIL PROTECTED] wrote:
I would like to know if anyone on the list would be willing to share some
information on training they may have taken at The Big Nerd Ranch.
I collected a number of reviews on BNR last fall for the cocoaheads
group. They were
On May 21, 2008, at 20:00, Vijay Malhan wrote:
But the problem is still open for discussion. Is there any
differences in sequence of events occurring while loading of Nib
between Tiger and Leopard platforms?
All UI-elements should be initialized by the time call reaches -
- (void)getSelectedAccount{
NSString *accountName = @Bank;
NSLog(accountName);
accountName = [[MLoutlineViewController selection]
valueForKey:@name];
NSLog(accountName);
//get managedObjectContext in preparation for fetch code
moc =
Yes you are right. If we see this as an optimization enhancement, it
completely make sense to have things work like this. But my point is
that this behavior is not in-sync with the Leopard framework
documentation (XCode 3.0) and Tiger implementation. Following is
extract from the Mac OS X
Here's why the OP was not aware of the behavior of an NSArray class
method:
Here's the verbatim documentation for +arrayWithObjects:
arrayWithObjects:
Creates and returns an array containing the objects in the argument
list.
+ (id)arrayWithObjects:(id)firstObj, ...
ParametersfirstObj,
I wrote an article on this topic that was published in the September
2007 issue of MacTech entitled Cocoa Boot Camp. You can find a
synopsis at http://www.mactech.com/articles/mactech-synopses/
304834-23.09-Cocoa-Synopsis.html
On May 21, 2008, at 10:11, [EMAIL PROTECTED] wrote:
I would
On May 19, 2008, at 1:51 PM, Jens Alfke wrote:
I would guess that the Security framework is requiring user
confirmation to allow the app to bypass certificate checking.
Well, no. NSURLRequest's setAllowsAnyHTTPSCertificate:forHost: does
exactly that, immediately and without user
Nonsense.
Nonsense again.
Yet more nonsense.
Lets avoid this kind of tone in emails on this list... correct,
clarify, explain, etc. and leave it at that.
-Shawn
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin
On 21-May-08, at 11:37 PM, I. Savant wrote:
Consider +(void)initialize ... also, *none* of them are
initializers by implication because they're class methods.
Sorry, these two sentences seem to be contradictory. Let me clarify:
+initialize is used to initialize the *class*. No class
On May 21, 2008, at 11:35 AM, Johnny Lundy wrote:
Seriously, read that assuming you wanted to try out the NSArray
class and tell me how it accomplishes its purpose of documenting
what it is intended to document. It doesn't. And this pattern is
repeated over and over in just about every one
1 - 100 of 225 matches
Mail list logo
