Is a bit of refactoring in order?
Steven T. Hatton
hattons at globalsymmetry.com
Sat Jun 4 23:58:03 UTC 2005
I've been looking at a lot of the central code for KDevelop, such as
parts/appwizard, language/cpp, src/, and have come to believe it could
benefit from some reorganization. There seem to be a lot of classes doing
too many different things, and there also seem to be certain kinds of
functionality dispersed throughout the classes that could be pulled together
to form classes specialized to provide that functionality. One example is in
the AppWizardDialog there are about 70 #ncludes, over 1300 loc, and the
favorites functionality should clearly be in a class of its own.
I believe this is part of the reason I find the code hard to understand and
Does anybody else share these opinions?
More information about the KDevelop-devel