Re: NautilusView lifecycle

No, it's not exactly. It is a wrapper API for creating bonobo controls
that use this defined interface. Components that use this wrapper API
are not embeddable in applications other than Nautilus. This somewhat
defeats the purpose of component systems. I would like to see the
wrapper API go away. A NautilusView can be implemented without using
the wrapper API and libnautilus, yes, but oftentimes, are not.

-- dobey

On Sat, 2002-12-28 at 11:33, James Willcox wrote:
> NautilusView is what you describe.  It is a bonobo control, with a
> defined interface for doing the extra stuff needed (like the throbber,
> navigation, etc).  When you embed a regular bonobo control in nautilus
> that also implements PersistFile or something (like eog), you don't
> get the throbber stuff (IIRC).  How is what you want different from
> this?
> Thanks,
> James

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]