Comments on: Responsible Asynchronous Scripting http://ajaxian.com/archives/responsible-asynchronous-scripting Cleaning up the web with Ajax Thu, 09 Feb 2012 06:55:33 +0000 hourly 1 http://wordpress.org/?v=3.2 By: zz http://ajaxian.com/archives/responsible-asynchronous-scripting/comment-page-1#comment-17974 zz Wed, 31 May 2006 18:26:34 +0000 http://ajaxian.com/archives/responsible-asynchronous-scripting#comment-17974 The back button! The back button! Oh my God!! It's a wonder how we've been using desktop applications for decades without a back button. Why must we be imprisoned by the back button? I understand the browser brings certain behavioral expectations, but does that mean we're enslaved to always maintain back button functionality? When will it be ok to stop? The back button! The back button! Oh my God!!

It’s a wonder how we’ve been using desktop applications for decades without a back button. Why must we be imprisoned by the back button? I understand the browser brings certain behavioral expectations, but does that mean we’re enslaved to always maintain back button functionality? When will it be ok to stop?

]]> By: Responsible Asynchronous Scripting http://ajaxian.com/archives/responsible-asynchronous-scripting/comment-page-1#comment-17601 Responsible Asynchronous Scripting Wed, 31 May 2006 03:19:55 +0000 http://ajaxian.com/archives/responsible-asynchronous-scripting#comment-17601 [...] Responsible Asynchronous Scripting: " On ThinkVitamin.com, there’s a new column that’s been written up by Shaun Inman, one of the brains behind Mint concerning ‘Responsible Asynchronous Scripting’. [...] [...] Responsible Asynchronous Scripting: ” On ThinkVitamin.com, there’s a new column that’s been written up by Shaun Inman, one of the brains behind Mint concerning ‘Responsible Asynchronous Scripting’. [...]

]]> By: Jacob http://ajaxian.com/archives/responsible-asynchronous-scripting/comment-page-1#comment-17389 Jacob Tue, 30 May 2006 21:23:26 +0000 http://ajaxian.com/archives/responsible-asynchronous-scripting#comment-17389 we brought up the same thing at JavaOne in our presentation with JSF-- such that common approaches to development exist and are simple-- the use of AJAX evolves as your needs arise. So you can take something like JSF and have it operate in 'normal' mode and then add event interception on the client to partially evaluate parts of the page without requiring you to necessarily 'code' for AJAX as with RoR or GWT. we brought up the same thing at JavaOne in our presentation with JSF– such that common approaches to development exist and are simple– the use of AJAX evolves as your needs arise. So you can take something like JSF and have it operate in ‘normal’ mode and then add event interception on the client to partially evaluate parts of the page without requiring you to necessarily ‘code’ for AJAX as with RoR or GWT.

]]>