aboutsummaryrefslogtreecommitdiff
path: root/libmessaging-menu/messaging-menu-app.c
Commit message (Collapse)AuthorAgeFilesLines
* libmessaging-menu: fix section link in the documentation and add ↵Lars Uebernickel2014-11-031-1/+1
|\ | | | | | | | | | | descriptions Fixes: 1313561 Approved by: Ted Gould
| * libmessaging-menu: fix section link in the documentation and add descriptionsLars Uebernickel2014-04-281-1/+1
| |
* | libmessaging-menu: allow numbers in object pathsLars Uebernickel2014-10-231-1/+1
|/
* Use serialized icons for messages and sourcesLars Uebernickel2013-09-051-13/+18
| | | | | The D-Bus protocol is not part of the public API, so it's okay to change it.
* Merge from trunkTed Gould2013-08-131-0/+4
|
* Remove variant wrapper from 'parameter' argument of the "activate" signal.Lars Uebernickel2012-12-171-1/+4
|\ | | | | | | Approved by Gustavo Pichorim Boiko, PS Jenkins bot.
| * Remove variant wrapper from 'parameter' argument of the "activate" signalLars Uebernickel2012-12-111-1/+4
| |
* | Make messaging_menu_app_remove_message() work for messages with a ref count of 1Lars Uebernickel2012-12-141-0/+4
|/ | | | | | | | | | This can happen if noone outside of MessagingMenuApp holds a reference to the message and somebody calls remove_message() with a pointer they got from _get_message() (which doesn't return a ref). messaging_menu_app_remove_message_by_id() really wants a valid 'id' pointer during its lifetime.
* Add messaging_menu_app_get_messageLars Uebernickel2012-12-041-0/+21
|
* Don't export the messaging_menu_message_to_variant symbolLars Uebernickel2012-11-301-3/+3
|
* Use aa{sv} instead of a(ssgav) to communicate actions to the serviceLars Uebernickel2012-11-281-1/+1
|
* Pass message action and its parameter through to the applicationLars Uebernickel2012-11-271-1/+22
|
* Move 'activate' signal into MessagingMenuMessageLars Uebernickel2012-11-271-23/+1
| | | | | And add parameters 'action' and 'parameter' (though they are not set yet).
* Allow adding actions to MessagingMenuMessageLars Uebernickel2012-11-271-24/+4
|
* Tell applications when messages and sources are dismissedLars Uebernickel2012-11-261-0/+21
| | | | | | Right now, this is only used to clean up internal data structures in libmessaging-menu. It's not exposed to the application itself.
* libmessaging-menu: emit the right signal when a message is removedLars Uebernickel2012-11-201-1/+1
|
* Add support for individual messages to MessagingMenuAppLars Uebernickel2012-11-151-5/+139
| | | | | This is not exposed in the indicator menu yet.
* MessagingMenuApp: fix leak (source list)Lars Uebernickel2012-11-141-1/+5
|
* Change application to service d-bus protocolLars Uebernickel2012-11-141-253/+258
| | | | | | | | | | | | | | Previously, the protocol was simply a menu model and an action group of the currently active sources. The service inserted the menu as a section into the indicator menu. This doesn't work anymore, because applications can (soon) expose individual messages, and the messaging menu doesn't always display all of those at once. This patch introduces a more specific d-bus API. That API is still considered private: applications have to use libmessaging-menu.
* Merge new libmessaging-menu APILars Uebernickel2012-11-051-64/+118
| | | | | | | | | Adds MessagingMenuMessage, which allows adding individual messages with titles and body previews to the messaging menu with messaging_menu_app_append_message. This only adds the new API, messages are not actually sent to the messaging menu yet.
* libmessaging-menu: add MessagingMenuMessageLars Uebernickel2012-11-011-0/+63
| | | | | | | | | MessagingMenuMessage allows adding individual messages with titles and body previews to the messaging menu with messaging_menu_app_append_message. This only adds the new API, messages are not actually sent to the messaging menu yet.
* libmessaging-menu: messaging-menu.[ch] -> messaing-menu-app.[ch]Lars Uebernickel2012-11-011-0/+1141