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

Do we need an upper limit on the UI resolution? #9

Open
mairin opened this issue Mar 5, 2015 · 4 comments
Open

Do we need an upper limit on the UI resolution? #9

mairin opened this issue Mar 5, 2015 · 4 comments
Assignees

Comments

@mairin
Copy link
Member

mairin commented Mar 5, 2015

I think right now Anaconda scales as large as you've got the monitor real estate. It might be good to cap it at a certain resolution, and allow for it to expand from some minimum (maybe 800x600, I think we support that at a minimum). There's a few advantages to this:

  • The widgets don't fly apart / space out so much making them sometimes harder to reach or look a bit awkward;
  • depending on the driver you're using for your vm, it might help make the window easier to use at a smaller size;
  • We can make the banners look a lot nicer by being able to design them to fit a min=>max size range. then they can scale rather than be tiny on big monitors.
@mairin mairin changed the title Do we need an upperlimit on the UI resolution? Do we need an upper limit on the UI resolution? Mar 5, 2015
@marcoms
Copy link

marcoms commented Mar 6, 2015

+1. My only concern is if Gtk would support the CSS-media-query equivalent that this would require

@luyatshimbalanga
Copy link
Contributor

+1 That would be great for most screen devices.

@garrett
Copy link
Contributor

garrett commented Jan 14, 2016

Do we know what resolutions most people using Fedora use?

FWIW: Even a tiny bit of JS on the default landing page could record that:

// Screen resolution of the current monitor that the browser is on
// (not combined, if there is more than one monitor)
var screenResolution = [screen.width, screen.height];

// Size of the browser window, including UI elements
var browserSize = [window.outerWidth, window.outerHeight];

// Just a quick way to determine if the browser is maximized
// based on some assumptions, like:
// - the combined panel/dock size being less than or equal to 64 pixels
// - having a browser within tolerance is probably maximized (not positioned manually)
var browserMaximized = (screen.width - window.outerWidth) + (screen.height - window.outerHeight) <= 64;

// OS & arch
var platform = navigator.platform;
var bitness = !!navigator.platform.match(/64/);

// Browser being used
var currentBrowser = navigator.userAgent;

It would just have to be reported back to a Fedora server. It wouldn't be super-accurate, but it would give people an idea.

You can see it in action @ https://jsfiddle.net/fcbgadqm/16/ (bottom-right pane has the output on page load and window resize; tested in Firefox, Chromium, and Epiphany)

If somewhat fresh results of these stats exist elsewhere, it'd be good to know, so we can figure out how to target the best screen resolutions for not just Anaconda, but also various websites and other software we develop.

@mairin
Copy link
Member Author

mairin commented Jan 14, 2016

Send the js to robyduck in #fedora-websites - namedrop me if you have to. He can check it in.

On January 14, 2016 5:58:28 AM EST, Garrett LeSage [email protected] wrote:

Do we know what resolutions most people using Fedora use?

FWIW: Even a tiny bit of JS on the default landing page could record
that:

// Screen resolution of the current monitor that the browser is on
// (not combined, if there is more than one monitor)
var screenResolution = [screen.width, screen.height];

// Size of the browser window, including UI elements
var browserSize = [window.outerWidth, window.outerHeight];

// Just a quick way to determine if the browser is maximized
// based on some assumptions, like:
// - the combined panel/dock size being less than or equal to 64 pixels
// - having a browser within tolerance is probably maximized (not
positioned manually)
var browserMaximized = (screen.width - window.outerWidth) +
(screen.height - window.outerHeight) <= 64;

// OS & arch
var platform = navigator.platform;
var bitness = !!navigator.platform.match(/64/);

// Browser being used
var currentBrowser = navigator.userAgent;

It would just have to be reported back to a Fedora server. It wouldn't
be super-accurate, but it would give people an idea.

You can see it in action @ https://jsfiddle.net/fcbgadqm/16/
(bottom-right pane has the output on page load and window resize;
tested in Firefox, Chromium, and Epiphany)

If somewhat fresh results of these stats exist elsewhere, it'd be good
to know, so we can figure out how to target the best screen resolutions
for not just Anaconda, but also various websites and other software we
develop.


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

Sent from my Android device with K-9 Mail. Please excuse my brevity.

@garrett garrett self-assigned this Jan 14, 2016
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

No branches or pull requests

4 participants