--nextPart1884950.zThHrfL5T9
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 16 November 2006 11:22, Lubos Lunak wrote:
>  Actually the real reason for the KWin/KWinModule split is that KWin has
> only static's while you need an instance of KWinModule (and so it can tra=
ck
> changes and so on). And the static's could simply move into KWinModule or
> whatever you call it.

yes, i understood that. from the perspective of someone who uses these=20
classes, though, the semantic separation between "information on a=20
window", "controlling aspects of a single window" and "information about al=
l=20
windows/desktops information" is really clear.

>  KDesktopInfo being current KWinModule, i.e. the class that also has sign=
al
> windowChanged( id, how ) ?

yes.

> I myself don't see any need to separate it this=20
> way, I think just having KWindowManager (or KDesktopManager or whatever)
> and its WindowInfo class should do.

and then we have a class that is used to both control aspects of a given=20
window as well as get information on desktops and all windows, which is a=20
quite a number of concepts in one class. i personally prefer classes with=20
clear, singular purposes. *shrug*

i wonder what others think =3D)

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

=46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com)

--nextPart1884950.zThHrfL5T9
Content-Type: application/pgp-signature

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

iD8DBQBFXLy51rcusafx20MRAswlAJsEasU1VrXsalDyLRmQIeos+9FoHACdFeQB
oh1UkFg7yu/rqI1J+yjld8k=
=4taJ
-----END PGP SIGNATURE-----

--nextPart1884950.zThHrfL5T9--