This week we learned a few new things. One of them was different careers that involve programming. For two days we made mini presentations about the research that we did previously for the communication part of our mark. The second thing that we learned was how to use the timer control. The timer control allows you to make things happen without even clicking a button. For example, we added a timer to our slide show presentations so instead of clicking the button every time to change the picture, it changed automatically. The final thing that we learned was while loops which are like for/next loops except there is no limit to when the loop will go for. Also this week, we had another test about strings and everything that we had done since the last test.
I only had one problem this week. The problem was that my program that used the while loop and checked how many times a number can be divided by two. When I first made my program, in the parenthesis that go with the "while" I put a statement that wasn't a boolean operator so my program didn't work. Then after I added a mod operator, I put a statement in the parenthesis so the program worked.
In the future, I hope that I can finish the SIN number program that was assigned (with no errors) so I could get a good mark on that. Also, I hope that I learn more about proper programming so later on in life, if I become a programmer, I will be able to create programs that don't have any mistake with them the first time that I write them. Lastly, I hope that I have done well on the test that we had on Thursday. Bye!
Friday, April 27, 2007
Friday, April 20, 2007
Weekly Status Report #11 (April 16 - April 20)
This week we learned more about the for and next loops. We only had one handout and it was for the exit for. This was the only new aspect to programming that we learned about. You use exit for when you want to stop a loop from continuing so when there is a exit for, the computer will notice that and will skip the rest of the steps and go just past the next. Other than that, we only did a written, communication assignment that was about different careers that involve programming.
There was only one problem that I encountered this week and it was a security problem. The problem was that before you save the program, you would be able to run it but right when you save it, there would be a security error with the G drives so the program wouldn't be able to run. We solved this problem by saving the programs onto our usb keys and then accessing the program from there.
In the future, I hope to learn how to add animations like fireworks so our programs will be more interesting. I wanted to add one to my guessing game but i didn't know how to soI couldn't. I hope the next week is as fun as this week too. Bye!
There was only one problem that I encountered this week and it was a security problem. The problem was that before you save the program, you would be able to run it but right when you save it, there would be a security error with the G drives so the program wouldn't be able to run. We solved this problem by saving the programs onto our usb keys and then accessing the program from there.
In the future, I hope to learn how to add animations like fireworks so our programs will be more interesting. I wanted to add one to my guessing game but i didn't know how to soI couldn't. I hope the next week is as fun as this week too. Bye!
Friday, April 13, 2007
Weekly Status Report #10 (April 9 - April 13)
This week we concentrated on one new aspect of programming. It was loops (For/Next). Being able to use loops is a mandatory component that you have to know to pass computer science and I agree with that since loops make a potentially long code, short and very easy to understand. To help us understand loops, we would have a short lesson at the beginning of each day and then we would get a sheet with different codes that we would copy into a new program. After that, we would trace the programs to see what was happening within the program and the different variables.
I didn't have any major problems this week. A minor one that I didn't initialize a variable so every time the button was clicked to calculate the answer, the numbers would keep adding up so if the user double clicked accidentally but didn't notice, they would have the wrong answer. another minor problem that I had was that I would make lots of logical errors mainly because I wanted to rush through the programs so I could be finished before class ended. Now, I take my time and don't care if I have to work at home or have to continue my work the next day.
In the future I hope that we create some more programs that use loops so I could get practice and become as familiar with that as I am with if and else and case statements. Also I would like to get more practice with tracing my programs so soon, I won't have to ask someone what I did wrong with my program and I will be able to trace my program and figure it out by myself. This week I learned a lot and next week I hope I learn a lot too.
I didn't have any major problems this week. A minor one that I didn't initialize a variable so every time the button was clicked to calculate the answer, the numbers would keep adding up so if the user double clicked accidentally but didn't notice, they would have the wrong answer. another minor problem that I had was that I would make lots of logical errors mainly because I wanted to rush through the programs so I could be finished before class ended. Now, I take my time and don't care if I have to work at home or have to continue my work the next day.
In the future I hope that we create some more programs that use loops so I could get practice and become as familiar with that as I am with if and else and case statements. Also I would like to get more practice with tracing my programs so soon, I won't have to ask someone what I did wrong with my program and I will be able to trace my program and figure it out by myself. This week I learned a lot and next week I hope I learn a lot too.
Weekly Status Report #10 (April 9 - April 13)
This week we concentrated on one new aspect of programming. It was loops (For/Next). Being able to use loops is a mandatory component that you have to know to pass computer science and I agree with that since loops make a potentially long code, short and very easy to understand. To help us understand loops, we would have a short lesson at the beginning of each day and then we would get a sheet with different codes that we would copy into a new program. After that, we would trace the programs to see what was happening within the program and the different variables.
I didn't have any major problems this week. A minor one that I didn't initialize a variable so every time the button was clicked to calculate the answer, the numbers would keep adding up so if the user double clicked accidentally but didn't notice, they would have the wrong answer. another minor problem that I had was that I would make lots of logical errors mainly because I wanted to rush through the programs so I could be finished before class ended. Now, I take my time and don't care if I have to work at home or have to continue my work the next day.
In the future I hope that we create some more programs that use loops so I could get practice and become as familiar with that as I am with if and else and case statements. Also I would like to get more practice with tracing my programs so soon, I won't have to ask someone what I did wrong with my program and I will be able to trace my program and figure it out by myself. This week I learned a lot and next week I hope I learn a lot too.
I didn't have any major problems this week. A minor one that I didn't initialize a variable so every time the button was clicked to calculate the answer, the numbers would keep adding up so if the user double clicked accidentally but didn't notice, they would have the wrong answer. another minor problem that I had was that I would make lots of logical errors mainly because I wanted to rush through the programs so I could be finished before class ended. Now, I take my time and don't care if I have to work at home or have to continue my work the next day.
In the future I hope that we create some more programs that use loops so I could get practice and become as familiar with that as I am with if and else and case statements. Also I would like to get more practice with tracing my programs so soon, I won't have to ask someone what I did wrong with my program and I will be able to trace my program and figure it out by myself. This week I learned a lot and next week I hope I learn a lot too.
Thursday, April 5, 2007
Weekly Status Report #9 (April 2 - April 5)
Throughout this whole week, we only worked on our pairs project. On Monday, we found out our groups and just got the setup of the programs and the names done. For the rest of the week, we worked on coding all of the aspects to the program. This program, Pizza Palace, was meant to allow the user to pick different types and sizes of pizzas (plus side orders and drinks). Then the programs will add up the total for the user to see. Also the user would be able to change the prices of each of the pizzas and sides.
This program was very complicated since used lots of different dialog boxes and there were lots of coding to do. The thing that took the most time was the naming though. We had to name all of the different tools with a correct beginning and there were way over 20 different tools that needed to be renamed and their text had to be changed. The main problem though, that we had was that when we opened the project, the numbers that we had in the dialog boxes wouldn't work right away. Instead you had to open each dialog box and click ok for those numbers to be in effect. The solution was that we needed to give values to each of the variables in the beginning when the project loads. That was the only big problem that KoolK and I had.
In the future, I hope to continue to get complicated programs like this because I like to have challenges where I have to use all of the knowledge that I have attained. These complicated programs are fun to work with. Hope more are on the way! Goodbye!
This program was very complicated since used lots of different dialog boxes and there were lots of coding to do. The thing that took the most time was the naming though. We had to name all of the different tools with a correct beginning and there were way over 20 different tools that needed to be renamed and their text had to be changed. The main problem though, that we had was that when we opened the project, the numbers that we had in the dialog boxes wouldn't work right away. Instead you had to open each dialog box and click ok for those numbers to be in effect. The solution was that we needed to give values to each of the variables in the beginning when the project loads. That was the only big problem that KoolK and I had.
In the future, I hope to continue to get complicated programs like this because I like to have challenges where I have to use all of the knowledge that I have attained. These complicated programs are fun to work with. Hope more are on the way! Goodbye!
Subscribe to:
Comments (Atom)
