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

List:       kde-core-devel
Subject:    Re: Can we drop KWrite ?
From:       Simon Hausmann <sh () caldera ! de>
Date:       2001-03-13 10:05:28
[Download RAW message or body]

On Tue, Mar 13, 2001 at 10:48:57AM +0100, Ralf Nolden wrote:
> Simon Hausmann wrote:
> > 
> > On Tue, Mar 13, 2001 at 10:33:14AM +0100, Ralf Nolden wrote:
> > > Torsten Rahn wrote:
> > > >
> > > > On Tuesday 13 March 2001 02:27, Neil Stevens wrote:
> > > > > Multiple desktops + Controlled SDI provide a reasonable enough simulation
> > > > > of MDI, that forcing single-document windows are a far smaller hardship to
> > > > > MDI users, than MDI apps are to SDI users.
> > > >
> > > Erm... I didn't follow this discussion too close but obviously (which is
> > > bugging me myself since *years* in KDE/Qt) we don't have a Document
> > > interface. Therefore I for example or anyone else has to "emulate" the
> > > CDocument structure of the MFC to get a reasonable Document-View model
> > > by inheriting from QObject to make an app-specific document class. You
> > > could argue that KOffice apps have a document-centric structure but that
> > > isn't all. What's lacking anyway is a base class like KDocument to
> > > provide standard methods so one can tie a QWidget inherited class to it.
> > > An example is QMulitLineEdit that does it's own writing/reading *inside*
> > > the widget code which makes it impossible to use in an MDI app or a
> > > multi-window SDI-like app (toplevel MDI).
> > 
> > What you describe is kparts? :-)
> 
> Still not everyone is using kparts ;-) And e.g. Qt-only apps don't use
> kparts either. 
 
What does a KDocument class help for Qt-only apps then? ;-)

Bye,
 Simon

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