Re: [PATCH] Implement support for treeview headers native rendering, add GTK implementation

Bjoern Michaelsen <bjoern.michaelsen -AT- canonical.com>
Sun, 8 Jul 2012 18:55:43 +0200

Hi Ruslan,

On Sat, Jul 07, 2012 at 10:06:37PM +0400, Ruslan Kabatsayev wrote:

These two patches implement support for listview headers (aka
HeaderBar) native rendering.
First one makes the "buttons" look natively, and second one makes
arrow showing sort order also look native.
Aside from adding support for this, these patches also add GTK
implementation of this.


Pushed as dependant patches:

https://gerrit.libreoffice.org/#/c/265/
https://gerrit.libreoffice.org/#/c/266/

for review on gerrit.

@Caolan: I would love to have you as a reviewer on this Gtk stuff. Could you
finally get yourself an account on gerrit(*)?

Best,

Bjoern

(*) https://wiki.documentfoundation.org/Development/gerrit/setup

Context

[PATCH] Implement support for treeview headers native rendering, add GTK implementation · Ruslan Kabatsayev
- Re: [PATCH] Implement support for treeview headers native rendering, add GTK implementation · Bjoern Michaelsen
  - Re: [PATCH] Implement support for treeview headers native rendering, add GTK implementation · Ruslan Kabatsayev
    - Re: [PATCH] Implement support for treeview headers native rendering, add GTK implementation · Bjoern Michaelsen
    - Re: [PATCH] Implement support for treeview headers native rendering, add GTK implementation · David Ostrovsky

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.