Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Easier to read small text #17

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Easier to read small text #17

wants to merge 1 commit into from

Conversation

gboudreau
Copy link
Contributor

I think subpixel-antialiased is the default, and thus unneeded. But it's hard to read small text with that.
Example: the "network throughput" text at the top of that widget.
Changing to antialiased makes it much more readable, but also changes the boldness of a lot of the fonts in the existing widgets.
Maybe you want to keep it at subpixel-antialiased in main.css, and just modify the widgets to use -webkit-font-smoothing: antialiased; just for the smaller text..?
Personally, I prefer how my widget look now that I changed it at the "top level" like this.

@gboudreau
Copy link
Contributor Author

Before:
before

After:
after

@felixhageloh
Copy link
Owner

I also prefer antialiased over sub-pixel font smoothing. I actually even switched off sub-pixel font smoothing completely on my mac. I enabled it because for some reason WebView wasn't giving it to be by default and I though it would be what most people are used to. Changing it now would of course affect all existing widgets, but maybe it is early enough to switch to a 'saner' default .... let me sleep over it :)

@frankieshakes
Copy link

Just joining in on this after having sent a pull-request for the exact same change ;)

I agree that having the antialiased font set as the default is the way to go; but I do understand it’s a matter of preference, and everyone has their own taste.

I’m wondering what the alternative, middle-ground fix might be. Perhaps a setting somewhere (either at a per-widget level) or a Ubersicht-wide preference?

Any thoughts?

@soberstadt
Copy link

I vote for uebersicht-wide setting.

On Wed, Aug 20, 2014 at 11:02 AM, Frank Manno [email protected]
wrote:

Just joining on this after having sent a pull-request for the exact same change ;)
I agree that having the antialiased font set as the default is the way to go; but I do understand it’s a matter of preference, and everyone has their own taste.
I’m wondering what the alternative, middle-ground fix might be. Perhaps a setting somewhere (either at a per-widget level) or a Ubersicht-wide preference?

Any thoughts?

Reply to this email directly or view it on GitHub:
#17 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants