Dialogue Branch v0.10.0: Core Java API updates
Just in time for the weekend, we released v0.10.0. This update focuses on the core Java library, making it easier to integrate Dialogue Branch into a Java application. Specifically:
- A dialogue in a few lines. Load a project, start a dialogue for a user, and each step comes ready to show: the speaker, the text and the replies. Choosing a reply gives you the next step. The home page has a short example, and the core library documentation has more.
- Replies into other dialogues just work. When a reply leads into another dialogue, the library follows it by itself, in the same language and with the same variables.
- Logs, going back and resuming. Your application can keep a log of the conversation, go back a step, cancel, and pick up a dialogue later from its log, just as the Web Service does.
- Clearer errors. All parse errors in a project are reported together in one exception, and choosing a reply that isn't on offer, or continuing a dialogue that has already ended, gives a clear error. Dialogues can be looked up by name and language, falling back to the source language when there's no translation.
- The command-line tool plays a dialogue in the source language when it isn't translated, and keeps variables from one dialogue to the next.
- Web Service and Studio. An unknown step or reply now gets a 404 Not Found instead of a server error, also in test sessions, and Studio's workspace follows the conversation into the next dialogue.
If you already use the core library directly, a few methods have changed: ActiveDialogue now needs to know where to find other dialogues, and choosing a reply is now a single selectReply(...). The release notes list what to change. The Web Service, Studio and the JavaScript client need no changes.
