see whatever…

jump to menu

April 20, 2014

Windows program scaling on High-DPI monitors

Filed under: Programming,Win8 — see @ 2:01 pm

There are more and more highdpi screens coming. Laptops like the Yoga 2 (3200×1800 on 13″) or highdpi monitors from Asus, Dell, etc. This is a challenge for the OS as well as programs which have to cope with this. Problems like blurring or tiny menus, text or icons are still very common. Also different operating systems have a different degree of “support” for highdpi.

Apple had their called “Retina” displays earlier, so the OS and third party programs had more time to adjust to the challenges of highdpi display. It took even companies like Adobe some time to adjust but their  Adobe Suite (Photoshop, Illustrator etc) seems to work on “Retina” on OS-X now. There still seem to be some niggles here and there but overall the situation is not that bad.

On Windows the situation is still a bit worse, partly as highdpi devices came later and so are not as common (yet).

So just for myself I tried to find out if the stuff I have installed (not necessarily use ;) on my PC does work or not. I do think older versions of Windows (or OS-X) cannot be be expected to work well so only tested in the current version of Windows which at this day is 8.1 Update 1.

Testing

As I do not have a highdpi monitor yet I adjusted the “Make text and other items larger or smaller” in the Screen Resolution control panel to the highest possible scaling on my machine. As this would be the same settings to adjust on a highdpi monitor I think this should emulate the situation on a real screen sufficiently.

Following the list of programs I tested in ordered by how good they work highdpi. It is quite a subjective and incomplete list of course…

Programs that are OK and work well

  • Windows own things like the File Explorer, CMD shell, and most other Desktop helpers like Task Manager, Control Panel, Defender, Notepad, Snipping Tool, WordPad, etc work well
  • Bvckup 2 (beta 65)
  • FileZilla
  • Firefox (28) – a few icons in menus are blurred but everything else is fine
  • IE (11)
  • Microsoft Movie Maker
  • NotePad++ – menu icons are pixelated and ugly (as always) but appropriately large
  • Office 2013 – not sure if the setup bug for advanced account is fixed yet but that would be a very minor niggle if still present at all
  • Paint (ok, I know…)
  • SourceTree
  • TunnelBear – images are not sharp but UI is
  • Visual Studio 2013 – menu icons could be sharper but else great
  • WebMatrix 3 – menu icons could be sharper but else great
  • Windows Phone App for Desktop (Metro version works anyway)
  • Metro apps (including PDF Viewer and Adobes own Reader, CodeWriter etc)

OKish but with some problems

  • cmder – font-size is adjustable so will work but tabs are small
  • InkScape 0.48.2 – if disabling scaling it actually scales(!) well except some icons so bad
  • Scite – icon bar too small but everything else looks good
  • VLC – icon bar too small but all else good

Blurred but usable

  • Windows helper stuff: Computer Management, Device Manager, Disk Management, Event Viewer, Hyper-V Manager – actally this is a bit surprising but these are all not used very often, maybe except Hyper-V. I did not test any VMs yet though, only the manager itself it blurry
  • Baregrep
  • dbPowerAmp
  • Fiddler 2
  • KeyPass2
  • Notepad! – unexpectedly as this seems quite a new and modern app
  • SE-Explorer
  • Sync-Toy
  • WinMerge
  • XAMPP (Control Panel)

Blurred and unusable

  • Adobe Photoshop 6.0(!) – not small but blurs even the files so basically useless. Even the newest Adobe Suite CC is AFAIK not really good (not blurred but too small, not tested myself though)
  • Calipers (very old 0.x? but free version) – even with disabled scaling in Properties does not work
  • Chrome 34 – I think Google is working on it but it is not there yet, the alternative browsers are though (see above)
  • GIFcam – records wrong part of screen

Some conclusions

I guess just working with text or code is fine on Windows already. You might have to switch to another editor but most seem fine.

Working with graphics is another thing. Sadly programs like the Adobe Suite need some work before becoming usable. In Adobes case this is unexcusable, Inkscape being Open Source and with much less resources is annoying but maybe understandable. (UPDATE: Actually Inkscape is not so bad if you manually disable scaling in compatibility settings for the program). I guess there might be alternatives that work better but I have not looked into that yet.

In general the situation can only get better so not all is lost. I actually read and heard from people who actually used a highdpi screen that the much improved reading experience may already justify the expense of such a display. I guess I for myself wait a bit but am very tempted and am sure my next desktop monitor will be highdpi ;)

If you have any additions of programs that work or work not please add them in the comments, would be very interesting. Thanks!

November 19, 2012

Windows 8

Filed under: Usability,Win8 — see @ 11:24 pm

I wanted to write a bit about Windows 8 for quite some time now but never came round actually doing it. While reading Nielsens Alertbox on Windows 8 I remembered and actually have a reason now to write something, mainly to address some points in Nielsens rant – ok, it is none ;) but some stuff in general too.

 

I have noticed quite a few reactions to Windows 8 until now:

In the beginning (maybe end of 2011/beginning of 2012) most were hostile, later on hate came to that…

Magazines like c’t magazine (maybe one of the leading german computer magazines?) printed pages over pages of basically rants about a system they never even tried properly (as it was not finished at the time). I don’t want to go into details but in my humble opinion they seemed kinda biased at the time. Everything a certain other company did (even the very minor and even to long time OS-X users lame Mountain Lion update) was great, everything MS did was not so.
Strangely enough this has changed in the latest issues. They now are critical as they are supposed to be (and which in one reason I like the mag) but not “ranty” in the sense of almost unfair and biased anymore.Actually Windows 8 seemed to have grown on them?

BTW, haters are to be seen elsewhere too of course. ZDnet seems to have a lot of writers on anything MS does and some like Win8, some just hate it. (Commenting on all the writers of all the online mags and blogs and if all the stuff they write is actually just for the sake of writing anything is another topic ;) .

Even reactions of people I know were partly “hate”. Ironically enough mostly from Windows users. Mac users were actually quite open and somehow interested (not that they would switch but still).

Other reactions by some people I know were simply “ignorant” – not in a negative way though.
I myself have not really  looked into any upcoming version of Windows until at least Service Pack 1 was out.
That is not since Windows 95 ;)
Exception was Windows 7 to which I upgraded almost immediately (not that I disliked Vista much, but Win7 seemed and was mature enough).

And then Windows 8. I got a Windows Phone in 2011 and immediately liked the UI. So guess because of this excitement actually installed the first version of Win8 I could lay my hands on (Consumer Preview in about April 2011?) in dual boot with Windows 7 on my main PC. I did not use CR that much (CR was an early preview) but the later version from I think May/June I gradually used more and more until with the general availability of the RTM (actually even earlier) I hardly ever booted into Windows 7 at all anymore.
So I guess I have used Windows 8 for almost 6 months now. Not exclusively as I still used Win7 (almost daily) at work but still. I actually updated to Win8 at work now too though ;)

 

So I think I have a bit of experience with this new Windows. And NEW it is. So I thought I comment a bit on the issues Nielsen writes about in his Alertbox.

  1.  The double nature of Win8 is jarring at the beginning
    True. At the beginning…
  2. Lack of multiple Windows?
    Desktop still works with multiple windows, just as before (more on that later). And actually there are at least two possible windows in Modern-UI. But true, it might not be the easiest thing to do this. But especially compared to e.g. iPad/Android tablets this is a great and welcome improvement (even if maybe used by more advanced users only).
    BTW, browser apps actually almost only have a single “screen” and not a lot of people complain about this. There would be the option of multiple browser windows at the same time, but almost no one I know uses this setup. There also are tabs in most browsers, but one could simply see multitasking on tablet OSs as this.
  3. Flat style:
    Maybe Nielsen is right, the “extreme flat” is basically a reaction to the extreme skeuomorphic style of especially iOS and maybe both are just too extreme. OTOH, I think MS did not have the chance to go the middle ground… And actually partly think this IS a matter of taste and actually I like it a lot :)
  4. low information density:
    True, but not necessarily bad. And mostly dependent on the app…
  5. Overly live tiles:
    Definitely true. But this totally depends on the app and the live tile it provides. Of course most app providers go over the top (like every website goes over the top with the homepage ;) and maybe MS should at least point this out during app submission (they should not reject apps for this, there are other companies whose name should not be spelled out ;) who would do this but I do hope MS does not). OTOH you can always disable a live tile, again, maybe an average user does not know this or won’t bother.
    AND: I think live tiles are generally the best thing since sliced bread. Ok, ok, not really ;) but still they are verrry useful (if done right like Nielsen points out, e.g. apps like Calendar, Mail etc) and are a big improvement over static icon-filled screens with no real value. I guess there always will be the typical offender with a massively annoying livetile but the same could be said for icons. I think tiles are simply the next evolution of app icons.
    Maybe comparable to static images vs video or a static JPG vs GIF. For some purposes the static version is better (and should be used static) but for some purposes (and especially with all the communication stuff like messaging services, email, social stuff etc) a live tile is just the thing to do (again, if used properly). With tiles you have the choice.
  6. Charms:
    True, they are hidden. A friend of mine did not even find the search in the Store app. And it took me some time to find out how to shut down my PC or print from the Mail app. But actually the charms are very useful once properly understood. I especially like the “Share” charm which makes better (than simple copy&paste) inter-app communicationpossible at all.True, maybe search and esp Devices (used e.g. for printing) need getting used to. But once they are, they are much faster and easier to use than app specific stuff.
    Guess a bit similar to websites where certain things have become almost the norm like the logo in the top left, search in the top right for the exact same reason they are the way now in the Charms bar. And the difference of a website or a single app to an OS feature is that people will get used to the feature just because no app can do different (unlike a website which may screw up almost any best practice – sorry for the use of this terrible term ;)
  7. Gestures:
    Yes, some are complicated. The most complicated (open tasks view) has two simplifications though: Use ALT-TAB if you have a keyboard. Use swipe-in from the left to quickly switch between all open apps.Actually multitasking on touch seems generally hard. Android now has an explicit button for it (copped out ;) . iOS double click and endlessly swipe through a lot of icons (no app preview) is actually worse.So I guess gestures on Win8 could be improved on and maybe we see this in Windows 9 or even in “Blue” already? But again, once you used to the gestures, they are real time savers (on touch at least).
  8. Terrible for PCs:
    Actually I think this is not true. Windows 8 could simply be used like Windows 7. Use the desktop only, maybe even install a start button replacement app (you won’t need one, just try without).
    This is actually the point where I think Nielsen is missing something. Maybe some Modern-UI apps are difficult to use on a non-touch PC. Yes, but there is always a desktop replacement. Windows 7 was complete(!) and Win8 did actually not remove anything from it (again, forget that start button!).Also, maybe people should try a touch PC. I am already happy without one but see e.g. Jeff Atwood’s interesting posts about touch laptops/replacement
  9. One Windows Everywhere:
    Nielsen says: “wrong”. I don’t think so. Just ignoring the fact MS could not simply have developed a completely new and totally unrelated OS (like Apple did with iOS in 2007) now, no one including me would have been interested.
    Nielsen totally ignores the interoperability aspect (or would the term network effect?) of different devices. The web was and still is so successful because it runs everywhere. And yes, the web also has a lot of usability problems, also and maybe because it runs everywhere…E.g. synchronization seems one of the most interesting and also hardest problems and having the same OS (or at least very similar, see Win8 vs WinRT) is a step towards it. And yes Windows 8 is far from perfect. But the direction is exactly right and a needed innovation.

Maybe to summarize a bit.

I think Windows 8 is at least as useful and productive as Windows 7. An average user maybe needs a week to come up to speed with it, but then would even be more productive than with Windows 7 (Windows 8 has quite a few improvement like improved startup time, native opening of a VM or ISO images which is very useful, an improved file explorer including improved libraries and even slightly improved taskbar, etc, etc). The average user probably won’t use much of modern UI (on a normal non-touch PC) but will use the desktop maybe for 95% of the time.
The new Start screen is in this scenario just a glorified Start menu (if using desktop apps only there would even be no live tiles but just program shortcuts just like in Windows 7).

But Windows 8 does add some stuff too and there are already quite useful and impressive Modern-UI apps which show even with keyboard and mouse new ways for programs.

On a touch PC (laptop, all-in-one, touch-monitor or whatever) Windows 8 mostly uses the same programs and apps, but more importantly the same services etc. And compared to other tablet OSs, Windows 8 usability is IMHO already better, just new and needs more time getting used to. I think like Windows Phone the Windows 8 UI is not learned nor liked in 5 minutes. It gets appreciated as you use it. And an OS does not need to be learned in 5 minutes if it is useful in the long run. (For if an OS needs to be liked in 5 minutes is  maybe a problem for marketing, but that is another topic altogether…).

Windows 8 with touch is even better. Or maybe a hybrid laptop is the best machine.

Anyway, there is no real reason not to use Windows 8. The very average user won’t upgrade anyway (he never does) but when getting a new PC/machine/laptop/device Windows 8 is an improvement over Windows 7 even a very average user will be happy with it I believe.

 

October 3, 2012

Touch handling in Windows 8 JS app

Filed under: CSS,HTML5,Javascript,Win8 — see @ 9:12 pm

Documentation for handling touch in Windows 8 style (Metro ;) apps with Javascript is not really sparse but nevertheless or maybe because of that a total mess. Lots of decriptions of classes (random links…),  some blog posts, a few samples which all seem very complicated and a few (better) pointers can even be found at StackOverflow (where else ;) .

Guess as until now I only used wrapper libs like Zepto or a few jQuery plugins for mobile touch handling (mostly iOS) which abstract the hard parts away I expected the code to handle a simple swipe left/right to be simpler.

After playing around a few hours, being lost in the depths of the Microsoft docs I came up with this:

 // define GestureRecognizer
 var recognizer = new Windows.UI.Input.GestureRecognizer();
 recognizer.gestureSettings = Windows.UI.Input.GestureSettings.manipulationTranslateX
 recognizer.addEventListener('manipulationcompleted', function (e) {
   var dx = e.cumulative.translation.x
   // **actually do something, left or right defined by dx > 0 or < 0**
 });

 // actual element which feeds the GestureRecognizer
 var processUp = function (args) {
   try {
     recognizer.processUpEvent(args.currentPoint);
   }
     catch (e) { } // translateYfails ?!
   }
 var swiper = document.querySelector('.swipearea')
 swiper.addEventListener('MSPointerDown', function (args) {
   try {
     recognizer.processDownEvent(args.currentPoint);
   }
     catch (e) { } // translateYfails ?!
   }, false);
 swiper.addEventListener('MSPointerMove', function (args) {
   try {
     recognizer.processMoveEvents(args.intermediatePoints);
   }
     catch (e) { } // translateYfails ?!
   }, false);
 swiper.addEventListener('MSPointerUp', processUp, false);
 swiper.addEventListener('MSPointerCancel', processUp, false);

All in all and in the end almost logical. You preprare a GestureRecognizer and feed it with events from a DOM element. This actually seems capable of doing lots of much more advanced stuff but for a simple swipe left/right gesture seems almost overkill. I wonder if there is something simpler?

In addition I do not understand why the recognizer feeding methods like recognizer.processUpEvent do actually raise an exception if in the above case a up/down swipe is used. One reason is that the element actually has a normal overflow, so the normal scrolling works there. This is the reason the recognizer is set up to only actually handle manipulationTranslateX gestures. But why the additional exceptions?

Anyway, the above seems to work (at least on my desktop and the simulator with both Mouse and BasicTouch mode). Not the simple stuff I have hoped for but maybe I did it all too complicated? Any hints are very much appreciated :)

Powered by WordPress