Work around the issue of GnomeCanvasItem amending its own flags to
GtkObject::flags (which is sealed) by giving it its own flags field.
This breaks libgnomecanvas ABI and API, but I see no other way.
This commit didn't work the first time because gnome-pilot libraries
were still pulling in the system-wide libgnomecanvas, and that was
interfereing with our bundled version which has a different ABI.
But gnome-pilot integration was dropped in the previous commit, so
everything is now using the bundled libgnomecanvas.
It just doesn't belong in Evolution anymore. We don't support syncing
with more modern devices -- see Conduits or SyncEvolution for that -- so
it does not make sense for older model Palm Pilot PDAs to be the lone
exception.
I have repackaged the Evolution-Data-Server conduit modules to be
provided by gnome-pilot itself in bug #619315. This should provide
eqivalent Palm Pilot syncing functionality; it's just being moved to
gnome-pilot.
This completely severs our dependency on deprecated GNOME 2.x libraries
which were still being dragged in by way of gnome-pilot dependencies.
It was also interfereing with our bundling of libgnomecanvas.
This reverts commit fd8b55edaa.
Something in this commit seriously hosed ETable, making Evolution pretty
much unusable. Reverting this until I can track down the problem.
Work around the issue of GnomeCanvasItem amending its own flags to
GtkObject::flags (which is sealed) by giving it its own flags field.
This breaks libgnomecanvas ABI and API, but I see no other way.
By tying the attachment view "editable" action group to comp-editor
"individual" group, these add/remove actions are marked sensitive /
insensitive in sync with the existing "Insert" menu items which are
already in the "individual" group.
Though not introduced with the other symptoms of this bug
(0597b877c5), the descreptency fixed
here is integrally related.
The "view-time-zone" and "view-categories" actions should not have
been grouped with the "individual" action group but rather the "core"
action group, as they should always be available regardless of whether
or not the element being edited is read-only/owned, as they simply
affect visibility of various widgets.
This fixes a bug introduced in 0597b877c5
where these two actions were accidentally grouped with other actions
that should legitimately be in the "individual" group.
This introduces a new action_group called "editable" in the comp-editor
that can be used by other components to assign actions that should be
sensitized separately from the existing "individual" group, such as the
"Alarms" and "Show Time as Busy" event actions.
This fixes a bug introduced in 0597b877c5
where these two actions were accidentally grouped with other actions that
should legitimately be in the "individual" group.
By tying the attachment view "editable" action group to comp-editor
"individual" group, these add/remove actions are marked sensitive /
insensitive in sync with the existing "Insert" menu items which are
already in the "individual" group.
Though not introduced with the other symptoms of this bug
(0597b877c5), the descreptency fixed
here is integrally related.
The "view-time-zone" and "view-categories" actions should not have
been grouped with the "individual" action group but rather the "core"
action group, as they should always be available regardless of whether
or not the element being edited is read-only/owned, as they simply
affect visibility of various widgets.
This fixes a bug introduced in 0597b877c5
where these two actions were accidentally grouped with other actions
that should legitimately be in the "individual" group.
This introduces a new action_group called "editable" in the comp-editor
that can be used by other components to assign actions that should be
sensitized separately from the existing "individual" group, such as the
"Alarms" and "Show Time as Busy" event actions.
This fixes a bug introduced in 0597b877c5
where these two actions were accidentally grouped with other actions that
should legitimately be in the "individual" group.
- Install evolution-alarm-notify in $(privlibexecdir) instead of
$(bindir).
- Set the X-GNOME-Bugzilla-Version in evolution-alarm-notify.desktop to
@BASE_VERSION@.x (patch was missing the .x suffix).
- Killed data/evolution.keys.in.in since it's full of CORBA cruft.
The MimeType field in evolution.desktop fills this role now.
- Copied the AS_AC_EXPAND macro from gnome-settings-daemon. The macro
sets up path-related substitutions for use in automake input files.
So for example AS_AC_EXPAND(PRIVLIBEXECDIR, "$privlibexecdir") in
configure.ac allows us to use @PRIVLIBEXECDIR@ in .desktop.in files.
- Simplified .desktop rules using gnome-settings-daemon as a guide.
- Install evolution-alarm-notify in $(privlibexecdir) instead of
$(bindir).
- Set the X-GNOME-Bugzilla-Version in evolution-alarm-notify.desktop to
@BASE_VERSION@.x (patch was missing the .x suffix).
- Killed data/evolution.keys.in.in since it's full of CORBA cruft.
The MimeType field in evolution.desktop fills this role now.
- Copied the AS_AC_EXPAND macro from gnome-settings-daemon. The macro
sets up path-related substitutions for use in automake input files.
So for example AS_AC_EXPAND(PRIVLIBEXECDIR, "$privlibexecdir") in
configure.ac allows us to use @PRIVLIBEXECDIR@ in .desktop.in files.
- Simplified .desktop rules using gnome-settings-daemon as a guide.
