aboutsummaryrefslogtreecommitdiff
path: root/libdino/CMakeLists.txt
AgeCommit message (Collapse)Author
2018-08-13accumulate conversation content in meta db tablebobufa
2018-08-13initial search logic / displaybobufa
2018-08-13refactor conversation item management (accumulate them in libdino)bobufa
2018-03-05Move notification sounds (canberra dependency) into plugin, introduce ↵fiaxh
libdino/NotificationEvents
2018-01-28Move Jid class to xmpp-vala, partially refactor namespaceMarvin W
2018-01-09Move to GNetworkMonitor (#236)Mathieu Bridon
* Move to GNetworkMonitor Dino currently talks to NetworkManager over DBus to know the state of the network. That doesn't work in a Flatpak sandbox by default though, because Flatpak filters DBus communications and only allows a very small set of things to pass (which are known to be safe). Gio provides an API to know the state of the network (and be notified of changes via a signal): GNetworkMonitor. And GNetworkMonitor works both inside a Flatpak sandbox, and in traditional builds. (in Flatpak it uses what we call a "portal", which are the clean, safe way to let apps exit their sandbox) Fixes #235 * Don't check for network connectivity for now The connectivity check really is the correct thing to do: * network_available means that the computer has network routes to "somewhere". That is, it is connected to a router. * connectivity.FULL means that the computer can access "the Internet". That is, if it is behind a router, that router is connected. As a result, only checking for network_available is not correct. Unfortunately, NetworkManager tends to wait a long time before checking for connectivity. As a result, it is possible that a transient network error leaves NetworkManager thinking that network_available is true but connectivity!=FULL, and it will wait several minutes before realizing that the Internet connexion did come back. During that time, apps checking for connectivity (e.g the whole GNOME desktop) will think they don't have access to the Internet, while apps that don't (e.g Firefox) will access the Internet just fine. Users are understandably confused when that happens. Removing the check for connectivity is an acceptable trade-off in the short-term, until this situation is improved on the NetworkManager side. https://bugzilla.gnome.org/show_bug.cgi?id=792240
2017-10-31Blocking setting in Contact Detailsfiaxh
2017-08-31Download & inline display imagesfiaxh
2017-08-29libdino: try to load all plugins found in the respective foldersMarvin W
2017-08-28Plugins providing conversation items for ConversationViewfiaxh
2017-08-25connection: keep-alive pings, act upon connection change (VPN)fiaxh
2017-08-22fixup 4a4b595fiaxh
2017-08-22Move settings from GSettings to own dbfiaxh
2017-08-17libdino: remove dependency to GTK+ (all GTK+ code is in main+plugins)Marvin W
2017-04-26cmake/signal-protocol: shared lib, mark_as_advanced and othersMarvin W
2017-04-10Gettext supportfiaxh
2017-04-04MessageStorage/Processor, correctly resolve conversations (fixup 22adbd3)fiaxh
2017-04-03Make FHS compliant, split RPMs, fix compilation on older GCCsMarvin W
2017-03-23New CMakeMarvin W
- add install and uninstall targets - compatibility for systems without pkg-config
2017-03-12Automatically compile and use gsettings schemaMarvin W
2017-03-12Split OMEMO plug-in into files, various fixesMarvin W
2017-03-12Move PGP support into pluginfiaxh
2017-03-11Move UI code into main dirMarvin W
2017-03-11CMake: merge created header+vapi files into a single directoryMarvin W
2017-03-11Plug-In API: allow adding custom entries to account settingsMarvin W
Also make OpenPGP code use this API
2017-03-11UI to choose PGP key/disabled in account settingsfiaxh
2017-03-11Improve Plugin API (allow to move encryption into plugin)Marvin W
2017-03-10Initial plugin systemMarvin W