LOI Kratong

Hey, I looking to write my first big program (in terms of functionality), a dictionary program. While thinking how to make this I came upon the idea of learning to use classes effectively. Although I know how to implement classes, I need some help/advice on how to design them.

Is there a good technical reference that I need to be pointed to? I really need an explanation from the top down, i.e. do I need to have a dictionary class? Or should I just have a ... actually I don't know where to go after that!

Any help would be much appreciated!

__________________
www.heldtogether.co.uk

DaWei

Imagine that you're building a lawnmower. There's a lot of diverse functionality there. How would you divide it all up into coherent objects (classes)? How would you restrict or constrain normal access to, say, the carburetor (its interface)? Don't let it buffalo you, it's a rational process.

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

bl00dninja

get a pen and paper and work with it. think about data structures that would be appropriate. maybe an STL map? most of your work here is not coding, but design.

__________________
i put on my robe and wizard hat...

Have you ever heard of Plato, Aristotle, Socrates?...Morons.

Booooze

I have had the same problems lately as well. Design is a big part of the project, and if done properly can save you tons of time. If you don't do a scope document or plan of some kind, you will most likely find yourself adding things in, and changing your main goal as you go along.

The one project I wrote a scope document for, turned out great. If your stuck at the design, write a scope document, and write down how everything works. While your planning what functionality you want in the program, you will realize and visualize the code in your head. With that said, you should be able to get a list or view of classes down. When you get lost on what to do next in the programming aspect, you can always refer back to the document. That's what I do. Face it, planning isn't nearly as much fun as coding it. Some planning is better than none. Try and at least have a reference. if your not sure how to write a scope document, google it. Don't know if this jibber jabber will help, but that's my little spiel.

LOI Kratong

Okay, so for my dictionary I may have:

a dictionary class which has the functions inside it, such as lookUp();
the main private variable may be string currentSearch;
the meaning of words may be held in an STL map which is private.

And from there I just need to plan!

Easy. Thanks, I'll dig out my pen and paper and see what I can come up with.

Thanks guys

__________________
www.heldtogether.co.uk