Abstract visualizers away from being tied specifically to p5 #41
Labels
future
Not being actively worked on, but might be worked on in the future
Comments
liammulh
added
the
future
|
Example libraries that one might want to use for visualization: three.js to produce 3D graphics; vis.js for networks and other data structures, including possibly "ordinary" graphs of sequence values; and/or bootstrap-table for tabular data (and quite possibly VisualizerDifference should really be done with a table library rather than p5). |
|
See #120 (comment) for how we will proceed. |
gwhitney
added a commit
to gwhitney/frontscope
that referenced
this issue
Oct 20, 2022
Adds a new module `shared/math` that has some convenience functions for math in frontscope, especially for working with bigints. Specifically this first revision has safeNumber, for converting to a number with a check for loss of accuracy; floorSqrt for finding a bigint square root; modulo for the mathematician's modulo of bigints; and powmod for calculating a power of a number to some modulus (much more efficiently than exponentiating and then modding). Also provides documentation and tests for the new features and a guide to using bigints in frontscope. Resolves numberscope#163. Partially addresses numberscope#41. Does the first half of numberscope#172.
katestange
pushed a commit
that referenced
this issue
Oct 27, 2022
* feat: math utilities for the frontscope Adds a new module `shared/math` that has some convenience functions for math in frontscope, especially for working with bigints. Specifically this first revision has safeNumber, for converting to a number with a check for loss of accuracy; floorSqrt for finding a bigint square root; modulo for the mathematician's modulo of bigints; and powmod for calculating a power of a number to some modulus (much more efficiently than exponentiating and then modding). Also provides documentation and tests for the new features and a guide to using bigints in frontscope. Resolves #163. Partially addresses #41. Does the first half of #172. * doc(CONTRIBUTING): make the comment on apis readable on github * feat(math): Natural log for bigints * docs/test: Respond to Kate review
|
Accomplished via #277. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We envision that there may be network visualizers and/or table visualizers and/or ... that will want to use other rendering libraries besides p5. Right now, the VisualizerInterface explicitly supposes that there will be a p5 sketch associated with the visualizer. It should be divided into a generic interface that is agnostic about what is doing the rendering, and a specialized P5VisualizerInterface that extends the generic one and assumes there's a p5 sketch, so that other sorts of visualizers can be introduced into the hierarchy.
The text was updated successfully, but these errors were encountered: