- Copertina flessibile: 400 pagine
- Editore: O'Reilly Media; 1 edizione (6 febbraio 2009)
- Lingua: Inglese
- ISBN-10: 0596154054
- ISBN-13: 978-0596154059
- Peso di spedizione: 499 g
- Posizione nella classifica Bestseller di Amazon: n. 1.157.718 in Libri in altre lingue (Visualizza i Top 100 nella categoria Libri in altre lingue)
- Visualizza indice completo
iPhone SDK Application Development: Building Applications for the AppStore (Inglese) Copertina flessibile – 6 feb 2009
|Nuovo a partire da||Usato da|
- Scegli tra gli oltre 8.500 punti di ritiro in Italia
- I clienti Prime beneficiano di consegne illimitate presso i punti di ritiro senza costi aggiuntivi
- Trova il tuo punto di ritiro preferito ed aggiungilo alla tua rubrica degli indirizzi
- Indica il punto di ritiro in cui vuoi ricevere il tuo ordine nella pagina di conferma d’ordine
Jonathan Zdziarski is better known as the hacker "NerveGas" in the iPhone development community. His work in cracking the iPhone helped lead the effort to port the first open source applications, and his book, iPhone Open Application Development, taught developers how to write applications for the popular device long before Apple introduced its own SDK. Prior to the release of iPhone Forensics, Jonathan wrote and supported an iPhone forensics manual distributed exclusively to law enforcement. Jonathan frequently consults law enforcement agencies and assists forensic examiners in their investigations. He teaches an iPhone forensics workshop in his spare time to train forensic examiners and corporate security personnel.
Jonathan is also a full-time research scientist specializing in machine learning technology to combat online fraud and spam, an effort that led him to develop networking products capable of learning how to protect customers. He is founder of the DSPAM project, a high-profile, next-generation spam filter that was acquired in 2006 by Sensory Networks, Inc. He lectures widely on the topic of spam and is a foremost researcher in the fields of machine-learning and algorithmic theory.
Jonathan's website is zdziarski.com.
Non è necessario possedere un dispositivo Kindle. Scarica una delle app Kindle gratuite per iniziare a leggere i libri Kindle sul tuo smartphone, tablet e computer.
Per scaricare una app gratuita, inserisci il numero di cellulare.
Garanzia e recesso: Se vuoi restituire un prodotto entro 30 giorni dal ricevimento perché hai cambiato idea, consulta la nostra pagina d'aiuto sul Diritto di Recesso. Se hai ricevuto un prodotto difettoso o danneggiato consulta la nostra pagina d'aiuto sulla Garanzia Legale. Per informazioni specifiche sugli acquisti effettuati su Marketplace consulta… Maggiori informazioni la nostra pagina d'aiuto su Resi e rimborsi per articoli Marketplace.
Se sei un venditore per questo prodotto, desideri suggerire aggiornamenti tramite il supporto venditore?
Le recensioni clienti più utili su Amazon.com
Other books walk you through screenshots using the designer and you're left without a solid understanding of the SDK. You're also left understanding how to use the convenience/crutch but without an understanding of the APIs in the SDK. Others have voted low because of it being too wordy without screenshots - that's the point, it's an SDK and code is the best way to understand an SDK.
Really bad idea. Delegates, controllers et al are different enough without throwing unnecessary hand-coding at the novice first. Further, in both books, the code is usually "just presented" (here: type this) with only modest followup as to what you've just entered actually does and where it fits into a larger picture.
Now it's obvious that I'm new to Xcode and iPhone, but I'm not new to programming per se: I started coding in 1978. I'm also a teacher, and can say that both these books represent the "jump into the lake and while you're gasping for air, I'll teach you how to swim" approach.
The beginner would have been far better served with the inclusion of Interface Builder right up front. That would help understand the whole paradigm used by the frameworks and how it implements MVC.
Once that was understood, -then- is the time to go back and say "... and this is how we hand code that..." - once the basic understanding and overview was in place in the reader's mind.
I'm even monitoring the Stanford class... and what I can say is that between that, and two books, and constant re-reading, I've finally managed to extract the conceptual overview needed to understand WHY thing are done, which any programmer needs to understand to write good, efficient code.
Copy/paste doesn't teach programming. It's like teaching "turn screwdriver clockwise to set screw" first, and expecting that to lead to carpentry skills.
It's a common problem when experts teach, and is why teaching is a profession unto itself.
I've figured it out.. and am still learning... but I should not have to "reverse engineer" it all to learn to do it.
In sum then: at least if you're starting from where I started, get everything you can find on iPhone programming - one book alone won't cut it.
My guess is that the editors or Apple got to the manuscript before it was published as there are items in the index that aren't in the book (check out Bluetooth if you don't believe me). There are also a lot of key items that appear in book, but are not in the index. Considering the size and scope of the index, I find this very puzzling. This makes the index worth a check, but not really as useful as you would expect.
All in all this is a handy reference to have, but it hints of how good it could have been and I find that disappointing. Not quite a programmers guide to development on the iPhone and not quite an authoritative reference. I find myself tempted to give it less than 4 stars due to it's failings, but when it is good it is damn near perfect.
So if you are starting programming with Cocoa or on the iPhone, I would recommend you start with something else. If you are familiar with the concepts and want to learn how to go that step beyond, this book might point you in the right direction.