I wouldn't use it, because it doesn't use the main hotkeys for user interaction on the alert box (enter, space) or the confirm box (enter, space, escape). I also would have liked it better, if the default functions of alert and confirm would have been overwritten, instead of recreated into an object. Overwriting the existent functions would have been made it a snap to integrate smoke.js into existing projects.
Smoke.js - A framework-agnostic styled alert/confirm system for javascript
21–28 of 28 posts
Re: Smoke.js - A framework-agnostic styled alert/confirm system for javascript
#22Similar interface http://thrivingkings.com/apprise/
Re: Smoke.js - A framework-agnostic styled alert/confirm system for javascript
#23Re: Smoke.js - A framework-agnostic styled alert/confirm system for javascript
#24Fly. On the usability tip, why don't you allow making the dialog appear near the user's mouse? Having to move it from the link (or wherever the user's mouse is at the time) to the action buttons is unnecessary.
Re: Smoke.js - A framework-agnostic styled alert/confirm system for javascript
#25I feel like the alert and confirm modals should not be allowed to be dismissed by clicking outside. Especially confirm: "Destroy all. Yes, No?" -> click outside...nothing.
It's the "panic" action, akin to a "close dialog" button. Clicking outside (should) default to the "safe" choice, in this case, "no".
Re: Smoke.js - A framework-agnostic styled alert/confirm system for javascript
#26Edit: rgbrgb posted http://news.ycombinator.com/item?id=2748038 about Apprise. It does what smoke.js does and then some. Thanks
Re: Smoke.js - A framework-agnostic styled alert/confirm system for javascript
#27Doesn't work on ipad
Re: Smoke.js - A framework-agnostic styled alert/confirm system for javascript
#28Sorry, but this is the latest entry in obsolete and obtrusive functionality. It's useless for mobile (just tested iOS Safari and Opera), which is the platform you should start with, and it's been proven out to be an annoying hindrance to the user on the desktop. Don't interrupt CRUD. If you can't trust the user to not perform an irreversible action, then you're doing it wrong.