New answers tagged objective-c
0
I wont recommend doing this. I have done this in the past and I have faced problems such as the orientation delegates were not working once I change the rootviewcontroller property of appdelegate like this. Looks like it is fixed in iOS 6, but my understanding is that this is something unusual and not supposed to do.
Instead have a dummy viewcontroller as ...
1
Personally I wouldn't. I use storyboards and would set a view controller as the root. If I need to do this I would leave the view controller blank (maybe have an activity indicator if it takes a minute to login), run the login code here and then either move to the login segue or the main app segue.
Making sure that both the next screens hide the back button ...
1
I recently completed an iOS internship having no former experience with iOS. Learning Objective-C was hard work but wasn't impossible. It helped that I was further into my Computer Science degree program because all the important concepts I already knew were applicable. Here are lists of my skills and weaknesses before the internship that I felt were ...
0
Of course you need to run XCode on OSX to create apps. You need a developer account to distribute apps through the app store. If you are willing to put up with the hassle you can get around those limits, but you'll be on the fringes of things.
A good starting place might be to check out the courses on iPhone/iOS programming available through iTunes U in ...
0
I've had some good luck using the detailed tutorials on Ray Wenderlich's site: http://www.raywenderlich.com/
There's a team of people writing tutorials about various aspects of app development. I'm just starting with Objective-C and have found most of them to be pretty straightforward.
1
I have interviewed and hired interns for Mac and iOS projects at a couple of companies. That said, treat this as general guidance, not "you said I could work for you if I did [X]".
Internships are often short: sometimes not as long as the probationary period full time employees start on. That means there's a risk of hiring someone who can't learn the skills ...
1
There are two reasons.
Apple wants to review all code that runs on an iOS device in order to ensure the quality of the overall platform. Obviously, in order to review the code, they need to have it. So, Apple requires that all code that is run by your app, needs to be either part of the app or part of the public iOS APIs. You can embed an execution engine ...
3
So is it a good idea to make the declaration of the
UITableViewDataSource and UITableViewDelegate inside the .m file with
a private category?
That depends. Is the fact that MyViewController these protocols a private implementation detail, or something that you want to communicate to anyone using the class?
Header files are there to communicate your ...
0
Technically, it's of no consequence. Interface Builder will recognize that your class implements the protocols and offer a connection.
Apple code puts the protocols implemented in the header, and it's common practice. So anyone browsing your code will expect to see them there.
I think you are over thinking it hiding the protocols. I can't imagine an ...
2
In Objective-C, by convention, you refer to properties with dot notation. Thus, you write myAppObject.theArray instead [myAppObject theArray].
In Objective-C the default getter is the name of the variable instead getVariable. For example, writing
@property NSArray *theArray;
creates an instance variable _theArray and generates the following accessor:
...
1
You're right to want to change technique. You can imagine all the work you'd have to do everytime you need to add a new theme.
Subclassing View/Controller
Some programmers may choose to subclass the base view controller in order to take into consideration multiple themes. If the adaptations you have to apply between theme to theme is radically ...
2
Everything you said applies to commercial, close-source software too.
Updates: the difference is that FOSS code is much more honest about their incremental development schedule. Closed source world wants to to think their product is the last and final finished version.. with regular security updates and patches.. until the next version comes out that they ...
0
I would do something like your version 4 but make that initialiser public.
@interface Frobulator : NSObject
- (instancetype)init; //uses default collaborators
- (instancetype)initWithThingifier: (id <Thingifiying>)thingifier doohicker: (id <Doohicking>)doohicker; //designated initialiser
- (NSData *)frobulate: (NSData *)unfrobulatedData;
...
Top 50 recent answers are included
