On 01/07/2013 01:12 PM, Tom Breton (Tehom) wrote:
> I remember your frustrations in porting to Qt 4. Yes, hopefully that was
> the only big hump.
That nearly killed Rosegarden. We spent well over a year slogging
through that mess blind, just making wild ass guesses at what code might
work, and then most of another year fixing the hundreds of things we
accidentally shot in the dark.
The no more Qt 3 thing was us turning around to go back in for another
round of the same kind of slog. It was a smaller scale that time, and
got done much faster, but it was still a lot of misery for little benefit.
> * What can Qt 5 do for us?
Probably nothing in particular, although I'll be more interested if the
Android/iOS port turns out not to be vapor.
I'm not necessarily interested in porting Rosegarden to Android, but the
idea is vaguely intriguing. I'm interested in developing for Android
more generally, but I'm a truck driver, not a code monkey, and I see no
point in having to learn a new language and a new toolkit when I can
knock out Qt code with ease.
(Of course if the free apps I've looked at are any indication, Android
is one of the worst platforms for audio ever conceived anyway. We're
talking 500-750 ms latency plinking an on-screen piano, for example.
> * When will rg requiring Qt 4 become an actual problem? I'm guessing
> much longer than 4 years from now.
You're probably right. We probably have two years before anybody even
gets halfway serious about porting to Qt 5, and then another four to six
before distros drop it from the repos, so probably 6-8 years. Hell,
I've only been at Rosegarden 10 years so far. It just SEEMS a lot
longer than that sometimes.
Anyway, the bottom line is whenever we get around to facing that
particular problem, it doesn't sound nearly as bad as the last one, so
there are no dark clouds looming on that particular horizon whenever it
D. Michael McIntyre