On Sat, Mar 28, 2009 at 11:26 AM, Philip Olson <phi...@roshambo.org> wrote:
> > On 28 Mar 2009, at 07:41, Daniel Convissor wrote: > > On Fri, Mar 27, 2009 at 09:51:21PM -0700, Philip Olson wrote: >> >>> >>> - http://www.djangobook.com/en/2.0/chapter01/ >>> >> >> Sounds neat. BUT, it seems they've gotten too big for their britches. >> It isn't working for me. I don't see any comment bubbles or have the >> ability to click in the "gutter" to initiate a new comment. >> > > Not important, nobody is suggesting we implement their code or do exactly > what they do. Guys, look at the big picture and not problems with specific > code ;) However, it's working for me in Safari and Firefox. > > Even if it was working, the whole thing requires JavaScript, limiting >> availability of the comments in some situations. >> > > I don't buy this argument and prefer we innovate and not limit ourselves to > the few people who choose to go through life without allowing JavaScript. > And besides, if disabled, we could let them use something like the current > system. > > Regards, > Philip > > Even though I don't actively contribute I still hope I can put my 2 cents into here: As far as using a "fancy" looking comment system, I would vote for it. Everything is going "web 2.0" with the "ooohhh" and "ahhh"s (gmail is a prime example, there are tons of libraries and sample code for Javascript effects). Almost every site I visit uses some sort of Javascript or AJAX in background (even vBulletin has gone AJAX to some extent). I believe that the "fancy" effects will not hinder a system, but actually make it easier and more useful for the general person (if its done right!). To defend the use of Javascript (and other Javascript-related effects); you can always have 2 versions of your site - one for people who have a Javascript compatiable browser and the rest who don't. I am 99% sure you can detect in some way if the browser does support Javascript or not and serve a page appropriately. If anything else I am sure you could analyze the user-agent string and determine if its a Javascript capable browser or not. But then again this who idea would requre you to keep 2 versions of the same site. My two cents anyways.
