Earlier quoted context omitted.
> Maybe it's a matter of how you think, but I can "see" the changes when I adjust the frames, colors, padding, resizing masks, and that's basically all IB will do for you. I know what you mean. I'm not an iOS/Cocoa dev by any means, but when I write CSS I typically know what the outcome is going to be in my head because I've done it so many times.
I can see it in both code and interface builder. Doing it in code on iOS is like using CSS where the only selector is `#id` and there are no child selectors. Would you write CSS if you had to do this? #username-label { text-align:right } #first-name-label { text-align:right } ... #last-name-label { text-align:right } #address-label { text-align:right } With CSS, you get nice things like: #user-form label { text-align…
Your First iOS App – 100% Programmatically
71–80 of 111 posts
Re: Your First iOS App – 100% Programmatically
#72Earlier quoted context omitted.
I jumped into iOS dev after storyboards so, I fear nibs... I've never used one. If I started with a storyboard, should I throw in nibs every now and then for certain tasks??
I like to think of Nibs like classes. A lot of times I'll have a certain design I want reused throughout the app, and this works perfectly. For instance, in an app I'm working on now, I have a few different views that have scroll-views inside of them, with each object of the scroll-view being a view itself. In the last of the chain of views, I use a nib because there's a solid amount of data there, and visually desig…
Re: Your First iOS App – 100% Programmatically
#73Earlier quoted context omitted.
I've been a Cocoa developer for close to a decade now, and I've gone back and forth on this many times, but by now I've settled 100% in the nibs-are-evil camps. There are several reasons for that: - Nibs are a nightmare when working with version control and merge tools. Now, at least, they are XML instead of a proprietary binary format, but it's still a joke… - Auto-layout in IB is provably the worst GUI I have ever…
Since you seem to be catching some flak for your post, I'll elaborate a bit further. AutoLayout is a constraint solver, and as such it's very easy to either over-specify or under-specify your constraints in a way where it no longer evaluates. On top of this, AutoLayout also has a priority for each constraint such that if/when such a conflict occurs AutoLayout has some ordering as to which constraints get abandoned fi…
Re: Your First iOS App – 100% Programmatically
#74Earlier quoted context omitted.
> Maybe it's a matter of how you think, but I can "see" the changes when I adjust the frames, colors, padding, resizing masks, and that's basically all IB will do for you. I know what you mean. I'm not an iOS/Cocoa dev by any means, but when I write CSS I typically know what the outcome is going to be in my head because I've done it so many times.
I can see it in both code and interface builder. Doing it in code on iOS is like using CSS where the only selector is `#id` and there are no child selectors. Would you write CSS if you had to do this? #username-label { text-align:right } #first-name-label { text-align:right } ... #last-name-label { text-align:right } #address-label { text-align:right } With CSS, you get nice things like: #user-form label { text-align…
Re: Your First iOS App – 100% Programmatically
#75Having made a few iOS apps in team/solo environments, I now stick to the following: Large team - don't use Interface Builder. Synchronizing it is too difficult and any productivity gains will be lost. Layout in code is best here, but really is time consuming for complex UIs. However, pixel-perfect match for designers is a great benefit since you're specifying everything in pixels that you can copy right out of the de…
Re: Your First iOS App – 100% Programmatically
#76Earlier quoted context omitted.
Not any of those points is justified, "a nightmare", "the worst". You need to provide something to support all those affirmations.
It's called an opinion. This isn't a peer reviewed paper we're talking about. And his opinion is that merging Nibs is a nightmare. Does he need to document how he did it, when, where, and what the room temp was at the time to "justify" an opinion? Hardly.
Which are like noses. Everybody has one.
>And his opinion is that merging Nibs is a nightmare. Does he need to document how he did it, when, where, and what the room temp was at the time to "justify" an opinion?
Does he needs to elaborate more in order to justify it?
Of course.
Re: Your First iOS App – 100% Programmatically
#77Earlier quoted context omitted.
Not any of those points is justified, "a nightmare", "the worst". You need to provide something to support all those affirmations.
Try merging a .nib. You'll see first-hand how hard it is.
Merging isn't even funny with regular code.
How about having a process for who works on what or when?
Either than or let a single person be responsible for the UI.
Re: Your First iOS App – 100% Programmatically
#78Earlier quoted context omitted.
> Maybe it's a matter of how you think, but I can "see" the changes when I adjust the frames, colors, padding, resizing masks, and that's basically all IB will do for you. I know what you mean. I'm not an iOS/Cocoa dev by any means, but when I write CSS I typically know what the outcome is going to be in my head because I've done it so many times.
I can see it in both code and interface builder. Doing it in code on iOS is like using CSS where the only selector is `#id` and there are no child selectors. Would you write CSS if you had to do this? #username-label { text-align:right } #first-name-label { text-align:right } ... #last-name-label { text-align:right } #address-label { text-align:right } With CSS, you get nice things like: #user-form label { text-align…
for (UILabel *l in @[self.usernameLabel, self.firstNameLabel, …]) {
l.textAlignment = UITextAlignmentRight;
l.textColor = [UIColor redColor];
}Re: Your First iOS App – 100% Programmatically
#79Earlier quoted context omitted.
> Maybe it's a matter of how you think, but I can "see" the changes when I adjust the frames, colors, padding, resizing masks, and that's basically all IB will do for you. I know what you mean. I'm not an iOS/Cocoa dev by any means, but when I write CSS I typically know what the outcome is going to be in my head because I've done it so many times.
I can see it in both code and interface builder. Doing it in code on iOS is like using CSS where the only selector is `#id` and there are no child selectors. Would you write CSS if you had to do this? #username-label { text-align:right } #first-name-label { text-align:right } ... #last-name-label { text-align:right } #address-label { text-align:right } With CSS, you get nice things like: #user-form label { text-align…
Re: Your First iOS App – 100% Programmatically
#80Earlier quoted context omitted.
If you say "provably" you really do need to... prove it. What studies are you citing when you say IB auto-layout is "provably the worst GUI?"
He might have meant "probably".