On Tue, 13 Mar 2018 at 14:37:53 +, David Woodhouse wrote:
> My concern was that I didn't want to just invoke Evolution — users
> might be using something different. But of course doing it through
> xdg-open resolves that.
If you are using a platform/runtime library like GLib or Qt (presumably
On Tue, 2018-03-13 at 13:38 +, Corentin Noël wrote:
> I wonder why is a D-Bus interface even required here. The simplest
> solution (and already working one) is to just pass an ical file to the
> calendar app with xdg-open.
Yeah... that might work. In fact Milan implemented that for Evolution
Le mardi 13 mars 2018 à 13:30 +, Simon McVittie a écrit :
> On Tue, 13 Mar 2018 at 13:11:45 +, David Woodhouse wrote:
> > We need to spawn a "new meeting" editor in the client of the user's
> > choice, pre-populated with meeting dial-in information, conference-
> > specific attendees, etc.
On Tue, 2018-03-13 at 13:11 +, David Woodhouse wrote:
> As part of a conference protocol plugin for Pidgin (like the one for
> Lync), we have the ability to create meetings.
>
> We need to spawn a "new meeting" editor in the client of the user's
> choice, pre-populated with meeting dial-in
I have a very limited knowledge in this field, but I would like
to point out that in Thunderbird such task is performed by
messages with attached ical files. So, why not to base meeting
creation on opening ical (existing standard) data (as a file, for
example)?
On Tue, 13 Mar 2018 at 13:11:45 +, David Woodhouse wrote:
> We need to spawn a "new meeting" editor in the client of the user's
> choice, pre-populated with meeting dial-in information, conference-
> specific attendees, etc.
Rather than inventing a small subset of iCalendar encoded into
D-Bus
As part of a conference protocol plugin for Pidgin (like the one for
Lync), we have the ability to create meetings.
We need to spawn a "new meeting" editor in the client of the user's
choice, pre-populated with meeting dial-in information, conference-
specific attendees, etc.
I've implemented a
