4 ms·

Cool! I like this. A couple suggestions: - Instead of asking "Are you sure" to delete an element, just go ahead and delete it, but make it undoable. This allow

by mholt 8y ago

Cool! I like this. A couple suggestions: - Instead of asking "Are you sure" to delete an element, just go ahead and delete it, but make it undoable. This allows for quicker workflow. - If I double-click an empty space, I would like to immediately insert a Text element and start typing, without having to aim the mouse again and click Text. I'll probably be coming back to this when I need some note taking. Thanks for sharing this!

NIckGeek 8y ago
Thanks for the feedback! I like the undo concept, that should be do-able. On the quick-typing thing I was thinking that I could make it so that if you just start typing with the insert thing open, it'll automatically put you in a text element. What do you think about that?
- CuriousSkeptic 8y ago
  I believe Raskins mentions this, and other ideas, in https://en.m.wikipedia.org/wiki/The_Humane_Interface https://en.m.wikipedia.org/wiki/The_Humane_Interface An interesting read none the less
- ygra 8y ago
  Generally for usability I'd suggest to take a good look at OneNote, which in my eyes gets the "type and draw everywhere, with minimal friction" concept very right. And while the underlying data model of such an application may necessitate a collection of objects being scattered on a canvas, that doesn't mean that the interaction model has to follow that directly. So indeed, just let me type anywhere. Another thing that adds friction in my eyes is that when editing text your first click changes the interface into text editing mode where the text neither stays at the position you've seen it before, nor can you actually interact with it with that first click. So when I see a word that I'd like to change and I click there, that will only spawn the edit window for that text object, instead of just placing a cursor there so I can directly edit it.
Sir_Substance 8y ago
>Instead of asking "Are you sure" to delete an element, just go ahead and delete it, but make it undoable. This allows for quicker workflow. Counterpoint: this makes it harder to tell that information that you might want to be really sure is deleted (like someone elses credit card number or your passport number) is actually deleted. The deletion workflow is now delete it->check to see if it's in the undo list->really for reals delete it. That's a way worse UX than a confirm dialog, and more risky for the customer. Remember that your grandmother might be using this to temporarily store her credit card pin.
- dan-robertson 8y ago
  I don’t think clicking yes in a confirm dialog implies that anything was “truly deleted.” It might well still be living in the undo history, other indexes, auto save files, backups, and it could certainly live in memory (especially if it was moved by the garbage collector). It would be very foolish to assume that just because one has clicked “yes, delete” that the data is gone forever.

by mholt 8y ago

NIckGeek 8y ago

Thanks for the feedback! I like the undo concept, that should be do-able. On the quick-typing thing I was thinking that I could make it so that if you just start typing with the insert thing open, it'll automatically put you in a text element. What do you think about that?

CuriousSkeptic 8y ago
I believe Raskins mentions this, and other ideas, in https://en.m.wikipedia.org/wiki/The_Humane_Interface https://en.m.wikipedia.org/wiki/The_Humane_Interface An interesting read none the less
ygra 8y ago
Generally for usability I'd suggest to take a good look at OneNote, which in my eyes gets the "type and draw everywhere, with minimal friction" concept very right. And while the underlying data model of such an application may necessitate a collection of objects being scattered on a canvas, that doesn't mean that the interaction model has to follow that directly. So indeed, just let me type anywhere. Another thing that adds friction in my eyes is that when editing text your first click changes the interface into text editing mode where the text neither stays at the position you've seen it before, nor can you actually interact with it with that first click. So when I see a word that I'd like to change and I click there, that will only spawn the edit window for that text object, instead of just placing a cursor there so I can directly edit it.

Sir_Substance 8y ago

>Instead of asking "Are you sure" to delete an element, just go ahead and delete it, but make it undoable. This allows for quicker workflow. Counterpoint: this makes it harder to tell that information that you might want to be really sure is deleted (like someone elses credit card number or your passport number) is actually deleted. The deletion workflow is now delete it->check to see if it's in the undo list->really for reals delete it. That's a way worse UX than a confirm dialog, and more risky for the customer. Remember that your grandmother might be using this to temporarily store her credit card pin.

dan-robertson 8y ago
I don’t think clicking yes in a confirm dialog implies that anything was “truly deleted.” It might well still be living in the undo history, other indexes, auto save files, backups, and it could certainly live in memory (especially if it was moved by the garbage collector). It would be very foolish to assume that just because one has clicked “yes, delete” that the data is gone forever.