Update: This is documented behavior.
Every now and again while doing development you stumble upon something that makes you go, hmmmm. Those are normally the moments at which you have to ask yourself, “is this a bug or a feature”. If it’s a bug, then you should file a radar with Apple, however, what if it’s a feature? You blog about it, of course!
I have done a bit less iPhone development than Marcus, so he was a little stumped while looking through some of my code where I created a view controller using a simple alloc/init. Most interestingly is that fact that the app works. It loads the correct nib and displays the view just fine without any trouble. Notice I said alloc/init and not alloc/initWithNibName. How can this possibly work? How did my controller “know” which view to use? (more…)
Having finally decided that I prefer the 1920×1200 display of the 17″ Macbook Pros I am finally committing to one size of laptop. To help force myself into that commitment I am going to be selling my gently used late 2008 15″ Macbook Pro.
The specs are:
- 2.53 Ghz Intel Core Duo
- 4GB RAM
- 320 GB Harddrive
- 512 Nvidia Video cards (9400 and 9600)
- 2 USB
- 1 FW/800
All of the original hardware and equipment are included.
The asking price is $1,800.00 plus shipping.
The machine is in perfect condition as shown in these photos on flickr (http://tr.im/kQ11).
If you are interested in this machine please contact me at marcus at cimgf dot com.
Thanks to the ability to have configurations in a Core Data Managed Object Model and being able to save data to multiple Persistent Stores, it is possible to have a Core Data Model that is constructed from not only an internal model, but from the models of all the plug-ins that are loaded into the application.
In this example we are going to build a basic application with the following requirements:
- A plug-in framework
- Plug-ins can extend the managed object model of the application
- Removal of a plug-in should not corrupt the persistent store.