ptrgags / barter Goto Github PK

On the Barter Web page, there should be an option to select a story from a list. Once I create a story, the user should be able to select between the tutorial and the the story at the very least.

A dropdown at the top of the page would be helpful

Add Travis CI support.

When exiting the program, write to a file (@story_dir/.save.json).

When beginning the program, look for that file. if it exists, read the data from that file instead of starting from scratch.

It would be nice to have more content. Add another story in the future.

• Find some story starters
• Plan a story
• Use the story creator to make a JSON file

Fix the Codacy Ruby style/error prone issues before we merge into master.

It would be nice to add some color to Barter Story Creator. maybe with the colorize gem.

It would be nice if items had sprites associated with them

It would be nice to have a Hidden attribute on options that have a non-empty give_items list. This way, the option will not appear until the user has the required items.

This requires a change in both the frontend and Story Creator.

Add Code climate.

Highlight table rows to show new items in the inventory.

• basic option commands
• Automatically create new situations as needed
• edit option command
• Add items to commands
• Handle back links
• Handle barter links
• Handle one-time links

While the code for Barter Story Creator works, it's rather messy to look at. Here are some things to refactor:

• commands only ever take 1 argument for simplicity. Don't pass in the name of the command.
• Refactor a StoryGraph class that manages the story data and a StoryCreator class that handles the
  CLI
• Refactor prompting for item lists
• See if the tab completion stuff can be refactored

Move data from data.js to Dropbox as a JSON file. Fetch the data from there.

I need to handle Ctrl + C in the REPL to make it equivalent to quit or bye

Add codacy analysis. I want to see how it handles Javascript

Add an item type called a "requirement". This is a type of item that represents fulfilling a requirement. This will be helpful for making options that are only available after completing a requirement.

Usually this item type should be hidden from the user, but the hidden attribute will handle this.

Now that we have GraphViz diagrams, it would be nice to make them look nicer and have more meaning.

• Color the start node differently
• One-time links should be colored/styled differently
• Hidden links should be colored/styled differently
• Back links could possibly be colored/styled differently
• Improve the overall look-and-feel of graphs
• Document the meaning of the above

I implemented tab completion with the GNU readline library, but I do not do this in the subcommands.

Add tab completion for the following things

• Loading filenames
• selecting items when defining item lists

Whoops, forgot to use HTTPs in the CDN URLs. Fix this soon!

The game logic is currently strewn all over the place. Create a new Barter class to manage it.

Add a Gemfile to list dependencies.

I want to write my own story for Barter that actually makes use of the bartering mechanic.

When I was editing the Add Items command, I must have called the wrong function for the help command. The items displayed should be the list of all available items, not the current items for this option.

Add commands to the Story Creator REPL to create and edit situation vertex data.

• Create the story files as needed
• Remove story files with prompt
• Edit situations
• Purge options on deletion
• Move code to Situation.rb

Make a gh-pages branch to host Barter here

I never make favicons. I want a favicon.

Once Version 0.2 is finished, update ptrgags.github.io.

We need the following classes:

• Item
• Situation (Graph Vertex)
• Option (Graph Edge)

It would be nice to use Graphviz to visualize story graphs.

Plain HTML buttons are ugly. Use Bootstrap please.

In the Readme, link to the Codacy badge.

The page has no title! oh noes! Fix it!

Use CoffeeScript to make the code a little nicer.

Tables overflow the parent panel on mobile. Fix this.

Do the following

• Choose a language I don't often use (C# or Ruby maybe?) that results in a program that is easy for even non-programmer users to use without needing to install things.
• Write a spec for the story creator program

Once a spec is made (see #14), implement it in whatever is the chosen language.

Add Codecov once we have unit tests.

Try the Readline library for tab completion of commands.

I listed all the commands for Barter Story Creator, but it would nice to have an example usage for overall story-writing workflow.

I don't currently create the back links in Story Creator. I should do this.

Create a story file that represents the overall plot of the future story.

Right now, clicking an option that requires items removes the item from the inventory. This works for one-time options, but repeatable options cannot be selected again since the items are discarded.

Find a way to avoid this problem. Either don't remove items from the inventory or modify the option the first time it's clicked.

I have the basic commands, but I need to allow existing items to be edited without needing to overwrite them

I tried to show a friend the website for Barter yesterday. I was getting no story data displayed. I'm guessing it's a problem with ES 6 features that are not supported, but I need to learn how to debug iOS devices on Windows.

Right now, Story Creator mentions when situation files are created, but it does not mention when an existing file is used. Make this more consistent.

Find places where new features like Promises will come in handy and refactor.

Forgot to add the set_start_items command

Codacy doesn't like my Python-based code style. I'll need to fix this soon and reconfigure Codacy settings.

Allow an option to prune situations from the graph when there are no non-back options left.

Update the README