1,104 karma · joined January 29, 2015
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.
paul@checksitepulse.com
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.
I've been working on a new software product (native Windows) that is for analysis of SQLite databases. It's geared towards non-technical and slightly technical who may not know anything about SQL. The software includes an ER diagram, ability to browse table data, query building, and charting (bar, column, histogram, line, pie, scatter). Trying to get it finished up so that it can be released (hopefully in next few weeks).
Oh? Are you referring to something different from a database's precompiler?
The 3 necessary components for fire are: oxygen, fuel, and ignition source. No stopping the presence of oxygen. Ignition sources are present with lightning strikes (among other things). That leaves fuel as the thing that can be controlled. If you can't reduce the fuel load around your dwelling, it doesn't make any sense to live there. I live in a forest that has experienced a tragic wildfire in the past, so I'm in a similar boat (but without the Santa Ana winds). Keeping fuel away from my home is something that I think about a lot -- and ACT ON a lot.
I have a neighbor who does practically nothing to reduce his fuel load. It's his legal right, but I think it's foolish. He's told me he likes to keep his property "undisturbed". It sounds like there's much of the same thinking that drives policy in California.
The combined practice of: (1) put out any fire immediately, and (2) do nothing to reduce fuel load, makes for a bad combination in the long run. It would seem to me that Californians should have figured these things out decades ago and be the experts on fire risk management. What am I missing?