See mumble-voip/mumble#1881

http://i.imgur.com/gkCflal.png

Is fine in dark and no skin, so I guess a lite skin problem?

@xpoke maybe you can clarify?

Suggested by @streaps here: #17 (comment)

It's about this icons:
https://github.com/mumble-voip/mumble-theme/blob/master/lock_locked.svg
https://github.com/mumble-voip/mumble-theme/blob/master/lock_unlocked.svg

Related to this pull request: mumble-voip/mumble#3929

They look inconsistent to the general theme, so maybe someone can improve them.

Information like torrent name, size, status, seeds, and peers is not readable because they are written in black whereas the blackground is a very dark grey. Can you make the text some color other than black or grey?
https://imgur.com/a/0ArnfI4

The fonts and font sizes need an overhaul for OS X.

We probably want to use the system font to fit in better -- unless we want to use the same Free font on all systems? @xpoke?

We probably want something like

font-family: ".SFNSDisplay-Regular", HelveticaNeue, LucidaGrande;

for OS X. (Per http://furbo.org/2015/07/09/i-left-my-system-fonts-in-san-francisco/)

For font sizes, we probably want something like this:

http://apple.stackexchange.com/questions/20898/what-is-mac-os-x-lions-finder-font/20910#20910

For reference, right now things look like this:

Context

Following mumble-voip/mumble#2137, I want to propose a modern icon for mumble.

Describe the feature you have in mind

A modern icon, I went for a try following material icon design.

mumble.svg.tar.gz

While trying to use this theme as the basis for my own variant, I came across a rather annoying issue: abuse of variables.

Example:

QCheckBox::indicator:focus:hover,
QTreeView::indicator:focus:hover,
QRadioButton::indicator:focus:hover,
QComboBox:focus:hover
{
	background-color:$button-focus-hover-bg;
	border-color:$button-focus-hover-border;
}

The naming suggests that $button-* variables are used for buttons, but they are used for many other components as well.

This leads to a situation where changing the appearance of buttons affects a dozen other elements in not predictable ways and I have to override a ton of style definitions if I follow the suggestion to not modify Base Theme.scss.

This is especially annoying since the design I'm trying to build uses a highlight color for buttons and that highlight color pops up in a dozen other places which are not supposed to be highlighted.

I'd suggest to stop using $button-* variables for anything other than buttons and introduce corresponding $input-* variables instead so the design is basically split into "buttons" and "all other input elements" just like many of today's CSS frameworks do.

The "1.3.0 Snapshot" message font color is barely visible in the snapshots:

https://github.com/mumble-voip/mumble-theme/blob/9c68c1453837b82f69e93d7df2dbdd086d96f27d/config_basic.png is the icon that represents the "Configure Mumble" action.

The other icons in the toolbar are all in SVG.

The file overlay.mumblelay contains a version string at

This may be a technical necessity, but it is very bad architecture because now the Mumble version depends on the themes layout file.

It makes version bumps in Mumble more complex and error prone. mumble-voip/mumble#3799 mumble-voip/mumble#3761

If at all possible the theme must not contain version specific code like this.

@xpoke Is the assumption correct that this is a layout file replacing the existing one for layout changes. And the version number being in there is a side effect because we override the entire file?

So the way to fix this would then to look for a way in Mumble itself to clear it from the layout file? (What is the file used for and how?)

The box where text is typed should be white in the new theme. As it stands it just looks like some text on a background, whereas it should look like a separated area.

We maybe want to add a help icon in the configuration options, to show additional information (e.g. regarding echo-cancel etc.).
For a first concept see:
mumble-voip/mumble#4127 (comment)

Maybe someone could provide a good looking icon that is also consistent with the overall theme.

We could implement some kind of robot icon:
https://duckduckgo.com/?t=ffab&q=bot+icon&iax=images&ia=images

Copy-paste from IRC:

the taskbar icon is awful as someone who is colour-blind
cannot tell the difference between talking and not whatsoever
it's easy to tell in mumble itself due to the white background, the "waves" next to the person are obvious
I think I'd rather it be the actual mumble icon when not talking
as a "person" while idle doesn't represent what kind of program it is
then have the talking guy when talking
that will make the difference pretty obvious

As mentioned by @Kissaki here,

Although this may not happen now or ever, I’d love to see a design documentation that shows and describes the icons with argumentation why they are used, for a feature and in relation to others.

A documentation for all icons and their purposes & usecases would be very good.

https://github.com/mumble-voip/mumble-theme/blob/master/LICENSE

I'm a contributor to minetest and we've had similar discussions with many contributors about mods, themes, etc.. My conclusion is that Unlicense (or, any form of Public Domain declaration) is an unfit license for media/assets, and in general is problematic due to the statement that in jurisdictions where Copyright exists, the items are declared Public Domain, which may not exist at all in those jurisdictions. This leaves a gray area for interpretation where it may not at all be usable to some users.

For media and assets, we've found the CC licenses to be ideal. While personally I feel one should always, at minimum use CC-BY licenses, even CC0-1.0 would be a major improvement over Unlicense for media, as it spells out in detail what is permitted use.

Most important Ref.: https://opensource.org/faq#public-domain

Suggested by @streaps here: #17 (comment)

It's about this icon:
https://github.com/mumble-voip/mumble-theme/blob/master/ear.svg

which is used for this (according to @Krzmbrzl ):

It marks listener proxies of the ChannelListener feature. Aka. this is a virtual ear that a user can drop into a channel in order to hear what is being spoken in it without having to join it.

It does not really look good at the moment, so maybe someone can improve or replace it.

Discuss ideas/changes below.

Following the discussion in #31, I noticed that the red tone of colour is a bit too orange.
Visible for example here: https://raw.githubusercontent.com/mumble-voip/mumble-theme/master/muted_self.svg

I would like a darker and more red tone.

As far as I can see, the colour would need to be changed in the following files:

config_msgs.png
/exported/config_msgs.svg
deafened_self.svg
lock_locked.svg
muted_self.svg
/mimetypes/image-x-generic.svg
/emblems/emblem-favorite.svg
/actions/audio-input-microphone-muted.svg
/actions/format-text-bold.svg
/actions/media-record.svg

Hey - It's been a while since I created the theme, but I saw you guys released 1.3 (!)

I was wondering if there's an interest in making variants using the icons from FontAwesome's GPL-friendly library.
https://fontawesome.com/
https://github.com/FortAwesome/Font-Awesome
https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt

I specifically think some users would like a less colorful theme, and we can easily add high quality icons.
Let me know if this fits with your plans for a 1.3.1 release