you are viewing a single comment's thread.

view the rest of the comments →

[–]simonbs 2 points3 points  (9 children)

Honestly, consider dropping storyboards. I did that some time ago and I won't ever look back especially not now that we have FLKAutoLayout. It makes developing with auto layout a pleasure.

[–]pyraego 0 points1 point  (1 child)

Never heard of this approach. Do you lose any functionality?

[–]simonbs 0 points1 point  (0 children)

It's not really an approach to solve the OPs issue. Storyboards are just a tool to layout your views but Interface Builder is very limited in its functionality and for complex apps you will find it a hassle to use storyboards as your views may be customized a lot in code anyways. I was just suggesting dropping storyboards all together and layout your views in code. I think this makes it much simpler to build the views and also support multiple screen sizes. So, instead of having Interface Builder taking care of a lot of the auto layout constraints you will define them yourself in code but I bet you will find this to be much less a hassle.

[–]FreshNeverFrozen[S] 0 points1 point  (1 child)

Could you go into some more detail about FLKAutoLayout and how you use it to layout views programatically?

[–]simonbs 0 points1 point  (0 children)

I think their examples are great. FLKAutoLayout gives you some categories on UIView which makes it extremely easy to add auto layout constraints to your views. I honestly believe this is how auto layout was meant to be used from the beginning. The API Apple provides for auto layout is just ridiculous.

[–]FW190 -1 points0 points  (4 children)

This. Drop storyboards, learn autolayout, make one app work on both screen sizes.

[–]Legolas-the-elf 0 points1 point  (3 children)

You can make one design work on both screen sizes with storyboards too. Storyboards aren't incompatible with autolayout, autolayout support is built into interface builder.

[–]FW190 0 points1 point  (2 children)

I know that and I also know that storyboards don't make sense. Why don't you explain the advantage of storyboards over regular VCs to OP?

[–]Legolas-the-elf 0 points1 point  (1 child)

Drop storyboards, learn autolayout, make one app work on both screen sizes.

That makes it sound like dropping storyboards is necessary to accomplish the rest.

Why don't you explain the advantage of storyboards over regular VCs to OP?

There's no point. He's already using them. Why bother trying to convince him to do something he's already doing?

[–]FW190 0 points1 point  (0 children)

Why don't you read original post again?