logo

blog

My website can't be that messy, right? git clone https://hacktivis.me/git/blog.git

decreases of usability.shtml (7337B)

    

  1. <!DOCTYPE html>
  2. <html xmlns="http://www.w3.org/1999/xhtml">
  3. 	<head>
  4. <!--#include file="/templates/head.shtml" -->
  5. 		<title>Decreases of usability — lanodan’s cyber-home</title>
  6. 	</head>
  7. 	<body>
  8. <!--#include file="/templates/en/nav.shtml" -->
  9. 		<main>
  10. 			<h1>Decreases of usability</h1>
  11. 			<p>Inspired by <a href="https://datagubbe.se/decusab/">The Decline of Usability | datagubbe.se</a>, which I would recommend reading.</p>
  13. 			<h2 id="ProgressBar"><a href="#ProgressBar">§</a> Progress bars</h2>
  14. 			<p>Few decades back progress bars often used to have nice separation with blocks so you could notice progress and count rough percentage easily if a number wasn't present. Nowadays if you don't only get a spinner or some waiting screen (games…) you have a simple-ass line, if there is no percentage next to it, you're basically lost with something where you can only get an idea of the quarters instead of a good indication of the dozens. Imagine having something like your mercure-based thermometer with no units on it.</p>
  15. 			<p>Nowadays you basically have to keep the pointer on the progress bar to notice progress. Great, as if doing separators was any kind of an hard thing to do.</p>
  17. 			<h2 id="documentation"><a href="#documentation">§</a> Documentation</h2>
  18. 			<p>I know, 90% of folks do not read them. But it doesn't means that it's completely useless, documentation can allow to repair a program or reimplement it (software rot). Some programs have litterally no documentation for their settings, Firefox is one example of that, specially for the <code>about:config</code>, meanwhile the linux kernel, the thing supposed to be hard to configure, like if you would need to be a confirmed wizard? Well each setting has a nice documentation, there is some pre-made configs for you, you can export/import your settings, and there is <a href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Documentation?h=v5.6.11">/Documentation/</a> which is useful for the runtime configs or APIs, including internal ones.</p>
  20. 			<h2 id="scrollbars"><a href="#scrollbars">§</a> Scrollbars</h2>
  21. 			<p>I think Ubuntu introduced this one, scrollbars that have something like 5 pixels width maximum and with poping alien buttons when you manage to hover it. Name of the thing in packaged form was named <code>liboverlay</code> and gess what? It looks like it got adopted right into GTK now because I have it on non-configured installs, at least you can toggle it off into GtkSettings (usually lives at <code>~/.config/gtk-3.0/settings.ini</code>) with <code>gtk-overlay-scrolling = false</code></p>
  22. 			<p>As datagubbe pointed out there is also contrast or even just indication issues, sometimes you're left wondering which part is the background and which part is the foreground.</p>
  23. 			<p>Want some system where the scrollbars are glorious? Plan9. Like the rest of the system the UI is simple as fuck but presents everything well. You get to choose how much to scroll on each click based on the position in the scrollbar or directly at a precise position with another click, meanwhile I had to hard-modify my current mouse so I would have less to no friction on the wheel.</p>
  25. 			<h2 id="NonNativeBehaviour"><a href="#NonNativeBehaviour">§</a> Behaviours from other platforms into yours</h2>
  26. 			<p><a href="https://www.jwz.org/blog/2012/04/why-i-use-safari-instead-of-firefox/"><cite>jwz: Why I use Safari instead of Firefox</cite></a>: <q>I don't <i>want</i> your Linux in my Mac. I want my Mac to behave like a Mac. That's why I bought a Mac.</q>. Well Firefox… I don't want your Windows into my Linux (or Unix), if you don't want to maintain behaviour consistent to the platform, maybe keeping on simply using GTK or making a small wrapper, or another toolkit would have been better, but no, you did you own <abbr title="Not Invented Here">NIH</abbr> with XUL, which you're doomed to be the only one using.</p>
  27. 			<p>And this isn't about the Operating System or linux patchwork distro taking things from other systems, because this can sometimes be good (but not always, like do not be a clone, this never works in the end). What should never happen is programs that are part of the operating system context to behave differently like a special snowflake. (to me games are the only exception as they are very standalone in terms of interface and OS interaction)</p> 
  29. 			<h2 id="GtkColorChooser"><a href="#GtkColorChooser">§</a> Gtk3 ColorChooser</h2>
  30. 			<p>GTK 3 came with the deprecation of the GtkColorSelection, which looks like basically any other colorpicker, you have a colorwheel, a way to tweak your color, optionnally a palette, a picker to grab a color from elsewhere, say your design guidelines and you have an entry where you can put a name or a <abbr title="Red Green Blue">RBG</abbr> hexcode.</p>
  31. 			<img loading="lazy" src="/images/GtkColorSelection.png" /> <img loading="lazy" src="/images/GtkColorSelection_palette.png" />
  32. 			<p>And next you have this bullshit, which is a huge usability failure. You are greated with a palette, now I don't know about everyone but how I do is usually pick a color close enough and adjust it with the color wheel. A bit like painting, you pick some pre-made color and you adjust it. Of course you still have the color wheel by pressing the Plus(+) button at the bottom but no way to go back.<br />
  33. 			And let me address the <em>bear</em> (gnome2 icon to me is a bear and that got stuck) in the room: Where is the fucking colorpicker? Why is the color name entry stashed away? I need this shit basically all the time, heck I made a Gtk2 application back in 2012 that I used for years mainly for the colorpicker and getting or putting hexcodes.</p>
  34. 			<img loading="lazy" src="/images/GtkColorChooser.png" /> <img loading="lazy" src="images/GtkColorChooser_custom.png" />
  35. 			<p>Also I have basically no idea how the ColorSquare works, x axis seems to be for the value, y seems to be saturation, okay fine but where do I find back my colors? Also Hue should always be a wheel, here for example adjusting the hue of red is basically impossible. I think this wasn't done by designers but by pure-coders that saw <abbr title="Hue Saturation Value">HSV</abbr> in a barebone way and re-invented a UI for it from scratch. The only improvement here is the alpha/transparency adjustment. So please go back to GtkColorSelection, put this alpha/transparency under the color wheel and it's done.</p>
  36. 			<p>And this is the kind of thing which isn't likely to change much until humans gets a way to see more colors (done) and have it fit into something like <abbr title="Hue Saturation Value">HSV</abbr> or <abbr title="Red Green Blue Alpha">RBGA</abbr>, otherwise it's just something else. and I'm ignoring <abbr title="Cyan Magenta Yellow Key/blacK">CMYK</abbr> because it's for the substractive model which is for paper/painting, while this is for the additive model which is for light (screen, photography, projection), both obeys to a quite different logics/environments and so should probably have different UIs/APIs.</p>
  37. 			<h2>See Also</h2>
  38. 			<ul>
  39. 				<li><a href="https://www.youtube.com/watch?v=AItTqnTsVjA">The GUI should be better. A lot better. — Ross Scott</a></li>
  40. 			</ul>
  41. 		</main>
  42. <!--#include file="/templates/en/footer.shtml" -->
  43. 	</body>
  44. </html>