I wonder how it would do with the djvu codec which tends to have been used specifically for archiving documents. I suppose it is best applied at source if the physical material is at hand.
Might still be worth taking a look at as an experiment since this codec separates text, background and images into different layers, even when converted from another format.
Oh interesting, thank you! I live in Cambridge an often walk past the Sinclair building but I had not heard of Lynx or Ace which are also based in familiar places! https://byte.tsundoku.io/#198301-050
Agree on DAWs. Even though I'm familiar with the general concepts, every time I try out a new one (Logic, Reaper, Ableton), it's quite overwhelming at first. You have a pretty good idea about what's supposed to be there, but the sheer amount of knobs and buttons... But once you get in the flow, you quickly find out it has all the information you need, nothing more nothing less, it becomes second nature.
(Notable omission: GarbageBand. It has the opposite effect, it instantly puts you into action, but becomes more frustrating the more you use it.)
Another, maybe forgotten one is Wavosaur on Windows [1]. Great modularity, one can quickly remove cruft that's not needed, or add a lot of data on waveforms when necessary. I admit being a fan of the Classic Windows era UIs, though. :)
A third, also forgotten one from the Win2k/9x GUI era is maybe Waveshop [2], also a great example of keeping things simple.
Funny thing: I used Reaper for years (occasional pro-level radio production), then had to switch to Pro Tools because of studio demands. Afterwards tried going with Reaper again, but got really overwhelmed with all those endless possibilities for customization. So... I ended up using Ardour, which was easiest to grasp from day one. Really well thought out and polished GUI. Possibly a great example of why it makes sense to have a subscription/payment based, non-free open source project.
Oh, and Audacity up to version 1.26 was also great. After 2.x, it started to add bloat IMO. I remember Eric S. Raymond highlighted it as a great example of modular, unix-y design in "The Art of Unix Programming" [3].
Logic Pro X really impressed me with its accessible UI. Yes, there are a lot of functions, but they don't get in the way, and the important ones are fairly discoverable. Reaper, OTOH, not so much. Its routing is ... flexible, but unfortunately also in places where it doesn't matter, or even gets in the way.
DAWs and audio plugins are a good example. Digital audio workstations can be somewhat varied in UI, but plugins can be vastly different from each other even for two of the same tools.
Creating intuitive interfaces for complex technical controls is challenging. Fabfilter has been a popular developer for years. Oeksound and Denise Audio are great examples too. Newfangled Audio makes good stuff and their limiter elevate handles multiple pages well. They all pack parameters into tight, cohesive UIs that look good and remain intuitive.
Fabfilter often uses submenus that can feel convoluted, but they're arguably necessary given their plugin's depth. Denise Audio takes a different approach with standard, simple UIs across their product line. Everything is visible with no submenus, though they may offer fewer controls overall.
Deciding what controls to expose and how to organize them intuitively presents a unique challenge. Multiple pages like how Newfangled does it works well. I don't find Fabfilter's submenus to be the best but that's often because they are unlabeled and use small, unique icons that are hard to grok. The overall UI for primary features is usually quite good though.
Renoise is a DAW with a very high density tracker UI that I think works well. It is a bit friendlier to new users than any oldschool tracker I have tried to use.
As someone who recently tried to use Blender for an extremely simple task... Blender's UI is absolutely terrible and should not be used as an example of anything except how to design an unintuitive UI.
Professional tools are often made for the efficiency of a professional user and are hard to grok at first glance. Other examples from the parent, like DAWs, suffer from this and Blender is no exception. By all accounts it used to be a lot worse.
I think intuitiveness and density are orthogonal properties (although often both desirable).
Regarding Blender specifically:
Do you have a background in 3D modeling?
I am genuinely curious.
I don't come from an digital art background and I bounced off Blenders UI several times but after doing a tutorial or two now I find I can use it for simple things. I have always wondered how much it was 3D modeling in general vs. Blender specifically.
In a similar case I have used both Inkscape and Illustrator as an amateur and, much as I love open source, there is no comparison. Illustrator was significantly easier to use and worked better.
I definitely get that. When I did 3D modeling, my start in Blender was very rough. After I got used to it and did some tutorials it got much easier to navigate. That was probably a decade ago, so I’m sure it’s only gotten more complex since
Sometimes I watch HOWTOs with Blender and it says stuff like "Hit NumPad +" and it makes me think, damn they going to tell me to start using the META key next?
The Republic of Ireland (the west most region on the first page) isn't part of the United Kingdom. The term for the group of regions shown is 'the British Isles'. See https://qntm.org/uk While it seems like a trivial distinction the whole thing is somewhat fraught (https://en.wikipedia.org/wiki/The_Troubles).
It's about as "trivial" a distinction as considering Crimea (or the entirety of Ukraine, for that matter) a part of Russia.
Many, many people have died for this triviality.
"Somewhat fraught" is a very interesting choice of words, but then again, so is "The Troubles" (when the subject matter is decades of bombings and killings).
I prefer the term “Atlantic Archipelago”. The “British Isles” encompassing a non-british sovereign state is contentious. Other good terms are “Britain and Ireland” or the “British-Irish isles”
pdfs/ 12.5 GiB
pages/ 91.96 GiB (Each page as a .png)
text/ 365.03 MiB (Each page as text)
byte_files/ 55.98 GiB (The 1024x1024 tiles as .jpeg)
I had not heard of https://github.com/lovasoa/dezoomify-rs before, that's really cool!