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

List:       kde-core-devel
Subject:    RE: QextMDI -> KDE ?
From:       Reginald Stadlbauer <reggie () troll ! no>
Date:       1999-11-11 13:22:18
[Download RAW message or body]

On Thu, 11 Nov 1999, David Faure wrote:
>> -----Original Message-----
>> From: Bo Thorsen [mailto:gobo@imada.sdu.dk]
>> Sent: Thursday, November 11, 1999 1:15 PM
>> To: kde-core-devel@kde.org
>> Subject: Re: QextMDI -> KDE ?
>> 
>> 
>> On Wed, 10 Nov 1999, Falk Brettschneider wrote:
>> 
>> > Hi,
>> > 
>> > Is it possible to place QextMDI in the KDE widget classes tree? 
>> > So it would be possible that people can use it without 
>> making a copy of
>> > it in their own project (like currently KDevelop-snapshot does).
>> > There is just one rub in it: QextMDI is only permitted to 
>> depend on Qt.
>> > It has to be portable in the same way as Qt.
>> 
>> This has been discussed a number of times with the same 
>> conclusion: MDI is a windows thing and should therefore not be a part of
>kde.
>
>Even more : it's a bad OLD windows thing. Even windows drops it
>(I cited Word 2000 earlier on). MDI is very confusing for users. 
>Which is why they removed it, and which is why we don't use it either. 
>But yes, it can be considered convenient for developers, which is why 
>they kept it for Visual Blah tools, and which is why kdevelop uses it.
>Although I'm personnally happy with the non-MDI XEmacs :)

But if you split the canvas in XEmacs you have also something which is not too
different from MDI :-))

-- 
Reggie

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