Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

makeArrayGadget improvements #22

Open
gergness opened this issue Mar 11, 2020 · 1 comment
Open

makeArrayGadget improvements #22

gergness opened this issue Mar 11, 2020 · 1 comment

Comments

@gergness
Copy link
Contributor

gergness commented Mar 11, 2020

The makeArrayGadget() doesn't do quite what Matt wanted. I also saw Natlia is starting design work on this exact same issue, so I don't know if we should work on the R package as a way to take pressure off, or if it would take away from the web app.

Current workflow:Screen 1:
Screen Shot 2020-03-10 at 2 12 14 PM

Screen 2:
Screen Shot 2020-03-10 at 2 12 43 PM

After hitting "Done" in top right, code is inserted into the editor pane.

Proposed improvements:

  1. Add option to choose between using makeArray and deriveArray (meaning existing variables aren't always forced to move inside array) (toggle on second screen)

  2. Add ability to select a single existing array variable (as an alternative to the current behavior where you can select multiple existing 1D variables)

  3. Remove "Done" button on the second screen, replace with buttons on bottom to either 1) Copy code to editor, or 2) Run code

@malecki
Copy link
Contributor

malecki commented Mar 11, 2020

1: is it feasible to always derive and not make users have to know about the distinction?
2,3: if possible — any sense of complexity/estimate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants