XnView Software

I still think that user-contributed themes would be a great idea (in addition to the "official" light-medium-dark themes). If there was a way to share layouts, toolbars, themes, thumb-designs, etc., then the best ones could be incorporated into the distribution packages and listed in settings for the user to switch between.

See again my post in the thread: here.

Partly this issue is about storage (INI files and what-not) and partly this issue is about the UI.

The issue with MP currently is that there is not yet a "simplification" layer (=WYSIWYG dialog) between the user and the style sheet that combines all of the options/adjustments.

A question: if a style element is defined twice in a QSS file, does QT use the second one? I think it does, and if so, then a style editor could layer changes on top of a basic theme by addressing a subset of the elements present in the "master" style.

Perhaps Tweak UI would be a good tool for something like that.

JohnFredC wrote: The issue with MP currently is that there is not yet a "simplification" layer (=WYSIWYG dialog) between the user and the style sheet that combines all of the options/adjustments.

So an unique dialog to be able to edit all colors of XnViewMP (currently in options), and theme qss file?

A question: if a style element is defined twice in a QSS file, does QT use the second one? I think it does, and if so, then a style editor could layer changes on top of a basic theme by addressing a subset of the elements present in the "master" style.

I think yes

xnview wrote:So an unique dialog to be able to edit all colors of XnViewMP (currently in options), and theme qss file?

Well yes, ultimately, that would be the best approach. (Though there are more important things to do for MP functionality first.)

But a logical reduction of the many different theme components into groups that share the same "colors" etc would be beneficial. For instance, in the current "dark" theme, the toolbars do not share the same backgrounds. The "mini" toolbar background is controlled by something else.

So the effort should be: simplify, simplify, simplify, and then group.

• 1. Identify an MP standard "look" (3D or not to be, that is the question!)
  
  • Most of the irritating visual "noise" in the current "dark" theme derives from superfluous lines and borders used to give a "3d" look. Some of them could be eliminated (see my example post, above) by assigning the same colors to them as the backgrounds they lie on.
  2. Identify which components should share the same "theme" colors
  • Toolbars, for instance.
  3. Identify a (relatively small) set of color settings to be exposed in the "theme designer" UI.
  
  • For instance: toolbar background, active tab, inactive tab, panel backgrounds, row backgrounds, etc.
  4. Publish a guide
  
  • ...that shows the relationships between the various widgets/controls and assigned colors.
  5. At this point, a theme designer UI could be built...

It would be best that direct manipulation of the QSS file by obsessives (such as myself) would remain, but an efficient tool to change MP 1.x's look/UI/behavior and "package" it for sharing would be huge.

Huge I say!

JohnFredC wrote:I used a text editor... if anyone knows of a good QSS stylesheet editor please speak up!

• Qt Quarterly
  • Issue 25 · Q1 2008: Qt Designer's New Features » Improved Style Sheet Editor
• TeamSpeak 3 Designs & Skins
  • Tutorials » How to create a Team Speak 3 design [basic]

This is all I got

In general, a good CSS editor will be enough for the properties, at least.

Do you have a recommendation?

I have serious doubts that a general purpose CSS editor can serve as “a ‘simplification’ layer (=WYSIWYG dialog) between the user and the style sheet that combines all of the options/adjustments” for skinning UI elements of a Qt application.

• Smashing Magazine
  • List of CSS Tools
  • 25 Useful WYSIWYG Editors Reviewed
  • CSS Editors Reviewed
  • 50 Extremely Useful And Powerful CSS Tools
  • 35 CSS-Lifesavers For Efficient Web Design
• Speckyboy Design Magazine
  • 7 Free CSS Editors, Which Is the Best? You Choose.
• Resources.SaveDelete.com
  • Top 10 Free Online CSS Editors For Web Designers
• CSShook Gallery
  • Best CSS Editors
• Oiko CSS Editor
• TopStyle Lite (via SnapFiles or Softpedia)

Thanks for those links.

XnTriq wrote:I have serious doubts that a general purpose CSS editor can serve as “a ‘simplification’ layer (=WYSIWYG dialog) between the user and the style sheet that combines all of the options/adjustments” for skinning UI elements of a Qt application.

I completely agree... was just hoping for something for us to use in the meantime.

Edit: Thanks for those great links!

JohnFredC ([url=http://newsgroup.xnview.com/viewtopic.php?p=89158#p89158]XnView MP & theme[/url]) wrote:Edit: Thanks for those great links!

You're welcome, Mister C.

More inspiration for a dark theme — This time courtesy of Nokia's own Qt Creator IDE:

LWN.net ([url=http://www.lwn.net/Articles/365842/]Qt Creator 1.3[/url]) wrote:

• 

Qt Creator Manual ([url=http://doc.qt.nokia.com/qtcreator-2.1-snapshot/creator-using-qt-quick-designer.html]Using Qt Quick Designer[/url]) wrote:

• 

Open Source Dev-Notes ([url=http://matgnt.wordpress.com/2010/01/25/problems-installing-qtcreator-from-git-master/]Problems installing QtCreator from git master[/url]) wrote:

• 

Qteveloper ([url=http://qteveloper.blogspot.com/2010/06/qt-quick-designer.html]Qt Quick Designer[/url]) wrote:

•