Re: newbie question re. cocoa front-end to sql db
Re: newbie question re. cocoa front-end to sql db
- Subject: Re: newbie question re. cocoa front-end to sql db
- From: Scott Ellsworth <email@hidden>
- Date: Wed, 22 Mar 2006 12:59:08 -0800
On Mar 22, 2006, at 12:20 PM, Russ McBride wrote:
Thanks for the reply. Too bad about the limited db access.
RunTimeLabs apparently has a db framework that looks quite nice,
but it's $700.
I'll probably try the RubyCocoa + ActiveRecord route and let you
know how it goes.
Now the standard question: any secrets for getting up to minimum
speed rapidly in Cocoa? Hillegas book? The usual Apple tutorials?
Others may disagree, but I really liked the Hillegas. book. I also,
though, own Vermont Recipies and Anguish/Buck/Yacktman, and found
them good for another perspective.
If you have $3500 to drop, the Big Nerd Ranch classes come very
highly recommended. (I gathered some testimonials for a recent Cocoa-
heads meeting, but these have not been posted yet.)
1. You will have to learn enough Objective C to read the examples.
The Hillegas book will teach enough.
2. Cocoa is easy to experiment with. Do not be afraid to create a
new project to try out a simple one-liner.
3. Use accessorizer <http://www.kevincallahan.org/software/
accessorizer.html> to generate your accessors. It gets the memory
management right, and when you understand all of the options it
has,you will understand the memory management rules too.
4. If you find yourself fighting the framework, stop for a moment
and hunt up Apple sample code and tutorials. They are not always
right or perfect, but they are pretty good and generally improving
with time. They can often give you a clue about what the designers
were thinking, and that can stop you from hitting a wall.
5. Make use of the Cocoa-dev wiki. Again, not perfect and sometimes
out of date, but there is good information there.
6. If you do not like your current book, try a different one.
Sometimes, all it takes is another phrasing.
7. The list is good about answering smart questions, but the easy
ones have likely already been answered. Make friends with google, so
you can find good answers to the questions someone else has already
asked. If nothing else, starting a post with 'I looked at the
following post ###, but I did not understand why they called
[something somethingElse]; at the end - the docs do not indicate
needing it.' makes it a lot easier to answer that question.
Scott
---
email@hidden
Java, Cocoa, Tapestry, and Database Consulting
_______________________________________________
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