On Thursday 09 October 2008, D. Michael McIntyre wrote: > > Anyway, it's your decision > > Not really mine, but majority rules and all that. I could fork it too, but > it isn't worth it.
That sounded a lot worse than it really is as far as this whole KDE4 vs. Qt4 thing. I've turned to the fork card many times over the years, because of the perpetual conflicting directions of the needs of sequencer users vs. the needs of notation users. That's always been the biggest source of my personal frustration with Rosegarden. I've adopted the sensible position of sitting down and trying harder to push Rosegarden into new notation territory though, and we can actually accomplish quite a lot without giving up on being a sequencer too. Nearly everything. I think the only thing on my list that will always remain completely impossible forever is kneed beams that span two staffs. On Thursday 09 October 2008, Chris Cannam wrote: > I have always been perfectly happy to use KDE stuff, and KDE desktop > integration has been handy, and I always found it irritating when > people complained about Rosegarden depending on KDE, and so on I find it irritating when people complain about depending on KDE too, but I don't think switching over to pure Qt is much of an answer to that, because the largest number of people whining about KDE are those who seriously wish we would do a GTK2 port. These people are all clueless morons, of course. I always knew that, but this deep into the Qt4 port with the goal still this far away, I have a much deeper appreciation for how moronic they really are. Good grief. > I'm still perfectly open to the idea of using KDE bits if we need > them. I just think that, where there is a straightforward choice > between KDE and plain Qt for a component, there's seldom much reason > to prefer the KDE version these days. If it turns out we really do > want KDE file dialogs or something, we could always make them an > option. I'm trying to come all the way over to the pure Qt4 camp for a couple of reasons. Well, for one thing, somebody already cut out the parts of KDE I was hoping to save, and it's done, so I might as well see how it comes out. For another, if I can manage to live with the result, I like the idea of only having to deal with one porting guide next time this happens, and there will surely be a next time. Also, Qt's porting docs are considerably better, and one might hope that is the case again when Qt5 comes to kick us in the teeth. Finally, I don't know if I will ever adopt KDE4 or not. I probably will, and I haven't really *tried* to live there yet, but so far I've done nothing more than glance at it and sigh. If I can't ever live there, I don't know where I'll go, since I can't stay comfortable with KDE 3.5.x forever. It's not an obvious choice though, no matter how I look at it. I just don't like the direction any of this is taking at all. -- D. Michael McIntyre ------------------------------------------------------------------------- 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
