Bug 714319 - Include the ClearLooks theme in the Fedora packaged version of FontForge
Summary: Include the ClearLooks theme in the Fedora packaged version of FontForge
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fontforge
Version: rawhide
Hardware: All
OS: All
low
low
Target Milestone: ---
Assignee: Paul Flo Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-17 22:58 UTC by Dave Crossland
Modified: 2011-10-03 13:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-10-03 13:49:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Crossland 2011-06-17 22:58:14 UTC
Description of problem:

FontForge's default UI theme is not similar to the default GTK/QT theme, because it uses its own X Window Toolkit. 

Version-Release number of selected component (if applicable):
All

How reproducible:
Always

Steps to Reproduce:
1. Run FontForge
2. Look at it
3. Look at any other GTK/QT application
  
Actual results:
They look very different

Expected results:
They look similar

Additional info:

I have described installing a theme to the user's home directory at http://openfontlibrary.org/wiki/How_to_setup_FontForge and this theme could be used as a basis for a theme that matches the current Fedora theme, as it is based on ClearLooks.

Comment 1 Paul Flo Williams 2011-08-18 07:38:11 UTC
I've tried the supplied theme on F15, and I don't know whether it needs tweaking, but it gave me enormous fonts on FontForge's main window, so I switched back. 

I would suggest that changing the default look of FontForge is simply a matter of taste, and it of course doesn't affect the fact that FontForge doesn't act like a GTK or QT application, and you might argue that "looks the same but doesn't act the same" is another type of user interface failure.

How to proceed? It might be possible to package this theme and others so that they are more readily available to users, but those would be separate packages along the lines of fontforge-theme-*, not part of FontForge.

I'm also mindful of the caveat about theming on the FontForge wiki: "playing with x resources may result in abrupt crashes at the very start of application. It appears then, that 'fontforge doesn't start'." Bug 720354 may well be one such.

So, I think
1. This isn't and shouldn't be part of the fontforge package.
2. You might want to package this separately so that users have a choice, and I'd be prepared to submit any useful changes to our fontforge package or upstream to support theming.

Any other thoughts, before I say this is notabug?

Comment 2 Paul Flo Williams 2011-10-03 13:49:36 UTC
Closing, with reasoning given in comment 1.


Note You need to log in before you can comment on or make changes to this bug.