aboutsummaryrefslogtreecommitdiffstats
path: root/libgnomecanvas
Commit message (Collapse)AuthorAgeFilesLines
* gnome-canvas: Remove GnomeCanvasBufBenjamin Otte2010-10-303-113/+0
| | | | It's not used anymore.
* gnome-canvas: Remove GnomeCanvasItem->render vfuncBenjamin Otte2010-10-309-519/+0
| | | | It's unused now
* gnome-canvas: Remove aa codeBenjamin Otte2010-10-306-368/+65
| | | | The anti-aliased code was never used, so remove it.
* Drop usage of GtkAnchorType.Matthew Barnes2010-10-276-374/+7
| | | | gtk+-3.0 removed it for being "unused".
* Bug #631870 - Memory leak in e_week_view after GtkObject removalMilan Crha2010-10-251-1/+1
|
* Remove EVO_MARSHAL_RULE.Matthew Barnes2010-10-231-2/+3
| | | | Use glib-gen.mak instead.
* Bug #631320 - GtkObject is gone in GTK3Milan Crha2010-10-0713-192/+101
|
* Use new GDK keysym names if available.Matthew Barnes2010-09-183-23/+28
| | | | | | | In GTK+ 2.21.8, the keysym names were renamed from GDK_* to GDK_KEY_*. I've added backward-compatibility macors to gtk-compat.h, which can be dumped as soon as we require GTK+ >= 2.22.0.
* Coding style and whitespace cleanups.Matthew Barnes2010-09-121-2/+2
|
* Various memory leaksMilan Crha2010-09-081-2/+0
|
* Coding style and whitespace cleanup.Matthew Barnes2010-08-2917-450/+450
|
* Coding style and whitespace cleanup.Matthew Barnes2010-08-291-6/+6
|
* Bug 624525 - Variable name collision in gtk-compat macroMilan Crha2010-07-222-2/+2
|
* Coding style and whitespace cleanup.Matthew Barnes2010-07-123-41/+76
|
* Remove an obsolete GTK+ header include.Matthew Barnes2010-06-291-1/+0
|
* Coding style and whitespace cleanup.Matthew Barnes2010-06-2041-1080/+1059
|
* Don't bother translating GnomeCanvas GObject properties.Matthew Barnes2010-06-203-106/+106
|
* Remove unused libart_lgpl API.Matthew Barnes2010-06-162-3/+0
| | | | According to CallCatcher.
* Install header files for libgnomecanvas and libart_lpgl.Matthew Barnes2010-06-161-29/+33
|
* Fix all remaining GTK3 issues.Matthew Barnes2010-06-168-174/+390
| | | | | | | | | | | | 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.
* Revert "Fix all remaining GTK3 issues."Matthew Barnes2010-06-158-390/+174
| | | | | | | This reverts commit fd8b55edaa88906b588aa07d9eadcacd34a7a774. Something in this commit seriously hosed ETable, making Evolution pretty much unusable. Reverting this until I can track down the problem.
* Drop the "2" from libgnomecanvas and libart_lgpl.Matthew Barnes2010-06-151-6/+6
|
* Fix all remaining GTK3 issues.Matthew Barnes2010-06-158-174/+390
| | | | | | 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.
* Embed libart_lgpl and libgnomecanvas.Matthew Barnes2010-06-1450-0/+20498
Both of these modules are deprecated and going away in GNOME 3 but we still rely heavily on them for GnomeCalendar and ETable. So, welcome to the island of unwanted libraries...