Re: [sigc] Re: [gtkmm] Bringing Bonobo to the masses :)
- From: Andreas Rottmann <a rottmann gmx at>
- To: ERDI Gergo <cactus cactus rulez org>
- Cc: Andreas Rottmann <a rottmann gmx at>, Chris Kuklewicz <chrisk mit edu>, gnome-components-list gnome org, GTK-- Mailing List <gtkmm-main lists sourceforge net>, jean de ratuld quadratec fr, GNOME hackers <gnome-hackers nuclecu unam mx>, SigC++ Mailing List <libsigc-mlist lists sourceforge net>
- Subject: Re: [sigc] Re: [gtkmm] Bringing Bonobo to the masses :)
- Date: 14 Sep 2000 22:45:16 +0200
ERDI Gergo <cactus cactus rulez org> writes:
> On 14 Sep 2000, Andreas Rottmann wrote:
>
> > ERDI Gergo <cactus cactus rulez org> writes:
> >
> > > Bonobo-- will use Gtk--, so it will depend on libsigc++ anyway.
> > >
> > Yes, but isn't Bonobo something widget-set independent (with default
> > to GNOME widgets, of course)? I strongly vote for seperating the
> > GUI-dependent stuff into its own shlib, or whatever.
>
> This is something the Bonobo-- developers will have to decide on. If we
> want to wrap Bonobo implementations consistent with gnomemm (which is the
> whole point), we will have to depend on gtkmm. You could separate a bonobo
> implementation into non-X-specific and X-specific parts (the later
> implementing stuff like Bonobo::Control or Bonobo::UIHandler), but for
> bonobomm this wouldn't make sense since when you use Gtk::Object, you
> already depend on gtkmm, which in turn depends on gtk+.
>
I see - I better had taken a closer look ;-). Can't we push the gtk+
people to seperate their sig/slot/object thingy out into a seperate
library, maybe even into glib? (this could be done keeping both source
and binary compatibility IMHO)?
Even if they don't: Whoever is making that decision: I beg: no mor
GUI/X deps than _absolutly_ necessary.
MfG, Andi
--
Andreas Rottmann | Dru ICQ | 54523380 ICQ | a rottmann gmx at
Pfeilgasse 4-6/725 | A-1080 Wien | Austria | Europe
http://www.8ung.at/rotty | GnuPG Key: www.8ung.at/rotty/dru.asc
Fingerprint | 3E9A C485 49A4 1D17 2EA7 2BA7 22AE C9BF 8173 6279
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]