OK, no objections, so we'll perhaps try to get started on this reorganisation during the coming week.
This will take quite a bit of work, I'm afraid, and I'd like to be able to parcel out individual directories to various people to do "fix-ups". This should principally mean adding any includes, declarations etc that the automated scripts have missed -- a sort of repetitive trial and error process that ends when all the files in the directory actually compile. Please let me know if you think you'll have a bit of time around the end of this week. The rules will probably be as follows. These should be imposed by the scripts that do most of the work, but anyone following up on them will need to know what they are: * One class per .h/.cpp file (except for nested classes, or in very unusual circumstances) * File name to be the same as the name of the class (mixed case) * All files renamed to .h/.cpp (i.e. no more .C files) * All Rosegarden classes moved into the rosegarden namespace * Command class names will lose any contextual prefix (e.g. the name of the menu the command is used in, which I should never have encoded into the name of the command but did, for several) * Indentation will be Java-style, 4 spaces at a time, no tabs The work will be done on a branch. I would ask that anyone with code to commit (Heikki?) does so before the branch is created, as it'll be harder to commit changes to the current layout after the reorganisation has happened. Any more thoughts welcome. 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
