[resending bounced email from last week] ---------- Forwarded Message ----------
Subject: Qt4, was Re: [Rosegarden-devel] semi-working tablature for anyone who's interested Date: Wednesday 25 July 2007 16:30 From: Chris Cannam <[EMAIL PROTECTED]> To: [email protected] Cc: "M. Donalies" <[EMAIL PROTECTED]> On Saturday 21 July 2007 20:14, M. Donalies wrote: > Any notation code been written for Qt4 yet? Nope. But at some point it's going to be more or less inevitable if we want to keep up with KDE4, and there will come a point before all that long where it's no longer going to be very attractive to make big feature releases that don't exploit Qt/KDE4. As Guillaume notes, QCanvas no longer exists in (native) Qt4, for good reasons (it has many limitations) so we'd want to switch to something else, such as (most likely) QGraphicsView, or a plain widget. I am just beginning to do some active work on making the notation view available as a component for use in other applications using Qt4 -- I have a probable "day job" requirement for this, in a specific other application. This work is going to happen in the recently created "kiftsgate" branch, probably with many missteps and a great deal of refactoring. The aim is to retain a working version of Rosegarden at the same time as a working exportable notation component. My first step is going to be to reduce the size and complexity of NotationView by factoring out any code that isn't strictly tied to the "notation-ness" of the view: for example, making command classes more self-contained so that the NotationView doesn't need to have logic for every single command built in to it. Making NotationView simpler should make it a less daunting proposition to mess about with it in other ways. I have vague ideas about how to progress from there, but vague they still are. I'm actually on holiday at the moment with only sporadic internet access, so I haven't looked closely at your tablature branch yet, but at a glance it looks like its approach wouldn't be affected a great deal either way. I'm going to be wary of saying "this is how I intend to proceed and this is how I'd like to see things done" this time around, because I'm aware that the usual result of that is only to stall things. Experimenting on Subversion branches to see what might work is a good approach. All that said, it's hard to overstate how big a piece of work switching to Qt4 is going to be, particularly if we don't want to use the Qt3 compatibility layer. Especially in our custom dialogs we have huge amounts of layout code that depends on widget and layout constructor syntax, and layout semantics, that have changed substantially in Qt4. Chris ------------------------------------------------------- ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
