I'm thinking of taking this opportunity to rename the classes RosegardenGUIDoc, RosegardenGUIApp and RosegardenGUIView.
Not right this minute -- I don't actually think we should do it until we've got things a bit more solid, and merged across the current updates from trunk. But during this cycle of revisions anyway. These classes have never had very sensible names -- they're essentially a hangover from the very first prototypical version of the GUI, which I believe Guillaume created in KDevelop with "RosegardenGUI" as the project name. RosegardenDocument is the obvious name for RosegardenGUIDoc. (It's in the Rosegarden namespace so it could just be Document, but I like the idea of retaining a unique string -- the uniqueness of the existing names means that this change would be very simple, and that seems like a benefit to me.) Then for RosegardenGUIApp, perhaps RosegardenMainWindow or RosegardenAppWindow? And, hmm, RosegardenMainWidget or something (what exactly?) for RosegardenGUIView. I would like to make it obvious that this widget is just a widget, not the whole window. Any objections, better ideas, or suggestions of other badly-named classes? Another goal is to refactor out all of the GUI parts from RosegardenGUIDoc so that it is just the document class it claims to be... but that's a bigger job. Chris ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
