Re: Invoke "Quick Event" from external application via parameter or DBus?

To be honest I have shared the idea in the very moment it came to my mind, so I have not yet made my mind up about details.

I am not even sure if a return value is of necessity, especially for an early implementation. For me as a user a simple libnotify message with the event details would be sufficient for having a quick glance and checking if it has been interpreted correctly. It may contain an "Edit" button for opening the event editing dialog.

What do you think about that approach?

California uses EDS as storage backend, right? I have no knowledge in that field, but guess that EDS somehow indexes its data sets. Maybe a simple index to the resulting EDS entry would be fine, so developers can query EDS themselves, if they really need access to the underlying data.


On Fr, Okt 10, 2014 at 9:55 , Jim Nelson <jim yorba org> wrote:
I would like to write a plugin for the "Kupfer" command launcher to add an event to California via the "Quick Event Syntax". Is there a way to pass such a string to california and maybe even get some sort of return value, like information about of how the string has been interpreted and the fields have been matched?

I am thinking of a command line parameter or some kind of DBus API call.
If not, I suppose that this would make a valuable addition, as the "Quick Event" functionality is imho predestined for being called by external applications.

I think that's a great idea.  There's no such faculty today for this, but I could imagine a couple of ways to do it.

What kind of information were you thinking would be returned?  Quick Add creates a pretty complicated data structure.  What elements of it do you think should be returned, and in what format should they be returned?

-- Jim

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]