aboutsummaryrefslogtreecommitdiffstats
path: root/widgets/misc/e-source-config-backend.h
Commit message (Collapse)AuthorAgeFilesLines
* Consolidate base utility libraries into libeutil.Matthew Barnes2012-12-131-94/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Evolution consists of entirely too many small utility libraries, which increases linking and loading time, places a burden on higher layers of the application (e.g. modules) which has to remember to link to all the small in-tree utility libraries, and makes it difficult to generate API documentation for these utility libraries in one Gtk-Doc module. Merge the following utility libraries under the umbrella of libeutil, and enforce a single-include policy on libeutil so we can reorganize the files as desired without disrupting its pseudo-public API. libemail-utils/libemail-utils.la libevolution-utils/libevolution-utils.la filter/libfilter.la widgets/e-timezone-dialog/libetimezonedialog.la widgets/menus/libmenus.la widgets/misc/libemiscwidgets.la widgets/table/libetable.la widgets/text/libetext.la This also merges libedataserverui from the Evolution-Data-Server module, since Evolution is its only consumer nowadays, and I'd like to make some improvements to those APIs without concern for backward-compatibility. And finally, start a Gtk-Doc module for libeutil. It's going to be a project just getting all the symbols _listed_ much less _documented_. But the skeletal structure is in place and I'm off to a good start.
* Bug 678634 - Criticals warnings when creating new book/calMatthew Barnes2012-06-241-1/+6
| | | | | | | | | | | | | | | | This required some reworking of assumptions I made early on when I first wrote ESourceConfig, before I thought up the whole "collection" concept. Not all ESourceConfigBackends will use a fixed parent UID, specifically collection backends. In fact we may use multiple instances of the same ESourceConfigBackend subclass if, for example, a user has two different Exchange Web Services accounts configured. We would need to show both EWS account (or "collection") names in the "Type" combo box. For the moment collection-based ESourceConfigBackends are not listed when creating a new calendar or address book since we lack support for creating new resources on a remote server. A D-Bus interface for that is in the works.
* Adapt to single-include E-D-S libraries.Matthew Barnes2012-06-041-1/+1
|
* Add ESourceConfig widget.Matthew Barnes2012-06-031-0/+89
Base class for building address book and calendar configuration dialogs.