Re: [Evolution-hackers] invoking composer via bonobo...
- From: Karl Pitrich <pit root at>
- To: Not Zed <notzed ximian com>
- Cc: evolution-hackers lists ximian com
- Subject: Re: [Evolution-hackers] invoking composer via bonobo...
- Date: 23 Jul 2003 10:13:42 +0200
On Tue, 2003-07-22 at 18:45, Not Zed wrote:
> On Wed, 2003-07-23 at 02:23, Karl Pitrich wrote:
> > On Tue, 2003-07-22 at 18:40, David Woodhouse wrote:
> > > On Tue, 2003-07-22 at 12:28, Karl Pitrich wrote:
> > > >
> > > > i found composer.c (by miguel) in some old cvs somewhere,
> > > > and am trying to make it work with evolution 1.4.
> > >
> > > P'raps I'm being dim -- it's not entirely unheard of... but what does
> > > this do that isn't also achieved by
> > >
> > > evolution-1.4 "mailto:address example com&subject=Fish&cc=pit root at
> >
> > well, i need to make a mozilla plugin, providing a JavaScript
> > LiveConnect object that interfaces to evolution.
> >
> > the main problem is, "mailto:..." cannot add attachments or set
> > the body content type.
>
> You can actually set attachments, not sure about the content-type thing,
> or setting the body content.
>
> I think you use a parameter like: attach=filename (or gnomevfs uri)
>
> If you're just going to exec a program anyway you should probably use
> that, and additional parameters could be added I guess.
>
> If you want a programmatic interface, then thats another issue ...
it's a lot more complicated. for instance, the document to be attached
needs to be retrieved via webdav and locked via soap.
>
> Are you saying show_composer works, but setting any headers doesn't? Or
> does nothing work?
right, Composer_show() works, setHeaders, setBody do not work they
segfault.
>
> Actually the composer is part of the mailer, which is a shlib object, so
> you can't really instantiate it outside of the shell anyway. Otherwise
> you'll get another copy, which could interfere with the existing copy in
> nasty (tho probably non data-destroying) ways.
why other copy? can't i just open a new composer window from an existing
evolution instance and fill in the fields?
thats what the mailto: does, i guess...
> So I think the 'current way' is to get hold of the shell (or mail
> component?) object and do a 'send to url' method, which is for all
> intents exactly the same as exec'ing evolution with the url.
so i have to instate a shell object via bonobo?
thanks,
/ karl
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]