- Added flow for working with editor:
- Allow for changing branches
- Recognize all options, with ease of implementing more
- Allow for exiting the editor
- Move assignment into initialize
- Dialogue should be responsible for the flow of a tree,
not displaying parts of it. With the exception of the prompt, all
display responsibilities fall to Gardner
- Remove functionality that doesn't belong in this module:
- Move printing of trunk to the dialogue class
- Remove tree generation entirely; let other modules generate trees as
they need them
- Style formatting
- Abstract functionality from talk into individual functions:
- display_trunk: Displays the trunk of the branch.
- display_branch: Displays the branch and option list
- get_response: Displays the conversation prompt, and gets the
response
- Of note, this allows the editor to make use of talk functionality
This should probably be on it's own branch, but too many of the changes I made
were already committed.
- Logic for a Plot, basically a data class
- Logic for Spade, the main functionality of the class
- Logic to load and parse the tree
- Functionality for loading the first branch with debugging mode
TO-DO
- Abstract branch display properly into Dialogue
- Abstract tree loading and parsing probably back into Gardner
- Change Gardner to a different name. Like... Druid or something...
- Actually build the editor
- Add logic for Planter, the editor module
- Add logic for catching a bad switch, and reporting accordingly
- Add logic for when no tree is included when required, and reporting
accordingly
- Move YAML file loading from Dialogue/Gardner to here
- Add doc/ directory, so publishing to gh-pages is a bit easier.
- Update .gitignore to not ignore the doc/ directory.
- Move manual documentation directory into new var directory (var/docs)
- Move example dialogue tree into new var directory (var/trees)
- Update YARD to find manual documentation in new var directory
- README.md: Remove unnecessary copyright line
- docs/config_file.md: Update the example YAML file to actually be proper.
- docs/config_file.md: Expand information to cover entire configuration file.
- Example Quest is a meta dialogue, designed to walk the user through
understanding what sapling is, and how it works.
- Used to be the configuration file example, but now it's all grown up and ready
for big-boy pants.
- Change the example configuration file from a tree to a self-documented
reference. You can still run it in sapling, but it's pretty boring.
- Moved previous example configuration to "Example Quest", in the trees
directory.
