You make a valid point about Google and Facebook. I have not tried to use their online apps with Javascript disabled. I assume it's either non-functional or a horrible user experience. (Editing a file with no AJAX? I can't even imagine it.)
Yet my site is going to be a paid site and I don't want to erect any barriers to people who want to give me money, at least if it can be avoided. My site could be functional without AJAX and javascript, but the power of these tools to make the site *compelling* is what makes it attractive to people. It's all about providing greater ease of use in this application domain that will get folks using the site. -- Joe B. On Sunday, December 23, 2012 10:18:39 AM UTC-7, Alan Etkin wrote: > > > El domingo, 23 de diciembre de 2012 14:04:21 UTC-3, Joe Barnhart > escribió:I'm thrilled with some of the improvements in web2py > > in the AJAX area -- esp. LOAD(). But I am a little concerned about > architecting my new website in a way that *requires* Javascript > > to access the basic navigation and display of my site's pages. > > If we must take Google, Facebook or any popular web service out there as > an example of good web practices, we can load all the client-side code we > are able code or reuse, even if an old system user must retire in front of > the display waiting for it to execute. Sometimes old pcs just wait there > for a considerable time until all that code is initialized in the browser, > and degrading gracefully seems not the way to go for those systems, as they > continuously ask the users not to use old graphic interfaces (you take > Google apps as example of this) --
