A brief history...
Okay, I am completely new to programming. My past attempts with trying to learn C++ from the two huge 3" books that I have was a waste of my time. When I did finally learn how to make something simple, I did not understand how to implement a "user-interface" with the project. But when I came across Visual Basic 2005, it completely opened up the programming basics to me...I am even able to understand more about the C++ and C# a little bit better (not because of VB, just because I am an idiot to understanding programming). The beginners video series really helped out.
Now, as with everyone else here, I am trying to write a program. This is just going to be used between some friends and myself. So learning as I go, I find it best to learn from this as I have everything else and make a personal notebook for references and stuff...something that I have written where I can understand it more "simply put" because I am an idiot.
I have searched the help database in VB, this forum, other forums here, other programming sites, googling keywords, for solutions to my problems with no specific help yet. I have even tried looking at other code for examples which confused me further. As I do not want to waste anyone else's time, all I am asking is for a link that you know of, or maybe something that you know or has worked for you concerning my issues.
Finally the questions...
First, I would like to know if there is a "non-official" or standard layout or hierarchy when writing a Class or file
Let me simplify:
If Fields, Properties, and Methods must reside in the "Context" or "Code-block" of a Class, and Classes must reside in the "Context" or "Code-block" of a Namespace, is that it Is there nothing that says: "When you write a Class (or any .vb file), the format is...such and such." or "The standard method is this, then this, and afterwards this." A file may not use all of these items, but in what order do you list certain ones
Second, where do I find a list with definitions, without having to search through the individually scattered items in help, of all the Classes that come included in the FCL. I know I may not need them all, but I would like to know what my 'limits' are before I need to write my own classes and/or import them accordingly. I have came across a few site that give the most commonly used Classes, but nowhere near anything of a list.
Last, maybe where can I get info on a "skinnable" interface, (the user has an option of chosing from different skins like windows media player), without purchasing a "Skin" program
Hierarchy and definition list problems.
Muthukumaran
hi,
regarding to writing a class its personaly convention for me when i write something i write in that order ( fields, properties, constractors, methods, functions) there are things so called "design patterns" you can look to it , i guess it talk about the patterns that you talk about , i saw a book and sites talk about that but i didn't read anything about that because i'm still learning and my knowledge doesnt' desreve to read something like that
for your second question you can simply look to msdn http://msdn2.microsoft.com/en-us/library/default.aspx and if you want to learn more about the fcl you can tryto find book called Applied Microsoft .Net Framework Programming(MSPress). it has 2 versions one for vb and other one for c#, i don't know if its good or not because i didn't get it because i didn't cover the basic use of the language to knwo more about fcl
fo you last question anyone else can answer it because i can't, all what i know about this is how to enable and disaple xp visual style to your project, but hey you use programing language that mean you have to make those skins first, you don't use program to ask someone else where you can get it from
the last thing is just advice to you ,don't call yourself some names because you don't know something you will know it but just take your time
best regards
Kennyb28
Second, where do I find a list with definitions, without having to search through the individually scattered items in help, of all the Classes that come included in the FCL. I know I may not need them all, but I would like to know what my 'limits' are before I need to write my own classes and/or import them accordingly. I have came across a few site that give the most commonly used Classes, but nowhere near anything of a list.
Your Object Browser Is your Friend.............
metafedora
Just wanted to thank you'all for the help.
I did however, find a list of great things from the msdn database. A lot of it is extremely confusing, but I am working through it as I go.
As far as everything that comprises of the FCL, I found that too on the msdn database. On the beginner's video series, it gives reference to when you find a class in the FCL that you want to use...
But what is the extent of my options before I design my own class to use I found the list, but each instance is divided into: Public Class; Public Interface; Public Structures; Public Delegates; Public Enumerations; etc. If there is references to Public instances, there are private right, but no listing for them.
I would find it redundant to make something that is already there for use, hence the need of a list. Also, everthing I am finding has reference to some other part of the.NET framework, circling around in an inevitable pile of confusion, that sends me looking where I began at.
I thought about just printing off the entire msdn database off for reference, but it does not put it into the basic terms that I am wanting for my personal reference, writen in words that explain stuff like:
Event handler defines codes or methods...but what is the definition of method in context to an event handler There are numerous descriptions scattered throughout the msdn database of a method, but which ones apply to my description
These are just some of what I am talking about when I say it's confusing. I am not trying to understand how to write a program here; I am simply trying to understand the process so as I do not get confused right in the middle of an important aspect/design feature of my project.
Anyways, as far as the skinnable interface goes, that is an option that I have saved for last for my project. As it is not a detrimental aspect of my project, I would believe that a skinnable option could be added in last, not effecting the fundamental aspects of the programs intentions/design. I will just burn that bridge when I get there.