Hi,
Another reason for excessive recompilation is the missing granularity due to the sodipodi/C heritage. Here are files that contain functions for several classes and must include headers for both. Although they are related, they could be perfectly separated into two files:
desktop.cpp: SPDesktop, SPDesktopWidget sp-item.cpp: SPItem, SPItemView display/sp-curve.cpp: SPCurve, NArtBPath display/sp-canvas.cpp: SPCanvas, SPCanvasItem ui/view/view.cpp: SPView, SPViewWidget
Granularity is good[tm]. I want to separate. Who is holding me back?
ralf
On Tue, Aug 23, 2005 at 06:04:35PM +0200, Ralf Stephan wrote:
Hi,
Another reason for excessive recompilation is the missing granularity due to the sodipodi/C heritage. Here are files that contain functions for several classes and must include headers for both. Although they are related, they could be perfectly separated into two files:
desktop.cpp: SPDesktop, SPDesktopWidget sp-item.cpp: SPItem, SPItemView display/sp-curve.cpp: SPCurve, NArtBPath display/sp-canvas.cpp: SPCanvas, SPCanvasItem ui/view/view.cpp: SPView, SPViewWidget
Granularity is good[tm]. I want to separate. Who is holding me back?
I've worked a bit on desktop.cpp and view.cpp last month, and in fact was also wondering about dividing those up better. I'd say go for it.
The *Widget classes might be more logical to put into ui/widgets/ instead of in the root dir or in ui/view/.
Bryce
participants (3)
-
Bryce Harrington
-
MenTaLguY
-
Ralf Stephan