Re: GEP 9: merging bonobo-activation & libbonobo

"Gustavo J. A. M. " Carneiro <[email protected]>
Newsgroups gmane.comp.gnome.desktop,gmane.comp.gnome.components
Organization INESC Porto
Message-ID <[email protected]>
On Qua, 2003-03-12 at 20:35, Mark McLoughlin wrote:
> Hi Michael,
> 
> On Thu, 2003-03-13 at 03:09, Michael Meeks wrote:
> > Hi guys,
> > 
> > 	I've added a new GEP to propose this; it's short enough for lightening
> > reading:
> > 
> > 	http://developer.gnome.org/gep/gep-9.html
> > 
> > 	Comments welcome,
> 
> 	I think it would be worthwhile to cc this to another list. There would
> be a lot of people with opinions on this but not on
> gnome-components-list. I've cc-ed desktop-devel-list.
> 
> 	You say "two seperate modules creates more problems than it solves".
> The two problems that you give are "packaging is hard" and "I want to
> use BonoboObject. Are there no other problems ?
> 
> 	I'm not sure either of these or really good reaons for merging the two

  I think they're powerful reasons...

> and thus forcing people to use libbonobo where they may just want
> bonobo-activation. But then again, bonobo-activation hasn't seen much
> use without libbonobo.

  I don't see what would be the problem in using libbonobo.  With both
packages merged, existing projects using bonobo-activation only would
sill be linking to one library only, that just happens to have a bit
more code.  With libbonobo already widely used as shared library, there
is almost no cost.  And think of the benefits of linking to one less
library in all gnome programs.

> 
> 	FWIW, the GObject adaptor would provide a solution to the "I want to
> use BonoboObject part". Granted its not finished, but I'm willing to do
> the last bit of work required ...

  Can you tell me what this "GObject adaptor" is?  I don't have a
clue...


  Regards.
-- 
Gustavo João Alves Marques Carneiro
<[email protected]> <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.