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

List:       kmail-devel
Subject:    Re: [PATCH] UI abstraction proposal (partially only)
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2003-06-03 7:45:50
[Download RAW message or body]

On Tuesday 03 June 2003 00:36, Zack Rusin wrote:
> On Tuesday 03 June 2003 00:00, Andreas Gungl wrote:
> > attached you find a diff containing a first idea on how to separate
> > the UI code from the processing code. It covers only the address
> > book access in KMail.
> > I formed an abstract class for the UI callbacks, then I inherited a
> > class covering the current Gui interactions.
>
> Hi, well this is probably the most desired of our goals for the
> not-so-near future, but definitely not the way you're doing it. The
> way you're doing it, has pretty much no appeal as the gui is still a
> compile time dependency therefore nothing changes except the fact
> that there's another level of method calls.

With changes like the ones from Andreas you are free to choose, if you 
make the gui a compile-time or a run-time dependency. By using an 
abstract class interface to access the GUI you can move a concrete GUI 
implementation into a module loaded at run-time.

> The patch you presented gain us nothing. The idea is that we need to
> seperate core from gui but not as a compile option, but a run-time
> one. Meaning one core is running and you can have twenty gui's for it
> running. One in a terminal, one in a remote X session, one in a local
> X session etc.

Really? I don't think it gains us much being able to run twenty KMail 
GUIs for the same core. I would be much more interested in a KMail core 
which can be used by other applications to handle mails without the 
need to run the KMail GUI. To abstract interaction of the core and the 
GUI, like the patch from Andreas intended to do, seems just the right 
way to achieve that.

-- 
Cornelius Schumacher <schumacher@kde.org>
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]