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

List:       kde-devel
Subject:    Re: KApplication design
From:       Sirtaj Singh Kang <ssk () physics ! unimelb ! edu ! au>
Date:       1999-03-08 12:59:53
[Download RAW message or body]


On Fri, 5 Mar 1999, Steffen Hansen wrote:
[snip]
> A possible solution is to use multiple inheritance. Some people think that
> MI should never be used, but in this case i find it a neat solution:
> 
>               KApplicationBase
>             /         |           \                
>        KI18NApp KStdOptionPaserApp KConfigApp        QApplication
>            \          |                    \        /
>             \	      |                KSessionManagedApp
>              ---\     |   /------------/
> 		KApplication

Just looking for clarification: are you sure that MI is a good way to do
this? Wouldn't it be easier just to create a wrapper class that provides
accessors for each feature required? 

-Taj, who is easily scared by MI :)

Sirtaj S. Kang       taj@kde.org         ssk@physics.unimelb.edu.au
School of Physics    Univ of Melbourne   KDE: The Desktop sans Toga

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