Chains Box2D
Collisionnnn
Second time is the charm
Well this will suck. I have to do all the "end lines" myself to not get it go all over the layout.
Alright, I figured that if I am going to write so much each day. Then at least I can use it to help me improve my english. I don't really know what I am going to write today since I haven't gotten that much work done today. But I guess I can reflect on what I have learned today and go from there.
So I had a meeting with Jerry and we talked about mostly objects and Friend classes and Inheritance. I was not sure about the whole thing when you wrote : Class, Class2, Class3.
I had a hunch about how it was working but I was not sure. And the tutorials(c++) I was looking at have taken more time than it has helped me. I am not a very quick reader though, so I guess that didn't help either. It's not always written in the way that we are used to. Instead of having a header and cpp file they make something in between. When I first looked at it i thought that I have never seen that in class.
Class Rectangle " "
Int width, height;
public:
void set_values (int, int);
int area (void);
" " rect;
And it said that rect was the object of the class Rectangle. I could not connect it to anything we had done up until then and it still feels like a weird way to write it.
So from what i can understand from with the meeting with Jerry, if you write Rectangle rect, then Rectangle is an abbreviation of everything that I wrote before rect. So instead of including the header from which it comes from you write all it contains to give rect the knowledge of what the class Rectangle exists of. The problem is that you can't refer to it later in the code since the whole class is inside another class. However, it is not a member variable or a method that is listed in the header file of said class. So it's a longer way of writing a code that does less for a bigger project really. If you really hate header files I guess you could use it for something that you don't want to use again later on.
The tutorials feels like they are good to use if you want alternate ways of doing the exact thing. Which is good in itself I guess, but when you read a tutorial to refresh your memory of something or that it isn't really making sense. Then it just makes it harder to find what you are looking for and what part is the most similar to what you have been taught. So it was good to be able to ask someone straight forward who can answer and describe the things you have a hard time with from different angles until you can see how it really is. This was a really long side track from the protected part. I got my hunches confirmed. That it is the class that is using the : Class, Class1, Class2 that is inheriting from the classes mentioned and that the "," is just for when it is more than one class that you are inheriting from. It is pretty logical as you use it when you declare many objects or variables on the same row. Then the object is not as clear, but I definitively got a better grasp on it after the meeting. So an object is something that you can change. It is not functions/methods and it is not member variables of classes you have not made. It is something that takes space so it can not be a pointer.
If its an int you cannot change variable since it is not something that you created. I think he agreed to something like "Member variables that are not the same data type as the class itself" but I think that it still has to be mentioned that it must be a class made by you in the first place. I think i will figure out a better definition when I have watched more code and thought about it a bit more. I felt good to get those thing confirmed and explained thought as it was hard to follow reasoning and code without that knowledge.
I had some trouble with calling variables and functions too. But that also got solved a bit back. It's not that I have no idea of how to use the code. But it's just that i don't know exactly what it does. I am still able to know about how and when to use them and what it does. But it gets troublesome reading someone elses code and it felt like a huge wall which spread to all corners of the project.
So i have a plan in mind so that I wont forget stuff like that again. I will write down all important things I learned during the day in a document so that as soon as i think that I might need to refresh my memory on something I can easily check it up. I guess it would have a similar effect as to writing this blog. This blogs only purpose is not to help me remember things I have learned, but it helps me know what I have worked with and how I did it back then and how I thought about it.
We also had out first meeting with Linus who will help us through the project and he recommended that we should use svn or git as opposed to dropbox as we are using now. It works with dropbox, but I can see how it might be a problem later on as the project grows to store all the parts on and off dropbox since we don't use it directly in dropbox since we would delete each others work easily. So that is something that i should check out as well. It took me way longer than I thought it would to write this so I'm glad that i started early.
So I am going to check the core of the project that Martin has made and then look up svn.
Hopefully I will have more to write about tomorrow but I would not mind some sleep either so I will se how much I will be able to add to tomorrow's blog from tonight.
I should make some more appointments with Jerry as well, the time went way to fast in that room. The thing is that our schedule doesn't help us very much as to when the classes will end. One only says when the class begins and one tells me until what hour the room the lecture will be held in is booked which seems to be way later than the lecture actually ends. And then there is the daily stand up meetings from scrum. I guess I can leave sometime for the guidance meeting but I don't think it is a good idea as long as I am the producer
(I'm not originally the producer but we were told to have at least one week as producer each).
That was akward
WORK HARDER
Alright, I figured that if I am going to write so much each day. Then at least I can use it to help me improve my english. I don't really know what I am going to write today since I haven't gotten that much work done today. But I guess I can reflect on what I have learned today and go from there.
So I had a meeting with Jerry and we talked about mostly objects and Friend classes and Inheritance. I was not sure about the whole thing when you wrote : Class, Class2, Class3.
I had a hunch about how it was working but I was not sure. And the tutorials(c++) I was looking at have taken more time than it has helped me. I am not a very quick reader though, so I guess that didn't help either. It's not always written in the way that we are used to. Instead of having a header and cpp file they make something in between. When I first looked at it i thought that I have never seen that in class.
Class Rectangle {
Int width, height;
public:
void set_values (int, int);
int area (void);
} rect;
And it said that rect was the object of the class Rectangle. I could not connect it to anything we had done up until then and it still feels like a weird way to write it.
So from what i can understand from with the meeting with Jerry, if you write Rectangle rect, then Rectangle is an abbreviation of everything that I wrote before rect. So instead of including the header from which it comes from you write all it contains to give rect the knowledge of what the class Rectangle exists of. The problem is that you can't refer to it later in the code since the whole class is inside another class. However, it is not a member variable or a method that is listed in the header file of said class. So it's a longer way of writing a code that does less for a bigger project really. If you really hate header files I guess you could use it for something that you don't want to use again later on.
The tutorials feels like they are good to use if you want alternate ways of doing the exact thing. Which is good in itself I guess, but when you read a tutorial to refresh your memory of something or that it isn't really making sense. Then it just makes it harder to find what you are looking for and what part is the most similar to what you have been taught. So it was good to be able to ask someone straight forward who can answer and describe the things you have a hard time with from different angles until you can see how it really is. This was a really long side track from the protected part. I got my hunches confirmed. That it is the class that is using the : Class, Class1, Class2 that is inheriting from the classes mentioned and that the "," is just for when it is more than one class that you are inheriting from. It is pretty logical as you use it when you declare many objects or variables on the same row. Then the object is not as clear, but I definitively got a better grasp on it after the meeting. So an object is something that you can change. It is not functions/methods and it is not member variables of classes you have not made. It is something that takes space so it can not be a pointer. If its an int you cannot change variable since it is not something that you created. I think he agreed to something like "Member variables that are not the same data type as the class itself" but I think that it still has to be mentioned that it must be a class made by you in the first place. I think i will figure out a better definition when I have watched more code and thought about it a bit more.
I felt good to get those thing confirmed and explained thought as it was hard to follow reasoning and code without that knowledge. I had some trouble with calling variables and functions too. But that also got solved a bit back. It's not that I have no idea of how to use the code. But it's just that i don't know exactly what it does. I am still able to know about how and when to use them and what it does. But it gets troublesome reading someone elses code and it felt like a huge wall which spread to all corners of the project.
So i have a plan in mind so that I wont forget stuff like that again. I will write down all important things I learned during the day in a document so that as soon as i think that I might need to refresh my memory on something I can easily check it up. I guess it would have a similar effect as to writing this blog. This blogs only purpose is not to help me remember things I have learned, but it helps me know what I have worked with and how I did it back then and how I thought about it.
We also had out first meeting with Linus who will help us through the project and he recommended that we should use svn or git as opposed to dropbox as we are using now. It works with dropbox, but I can see how it might be a problem later on as the project grows to store all the parts on and off dropbox since we don't use it directly in dropbox since we would delete each others work easily. So that is something that i should check out as well. It took me way longer than I thought it would to write this so I'm glad that i started early.
So I am going to check the core of the project that Martin has made and then look up svn. Hopefully I will have more to write about tomorrow but I would not mind some sleep either so I will se how much I will be able to add to tomorrow's blog from tonight.
I should make some more appointments with Jerry as well, the time went way to fast in that room. The thing is that our schedule doesn't help us very much as to when the classes will end. One only says when the class begins and one tells me until what hour the room the lecture will be held in is booked which seems to be way later than the lecture actually ends. And then there is the daily stand up meetings from scrum. I guess I can leave sometime for the guidance meeting but I don't think it is a good idea as long as I am the producer(I'm not originally the producer but we were told to have at least one week as producer each).
Nya kurser
And we are done
Lördag 18/1
Fredag 17/1
Torsdag 16/1
Lördag 11/1
Söndag 5/1
Lördag 4/1
Onsdag 1/1
Måndag 30/12
Torsdag 26/12
Söndag 22/12
Fredag 20/12 2
Fredag 20/12
Tisdag 17/12
Post mortem
First post
Välkommen till min nya blogg!
Mitt första inlägg.