Thursday, January 19, 2017

Will it crash reflection

For “Will it Crash” - what was easy? what was hard?
Fairly easy for me.
For this lesson, writing if-statements - what was easy, what was hard?
It was easy to follow the logic of the if-statements and although nested statements look messy I could also track those fairly well. This is largely in part to my previous coding experience specifically in javascript.
If there was one thing you wish you understood better at this point, what would it be?
I always get confused about boolean logic.


Monday, January 9, 2017

Multi Screen Code

setScreen("HomeScreen");
onEvent("Beginbtn", "click", function(){
setScreen("ScheduleOrCalendar");
});
onEvent("Blocks", "click", function(){
setScreen("BlockSchedule");
});
onEvent("Calendar", "click", function(){
setScreen("JanCalendar");
});
onEvent("Homebtn", "click", function(){
setScreen("HomeScreen");
});
onEvent("Homejan", "click", function(){
setScreen("HomeScreen");
});
onEvent("HomeBlock", "click", function(){
setScreen("HomeScreen");
});

Error Messages

You probably had some error messages today. What error messages did you have?  How did you solve the error message?  Is is common to get error messages as a coder?  Why might a programmer "like" or benefit from error messages?

I did not experience any error messages since the project was fairly simple especially since I have used Javascript frequently in the past and am familiar with the syntax. Some common errors however that I have received in the past or my peers could have received would be mismatching ids or misspelling ids when you call things in your code. A programmer like myself would benefit from receiving error messages because it teaches the programmer how to deal with and solve problems in their code. 

Design Multi-screen Program

My plan for my multi screen program project.