|
Home > Archive > microsoft.public.cert.exam.mcsd > September 2003 > forms and classes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Here is another analogy that might help:
The class is the cookie cutter, and the class instance is
the cookie 
>-----Original Message-----
>Ok, I think I got it, a form is more of the physical
>representation, I don't know why I couldn't grasp this
>concept.
>>-----Original Message-----
>>Even simplier.... Everything you write is a class (or
>>structure).
>>
>>Form is the name or type of the class.
>>
>>Instance is the in-memory representation of the class.
>>
>>
>>>-----Original Message-----
>>>Ok this is confusing to me in the MCSD self paced
>>training
>>>book for exam 70-306 it says:
>>>"When you create a new windows form project, an initial
>>>form, named form1, is added by default. Form1 is not
> an
>>>actual instance of a form, however, but rather a class
>>>that represents the code behind an instance of a form".
>>>It makes it sound like it's a class not a form, I feel
>>>like I'm missing something really simple.
>>>
>>>.
>>>
>>.
>>
>.
>
| |
| Kline Sphere 2003-09-27, 5:23 am |
| >That is what makes VB .NET so much better than VB6.
>Because the form is a class,
True visual basic 6 does not support oo constructs, but then what do
you expect from a [relatively] poor development tool?
However, In VB6 a form is treated [loosely] as a class. A form defines
state, behavior and an interface through which clients can manipulate
state and behavior of individual instances.
> you have much more control
>over it and can use visual inheritance.
Why visual basic as microsoft [failing] flag ship was never made into
to true oo compatible tool [until dot not], is quite beyond me. Had it
had been microsoft who release released Delphi back in 93/94, visual
basic would have dead there and then.
>Everything is VB .NET is a class.
A module is not.
| |
| Simon Smith 2003-09-29, 12:24 pm |
| On Sat, 27 Sep 2003 09:36:09 +0100 in article
< maianv4g3rebjaf4df8j2k0n6fcths
s9ap@4ax.com> in
microsoft.public.cert.exam.mcsd , Kline Sphere <™> wrote:
>>That is what makes VB .NET so much better than VB6.
>>Because the form is a class,
>
>True visual basic 6 does not support oo constructs, but then what do
>you expect from a [relatively] poor development tool?
Well, it does. Just not implementation inheritance.
>
>However, In VB6 a form is treated [loosely] as a class. A form defines
>state, behavior and an interface through which clients can manipulate
>state and behavior of individual instances.
Yep.
>
>> you have much more control
>>over it and can use visual inheritance.
>
>Why visual basic as microsoft [failing] flag ship was never made into
>to true oo compatible tool [until dot not], is quite beyond me. Had it
>had been microsoft who release released Delphi back in 93/94, visual
>basic would have dead there and then.
Our world would have been different for sure.....
>
>>Everything is VB .NET is a class.
>
>A module is not.
It compiles to a class with only static methods.
--
Simon
simon dot smith at snowvalley dot com
"Insomnia is a small price to pay for the stuff you read on UseNet"
| |
| Kline Sphere 2003-09-30, 5:24 pm |
| >>>Everything is VB .NET is a class.
>>
>>A module is not.
>
>It compiles to a class with only static methods.
Another cludge...
|
|
|
|
|