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
..
common.h	tests: Add tests for Origin and Calls	2018-10-03 14:21:28 +00:00
meson.build	tests: Disable atk bridge	2020-06-08 09:46:58 +00:00
setup-call.c	tests: Add tests for Origin and Calls	2018-10-03 14:21:28 +00:00
setup-call.h	tests: Add tests for Origin and Calls	2018-10-03 14:21:28 +00:00
setup-origin.c	provider: Use GListModel to track origins	2021-02-25 08:44:56 +05:30
setup-origin.h	Turn providers into plugins courtesy of libpeas	2018-11-23 15:51:46 +00:00
setup-provider.c	tests: Add tests for Origin and Calls	2018-10-03 14:21:28 +00:00
setup-provider.h	tests: Add tests for Origin and Calls	2018-10-03 14:21:28 +00:00
test-call.c	calls-dummy-origin: Fix ordering of state change and call removal callbacks	2019-07-22 14:37:27 +01:00
test-manager.c	provider: Use GListModel to track origins	2021-02-25 08:44:56 +05:30
test-origin.c	tests: Add tests for Origin and Calls	2018-10-03 14:21:28 +00:00
test-provider.c	provider: Use GListModel to track origins	2021-02-25 08:44:56 +05:30