Open mairin opened 9 years ago
+1. My only concern is if Gtk would support the CSS-media-query equivalent that this would require
+1 That would be great for most screen devices.
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.
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 notifications@github.com 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: https://github.com/fedoradesign/anaconda/issues/9#issuecomment-171612817
Sent from my Android device with K-9 Mail. Please excuse my brevity.
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: