[Kde-bindings] Splitting up the SMOKE library

Arno Rehn arno at arnorehn.de
Tue Jul 17 10:07:17 UTC 2007


Am Dienstag, 17. Juli 2007 schrieb Ashley Winters:
> --- Thomas Moenicke <tm at php-qt.org> wrote:
> > The kalyptus generator should generate the qt_Smoke instance in
> > smokedata.cpp only for the Qt smoke, for KDE smoke it should have
> > a kde_Smoke instance which has a pointer to qt_Smoke. In case the
> > inline methods of kde_Smoke don't find the index they can ask the
> > qt_Smoke before it returns 0.
> > Thus we can create a hierarchy of dependencies and don't need to
> > touch too much in the implementations:
> >
> > + qt_Smoke
> > +--+ qwt_Smoke
> > +--+ kde_Smoke
> >     +--+ whatever_in_kde_Smoke
> > +--+ qscintilla_Smoke
> >
> > I think this way would follow the design currently implemented in the
> >
> > bindings, but i would like to hear the opinion of Ashley though.
>
> Yeah, a single-inheritance hierarchy should work. You first search your
> "local" copy of smoke, and if something's missing you forward the
> search to your parent.
Actually I designed my current code with a multiple inheritance hierachy in 
mind. So this should be also possible:

         qt_smoke
       /                  \
kde_smoke  qscintilla_smoke
       \                  /
   whatever_smoke

-- 
Arno Rehn
arno at arnorehn.de



More information about the Kde-bindings mailing list