Well, this is becoming quite the little nightmare.
The executive overview goes something like this.... Rosegarden was
designed to be a MIDI editor. Then someone decided to add MIDI
sequencing to it. But what's ok for a MIDI editor (very CPU intensive
updates in response to infrequent edit events from the user) is not at
all ok for a MIDI sequencer (constant edit events due to massive amounts
of incoming MIDI data courtesy of Herr Beethoven).
This is some really complex stuff. It is going to take me months
(maybe years) at my current rate of about 5 hours/week. Plan is as follows:
1. Try to understand the Segment notification mechanisms and all of the
observers. This is a massive undertaking as the number of observers is
very large and the observer code is quite complex.
2. Come up with a plan to fix this issue.
3. Slowly evolve the code in this new direction without disrupting
things. ("Refactoring" is the popular, though misleading, term.)
Unless somebody has a better idea.... Looks like I'm in this for a
very long time. On the upside, this was one of the projects I really
wanted to tackle. Wish I had more time than just 5 hours/week.
Ted.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
