sbenthall / dstny Goto Github PK

so that the header issue is less annoying

When a metadata property is made, user should be able to say what type it is (say, with a radio button)

If it's text, then it should be editable with a text box.
If its a boolean, then it should be editable with a checkbox.

Whenever the metadata property is edited, these type options should be available but should open to the current type of the property, with its current value in place. Switching back and forth should preserve data in each.

Flask is giving grief on deployment, and others will be more likely to get involved if this is written in Django.

So, onward and upward.

allow users to rename nodes

ass boilerplate css for cross-browser compatibility and tweak for niceness

To show error, edit a metadata item, making it a string, and include some double quotes in it.

float right the metadata controls (edit, remove, etc.)

In the index, when a node is deleted it should also clear out the anchor links listed under other nodes

Currently metadata records are displayed in an arbitrary order.

One could imagine their order being instead configurable so that, for example, a 'summary' field could come first.

make the draw dependency graph horizontal

for metadata value edits, rather than going to a separate page this should be doable in the same view that the metadata is viewed in (ajaxy)

include an image on node pages showing the local dependencies (graphviz output)

there is a flicker on the edit metadata view due when there is a boolean metadata because it switches the input element after an AJAX request. Fix it.

the dependency links in the index should just go to the node page not be anchors

give an endpoint for a dynamically rendered (visual) graph (could be a .png) from the graph data.

Slashes in a node name aren't escaped and so break the program on URL parsing

Currently the persistence of dstny is very fragile because it is stored as a flat file with no history. It should be versioned with some VCS like SVN or bzr or git so that there is a revision history and the ability to roll back changes.

Allow users to rename metadata keys from the node view

cut out the in-line css and put it into an external style sheet linked to in the layout template

a gui widget for editing a list of elements (strings?) if the value of a metadata entry is a list.

use json-schema for this. it's cool!

When multiple types of metadata are allowed (i.e., boolean, category, etc.), then when a user edits metadata they should be able to change the type of the metadata on the fly.

use a fixed width to keep it central

moving the remove span into a list broke its functionality to remove the containing metadata div when clicked.

When adding a link to another node, autocomplete on the list of nodes

The graph output from the /draw endpoint should be styled according to the properties of the nodes and edges from the jsgn representation.

Configuring this style should involve a mapping from types and properties to graphviz styles.

Maybe something cascading like CSS?

allow radio button metadata properties.

users should be able to add new properties at will but existing properties should be in place. So, a node's property is both a set of options and the option chosen. The UI lets them add new options (and remove some).

The idea is to given maximal flexibility while making it easier for the user to use an existing option. The node template can give the user the start.

as an API move that will help with other tickets, put a GET endpoint at /node/:id/metadata that returns all of a node's metadata as a JSON object.

Allow node renaming

when adding a link from a node, use the node_template instead of creating a blank node