sethpoulsen / data-structures-playground Goto Github PK

There are a few issues here with the default placement of things:

• Nodes end up on top of each other when created consecutively
• If you point a node to itself, the pointer intersects with the node

Change the type signature of makeLine form

export function makeLine(coords: number[] = [0, 0, 0, 0]) 

to

export function makeLine(start: Point, end: Point) 

where

type Point = { x: number, y: number }

for better type safety and so its easier to call.

Let user write code to directly manipulate the data structure diagram.

Start with C++, since that's what they use in CS 225 at UIUC.

Also, generate code to show the user based on the operations they did.

Options

• Circle vs. Box
• Multibox (space for pointer)
• head/tail pointer/no pointer and label/no label
• lines or arrows for pointers
• pointer starts in box/on edge of box
• wrapper around linked list
• wrapper around Node
• Nodes arranged non-linear/linear
• Implict NULL vs. word NULL vs. empty set vs. slash vs. ground symbol
• memory address of node
• memory address of next node

Currently, you can tab through all the control boxes in a sensible order, which is good. As an improvement, we should also have

• shortcuts for undo/redo
• pressing "enter" while on an input element should click the button that is in that control box, e.g. after typing "5" in the create node input box, then pushing enter, the "create node" button should be clicked
• any other useful keyboard interactions we think of

Pointer variable names should be validated the same as C language variable names, and should be checked for duplicates.

Operations:

• create Node
• create pointer
• reassign pointer

The UI is all there, but none of it works:

Currently if we have a pointer p and p->next is NULL, then attempting to reassign another pointer to p->next does nothing, but it actually should work just fine.

There should also be the word NULL as part of the input list for reassigning pointers, so you can just reassign anything to NULL whenever you want.

Each file should have exactly one newline at the end

Let the user provide a comma separated list of numbers to initialize the linked list.

I think users are going to want this feature.

We're going to need to come up with some sort of sensible versioning system to make it happen.

Some automated tests would be really nice.

Sure, unit test would be nice, but for a start lets just get some simple integration tests going:

1. Feed the LinkedList a list of actions to perform
2. verify that the constructed list is correct

This will at least help us make sure we don't ever completely break things.

Ideally, we would have a development build to run while developing, then a release build which runs all the test and does all the linting, and which is automatically built anytime someone opens a pull request or pushes to mainline.

I assume people will want to be able to delete nodes and pointers somehow, even when in the mode where nodes that are left dangling are still drawn on the screen.

We need to come up with what the UI should be like, then implement it.