This is a heads-up that EDDI 2 is on the way.
EDDI started out life as a VoiceAttack plugin, but in fact doesn't have that much interaction with VoiceAttack outside of publishing a large number of variables for use in scripts. As such, the next release of EDDI is moving away from requiring VoiceAttack and runs as a standalone program.
EDDI now acts as a message hub, with monitors that generate messages and responders that act on them. The only monitors in place today are for the netlog and the journal. There is a slightly wider range of responders today, including:
Events are individual classes (e.g. DockedEvent) and contain well-formatted information using appropriate types and with links to common objects (ships, stations, systems etc) for more detail.
If you are thinking of writing some additional functionality for Elite it might be worth considering using EDDI as the base for your code. It means that you don't have to carry out all of the tedious work of reading log files, formatting them, translating the FD item keys in to sane names, etc. and can instead focus on your own features.
Right now EDDI is under pretty heavy development as it gets ready for the 2.2 release. If you have an idea for a program that uses information from the journal (or elsewhere) and would like to know if EDDI can cut down your development time then feel free to ask away in this thread and I'll let you know if it's possible and of course help you to integrate your idea with EDDI.
EDDI started out life as a VoiceAttack plugin, but in fact doesn't have that much interaction with VoiceAttack outside of publishing a large number of variables for use in scripts. As such, the next release of EDDI is moving away from requiring VoiceAttack and runs as a standalone program.
EDDI now acts as a message hub, with monitors that generate messages and responders that act on them. The only monitors in place today are for the netlog and the journal. There is a slightly wider range of responders today, including:
- A speech responder, which reads scripts for each relevant event
- An EDSM responder, which sends real-time flight logs to EDSM
- An EDDN responder, which sends relevant journal entries such as market and outfitting information to EDDN
- A VoiceAttack responder, which populates VoiceAttack variables with up-to-date values and triggers VoiceAttack events
Events are individual classes (e.g. DockedEvent) and contain well-formatted information using appropriate types and with links to common objects (ships, stations, systems etc) for more detail.
If you are thinking of writing some additional functionality for Elite it might be worth considering using EDDI as the base for your code. It means that you don't have to carry out all of the tedious work of reading log files, formatting them, translating the FD item keys in to sane names, etc. and can instead focus on your own features.
Right now EDDI is under pretty heavy development as it gets ready for the 2.2 release. If you have an idea for a program that uses information from the journal (or elsewhere) and would like to know if EDDI can cut down your development time then feel free to ask away in this thread and I'll let you know if it's possible and of course help you to integrate your idea with EDDI.