Is there a document that gives me a literal picture of the architecture of rosegarden? (UML?)
Is there a list of requirements that rosegarden must fulfill? (UML use cases) At present I am not sure of the focus of rosegarden and what I am attempting to achieve with the guitar tab editor. I am concerned that my data structures will not fit into the existing data structures used to play back a section of music. For example, eventually it would be nice to have a guitar chord played back as a strummed chord. So my questions are centering around what are the requirements of rosegarden and why it is built the was it is. I know these items are "documentation" issues. In my experience I have found that once I have a good plan I know exactly how I need to built something. Personally I want to have someone to mentor me on software design. To know when to use design patterns, software design methods (Agile software development) and when the best time it is to use UML in a software design. I believe what I am asking is in line with the RAISONDETRE: "If we lose focus again, RG is dead. It has already been brought back from limbo a couple of times, there won't be a next one." GL, 06.06.2001 Stephen ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
