Processing Math: Done
No jsMath TeX fonts found -- using unicode fonts instead.
This may be slow and might not print well.
Use the jsMath control panel to get additional information.
jsMath Control PanelHide this Message

jsMath
Differences between revisions 4 and 13 (spanning 9 versions)
⇤ ← Revision 4 as of 2008-03-30 21:22:38 →
Size: 918
Editor: schilly
Comment:
← Revision 13 as of 2017-03-22 00:03:17 → ⇥
Size: 1819
Editor: mrennekamp
Comment: follow naming scheme
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from interactSuggestions
Line 9: Line 10:
    5. Show current value next to slider control, perhaps also min/max: e.g. [min] |----------------[-]----| value [max]     5. Show current value next to slider control, perhaps also min/max: e.g. {{{[min] |----------------[V]----| value [max]}}}
    6. Add a 'point' control. One way to do it is to display two text boxes with the x and y coordinates for the point (measured in [0,1] coordinates) and a big colored dot. Whenever the dot is dragged onto an image, the x and y coordinates are updated to the ratio of the click coordinates to the image size. Less general than 4, but maybe simpler to implement.
    7. Integrate [[pyjamas|http://pyjs.org/]] into Sage so that we can build interactive widgets using standard object-oriented code. Include a new Callback_Canvas widget, such that a click or drag event on the Callback_Canvas triggers a call to the server that updates the image within the Callback_Canvas, or performs any other change in the interact.

== Links ==
 * [[http://code.google.com/p/playwith/wiki/Screenshots|R package playwith]] - similar idea, inside a gtk2 window

This is a informal page for coordinating suggestions on improving the interact command. At some point it should be either deleted, turned into a trac ticket, or more formal enhancement proposal. Any commentary on the nuts and bolts of what code should be changed would be appreciated as well.

  • Improvement/Suggestion list
    1. Input boxes should have a changable length - sometimes longer inputs are necessary, and these are not handled gracefully.
    2. Controls placed horizontally - it would save a lot of screen real estate if controls could be placed next to each other.
    3. Controls changing state of other controls - currently this is not possible.
    4. Image input - for example, being able to click and drag a point in a displayed image. Probably hard to implement.

    5. Show current value next to slider control, perhaps also min/max: e.g. [min] |----------------[V]----| value [max]

    6. Add a 'point' control. One way to do it is to display two text boxes with the x and y coordinates for the point (measured in [0,1] coordinates) and a big colored dot. Whenever the dot is dragged onto an image, the x and y coordinates are updated to the ratio of the click coordinates to the image size. Less general than 4, but maybe simpler to implement.

    7. Integrate http://pyjs.org/ into Sage so that we can build interactive widgets using standard object-oriented code. Include a new Callback_Canvas widget, such that a click or drag event on the Callback_Canvas triggers a call to the server that updates the image within the Callback_Canvas, or performs any other change in the interact.

interact/Suggestions (last edited 2017-03-22 00:03:17 by mrennekamp)