Zim

look and feel on windows: default gtk laf is used

Bug #830043 reported by Sebastian Niedworok
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Zim
Fix Released
Undecided
Brendan Kidwell

Bug Description

Hello all,

on windows zim (0.50) uses the default gtk look and feel, which does
not integrate very nicely into the rest of the OS.
The problem can be solved by putting a gtkrc file into the etc\gtk-2.0\
folder. a one liner is sufficient, something like:

gtk-theme-name = "MS-Windows"

best regards,
Sebastian

Related branches

Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote : Re: [Bug 830043] [NEW] look and feel on windows: default gtk laf is used

Can add this to the manual as a tip, but not going to touch the gtkrc from
the zim source code.

-- Jaap

On Sat, Aug 20, 2011 at 2:35 PM, Sebastian Niedworok <
<email address hidden>> wrote:

> Public bug reported:
>
> Hello all,
>
> on windows zim (0.50) uses the default gtk look and feel, which does
> not integrate very nicely into the rest of the OS.
> The problem can be solved by putting a gtkrc file into the etc\gtk-2.0\
> folder. a one liner is sufficient, something like:
>
> gtk-theme-name = "MS-Windows"
>
> best regards,
> Sebastian
>
> ** Affects: zim
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to Zim.
> https://bugs.launchpad.net/bugs/830043
>
> Title:
> look and feel on windows: default gtk laf is used
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/zim/+bug/830043/+subscriptions
>

Revision history for this message
Sebastian Niedworok (niedworok) wrote :

This bug report is more of a bug report for Brandan, who packs the windows installer.
Including the proper gtkrc would make for a better first impression on that platform.
There is no gtkrc in the zim source code, neither should there be one, imho.

Sebastian

tags: added: win32-installer
Changed in zim:
status: New → Confirmed
Changed in zim:
assignee: nobody → Brendan Kidwell (bkidwell)
Revision history for this message
Brendan Kidwell (bkidwell) wrote :

The Windows package builder is a folder off the main Zim source tree and the proposed gtkrc change should go in there. Shouldn't be hard to accomplish. Will target 0.53 release.

Revision history for this message
Brendan Kidwell (bkidwell) wrote :

Just to clarify: currently, Zim includes it's own full GTK library with (possibly) its own GTK config files. Since it doesn't share any GTK things with other Windows apps -- there is no real standard protocol to do so -- it's perfectly appropriate for us to include any sane defaults in the gtkrc file in Windows since it will only be used by Zim. The user can override these defaults by investigating the proper path to write their own gtkrc file under ~ .

Revision history for this message
Brendan Kidwell (bkidwell) wrote :

> gtk-theme-name = "MS-Windows"

Actually... it's not that simple. I had a look at this tonight, and I got bogged down with how GTK themes work. I played around a little and couldn't make head or tail of it. I think it looks just fine AS IT IS in Windows 2008 Server.

If anyone thinks they can help, please download my latest updates for the Windows installer from lp:~bkidwell/zim/pyzim-win-installer and suggest specific changes or send me a patch if you get it to work.

Revision history for this message
Brendan Kidwell (bkidwell) wrote :

Found fix here http://www.no-ack.org/2010/09/complete-guide-to-py2exe-for-pygtk.html (search for "gtk-theme-name"). Checked in; will send merge request to Jaap before 0.53 release.

Changed in zim:
status: Confirmed → Fix Committed
Revision history for this message
Brendan Kidwell (bkidwell) wrote :

Actual fix is:

Where "." is the folder of zim.exe... create "./etc/gtk-2.0/gtkrc" with this line of text
   gtk-theme-name = "MS-Windows"

Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

Fix released in zim 0.53.

Changed in zim:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.