neverartful
Joined 11 years ago
Joined 11 years ago
Successor - Visual FoxPro: https://en.wikipedia.org/wiki/Visual_FoxPro
The basic idea is to separate an application's UI semantics from the toolkit that actually renders it. The same application can currently be presented using native Win32, Cocoa/AppKit, Qt6, GTK3, GTK4, Swing, or a web browser. The UI can run locally or be rendered remotely by a client, without the application itself being rewritten for that environment.
I've also been working on a declarative layout format and, lately, a visual designer.
It started as a rewrite of an architecture I worked on many years ago, mostly because I wanted to see how far the idea could be pushed with modern systems. It has turned into a considerably larger project than I expected.
Still private and very much under development, but I'm curious whether other people have run into the same problem: maintaining applications that need to survive changes in GUI toolkits, operating systems, deployment models, or client environments.
One thing I've focused on is producing reports that are actually actionable instead of overwhelming. I'm also putting a lot of effort into reducing false positives—for example with spell checking and URL analysis.
It's still under active development, but it's reached the point where I'm starting to get feedback from other developers and site owners.
I'd love to hear what kinds of website issues you wish existing audit tools did a better job finding.
[email protected]
However, there are many companies with products/services that are just as much for the blind as the sighted (government, insurance, legal, medical, etc.) and many of them don't even make an attempt. The blind are still people and they should have equal access.