Demystifying Views in iOS · Scene Dock | raywenderlich.com


This is a companion discussion topic for the original entry at https://www.raywenderlich.com/4518-demystifying-views-in-ios/lessons/13

Just a handy tip when making these videos: you don’t need to talk at 100 miles per hour and edit out every microsecond between sentences. It’s not like there’s some time limit, after which your video is going to explode. I find myself spending 90% of my time rewinding and pausing to figure out what the heck you just said and did. If you two were on Seinfeld, you’d be the “fast talkers.”

@nathandickson Thank you for your feedback - much appreciated!

@nathandickson, thanks for the comment. I’ve been wanting to say this since the last section. I think what’s lacking in this course are visuals. If there is, it’s not enough. The pace is too fast to know or at least imagine what will come up when we type this set of code. There should at least be a diagram of the connections if we can’t run the code yet because it’s for future use.

Thanks for your feedback. We’re always trying to improve our courses!

We recently reviewed this course internally, and came to some similar conclusions. Generally speaking, I think it could use more high-level overviews with diagrams, and we’ll keep that in mind for future updates.

1 Like

@catie @jessycatterwaul at around the 3:30 mark you guys adjust content hugging but say “compression resistance” . Just curious which one is correct. thank you!!

Oh! Sorry about that, we did mean Content Hugging :grimacing:

I’m quite sure I’m missing something here, but why not constrain the CelebrationView to the view’s safe area straight away instead of going to the trouble of calculating the value through the inverse?

And another, unrelated question: How would you go about doing the whole thing purely in code? I don’t mean adding the constraints and such, but the temporary presentation of the view. I’m still struggling with the whole notion of presenting and transitioning to views and view controllers in code (instead of, say, with segues or the scene dock), so that would be highly interesting for me to know.

I’m quite sure I’m missing something here, but why not constrain the CelebrationView to the view’s safe area straight away instead of going to the trouble of calculating the value through the inverse?

I thought that the code in the video was the simplest way to preserve the correct aspect ratio, but you may have a good idea we didn’t think of. I’d love for you to upload it if you get it to match in a simpler fashion!

And another, unrelated question: How would you go about doing the whole thing purely in code? I don’t mean adding the constraints and such, but the temporary presentation of the view.

I feel like the project already matches that description. Maybe it’s the creation of the view you’re asking about? If you don’t make use of the scene dock, the next place I’d go is a nib.