4f4ba88878
* Add event-based LogMonitor state changes to better handle batch reads Pre-reading hackily used read-all to suppress notifications. But that broke some assumptions about what read-all meant. Furthermore, the Core UI told plugins about read-all rather than the log monitor telling them -- which is really what should be telling them. To address these concerns, LogMonitor now provides an event that both the PluginCore and PluginEventHandler listens to or tracking logging state allowing more granular information about the activities of LogMonitor, including distinguishing between ReadAll and Pre-read batches. Plugins no longer need to track if LogMonitor is in batch-read mode or not -- PluginCore now provides it. I've also converted all built-in plugins to use the new event-based system. The old system is marked deprecated and will go away once other known contributed plugins have converted to the new system. * Change LogMonitorState enum to [Flags], drop 'None' state As requested, and did associated simplifications and cleanup that followed.
Elite Observatory Core
Tool for reading/monitoring Elite Dangerous journals for interesting objects. Successor to the original Elite Observatory, rewritten from scratch using .NET 5.0 and AvaloniaUI.
IMPORTANT
Observatory Core and it's associated plugins are currently in an alpha state and are neither feature-complete nor using a finalised UI. Over the coming weeks I will outline in detail what functionality is missing but still planned, and begin work on getting it to feature parity with the original Elite Observatory.
Omissions to current functionality include:
- Integration with Frontier's Companion API
- Data submission to IGAU
- More that I'm just not thinking of right now
How To Use
Observatory Core differs from the original Elite Observatory in that it is a fully generic reader for the Elite Dangerous journal files, passing those events along to plugins to do the actual work.
Observatory will attempt to locate your Elite Dangerous journal location in its default location, though other locations can be specified from the settings in the "Core" application tab. Due to the variety of possible system configurations this automatic detection does not function under Linux, so all Linux users will need to browse for the correct location.
The "Read All" button will read all journal files in the specified folder, handing their contents over to all loaded worker plugins. "Start Monitor" will begin watching files in the journal folder for changes, and pass new journal lines as they are created, as well as all changes to the status.json file, over to the worker plugins.
In addition to updating the content of their respective UI tabs, some workers can also send notifications, which will be distributed to all notifier plugins, as well as be passed to Observatory Core's native notification popup.
For specifics on what each plugin does, please refer to their respective wiki pages:
If you're interested in Custom Criteria for Explorer in particular you can find the documentation for writing them in the project wiki.
If you want to chat or collaborate with other users of Observatory you can find us either in the Elite Dangerous forum thread for Observatory, or on the Elite Observatory Discord.
For information on how to create a plugin, refer to this article about ObservatoryFramework.
Prerequisites for use
.NET 5, and by extension one of its supported OSes.
Prerequisites for building
C# 9.0, .NET 5.0, AvaloniaUI 0.10.3, and of course ObservatoryFramework.