apoch / curvature Goto Github PK

Brainstorm content and implement something cool for Project Overviews.

Currently the UI shows a blank area when no behavior set object is selected (including but not limited to when no object exists). Come up with a better solution for this that makes effective use of space.

Several seconds seem to elapse for a couple of clicks on Advance 100ms. Double check the plumbing.

Currently all inputs are set up to assume a fixed range. Extend support for parameterizing ranges such that inputs can have a custom range on each consideration.

As part of this, make sure that the higher-level experimentation modes merge the ranges correctly, i.e. all possible values for an input should be settable from the experimentation UI without needing a slider per range.

Have rename events maintain the selected item in each appropriate listview.

Do a thorough code review and clean up all the annoying stuff.

Some concepts are named inconsistently, e.g. "EditProject" vs "EditedProject" vs "EditingProject" etc.

Add UI functionality for deleting considerations from a behavior.

Introduce a guided step-by-step process for creating new response curves. Should be a complete solution for adding curves with various common shapes. Probably encompasses/supplants preset curve UI.

Do a complete pass over all UI elements for tab ordering.

The Random Seed dropdown UI should be completed to support actual selection of a random number seed for a simulation. Tracking a history of selected seeds would be cool.

Implement loading/saving of projects. Probably worth waiting on this until most of the functionality is in place to avoid versioning nightmares.

Creating a bunch of content does not cause the Project tab stats to refresh directly; other events can force a refresh (such as renaming the project or saving/reloading) but it'd be preferable if the numbers were always accurate. Just for fun.

Scenario locations need properties for things like tagging.

Needs design, but add a UI layer for setting up archetypes of characters.

Add offset adjustment buttons and/or click-and-drag support to the response curve editor.

One example: create a behavior and add a consideration to it. Rename the consideration. The list of considerations does not refresh until the behavior is re-clicked.

Add some kind of iconography to the buttons that create objects.

Implement project "dirty" flag such that edits flag a project as dirty and saving clears the flag.

Implement a few features to make the scenario rendering nicer:

• Configurable colors for each agent/location
• Implement and display facing-direction for each agent
• Add simple animations for actions/intentions

Add a checkbox in Scenarios so that agents can be given a random (based on a user-specified seed!) start location. Probably needs a "suggested boundary" concept or something similar to help keep things from going crazy.

Set up an input axis with range of [0,1] and clamp its consideration range to 1. The input slider on the behavior scoring tab (among other places) will be busted.

When a consideration uses an input axis that has an enumeration constraint, the Consideration Wizard dialog talks about scaling the input value from 0 to 1 by dividing by the parameter. This prose is correct for fixed-range params but wrong for enumerations. Detect if the parameter being chosen is an enumeration and dynamically change the prose as necessary.

• Pick a thing to rename, such as an Input Axis
• Click the rename icon (currently a blue pencil)
• Click the icon again

A pair of input fields will appear and the rename functionality will start behaving badly.

Any nameable object should trigger UI updates when it is renamed.

As demonstrated in the image below:

The button to create Behavior/Archetype/Scenario is almost not accessible.
Also, the Considerations UI inside Behaviors Tab (Edit Consideration) is not visible.
Something similar happens in the Behavior set tab (right part)

Changing the size of the window does not solve the problem.

Build a UI for placing characters in a simple 2D world and having them "think" through their respective behavior sets.

Implement keyboard shortcuts for menu items and common navigation actions/etc.

Repro:

• Create a consideration on a behavior
• Input some values in the wizard
• Click the consideration in the list of considerations for the behavior
• Click the Wizard button to the right of the Input dropdown
• Scramble some values
• Click Cancel instead of OK
• De-select and re-select the behavior

The scrambled values will be reflected in the consideration editor even though the dialog was canceled. This should instead roll back the dialog's changes to the state the consideration was in prior to opening the wizard.

Currently when editing an input axis there is UI for selecting exactly what inputs will be used (and where they will come from). Unfortunately this UI does nothing.

The logs of decisions in scenario mode do not record the (raw) input values of various properties used to make decisions; only the normalized input scores. See if this is viable to add.

A number of hint links in the UI point to non-existent wiki documentation. There are also pages on the existing wiki that don't link to anything because the thing they should link to has not yet been written.

Do some writing!

Do a pass on all UI and make sure terms are consistently used.

Currently the UI shows a blank area when no scenario object is selected (including but not limited to when no object exists). Come up with a better solution for this that makes effective use of space.

Currently the UI shows a blank area when no behavior object is selected (including but not limited to when no object exists). Come up with a better solution for this that makes effective use of space.

Consider moving all controls into a single horizontal row instead of the current two-row split.

Finish design and implementation/UI for enumerated parameters.

Currently the UI shows a blank area when no archetype object is selected (including but not limited to when no object exists). Come up with a better solution for this that makes effective use of space.

Scenario locations can currently be added but not modified or removed.

The consideration wizard text needs some attention, especially the last tab on naming.

If two inputs are provided that read the same KB record but use a different origin (me vs. target) the Union function will still be called and (rightfully) barf out an exception.

Add context menu item and other applicable UI to enable renaming of content objects.

When using the Curve Preset dialog, the selected preset is not successfully applied to the project even if OK is clicked.

Implement the many-axis compensation formula into the scoring system, so that decisions with many inputs are not artificially penalized.

Add inspection capabilities so that agent thought processes can be monitored and debugged during the playback of a scenario.

Editing content in a Scenario does not mark the project as having unsaved changes.

Adjust the output of numbers in Scenario Logs to 3 decimal places.

Scenario agents need a Delete button.

Rearrange the data hierarchy (and UI) so that behaviors are a soup and behavior sets are assembled piecemeal from the list of existing behaviors. Consider adding a "behavior category" ply to the hierarchy, so that the behavior soup is not unwieldy.

Complete the implementation of object deletion for:

• Behavior sets
• Archetypes
• Scenarios