For the demo, use screenshots to fake to tools panel and the files panel in the sidebar.

Work with @Sheyne

Plugins should be able to define the set of properties for every node/edge. This fulfills part of issue #1

Right now you can only connect two different nodes.

Hit detection needs to be updated for the new bezier edges. Either use the technique of mapping drawables to hit functions or utilize the native canvas hit regions.

The currently selected graph needs to change on tab switch. Currently the previous graph stays selected. Even if the tab was closed.

Lets go over these files and document them so I can transfer control of them to you.

Right now they are just straight lines with no direction indicated. Simply make sure that it is an arrow instead of a line.

This lists files in the current directory similar to Atom or Visual Studio Code.

The properties panel needs these updates to be more maintainable/readable. #58 laid the groundwork for this and has some relevant discussion.

When using the like parameter for createEdge, the properties of the like edge are not carried over to the newly created edge. In particular, the label is not set. I assume the same issue is the case for createNode.

Users should be able to write reusable tests as well as execute them on a graph. This fulfills part of the requirements of issue #7

This is the menu responsible for standard menu stuff like saving, loading, exporting, etc. While it is marked for the Prototype, it is an optional feature at that stage but is required for Alpha.

A plugin should be able to declare itself as as part of a group of plugins (such as the formal languages and automata package (FLAP) group). This fulfills part of issue #1

Right now, there is pretty much no integration between the components. These should be combined together into a single Angular app.

The graph editor needs to be able to handle user-defined drawing behavior for nodes and edges in addition to styling properties.

There should be menu actions for saving and loading a graph. Relates to #16 #3. Needs to deal with the bridge between electron and angular to access the file system.

This will be a command line version of the JavaScript api in issue #8 for enabling easy use from other programming languages besides JavaScript.

Non-black borders look weird on my machine. It looks like it always draws a black border before drawing the colored border.

Selection messes with the look of a node/edge. Makes preview difficult. So for selected entities, draw a blue "shadow" (or larger thickness edge) and then draw the node/edge with no change to its styling on top.

For input gestures, pinching should affect zoom and two-touch dragging should affect pan.

Plugins should be able to be written in order to handle graph based programming languages that Sinap was not originally designed for.

This panel is the comprised of the graph editor and has tabs to indicate multiple open documents.

This component is responsible for rendering and manipulating graphs and will directly manipulate the HTML canvas rather than being itself written in HTML.

When the user wants to create or move an edge, there needs to be some visual feedback indicating whether or not the edge can be successfully moved or created on the destination node.

Right now nodes have additional edges overlap. These should instead adjust so that both edges are visible. This obviously can not be done until issue #20 is accomplished.

I think it’d make sense if when dragging an element it selects it before. Currently it selects an element on mouseup when you’re done dragging. (Or, don't select an element if just dragging it.)

Copy/paste shortcuts behave weird within electron. Without menu items for these, the functionality doesn't work.

The lines:

    let rect = makeRect(
      e.source.x, e.source.y,
      e.destination.x, e.destination.y
    );

in drawEdge of graph-editor.component throw an error the first time an edge is created.

Currently an edge is created by clicking and holding on a node for some delay. Change the implementation so that an edge can be created by clicking from some border region around the edge of a node. The region should be highlighted in some way to indicate that an edge will be created if clicked from within.

This panel is responsible for things like tests as well as the REPL interface for interpreters.

Graphs will be represented as a list of nodes and edges in JSON with any semantic properties contained therein.

If possible, two semantically equivalent graphs should have the identical serialization. However, if that is not possible, then they should be as diffable as possible (such as through using UUIDs instead of an incremental id).

This fulfills part of issue #1

Actually handle structs with arbitrary fields and list the field names. If we're not going to show the field names then position should be a SinapTuple

These interfaces are to be written for easy scripting and use of existing interpreters (for instance a headless Jenkins automated test server). This will be closely related to the plugin API ( issue #1 ) but differs in emphasis. This API will be focused at generating and running Sinap programs using given plugins.

This panel displays the current properties of a selected component such as whether a node is a start/end node for automata.

Graphs should be able to describe various things about nodes, edges, as well as entire graphs such as what comprises a valid graph entity and the type of input to a graph.

Currently the selection box only works on nodes and only selects a node if the center of the node is in the selection box. Any edges connected to the selected node are also added to the selection set.

The selection box needs to be able to add components to the selection set if any part of a component is within the select region. E.g. if an edge passes through the select region, it should be added to the selection set.

If you open 2graph-sinap.sinap and try to select and move all the nodes, it takes many seconds to complete the move.

Plugins should be able to describe various metadata properties about themselves such as name, version, author, licence, etc. This fulfills part of issue #1

1. Everything to do with computed properties on PropertiedEntities
2. The interface for a graph that's passed to interpreters
3. graph.ts, specifically the handler argument that most constructors take
   and the way that changes are detected and propagated.

This component should accept some input from the user and immediately evaluate the input, displaying the result (similar to a REPL in Python, LISP, etc.). This fulfills part of issue #7

The arrows aren't getting drawn for edges

pertains to #2

Right now it acts like MS Paint but should just have some display for nodes/edges. This fulfills part of issue #2