Re: Abiword in Evolution. (fwd)

From: Martin Sevior (msevior@mccubbin.ph.unimelb.edu.au)
Date: Fri May 03 2002 - 02:20:57 EDT

  • Next message: Jesper Skov: "Re: Houston, we have a problem."

    On Thu, 2 May 2002, Dom Lachowicz wrote:

    > > Wow this is really cool. I've just been thinking
    > > about using AbiWord in an email context though.
    > > We don't usually want to write emails in .abw format
    > > right - we all hate Word, HTML and rich text emails.
    > > The AbiWidget needs a method to set its default file
    > > format which in this case should be Plain Text.
    > > It is possible to write emails in lots of text
    > > encodings for emails and there are standards for this
    > > that I bet Evolution supports. So it might even be
    > > good to be able to save as Encoded Text and set the
    > > encoding from the AbiWidget.
    > >
    > > Another 2 cents worth of Andrew's i18n ramblings (:
    >
    > Hi Andrew,
    >
    > The Bonobo control and the AbiWidget can be used for both editing and
    > creating new documents, as well as viewing existing ones. The current
    > AbiWord editing frame (the white document) is actually one of these
    > AbiWidgets.
    >
    > So it would be possible to use AbiWord as Evolution's composer. We'll
    > want to get some things in place first though:
    >
    > 1) Toolbar and menu merging
    > 2) A decent file saving API from these controls
    >
    > Once we get both done (and I contend that #1 is just as important as
    > your #2), we'll be able to fill this role. You'll be able to do some
    > *quite impressive* HTML emails inside of evolution, since Abi is so
    > well-featured. It will be even better once we support tables. And you'll
    > be able to handle text and text encodings too.
    >
    > This is all on my TODO list once Martin commits his next round of
    > AbiWidget/Bonobo Control stuff. NB is the fact that AbiWord might be too
    > "heavyweight" for an email editing control (they currently use GtkHTML),
    > but this is Evolution we're talking about. RAM YUMMY! CPU TASTY!
    >

    Right! Regarding both these, Bonobo has interfaces building menus (and I
    think) toolbars from XML files defining ui properties. Given that our
    menus and toolbars are also defined in text file, this should be possible
    by mapping our menu and toolbar definitions to bonobo's.

    The Bonobo save interface is a part of the "persist stream" and "persist
    file" interfaces. These can be implemented by actually coding a callback
    for this call.

            stream = bonobo_persist_stream_new (load_document_from_stream,
    NULL, NULL, pstream_get_content_types, abiwidget);

    In place of one of the NULL's. Implementing bonbo interfaces is simply a
    matter of creating new bonobo objects (in this case by a call to
    bonobo_persist_stream_new(....) and aggregating them with...

            bonobo_object_add_interface (BONOBO_OBJECT (to_aggregate),
    BONOBO_OBJECT (stream));

    calls.

    Tne you just make sure the interface is defined the oaf file.

    I'll leave the Evolution replacement editor to you Dom :-)

    I'll do a Nautilus view for abiword next :-)

    Cheers

    Martin



    This archive was generated by hypermail 2.1.4 : Fri May 03 2002 - 02:23:17 EDT