Has development on this now stopped?
I've not stopped work on it but for the last couple of years I've been focused more on
Ardent Insight (ardent-insight.com) because I wanted to add features to ICARUS that I wasn't able to because there wasn't a public API that supported them, so I had to go and build something to collect the data from EDDN (
Ardent Collector) and then an API on top of that (
Ardent API) and add the ability to sign in to it to support some of the features I want to be able to add (
Ardent Auth).
I've actually copied a few of the features across from ICARUS into Ardent, for example
the system list view has been ported across - and, while doing that, improved the logic for working out what stations are orbiting what bodies (because that data is missing from the journal) and would like to surface that same improved functionality back into ICARUS.
I'm not sure what I will do next exactly... (1) I could port more features into Ardent, things like engineering and system map views, route plotting, cargo management, etc (which, because the Ardent tools supports sign in can also now support Fleet Carrier and Construction activity) as well as things like UI customization - and expand into features like Power Play or (2) go back and port features into ICARUS and address some of the known issues and gaps in functionality.
I suspect the future will look more like porting ICARUS features into Ardent; mostly because it's MUCH quicker to do feature development in Ardent than ICARUS because there is a bunch of work to do on ICARUS if I want to go back to it; but I do still really like the idea of something that is fully local and only optionally uses 3rd party APIs to enrich the experience.