From: Dom Lachowicz (firstname.lastname@example.org)
Date: Tue May 07 2002 - 09:50:18 EDT
On Tue, 2002-05-07 at 08:04, Martin Sevior wrote:
> On Tue, 7 May 2002, Christian Biesinger wrote:
> > On Tue, May 07, 2002 at 06:44:14PM +1000, Martin Sevior wrote:
> > > Ok this is the basics of a nautilus viewer for abiword. It doesn't work
> > > yet but I'm hoping that Dom or others can finish it.
> > Hm? Do Bonobo controls need a new implementation for every app which uses
> > them, or why is this needed?
> > Or did I misunderstand something?
Bonobo controls don't need a new implementation for every app which uses
them. However, different apps have different requirements for the
different types of controls they accept.
For example, Gnumeric may only support controls that are capable of:
loading/persisting itself to a stream (Bonobo/Persist*:1.0)
printing itself inside of a given rectangle (Bonobo/Print:1.0)
being embedded (Bonobo/Embeddable:1.0)
Now if you want your control to work inside of Gnumeric, you'll need to
implement & support those interfaces. You can probably plainly see why
gnumeric has those restrictions on its controls, what with it being a
printable, savable spreadsheet. An application like Evolution may have
similar requirements of its controls.
Nautilus, however, baffles me. It should need nothing more than the
Embeddable and Persist interfaces. Using Persist, it can load an object
from disk. Using Embeddable, it can either embed the object inside of
its main frame, or embed it in a toplevel window, take a screenshot, and
embed the PNG representation of your document instead. The reasons why
Nautilus does not do either of these are beyond me. So if we want to do
Abi previews inside of Nautilus, we have to conform to what Nautilus
wants, no matter how insane we think its requirements are.
This archive was generated by hypermail 2.1.4 : Tue May 07 2002 - 09:53:32 EDT