Hei,

this is just how i see it from what i've gathered in the discussions and
the statements to be found in different locations on the web:

On Tue, 2007-04-17 at 23:43 +0100, Chris Monahan wrote:
> In the case of integrating a Mozilla and an OpenOffice application
> what would that mean for the respective underlying frameworks (NSPR
> and UNO)

I'd say those frameworks will only need slight adjustments, if at all.

> I mean will they begin to merge, or form an extensive bridge between?
> or is it possible to ignore the underlying frameworks and just mash up
> some bindings? (and what would be the best thing  for it?)

Neither. From how i get it, the plan is to have OOo as is and then have
Thunderbird/Lightning as is (that is, as if the other one wouldn't exist
- almost). Both products extension APIs supposedly are already flexible
enough to do whatever integration is needed.

Integration would then be done by writing extensions for both OOo and
Thunderbird/Lightning.

> Consider, if openoffice and thunderbird were to be integrated, what
> about widgeting? Would OpenOffice be able to use Mozilla widgets, or
> should it be the otherway round, or both?

Nope. It would be more like...when in OOo you'd have OOo widgets, when
in Thunderbird, you'd have xul widgets. Imaginably, there might be ways
to trigger a Thunderbird extension from OOo, so you could possibly
launch an xul window from within OOo, but the xul window would still be
running within Thunderbird.

> Consider, would we be able to open Thunderbird from openoffice? or
> edit mail in openoffice from thunderbird?

Just launching an application isn't a big deal at all.

> I ask partly since this thread is referring to MS Office 2007 outlook,
> and that has extensive integration, so in one sense the question is,
> how /integrated/ is 'integrated'?

Simply look at what current extensions for both applications can do.
Both extension APIs are extremely flexible and powerful.

André.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to