Re: bonobo question - what parts should be bonobo?

"Gustavo J. A. M. " Carneiro <[email protected]>
Newsgroups gmane.comp.gnome.components
Organization INESC Porto
Message-ID <[email protected]>
On Sex, 2003-02-28 at 12:11, Ronald Bultje wrote:
> Hey,
> 
> I'm doing a GStreamer-based project which should one day become a great
> video recorder app. I want to use layering here, so some parts are
> gstreamer plugins, one part should become a bonobo element as well. Now
> my question is about what people normally make bonobo components.
> Basically, the app can be really small, see
> http://www.gstreamer.net/apps/gst-rec/gst-rec-new.png for a screenshot.
> Possibly bonobo'izeable widgets around here: a tv widget (it's gray
> here, but that's because my laptop doesn't have a TV card), a
> preferences screen (where things like capture format, audio codec, video
> codec, audio and video source settings are located) and a control screen
> (where audio volume, video image (brightness etc.) and video channel can
> be changed).

  As Michael said in this list some time ago, widget-level embedding
with bonobo is not recommended.  For one thing, mnemonic activation of
bonobo widgets doesn't work, as I discovered some time ago.

> 
> The question is, what parts here would normally become bonobo
> components? I could make the preferences screen, control screen and TV
> widget a bonobo component, but is that a wise idea? I could also make
> the TV widget a bonobo component and make everything else properties of
> this component (so that the bonobo client needs to implement all GUI
> stuff for this), or make the widgets inside the control screen bonobo
> components on themselves... What do normal people do here? How far
> should I go here?

  Some people wouldn't call me 'normal', :) but a good a example to look
at would be eog.
  Looking at the screenshot, I would say that everything except the menu
bar, tool bar and status bar should be a single bonobo control.  You
would also export the toolbar items and menu layout in a bonobo ui xml
file (read by the component, not the shell). The preferences dialog too
would be in the component factory, invoked by some menu item.

> 
> (The idea is that other GStreamer applications, like Wim's gnonlin NLE,
> can call gst-rec's video-recording function via bonobo, and maybe
> there's other weird people out there that would want to use gst-rec for
> some weird reason).
> 
> Also, related to this, is it normal for applications that call a
> bonobo-component to keep their own configuration of this component, or
> should the configuration be inside the bonobo component? I.e., should I
> use GConf in the component or in the application part?

  I don't have any strong opinion in this matter, but I would say that
using GConf directly in the component is fine.

> 
> Thanks for any help,
> 
> Ronald
> 
> [please CC me, I'm not subscribed]
-- 
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.