Mohammed Sadiq eda460ac15 provider: Use GListModel to track origins ... And adapt to changes It's easier to track changes if we are using GListModel than a GList. Also, eventually we shall have multiple providers, and we can use GtkFlattenListModel to merge multiple origins without manually managing pointers ourself. Since several widgets has APIs to handle GListModels, it will also help us create widgets from GListModels easily.		2021-02-25 08:44:56 +05:30
..
calls-dummy-call.c	Don't localise property descriptions in calls-call and calls-origin properties	2020-12-07 17:25:33 +00:00
calls-dummy-call.h	plugins/dummy: Implement inbound property	2019-06-28 15:14:41 +01:00
calls-dummy-origin.c	Don't localise property descriptions in calls-call and calls-origin properties	2020-12-07 17:25:33 +00:00
calls-dummy-origin.h	plugins/dummy: Implement inbound property	2019-06-28 15:14:41 +01:00
calls-dummy-provider.c	provider: Use GListModel to track origins	2021-02-25 08:44:56 +05:30
calls-dummy-provider.h	Let calls-provider be an abstract class	2021-01-31 23:01:13 +00:00
dummy.plugin.in	Turn providers into plugins courtesy of libpeas	2018-11-23 15:51:46 +00:00
meson.build	Turn providers into plugins courtesy of libpeas	2018-11-23 15:51:46 +00:00