Class code
My guess is that you and I would write the class code differently than you would, but that doesn't mean my design is better. My puposes for such a program may be different than yours. For example, if I have an image library, I would likely create DB tags that would classify each picture into broad catagories (e.g., vacations). I might then have a secondary tag that would allow me to group by year or state. It depends on what you need. Think about the organizational structure you want for each class type and work accordingly.
Here's an idea: design how you think the DB classes should look now. Do it on paper, but don't actually write the code. Indeed, this would be a good place to get a little UML under your belt. Now, finish the book. Having done that, go back and look at your design. My guess is that you will design it differently after you have read the chapter on Inheritance.
Keep me posted!
__________________
Jack Purdum, Ph.D.
Author: Beginning C# 3.0: Introduction to Object Oriented Programming (and 14 other programming texts)
|