On Wednesday 02 Aug 2006 16:01, Chris Cannam wrote: > Another thing is that this would do absolutely nothing to solve the > problem of some of our individual classes (RosegardenGUI*, > NotationView etc) being so ridiculously huge. We'd have to address > that in a separate refactoring stage afterwards.
On reflection, I think if we were to do this it would be better to find a way to split up the three or four most unwieldy classes first. Then any script that did things like trying to add the right #includes for your new one-class-per-file files would be more able to save a bit of work compared to having to slim down the headers for the files yourself afterwards, and also splitting up the classes might turn out to have some influence on the directory structure we wanted to use. Chris ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
