Ray Wenderlich Course - SwiftUI (Part 7)

So this may be the last bit for now from Laurie. I've learned a lot from him but it is taking a long, long time to go through the technical stuff. I will finish this chapter, then review what else there is on rw.com. With a Black November, I've signed up for the year! So no pressure in terms of renewing per month. A year should give me enough time and access that I need. 

 Start Time - 16:58

 Navigation View

 Yes! These are for navigating views - for going from one to another. Navigation controller used to be used for this.

Back to the same project as last time.

So, again hard stuff! The code has been wrapped in a NavigationView, then there was a bit more code to go with that. A new SwiftFile to have each of the book pictures and titles.

COOL FEATURE!

You can select a certain bit of a code - in this case, the VStack with that whole section. Command click, then go to Extract Subview. From there, you can rename the extracted view what you want, then create a new Swift UI view with that name! That is so good for keeping the code neat and tidy.

Lots more code that I'm not going to type out all of. The key thing here is that you can have smaller components - a few SwiftUI View files that link together and can be combined.

Sheet - this is bringing up a separate page that can be toggled in a certain condition. So in our example, a HelpView SwiftUI file was already created by Laurie with all of the correct properties. The 'Help' text appeared at the top for this.

Tab Views

There are limitations with these - can be text, image or image followed by text.

So this is again, cool! You can basically have a tab bar with different buttons (text and/or image). These then take you to different views!

Finish Time - 17:52 (approx 45 mins with interruptions)

There is a LOT here to play around with. Next entry will be a consolidation one to put all this into practice. Before I do that, I need to choose something definitive - something that I can actually play around with...
I think I will stick with that F1 idea. Yes. What I can do is have an image (resizing will be important...) with key info e.g. name, then other key stats in a separate struct. Then I will use that to display each driver, with the name... THEN I can other screens coming up of their key stats and info when clicked on. The other screens e.g. help, then the tab buttons.... All of that I can add in and gradually make my own F1 driver app!

 Very simple and of no real actual use, but perfect just to get used to these features with. Cool!

Comments

Post a Comment

Popular posts from this blog

*Xcode Project Entry 2* F1 Quiz - part 1

Image
It's Christmas Eve and time to code! To think, a year ago, I was plodding along with some eBook, blindly convincing myself that I was on a steady road to coding greatness. Really, it was from June where I made the decision to start again, humbling as that may seem. It would have been comforting to have completed endless 'beginner' courses but branching out and applying the theory is the key thing, which brings us to this entry. Yes, my second Xcode OWN project! I thought about doing an educational one, as there is certainly a lot of scope and relevance for that, being a teacher and all. However, making a quiz makes sense, for various reasons.  First off, I have made this before through Angela's excellent tutorial. No offence to Sandra, but hers is not even close to the elegance and effectiveness of Angela's project. The one thing to take from Sandra is the stack views. Definitely something I will use from now on. This is one of the great things about learning from...
Read more

Angela Yu Course Part 10 (up to lesson 112)

Image
It's unlikely that I'll be able to do any Swift tomorrow as I'm going to Eastbourne today, for the weekend. So I can give half an hour now, maximum! Coding Challenge - Destini App! Choose your own adventure books! I used to ADORE these. Angela explains that these have had some sort of revival through the Lifeline games. It's very binary - yes/no mostly. I have my own experience of this based on WDC... Now the challenge is to complete the game! Having followed the first few instructions, which I found a bit confusing it must be said, I was about to surrender and see the answer. Then I managed to stop myself - I CAN do this, or at least have a good go! Even if I don't get the correct answer, it will be good practice to put what I know into practice. This is my weakness, which I keep coming back to - that when some problem solving is required, I fold far too quickly. So here is what I need to do: Let's break this down... I need to use the...
Read more

Angela Yu Xcode 12 Course - Part 7 (lectures 74 to 79)

Image
No time to waste! Only got a short amount of time now so going to get a few minutes or so in! Start Time - 20:14 Conditionals If statement for 'love calculator' example. So a simple example for this. The idea will be that conditionals are used to show that the print statement will do it differently for whatever the number is. With updated Swift, I would use the Int.random(0...100). Easy fix that would be. Also no UIInt32 needed but just an Int. So with the if statements, it would be a STRING being returned.   Linked to the whole choose your own adventure - if/else for each choice. BMI Challenge No need to do this - easy enough to be honest. Just skimming through. BODMAS principles... So something I picked up on before is not needing the greater than AND less than value for the middle line (for the else if bmi > 18.5) A better solution, which Angela is already explaining before I could say it is returning a string instead of a Double. So the...
Read more