D. Michael McIntyre wrote: > On Thursday 02 October 2008, Matthew Woehlke wrote: >> - rosegarden is moving away from KDE? > > Yes. We were originally aiming at being something like 90% Qt4, 10% KDE4, > but > in practice we're down to i18n() being the only part of KDE it's going to > take real effort to work around, and I fully expect we'll switch over to Qt's > tr() in due course, and wind up with a pure Qt4 application, with no > dependency on KDE4 at all. > > I love KDE, and part of me hates this shift, but I can't argue with how much > sense it makes from an overview perspective. When we started this, I was > extremely reluctant to move away from KDE, to the point where I thought I > might wind up quitting the project, but now that I have been waist deep in it > for awhile, I think we can probaby make the whole thing liveable. We might > have to go to some trouble to get file dialogs that don't suck, but Sonic > Visualiser has decent file dialogs, and it's pure Qt4. MusE and MusE Score > and Canorus are all pure Qt4. Lots of other apps in this arena have always > been pure Qt3, and I'm sure they'll be moving to pure Qt4. > > It's really not that bad. At least we're not switching to GNOME. If > Rosegarden ever did that, I'd vomit in my hat, and then shoot someone.
:-D > I really don't think removing the dependency on KDE is as much of a deal > breaker as you think, but either way, you're stuck with it just like I am, > for better or worse, and since there's nothing quite like Rosegarden > anywhere, on any platform, at any price, we're all just shit out of luck if > we can't live with it. My problem with moving away from KDE is that a: it means I can't work on KDE integration (which is what I probably would have been most interested in), and b: (apparently) means more of a bias towards qmake instead of cmake, which in turn means I can't use my build infrastructure (not to mention having to learn Yet Another Build System). And working on a qt-only project makes me feel somehow dirty :-). > and since there's nothing quite like Rosegarden anywhere, on any > platform, at any price, we're all just shit out of luck if we can't > live with it. Technically, I could fork it, but that's probably more effort than I'm willing to expend at the moment. It's not that I'm going to refuse to /use/ RG, just that being a KDE app was a point in its favor toward using it, and an even bigger point in favor toward possibly becoming a developer. As it stands, I'm probably going to go back to shopping around, at least until 'yum install rosegarden4' doesn't want to pull in Fedora's KDE4 packages as well. It's also discouraging that I can't recall any mention of rosegarden on, say, kde-devel. I think the KDE crowd would have been happy to help with the porting effort, but RG seems to be pretty well distanced from the KDE community (well, and now it is no longer part of the KDE community at all, which is another reason I'm less motivated to get involved). Anyway, it's your decision, so please don't feel like I'm trying to stop you. I'm just sad because moving away from KDE means I won't be getting involved. -- Matthew ENOWIT: .sig file for this machine not set up yet ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
