How, after over 30 years of graphical user interfaces, have we not managed to stop modal dialog boxes from popping up and intercepting keyboard strokes while in the middle of typing a sentence?
Back in 1991, the sysops of the "STaTus BBS" in New Zealand created a #GUI for their board.
The system was powered by "Instant Graphics and Sound," a plain-text vector graphics scripting language for the Atari ST similar to RIPscrip, but predating it by several years.
Here's a video showing an IGS demo they made to give an idea of their impressive "GEM Desktop" #BBS interface:
If you're wondering why #java applications have a bad rep for #GUI#accessibility: the default GUI frameworks (SWT, JavaFX, Swing) are not accessible out of the box. None of the components support the keyboard shortcuts available on the various operating systems. It's like they were designed to be as different from everything else as possible. Thinking different hurts accessibility. Do better.
Sometimes I decide to blame #Windows for something, only to check and realise that I haven't rebooted for two weeks and hence should give it the benefit of the doubt. Then I remember that #Linux on my #RaspberryPi can go years without restarting and I'm right back to blaiming Windows again. Then I start to think that the #Pi doesn't run a #GUI so that's maybe not a fair comparison and... I should probably just stop thinking and reboot.
v1.0 then:
“Perl is kind of designed to make #awk and #sed semi-obsolete […] The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal).” https://github.com/Perl/perl5/releases/tag/perl-1.0
Let me start this by saying that I know there are people and creators out there this absolutely does not apply to, I just need to vent. I understand that different #programming languages are going to have different ways they set up the #GUI but surely if the #program is already complete and the various elements like buttons, check boxes, drop downs and so forth are there it doesn't take but a few minutes to go back into where they get created on a static display and to put #labels on them so that a #screenreader can detect them properly. I really hate pulling the #blind card, but DriveThruRPG has repeatedly been told they have accessibility issues and yet they just don't seem to care. They just continue to either give the excuse of we're working on a redesign of the website (been happeneing for years now apparently and they can't spare anyone to look at anything else), or they simply just don't care. That latter being mostly involved with the watermark they put on their pdf's. It completely destroys the accessibility that the publisher works so hard on and yet they are unwilling to even consider examining it, nor do they seem inclined to inform the publisher's that it is a known issue and that it messing up #accessibility. I know a couple of publishers that I have spoken to directly that admitted they didn't know this fact and they went through a whole testing and debugging process to make their pdf fully accessible with testers. I get that something are going to require #DRM, personally I think that is an entirely different stupid rabbit hole, but if it is required and I'm going to pay money for it, then you should at least take my concerns seriously and find some sort of accomodation. Dealing with a #PDF is already kind of a pain unless they are created just right, adding in the classic layout of 2 columns that most #TTRPG like to use makes that even worse, but then #DriveThruRPG goes and adds this watermark that destroys the whole thing, on top of that a lot of publishers haven't really even bothered to make the #PDF properly accessible to begin with so you have things like bad reading order, tables that are actually images that according to the screen reader perspective are only partly in a table format, then some mishmash of text with hardly any spaces and no line breaks, and worst of all the PDF that you open and find that While there are line breaks and even paragraphs breask there don't seem to be any spaces and the creators of the document thought it would be a grand idea to use multiple different font styles of multiple different sizes in some weird ass layout that inserts things like graphics, tables, notes, and various other elements right in the middle of the text where it only makes sense to a sighted person reading the page. Okay, rant over. I just wish someone would do something, but I guess I'm just too small a demographic for the bigwigs of #TTRPG to listen to.
Dzisiaj artykuł wyjątkowy, bo... nienapisany przeze mnie. Powitajcie Ewelinę, która mam nadzieję, że co jakiś napisze coś o byciu PO oraz swojej pasji, czyli UX. Na pierwszy ogień bierze temat Design Systemu. Zapraszam.
When you discover an interesting tool, and it turns out there's no executable GUI, but to get it running you need to pip a git, hub a stub, sudo a judo, brew a stew, python a cobra and unix a linux… 🤡
📽️ A couple of months ago, travis.media surprised us with an awesome video titled "you need to build a RUST desktop app!!" https://www.youtube.com/watch?v=7aFgeUG9TK4 🦀 Since then, we've noticed a surge in GitHub projects using Slint to create small tax calculators! 💼Coincidence? 🤔 #rustlang#gui#Slint
David Vincze delve into the similarities, advantages, enhancements, challenges, and intricacies of adopting Slint as an alternative to Qt QML. Is the transition to Slint a worthwhile endeavour?
David will discuss this question, exploring the feasibility, benefits, and potential pitfalls of integrating Rust and Slint in the #GUI development landscape. #Rustlang#QtDev@slint
Dive into a live coding session & develop a simple application using @slint
Learn how Slint enables the creation of applications that can run seamlessly across various platforms with minimal adjustments, showcasing the framework’s versatility and efficiency. #RustLang#GUI#Slint
This 1-day workshop at #OxidizeConf begins with an introduction to @slint, a Rust-based declarative #GUI toolkit. By the end of the workshop, you will have built a fully functioning cross-platform application in Rust. #RustLang
why:
std::string a = "Hello world";
if (a.find('r') != std::string::npos)
fmt::println("{}", pos);
else
fmt::println("not found");
and why not:
std::string a = "Hello world";
if (a.contains('r')) // Do member function overloading in the class
fmt::println("{}", pos);
else
fmt::println("not found");
why standard doesn't implement trimming functions for white spaces? why do I always have to rely on iterators for such things... (it's just feels like I've to type too much for a basic functionality)
@jhx@stefano@jcamos@cuddle I'll just finish coding C++ for today. I'm not even sure it's C++ or just "whatever the f** I need to use #Qt for a #GUI with as much non-GUI stuff done in pure #C as possible" 😎
Not a huge fan of #python either, I never liked "syntactic whitespace", and observing the drama trying to get rid of python2 (impossible because breaking changes in 3 and upstreams unable to adapt their build(!) scripts) didn't really change my mind 😂
Python GUIs — A website focused on only python GUIs (www.pythonguis.com)
Learn how to Create Python GUIs with Python & PyQt.