aboutsummaryrefslogtreecommitdiff
path: root/libmessaging-menu
Commit message (Collapse)AuthorAgeFilesLines
* Do a natural CMake file configurationRobert Tari2021-10-212-10/+5
|
* Remove Automake filesRobert Tari2021-10-211-76/+0
|
* Add CMake filesRobert Tari2021-10-211-0/+106
|
* Fix pkg-config file library and path flagsLuca Boccassi2019-03-101-2/+2
| | | | | | | The ayatana prefix was dropped from the library name and the include directory, but the pkg-config file was not updated. Fix it. Fixes Debian bug #923958
* Fork from Ubuntu's Indicator Messages.Mike Gabriel2017-10-273-9/+8
|
* libmessaging-menu: fix section link in the documentation and add ↵Lars Uebernickel2014-11-032-1/+8
|\ | | | | | | | | | | descriptions Fixes: 1313561 Approved by: Ted Gould
| * libmessaging-menu: fix section link in the documentation and add descriptionsLars Uebernickel2014-04-282-1/+8
| |
* | libmessaging-menu: allow numbers in object pathsLars Uebernickel2014-10-231-1/+1
| |
* | messaging-menu-message: add missing break statementsLars Uebernickel2014-07-111-0/+2
| |
* | Add an example for client usage from a python script.Charles Kerr2014-05-281-0/+21
|/
* Use serialized icons for messages and sourcesLars Uebernickel2013-09-052-28/+30
| | | | | The D-Bus protocol is not part of the public API, so it's okay to change it.
* libmessaging-menu: default MessagingMenuMessage::draws-attention to TRUELars Uebernickel2013-08-291-1/+2
| | | | | | In most cases, apps will want to draw the user's attention when they add a message to the menu.
* Merge from trunkTed Gould2013-08-131-0/+4
|\
| * Notify the service when an app unrefs its MessagingMenuApp. Fixes: ↵Lars Uebernickel2013-06-071-0/+4
| |\ | | | | | | | | | | | | | | | https://bugs.launchpad.net/bugs/1154099. Approved by PS Jenkins bot, Ted Gould.
| | * Notify the service when an app unrefs its MessagingMenuAppLars Uebernickel2013-02-191-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Prior to this patch, the messaging menu only marked apps as "not running" when they quit (i.e. disappeared from the bus). This was okay, since most applications only ever release the ref to their MessagingMenuApp when they quit, or after calling _unregister explicitely (which removes them from the menu entirely). However, this is according to libmessagingmenu's documentation, and at least indicator-telepathy relies on it.
| * | libmessaging-menu: don't use detailed action namesLars Uebernickel2013-05-151-1/+2
| | | | | | | | | | | | | | | | | | | | | Detailed action names are of the form action::target or action(target), so they can't have colons or parens in them. This restriction does not apply to messaging menu ids.
| * | libmessaging-menu: Set correct boolean value in _remove_attention and ↵Jason Conti2013-02-121-2/+2
| |/ | | | | | | _set_draws_attention
| * libmessaging-menu: fix crash in _draws_attentionLars Uebernickel2012-11-221-1/+1
| | | | | | | | | | | | The format string passed to g_variant_get calls for four parameters, but only three were given.
* | added gio-2.0 to vapigenKen VanDine2013-07-121-1/+1
| |
* | generate vapiKen VanDine2013-07-111-0/+18
| |
* | 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-042-0/+24
| |
* | Don't export the messaging_menu_message_to_variant symbolLars Uebernickel2012-11-302-5/+5
| |
* | Use aa{sv} instead of a(ssgav) to communicate actions to the serviceLars Uebernickel2012-11-282-17/+12
| |
* | Pass message action and its parameter through to the applicationLars Uebernickel2012-11-271-1/+22
| |
* | Move 'activate' signal into MessagingMenuMessageLars Uebernickel2012-11-272-23/+21
| | | | | | | | | | And add parameters 'action' and 'parameter' (though they are not set yet).
* | Allow adding actions to MessagingMenuMessageLars Uebernickel2012-11-273-24/+170
| |
* | 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-152-6/+140
| | | | | | | | | | 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.
* | Remove gtupleaction, it isn't used anymoreLars Uebernickel2012-11-133-397/+1
| |
* | Move service .xml into a common directoryLars Uebernickel2012-11-131-18/+6
| | | | | | | | | | | | | | | | | | | | Both the service (in src/) and the client library (in libmessaging-menu/) need access to the dbus interface description file. Until now, it resided in src, with both Makefiles calling gdbus-codegen on it. This patch moves the file to common/ and builds a convenience library that contains only the generated code.
* | Merge new libmessaging-menu APILars Uebernickel2012-11-056-128/+671
|\ \ | |/ |/| | | | | | | | | | | | | 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-015-2/+518
| | | | | | | | | | | | | | | | | | 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-014-127/+153
| |
* | libmessaging-menu: clear time when set_count is calledLars Uebernickel2012-10-281-42/+68
| |
* | messaging_menu_app_set_source_icon: unset x-canonical-icon if NULL is passedLars Uebernickel2012-10-241-5/+15
| |
* | Merge lp:~jconti/indicator-messages/unexport-itemsLars Uebernickel2012-10-181-15/+33
|\ \ | | | | | | | | | | | | libmessaging-menu: unexport action group and menu model on dispose.
| * | Unexport actions/menus on disposeJason Conti2012-10-101-15/+34
| |/
* / libmessaging-menu: clear error before reusing itLars Uebernickel2012-10-111-2/+2
|/
* Fixed typo in docstringKen VanDine2012-10-091-1/+1
|
* libmessaging-menu: don't crash when getting an invalid desktop idLars Uebernickel2012-10-011-3/+14
| | | | | | Instead, silently don't export menus and actions. The single warning about the desktop id being invalid should be enough.
* Set the global chat status more intelligentlyLars Uebernickel2012-09-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Up until now, the global chat status was set every time an application called _set_status. Thus, global status really meant "status of the app that last changed the status". Now, the service remembers the chat status for each application and sets the global status as a combination of all of application statuses. If applications have different statuses, the menu items are shown in an inconsistent state. This is implemented in IdoMenuItem by making it accept state as an array of strings in addition to a single string. It is drawn inconsistent if the state contains the menu item's target value in addition to other values. When the global status is changed through the messaging menu, the service doesn't update the action immediately anymore. Instead, it notifies all applications about the change via the "status-changed" signal. Applications must call _set_state to acknowledge that they have indeed changed their state. This is consistent with libmessaging-menu's documentation and design. Also, the SetStatus D-Bus call was missing a "desktop-id" parameter to tell the menu which application changed status. Changing this doesn't break existing apps, as the D-Bus interface is considered private to indicator-messages.
* libmessaging-menu: don't set app->status when global status changesLars Uebernickel2012-09-181-2/+1
| | | | | | | | | The application's status only changes when it calls _set_status, so it's wrong to set the internal status when the global status changes. This shouldn't be a problem in practice, as app->status is not accessible from the API.
* libmessaging-menu: don't call SetStatus(OFFLINE) for all appsLars Uebernickel2012-09-181-2/+5
| | | | | | | | Only notify the service about status if the application has actually called messaging_menu_app_set_status. This saves a d-bus call per non-chat application and - more importantly - doesn't make the messaging menu go into "unknown status" mode when one application is reporting 'online' status.
* libmessaging-menu: fix shortcut action documentationLars Uebernickel2012-09-041-4/+5
|