Richard Bown wrote:
> Thoughts?
I think you're fucking nuts.
I think if Guillaume was embarking on a similarly gross piece of
refactoring just to attempt to remove some short delay somewhere,
you'd be furious. Rightly.
I want to know:
1. Why you think this way will be better in the long run. Is
it really a good idea to have one view across all documents?
For an MDI-style or multiple-window interface we'd presumably
still want one view per document and many views active at once.
(Convince me I'm wrong here, and you've pretty much convinced
me of the whole thing.)
2. Exactly what problem you're trying to solve, and:
a. Why it can't be solved in any other way, such as by sticking
processEvents calls in apposite places (e.g. last thing in
RosegardenGUIApp::initView).
b. Why it's so serious as to justify something so major even
if it can't be completely solved in any other way.
Just since you didn't bother replying to my last question along
those lines.
I appreciate you're generally pissed off with the apparent
slowness of things like file loading, but this is really no way to
go about fixing it. We need to know _where_ it's slow and _why_
it's slow before we go completely redesigning the view structure
and breaking absolutely fucking everything just on the off-chance.
There may be a good case for some of the topical changes you
suggest, such as replacing m_document generally with calls back to
a parent. But that's just trivial stuff.
Chris
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
