[Chicago-talk] super complex object
jt at plainblack.com
Mon Aug 1 14:08:35 PDT 2005
I have created a monster super complex object. It only has a half dozen properties, but
those properties can be manipulated in a near infinite number of ways.
The problem is that I want my main class to have all sorts of methods for use by the
subclasses in order to keep the subclasses small. The problem is that I now have a
master class that has almost 100 methods in it. That just seems wrong to me, but at the
same time, every one of the subclasses uses all of those methods at one time or another,
so I can't just get rid of them. And since they're always in use by all the subclasses,
it doesn't seem to make sense to create any sort of middle tier subclass.
What I'd like to do is break them out into seperate files by functional groupings, but
bring them all in as methods to the master class. Does that make sense to do? Is there a
good way to do it?
I've also been trying to figure out how I can break the master object down into simpler
classes that the master can then inherit from, but I haven't been able to do it. The
methods seem to rely on each other too much to make that work.
Any suggestions? It seems that I can't be the only one to have run into an
overcomplicated object. Help a brother out. =)
JT ~ Plain Black
ph: 703-286-2525 ext. 810
I reject your reality, and substitute my own. ~ Adam Savage
More information about the Chicago-talk