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

History Mechanism #27

Closed
kanitw opened this issue Jan 14, 2015 · 7 comments
Closed

History Mechanism #27

kanitw opened this issue Jan 14, 2015 · 7 comments
Assignees
Labels
Milestone

Comments

@kanitw
Copy link
Member

kanitw commented Jan 14, 2015

Enable Undo (and Redo?)

@kanitw kanitw added the Feature label Jan 14, 2015
@kanitw kanitw added this to the User Study milestone Jan 14, 2015
@domoritz
Copy link
Member

We should use https://github.com/decipherinc/angular-history or https://github.com/Blitzen/Angular-Chronicle but it seems to be a good idea to add reactive data propagation first.

Is this required for the user study? if yes, I can look into it.

@kanitw
Copy link
Member Author

kanitw commented Jan 27, 2015

Recording User Interaction is required.
Next/Back button is not strictly required but it seems like UI design 101 to provide undo mechanism.

@domoritz
Copy link
Member

but it seems like UI design 101

Definitely

@kanitw
Copy link
Member Author

kanitw commented Jan 31, 2015

It would be also great to save program’s state via cookie so when browserify syncs, we do not have to start all over again.

@domoritz
Copy link
Member

domoritz commented Feb 1, 2015

Related #26

@kanitw
Copy link
Member Author

kanitw commented Feb 4, 2015

We need to make sure that clicking browser’s back/next/refresh button doesn’t crash our experiment

@domoritz
Copy link
Member

domoritz commented Feb 4, 2015

I'll add this this weekend.

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

No branches or pull requests

2 participants