So the plan is to complete this app today - the Quizzler! Like I've said before, this template could easily be adapted. Once it's done, I could use it for F1 questions, GoT...anything! So being able to understand each step, as well as the object oriented programming being clarified, there have been lots of positives. Here we go!
Init the First Question
letfirstQuestion = allQuestions.list[0]
I figured out that this must be the 0 index with that format. Makes sense!
uestionLabel.text = firstQuestion.questionText
Having the class makes a huge difference to the simplicity of the code!
OK, the tag system makes a lot fo sense. Grouping together several buttons and putting in the tags of 1, 2 etc. That would have been useful for the Yahtzee buttons for each option to click. Anyway, that's something to play around with another time.
func checkAnswer() {
let correctAnswer = allQuestions.list[0].answer
if correctAnswer == pickedAnswer {
print("You got it!")
} else {
print("Wrong!")
}
}
How to Progress Through the Question Bank
var questionNumber: Int = 0
So this is a great way of keeping track of something, whether it's the level one is on, the score, or in this case - the question number!
Using += 1 - that is the best way of adding on one! Not ++. Swift removed the ++ for some reason. But never mind!
OK - challenge was to try to figure out what to do when the questions were up - I failed. Tried a few things but they did not work.
Using the Xcode Debug Console
Right, so using the debug console, using the debug area is important here. You can print the question number here, to establish the value. This is 13. OK so I was actually close, just some of the order of things. Encouraging!
How to Implement UIAlertController
Here is how it looks:
Whenever you see the word 'in', you should also use the word 'self'. Not for for-in loops though!
This is linked to CLOSURES. We'll come back to this apparently.
let alert = UIAlertController(title: "Complete!", message: "You have finished all of the questions. Do you want to play again?", preferredStyle: .alert)
This is REALLY useful stuff! It seems of huge importance to have these action buttons in the code - especially for restarting etc. The code is complex so I'm not going to worry about memorising the syntax!
I'm still going for more complex solutions rather than simpler ones - repeating myself. Remember DRY!
High Level Overview
This was all fine.
Track Progress and Score
I haven't typed anything here but lots of logic and problem solving - very rewarding!
UPDATING score in the code so it resets to 0 every time - already done my friend!
Incorporating Objective C code into Swift
OK, so this is to get pop ups to show if they got an answer right or wrong!
We're going to use a code library - we can access this for free basically.
HUD - Head Up Display
So I've copied over the files - no problem. I've included the 'bridging' option too.
I've also created an alteration - randomised messages for the correct/wrong answers! I posted this in the questions as am proud of it!
Well that is all for now. Lots learned but gotta go!
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...
Yes - one day's break, but not because I needed or wanted one! I was genuinely to busy for any Swift yesterday, so it feels good to be back! Having written entries each day for a week, I missed it! Enumerations are done for now; Optionals are next... The Absence of Data I think the idea of this is 'nil' - nothing! Pasan explains 'safe' code, where crashes need to be avoided. Optionals are new - since the inception of Swift I believe. struct Person { let firstName: String let middleName: String ? let lastName: String } I've pre-empted the ? - to make middleName an optional. If I didn't have this, then an error would be caused - you can't input nil. The question mark - making it an optional - means that nil CAN be used. So it means it may have a value OR may be nil. They do seem cumbersome, but apparently they are powerful and useful! In the example above, it means that it is a string and ma...
So this is probably the shortest time between blogs! As described in my last entry, working through the eBook was not working. So I've decided to go back to Treehouse. I always had a positive experience with it before; it helped me to understand the concepts and there were constant practical challenges that helped me gain and develop my knowledge. It was basically more hands-on and an active way to learn. It does mean a charge of $25 a month, but to be honest, that should be a motivation to use it - rather than dread or guilt for not utilising it and wasting money! Rather like paying for a gym membership, then not actually going to it - that would be the worst thing of all! So this way, it will mean quality time with coding, rather than trying to make sense of something that is beyond me, with no way of testing whether I'm actually at the right point or not. Right now, I have re-enrolled on Treehouse, where all of my progress has also been saved. That makes life easier ...
Comments
Post a Comment