Dear Chris / RG Team
Do you have same idea/help, how to transform this to qt4 ?:
KMimeType ==> QMimeData is different, other purpose
KRecentFileAction ==> convert to QAction too? I assume so.
how / where to set (replace) global variables that are requested like:
( does not exist for qApp )
How to do recent file handling ?
KTmpStatusMessages ==> use statusbar ? disable ?
From: Chris Cannam <cannam@al...> - 2008-09-15 14:39:57
On Mon, Sep 15, 2008 at 8:23 PM, Emanuel Rumpf <xbran@...> wrote:
> createGUI("rosegardenui.rc", false);
This is the entry point for KXMLGUI, which is a bit of infrastructure
that reads an XML layout of texts and menu locations for actions and
attaches the actions appropriately (provided they have already been
created and entered into the action collection).
I don't know the status of this in KDE4. It's probably still there,
but I assume that the entry point is no longer available because the
class from which we're trying to call it is now a "pure Qt" class
(QMainWindow or whatever it is) rather than a KDE one.
I don't think KXMLGUI is a very big piece of work, although it may
have its subtleties. I wouldn't object to pulling this bit of code in
to our own codebase and tweaking it to work with a non-KDE window, if
it's one of the only things that would tie us down to KDE. I don't
expect it's very hard to do and I wouldn't mind losing the dependency
on this rather inscrutable bit of KDE.
> KMimeType ==> QMimeData is different, other purpose
No idea, I'm afraid (I don't really know what we do with this, it's
not a piece of code I'm familiar with).
> KRecentFileAction ==> convert to QAction too? I assume so.
I have recent-files handling classes from Sonic Visualiser that work
fine in Qt4; why don't I pull those in? Shouldn't be much work.
Shall I put that on my list?
> how / where to set (replace) global variables that are requested like:
> kapp->checkRecoverFile(filename, canRecover);
> ( does not exist for qApp )
Don't know. Probably the best bet is to reimplement these, even if it
means effectively copying and pasting from KApplication.
> KTmpStatusMessages ==> use statusbar ? disable ?
Use statusBar()->showMessage(...), I think? KTmpStatusMsg is our own
class (in gui/kdeext directory), so we can do whatever we like within
However, many of the status messages (generally the ones showing
progress of things, which basically means practically all occurrences
of KTmpStatusMsg) are entirely useless and could be removed handily.
Shout if you disagree, anybody, but I don't recall them ever having
told me anything useful.
The useful ones are the tool help messages (slotToolHelpChanged in
MatrixView and CompositionView). We want to make sure they work.