--nextPart1327408.UI8FFOts5g
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 uirt=
k=20
as it is still called. Will be renamed, when we move it to kdesdk).


Just install kdenonbeta/uirtk/ and run=20
  kuiextractor yourApplication=20
(kuiextractor just calls "LD_PRELOAD=3Dlibkuiextractor.so yourApplication")=
, and=20
you can extract widgets/dialogs by Ctrl+Shift+Alt and a double-click with t=
he=20
right mouse button on the widget. Currently, there's one bug in there, wher=
e=20
the top-level widget gets assigned the wrong class name, so extracting a=20
KCModule will create a top-level widget of class KCModule instead of QWidge=
t=20
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 (se=
e=20
the TODO file). Also, there might be a few layout levels too much (I extrac=
t=20
what's really there, not how it might be done simpler), which might be=20
simplified in designer later on.=20

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

Cheers,
Reinhold

--nextPart1327408.UI8FFOts5g
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBRLC4TqjEwhXvPN0RAvdpAJ0QRYcIw1PajgFbutehsBI7W5fFwQCfZVSu
Y4BUoYugBXZsIzpoAXcGrI4=
=Y6VU
-----END PGP SIGNATURE-----

--nextPart1327408.UI8FFOts5g--