Bark at the moon wrote:I think he did it because it was fun. Let's apply Occam's Razor and assume that the motive is that it was fun to do.
Thats pretty much what I was going to say about this, he did it to show he has a sense of humor........
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
I've just purchased Dan Brown's Deception Point as an e-book. This is the first e-book I have purchased.
I have an m200 tablet pc which I found got to hot (even with the backlight on low and the proc set to min), also I was very nervous with the thought of dropping of to sleep and dropping it.
I then switched to reading the same book on my PDA, which as others have said is the best way. The light doesn't bother my wife-to-be at night. If I drop it, which I have it doesn't break.
jonathanh wrote:If I recall correctly, poorly-written anti-virus software is the #2 cause of bluescreen crashes. #1 is poorly-written display drivers!
sheeeng wrote: Norton always crashes my system after sometimes... I don't use Norton anymore.
Wells I don't mind being corrected on my English! As it's rubbish...... thanks for the tip!
What you says makes sense. I think I begining to get my head around this now.
I think I'm going to start writing some code and play around with some ideas. I'll also re-read what I've already read, to see if it makes more sense.....
This is great so much easier than trying to figure out if you really understand a topic on your own.
Keep them comming!
Objects are instances of Classes. Classes are like the blue prints of a house. Objects are actual houses built using the blue print.
Classes allows you to encapsulate functionalities and relevant properties. The hard question is often where to draw the class boundary, i.e. how do you decide this functionality belong in one class and not another? Depending on the development methodology and the type of application you are writing, you may not care.
Well designed classes encourages reuse. Couple with other features of OO e.g. Inheritance you can build powerful reusable and extendable frameworks. The Dot Net framework is a true testament of this.
I don't know of any good materials, the best way to learn is probably to start your own toy project and get stuck into it. Build a Wiki or something.
Thanks for the reply. This is beginning to make sense.
So if I wrote an application to track site visits to customers, then I could write a class called customers and that class would have certain functions, routines and properties that I could call over and over?
I'm a novice programmer, I use to write software when I was younger back in the Quick Basic Days....
I'm trying to get back into more of a hobby than anything else. I've been reading up on a few things, but I seem to have two areas which I think I'm over complicating in my head.
These are Databases and Classes.
Right now I want to get my head around classes, can any one help? From what I understand thus far a class is your object in OOP, is that correct?
Why right a class, I don't fully undertand the advanatge, although it appears the "right thing to do!".
I hope people can recommend some good advice reading material to get me started.
I'm the kind of person who really wants to do things the correct way.
Thanks in advance.