--nextPart2226636.scDFKGXdec
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Tuesday, November 2, 2010, John Layt wrote:
> Aye, it is something I really need to document properly, where Qt falls
> short, where we fall short, etc.  At the moment it's just knocking around
> my head. For big stuff like that, a wiki might work OK.

a wiki could work, with some discipline, though there are F/OSS web apps ou=
t=20
there that provide a built in work flow. Suse's openFate for one and whatev=
er=20
it is that Canonical uses for their task proposals (part of launchpad?) for=
=20
another.

> Documenting what each class adds to the Qt equivalent could also be
> valuable to figure out more concrete proposals too, and I don't just mean
> in a wiki which could quickly get stale, but right in the classes
> themselves.=20

per-class notes is a bit more fine-grained than what i was thinking. for=20
something like the KComboBox example you provided, that might be part of a=
=20
larger "identify widget class in libkdeui that are candidates for merging w=
ith=20
Qt" and it could contain a list of those widgets, brief summary of target=20
funcdtionality and the rest could, as you note, go into the apidox.

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks

--nextPart2226636.scDFKGXdec
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEABECAAYFAkzQnUIACgkQ1rcusafx20MT5QCeP0GgB5YJBDR2dc0T+ysx55WJ
E6cAn2LmNkcfWgbtGvPPV3zu3boo1Aof
=cdUY
-----END PGP SIGNATURE-----

--nextPart2226636.scDFKGXdec--