Re: Generic Embeddable plugins.

On Sat, 2005-01-15 at 09:45 +1100, msevior@physics.unimelb.edu.au wrote:
> Hi Dom and Jean,
> I've thought about most of your points for sometime.
>
> Dom, the one thing I don't have a solution for is scroll-bars in the
> embedded object. However in the case of Word Processing document, I think
> scroll bars are not wanted. I would rather increase the size of the object
> and relayout.
>

Erm, the component itself would add its own scrollbars. AbiWord has
nothing to do with it.

> The UI I'm suggesting for this round is extremely simple. The external
> program is fork/exec'd with the data used by AbiWord to draw the component.
> Like our AbiGimp plugin. So I imagine Gnumeric firing up with the contents
> loaded. On every save from Gnumeric the image displayed in AbiWord is
> updated.

OK, so you are definately not talking about a Component architecture
here. See my mail titled "Generic Embeddable plugins - Take 2"

AbiGimp has nothing to do with embedding as far as I can see.

[snip]

> My vision is to relayout every time the user presses "save" in the
> external application. We simply stat the filename we pass to the
> program and relayout every time the file changes.

Won't work if there is no file involved.

Anyway, I think this discussion would be a lot clearer if the definition
of "embedding" was stated, as I think martin has a totally different
idea of what he wants to achieve than, say, Dom and Juan.

Bye!
  Marc
Received on Sat Jan 15 01:04:04 2005