mabotkin / complex Goto Github PK

Unsure if speed is an issue for the mapping process, but if so, we can try to use Turbo.js to optimize mapping speeds. Also, my initial plans were to map the entire grid each time, but that proved to be too slow - perhaps a parallelization will make it possible?

Even with brackets, the graphs are inconsitent. Same issue appears with (conj(z))*1

Axes are always in center of screen, regardless of window location. Needs to respond to when the screen is not centered.

Moving the mouse quickly results in a low number of input points. This in turn reduces the number of output points and since it seems the output values are interpolated with a straight line, bad looking mappings are easily produced. Better mappings would be produced if the line in the input plane is interpolated with multiple points and all those points are then mapped to the output plane.

The attached image shows what I'm talking about. The red line is produced by quickly dragging the mouse, and the green line is when moving slowly. I'm saying the mapper should automatically work in such a way so that the output of both of these is of the same "quality".

Make it easy to draw straight lines - also circles and other things if possible.

The way that the Javascript is currently written and organized is a bit of a mess - needs to be fixed if anyone wants to help/has experience in cleaning up Javascript.

It would be helpful if the axes would show numbers, like the example shown below (Desmos's default). Gridlines would be helpful as well.

Create gridlines as to better indicate where Gaussian integers are (x and y grid that updates properly as window range is shifted).