--qlTNgmc+xy1dBmNv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


[Crossposted to kde-look]

On Mon, Mar 12, 2001 at 10:07:39PM +0100, Richard Stevens wrote:


>> I think SDI is still the preffered way. Toplevel MDI is broken by design
>> IMO.=20

>I really don't understand why many KDE-Developers are agains MDI but I'd l=
ike=20
>to understand. Is there some document covering the reasons for not having =
MDI=20
>in KDE? Maybe somebody remembers, where to look in the mailinglistarchive.=
 I=20
>heard it has been discussed heavily in the past.

And KDE applications in the core should follow the style guide. It explicit=
ly
states that KDE is SDI-only:
http://developer.kde.org/documentation/standards/kde/style/basics/windows.h=
tml

The main reason: The KDE offers a way to switch between sevberal instances =
of
programs: kicker including taskbars and so on. This is the accepted way.
That way a user has to learn one way to switch between documents, programs =
and
so on. Not one way for every application. Consistency!

Only exceptionally should you introduce another way to adress several insta=
nces
of a program. A good example: konsole.

Not having used kant, I can not judge if MDI makes sense for it.


BTW: "Stacking" several instances of an app in a single kicker taskbar inst=
ance
(like Windows XP seems to do) would make MDI even more silly.


>> With a more general MDI solution, applications should default to SDI with
>> an configration option to enable MDI mode. That way the application can
>> dump a bunch of its menu-entries when running SDI, making it less heavy
>> handed and overwhelming for new users.

I like that approach. SDI =3D Default, MDI only for the people who like it =
and
find the configuration option.

>Can't resist. Most of them will come from Windows and know MDI anyways ;)

Yes, right and fuck stability of KDE as well, they are not used to anything=
 better.

--=20
Moritz Moeller-Herrmann ICQ #3585990

--qlTNgmc+xy1dBmNv
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Weitere Infos: siehe http://www.gnupg.org

iD8DBQE6rT+5zPDJgxvnSxERAq5uAJ9JwDuMBAHJIWO1ay68BCosZUHnRACgl6q6
XKmZtXXKoAGnv1fsGhaxjSo=
=GODy
-----END PGP SIGNATURE-----

--qlTNgmc+xy1dBmNv--