Re: Creating a large Cocoa project - tutorials?
Re: Creating a large Cocoa project - tutorials?
- Subject: Re: Creating a large Cocoa project - tutorials?
- From: Marcus Roberts <email@hidden>
- Date: Wed, 23 Mar 2005 13:28:08 +0000
On Sat, 19 Mar 2005 11:11:10 -0800 (PST), Keith Blount
<email@hidden> wrote:
o all.)
>
> I think you should have a word with your UK suppliers,
> though, as it is out of stock at all of the major
> online bookstores! I finally managed to order it
> direct from Pearson Education who imprint Peachpit
> Press, so look forward to checking it out.
>
Keith, thanks for the hint. After reading about this book, it seemed
ideal for what I wanted too - I'd taught myself the basics of Cocoa,
but wanted to know the best practices for bringing them together and
creating the architecture of a Cocoa app. Even though I've got lots
of experience of .Net programming, and Java Jakarta Struts programming
where I learnt about MVC for the first time, I was missing the
knowledge that many Cocoa programmers before me must have learnt as
they started programming in the environment.
I too could only find the book with 2-3 weeks wait in all the online
UK bookstores, but thanks to your information I ordered the book from
Pearson and it just arrived this morning. Reading the introduction, I
think it's exactly what I'm looking for to take me to the next level.
It arrived just in time for the Easter weekend, so I should have
plenty of time to read through it too.
Cheers
Marcus
> Thanks again,
> Keith
>
> --- email@hidden wrote:
>
> > Send Cocoa-dev mailing list submissions to
> > email@hidden
> >
> > To subscribe or unsubscribe via the World Wide Web,
> > visit
> > http://lists.apple.com/mailman/listinfo/cocoa-dev
> > or, via email, send a message with subject or body
> > 'help' to
> > email@hidden
> >
> > You can reach the person managing the list at
> > email@hidden
> >
> > When replying, please edit your Subject line so it
> > is more specific
> > than "Re: Contents of Cocoa-dev digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: sigbus error 10 (newbie) (Hamish Allan)
> > 2. Progress bar (M M)
> > 3. Re: sigbus error 10 (newbie) (Matt Neuburg)
> > 4. Re: NSTimer causes events to be lost (Shaun
> > Wexler)
> > 5. TSMProcessRawKeyCode failed (-50) (dan
> > pahlajani)
> > 6. Re: dotmac framework wrappers? (Steve Gehrman)
> > 7. newbie memory issues continued (Daniel Child)
> > 8. Re: newbie memory issues continued (Steve
> > Christensen)
> > 9. Help with CFXMLTreeCreateFromData with an
> > NSMutableURLRequest
> > response. (Scott Andrew)
> > 10. text selectable in NSTextField (david kiers)
> > 11. Re: newbie memory issues continued (Jyrki
> > Wahlstedt)
> > 12. Re: slow NSWorkspaceDidWakeNotification
> > (Finlay Dobbie)
> > 13. Creating a large Cocoa project - tutorials?
> > (Keith Blount)
> > 14. Re: Creating a large Cocoa project -
> > tutorials? (Bill Cheeseman)
> > 15. Re: NSTimer causes events to be lost (Nicko
> > van Someren)
> > 16. Re: sigbus error 10 (newbie) (Hamish Allan)
> >
> >
> >
> ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sat, 19 Mar 2005 02:55:59 +0000
> > From: Hamish Allan <email@hidden>
> > Subject: Re: sigbus error 10 (newbie)
> > To: email@hidden
> > Cc: Cocoa List <email@hidden>
> > Message-ID:
> > <email@hidden>
> > Content-Type: text/plain; charset=US-ASCII;
> > format=flowed
> >
> > Daniel,
> >
> > You need to learn about Objective-C memory
> > management right from first
> > principles. You're doing all sorts of things wrong:
> >
> > -- allocating objects and then leaking them straight
> > away (if you know
> > C, what you're doing is equivalent to e.g. "int *p =
> > malloc(xsize); p =
> > other_p" which doesn't free the allocated memory,
> > merely loses the
> > pointer to it. If you don't know C, learn that
> > first).
> > -- trying to release the objects in an array every
> > time round the loop.
> > (This would be equivalent to having a C array of
> > pointers and calling
> > free() on them multiple times round a loop).
> > -- You should be returing an autoreleased object.
> >
> > I suggest you read a good book or web tutorial
> > (e.g.,
> >
> http://www.macdevcenter.com/pub/a/mac/2001/07/27/cocoa.html).
> > But make
> > sure you have a good understanding of pointers in
> > straight C first.
> >
> > Best wishes,
> > Hamish
> >
> > > Hi All,
> > >
> > > Just when I thought I was getting the hang of
> > this.... I keep getting a
> > > signal 10 or signal 11 error with the following
> > code:
> > >
> > > // This method takes a string representing a
> > stroke description (e.g.
> > > "SS-EE-SE")
> > > // and checks the knownStrokes array to find out
> > what types of strokes
> > > this
> > > // description may correspond to. Usually, a
> > description may correspond
> > > to only
> > > // one kind of stroke, but occasionally the
> > returned set of matching
> > > types may
> > > // have more than one members in the set.
> > > - (NSMutableSet
> > *)strokeTypesHavingDescription:(NSString *)d
> > > {
> > > int i = 0;
> > > NSMutableSet *matchingTypes = [[NSMutableSet
> > alloc] init];
> > > NSString *thisDesc = [[NSString alloc] init];
> > > NSNumber *thisType = [[NSString alloc] init];
> > >
> > > for (i = 0; i < numInList; i++)
> > > // Note: numInList is a member variable that
> > counts knownStrokes
> > > {
> > > thisDesc = [[knownStrokes objectAtIndex: i]
> > desc];
> > > thisType = [[knownStrokes objectAtIndex: i]
> > strokeType];
> > > // printf("thisType %i thisDesc %s\n",
> > [thisType intValue],
> > > [thisDesc cString]);
> > > if ([thisDesc isEqualToString: d])
> > > {
> > > [matchingTypes addObject: thisType];
> > > printf("types retaincount is %i\n\n",
> > [matchingTypes
> > > retainCount]);
> > > }
> > > // [thisDesc release];
> > > // [thisType release];
> > > }
> > > printf("matchingTypes set's retain count is
> > %i\n", [matchingTypes
> > > retainCount]);
> > > return matchingTypes;
> > > }
> > >
> > > I've been fiddling with this for ages and can't
> > see what is wrong. I
> > > have tried it with and without the release lines,
> > as well as with or
> > > without the alloc/init following the variable
> > declarations.
> > >
> > > By the way, are the signal/sigbus error numbers
> > useful hints at what is
> > > wrong?
> > >
> > > Thanks in advance.
> > >
> > > Daniel
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Fri, 18 Mar 2005 19:07:19 -0800 (PST)
> > From: M M <email@hidden>
> > Subject: Progress bar
> > To: email@hidden
> > Message-ID:
> > <email@hidden>
> > Content-Type: text/plain; charset=us-ascii
> >
> > Hello,
> >
> > How do i disable the buttons or the main window
> > while
> > there is a progress bar executing?
> >
> > I tried to disable the buttons manually while there
> > is
> > a progress bar and enable the buttons if it is done
> > processing. But it seems ugly. Is there a better way
> > how to do it?
> >
> > thank you
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Small Business - Try our new resources site!
> > http://smallbusiness.yahoo.com/resources/
> >
> >
> > ------------------------------
> >
> > Message: 3
> >
> === message truncated ===
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden