Evaluation

Overall I think my project was completed with success. I met all my expectations and have done exactly what the coordinator told me to do. I made this product with very little time, considering how long it takes to make an application for an Iphone/Ipad. The websites have really helped me out considering I watched many Youtube videos. The Youtube videos are the quickest way to learn how to make an application, since you can follow and do what the video tell you to do. It was easier to do rather than just reading it. I really wish to make another application, and next time not do it for fun, but to make money with it as well.  An application can do many wonderful things and helps peoples life, due to the advancement of technologies. Overall I really have enjoyed this project.

Teacher and I talking

I have discussed with my teacher about my project, and have been helped many times. We first discussed on what I was missing. I figured out that I was missing my time line and my goal. My goal was to make a simple application, learn objective c. I manage to complete these both and was able to finish my project. My timeline was a bit messy. I could not make an official timeline since the application making could take very long, and hard to estimate when it will be finished. I also needed my Dads computer to due this, since the Xcode only worked for lion now because of the new update. I could only work for 1 week, so I could not make the application I wanted. I worked for 2 hours each day, sometimes more. It was not organized as I wanted it to be. Overall, I thank my teacher and my father for all the advices and telling me the steps I needed to take to finish this application.

Near the finish

I:m nearly done my personal project for my school. I  have gotten all my data, and my application is looking good. I could add other stuff to the app, but for now its good. I think I manage to make this application due to me taking my time and going to websites looking at the language of programming. I would insist anybody out there to first learn a language, and then when you get comfortable with it, you can start making an application. You should always learn the basics before you go to anything advanced, such as making an application. I will post screen shots of my application tomorrow.

X code 4.2

Hey guys, guess what? The new X code Update came out. The features changed a lot, but if you watch tutorials on it, you will be able to make application with ease. They added a new feature called smart bored, which allows you to see what the application will look like. It also decreases the amount of code you have to put in to the application. Also, they added a feature where you can make an app that can be used for Ipad and Iphone. Which really helps, since making two apps is very time consuming. I recommend to watch this tutorial by geeky lemon.http://www.youtube.com/watch?v=k9yUcJJmCzo&feature=list_related&playnext=1&list=SP4CA1BF75F53F1BC8

HEY

Hey guys, i've been looking at many tutorials on objective C and now have a basic knowledge of all the codes and other features on objective c. I decided that my first app that I will be making would be a calculator. A simple, but not too easy to make app. Now I'm not sure how long this will take me, though I suspect it will take long, so I will take screenshots of the process. I'm sure there will be many false on the code it self, but please bare with it, and I hope that you could contact me and help me on what I did wrong.
Thank-you

The good use of posting an application on the app store

When you make an app that you think is good and have confident that people would like it, you should post it on to the app store. The reason is that apple is a reliable company, it produces many awesome apps, and will never betray your expectations. But say that you will be posting an app for the school you go too. It may be easier to post it, but you will only get ratings from people inside of school, not out side of school. If you want to be more famous, or to be a better programmer, I would be posting it on the app store to get reviews from world wide, so you can improve on how to be a better programmer or an app maker. Once you become a good programmer or an app maker, the apple company may hire you and now you have a reliable job.

Day 3

Hi, today i'll be taking you into day 3 of the objective C. I'm sure you see "NS" in many codes. NS stands for next step. For example, you sometimes use the code nsstring. This means it is a text that is unchangeable. These are all classes. There other classes such as, NSMutableString, NSArray, NSMutableArray, and NSNumber. Array is an arrangement of memories. For the pointers, this is meant to make a static string of text, this means to make it a stationary condition. You will be using this a lot when you are creating classes. I also put a picture on this were it shows the inheritance of each class. By this inheritance class, we can inherit the class and add more to the class, writting your own method, and code.
That is all for this week.

Day 2

This tutorial is does not explain much on the codes, but more like an explanation of how the objective works. I would like to explain this, but I do not have much time, so I would like to tell you just on the codes. First off, the interface and implementation. When you open up Xcode, I think you see a lot of folder that ends with .m and .h. Implementation is .m and interface is .h. Also, you will see a lot of -(void)/ This - means it is a instance method, and void means that it will return nothing back when it checks the code. There will be more further tutorial on day 3 on instance method. I hope this helps you understand more of the Objective C.

Day 1

The first thing I learned in this tutorial is the variable. You need to know this to store data. There are many different kind of variables, but in this tutorial, the main variables you should know right now are int, char, float, and double.  Now for our conditionals, the if statement. This is meant to check if something is true. Take not of that when using an equal sign on your Xcode, make sure to know that two equal sign,== means it is going to check if the two thing are equal to each other. One = is to assign the first value to the second value. The else statement is to check something that is not true. Now for the loops. Loop is to go through your piece of code and checks it for you. The three most common loops are the for, while, and do loop. The for loop is the basic, it executes the initiator.  Say you have the letter y= 1, and the letter i=5. Then you have x increase by 1 each time. Then soon or later x will be greater than i. Then the loop is done its job and the loop will stop. The while loop is the same as for loop, but it is like an infinite loop. This will execute the code between the brackets until something becomes false. The last is our do loop, which will execute after the block of code. The code is meant to at least run once.

Last thing would be the pointers. I was reading the tutorial, and it was very hard to understand, even the tutorial it self said it would be the hardest to learn if you are trying to learn language C. The basic wa to interpret is that if we use the word foo, and represent it with the number 123. We use the pointer to point to foo, which is the number 123. There will be more detail to this as I continue to follow this tutorial. 

Hello World

I followed a youtube video that lets you get a basic idea of how to make a touch application. The application itself is very easy to make, but if you do not understand the language, you will be thinking, "what does this mean?" That is why first you learn the language of objective c or language c. This will give you the basic knowledge of how to make an iPod/iPhone application.  After you learn it, everything else would make totally sense. I will post the website I use to learn the Objective c. Also, a youtube video if you do not like to read and learn. I prefer reading it, but if you like to visually see and hear, I suppose the youtube video may be easier to understand.

Hi

The book I bought on Amazon did not turn out so great as I thought it would. The book had very good details, information, and screenshots. The problem was the screenshots. The screenshot for some reason was totally different than what I had on my screen. I would not say it is the book's fault,but it could have been Xcode's problem. The edition of the Xcode that the book was using nay have been different than my Xcode. I decided to switch the way of learning how to make an application by suing the internet to find a reliable source. I will post the source when I think it is good for anyone else to use.
I deeply apologize for the late update, I will be doing my best to work on this application when I have my free time.