[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: kdenonbeta/uirtk
From:       Reinhold Kainhofer <reinhold () kainhofer ! com>
Date:       2004-09-12 20:25:11
Message-ID: 200409122225.28392.reinhold () kainhofer ! com
[Download RAW message or body]


On Sunday 12 September 2004 22:07, Frans Englich wrote:
> On Sunday 12 September 2004 19:57, Reinhold Kainhofer wrote:
> > CVS commit by kainhofe:
> >
> > Don't use K* widgets/windows as base class. Will lock up designer...
>
> Let me get this straight.. Does the existence of uirtk mean Designer files
> for about 50 KControl modules can be created in an afternoon?

Yes, more or less. Modulo the time to fix the bugs in kuiextractor (or uirtk 
as it is still called. Will be renamed, when we move it to kdesdk).


Just install kdenonbeta/uirtk/ and run 
  kuiextractor yourApplication 
(kuiextractor just calls "LD_PRELOAD=libkuiextractor.so yourApplication"), and 
you can extract widgets/dialogs by Ctrl+Shift+Alt and a double-click with the 
right mouse button on the widget. Currently, there's one bug in there, where 
the top-level widget gets assigned the wrong class name, so extracting a 
KCModule will create a top-level widget of class KCModule instead of QWidget 
or QDialog. I don't know when I will find the time to fix this.
See the README file.

There are still some shortcomings, which I haven't yet been able to fix (see 
the TODO file). Also, there might be a few layout levels too much (I extract 
what's really there, not how it might be done simpler), which might be 
simplified in designer later on. 

Also note that I wrote this mainly to help usability people to play around 
with dialogs that are created by c++ code, so the .ui files might have to be 
simplified to be usable in a KDE application.

Cheers,
Reinhold

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]