On Sun, Sep 7, 2008 at 6:39 PM, D. Michael McIntyre <[EMAIL PROTECTED]> wrote: > It looks like this is a good case for cutting out KDE entirely, and going with > a QT solution. Rewrite the widget as a local Rosegarden widget in QT? Any > thoughts from Chris in particular on this?
Not hard to do. The existing code is basically a self-contained Qt3 widget (obscure KDE headers notwithstanding). Porting it to a self-contained Qt4 widget is fiddly but straightforward. However, there's no need -- it's already been done. This class originated in the kdeui library as an un-anti-aliased LED widget. I pulled it into RG and modified it to introduce anti-aliasing (in a very crude way -- drawing it at three times the size and then scaling it down). Guillaume then pushed the changes back to KDE. That was four years ago, so any moderately recent version of KLed is actually the same as our own version anyway. And this carries through to KDE4: http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/widgets/kled.cpp?view=markup My changes are definitely still there, in their full unfettered crudeness (no copyright note for me though -- perhaps I should sue someone). So we could either just use the standard KLed, or avoid the KDE library dependency by updating our own KLed class from the KDE4 repository. Any preference? Chris ------------------------------------------------------------------------- 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
