Slashdot Mirror


Ajax and the Ken Burns Effect

An anonymous reader writes "IBM DeveloperWorks has an interesting project posted that shows how to design a client-side slide show using the 'Ken Burns Effect.' From the article: 'If the Web 2.0 revolution has one buzzword, it's Asynchronous JavaScript and XML (Ajax). [...] Here, you discover how to build XML data sources for Ajax, request XML data from the client, and then dynamically create and animate HTML elements with that XML.'"

239 comments

  1. This is detailed Ajax, Ken Burns style... by crazyjeremy · · Score: 5, Informative
    Ken Burns effect from wikipedia:

    "In his documentaries, Burns often gives life to still photographs by slowly zooming-in on subjects of interest and panning from one subject to another. For example, in a photograph of a baseball team, he might slowly pan across the faces of the players and come to a rest on the player the narrator is discussing. ... This technique came to be known as the Ken Burns Effect, even though he did not originate the technique, and has become a staple of documentaries, slide shows, presentations, and even screen savers."

    Ken Burns effect in Ajax: Use good ole DHTML and XML to whip stuff around on your screen. Or as the link says "I animate the images with random slow moves, zooms, and fades to give a pleasing version of the Ken Burns Effect without having to download Macromedia® Flash or any other heavyweight animation tools."

    1. Re:This is detailed Ajax, Ken Burns style... by caffeination · · Score: 1

      The Ken Burns effect? I'd always just thought of it as the cheap way of dealing with a lack of material to work with. I wonder if he's proud that his name has become synonymous with a method of padding out content?

    2. Re:This is detailed Ajax, Ken Burns style... by hazem · · Score: 2, Insightful

      Isn't most of what's on TV just padded-out content anyway?

    3. Re:This is detailed Ajax, Ken Burns style... by fm6 · · Score: 3, Funny

      It isn't really Ken Burnsy unless there's corny and/or maudlin music playing in the background. Also, the pictures have to be so goddamn sentimental, you want to puke.

    4. Re:This is detailed Ajax, Ken Burns style... by GGardner · · Score: 1

      No, the reason is that the source material (e.g. the photographs) have way more information than can be displayed on a standard def television screen. Panning around a zoomed image is one way to show all the detail that's there.

    5. Re:This is detailed Ajax, Ken Burns style... by Billosaur · · Score: 1, Troll
      Ken Burns effect in Ajax: Use good ole DHTML and XML to whip stuff around on your screen. Or as the link says "I animate the images with random slow moves, zooms, and fades to give a pleasing version of the Ken Burns Effect without having to download Macromedia® Flash or any other heavyweight animation tools."

      Great. So now I have to sit through pointless slideshows on web sites instead of pointless Flash animations. That makes things so much better. I think I'll go back to reading books.

      --
      GetOuttaMySpace - The Anti-Social Network
    6. Re:This is detailed Ajax, Ken Burns style... by Anonymous Coward · · Score: 0

      Oh shit, it's moving Marge. Ya, things on the screen, they're moving.

    7. Re:This is detailed Ajax, Ken Burns style... by fm6 · · Score: 2, Funny
      You just reminded me of why I despise Ken Burns. I was about halfway through The Civil War, which I had mostly enjoyed up til then. Then I realized I was watching a hyper-sentimental set of images from a veterans' reunion for the third time. Not the same reunion all three times, of course, but all three sets of images pretty much said the same thing. Then I realized I wasn't watching history, I was watching sentiment porn.

      But this sort of crap plays well with the big corporations that underwrite Burns's projects. After all, it's not that different from the corny TV commercials they spend even more money on. And that's the audience Burns is playing to, not TV viewers. When something generates money, yeah, people are proud of it!

    8. Re:This is detailed Ajax, Ken Burns style... by Anonymous Coward · · Score: 0

      "...This technique came to be known as the Ken Burns Effect, even though he did not originate the technique..."

      Isn't it ironic that AJAX also gets credit for something that was used well before its time?

    9. Re:This is detailed Ajax, Ken Burns style... by divide+overflow · · Score: 2, Informative

      > No, the reason is that the source material (e.g. the photographs) have way more information than can be displayed on a standard def television screen. Panning around a zoomed image is one way to show all the detail that's there.

      Actually, the main reason is that 1) most TV viewers expect to see action rather than still images, and 2) a lot of Ken Burns's material either predates motion pictures OR was never captured on video media. It's common knowledge in the broadcast industry that most viewers are so conditioned to expect movement that they become irritated and bored by still images and tune them out. Burns simply employed "The Ken Burns Effect" to give still images the sense of movement and thereby hold the interest of the "patience impaired" subset of his audience.

    10. Re:This is detailed Ajax, Ken Burns style... by gad_zuki! · · Score: 1

      >Also, the pictures have to be so goddamn sentimental, you want to puke.

      Puke over IP or PoIP isn't scheduled to be released until Web 3.0.

    11. Re:This is detailed Ajax, Ken Burns style... by fm6 · · Score: 1

      Unfortunately, Ken Burns stuff still mostly goes out over the air, and broadcast puke has been implemented for decades.

    12. Re:This is detailed Ajax, Ken Burns style... by newrisejohn · · Score: 1

      So what? You're too lazy to read a book on the Civil War, but too haughty to enjoy a book on tape with pictures?

    13. Re:This is detailed Ajax, Ken Burns style... by I+Like+Pudding · · Score: 2, Funny

      Not at all. There are many interesting occurances that happen on a regular basis. Many shows are full of content. The content of the shows is bold, yet smooth. Things are full of things. In conclusion, TV is a land of contrasts.

    14. Re:This is detailed Ajax, Ken Burns style... by Tack · · Score: 1

      Unfortunately, without subpixel precision the Ken Burns effect looks too lame.

    15. Re:This is detailed Ajax, Ken Burns style... by lysergic.acid · · Score: 5, Insightful

      The point of the article isn't to entertain you with a slideshow. It's an intro guide/tutorial to AJAX for developers interested in the technique. Personally, I found the article to be very informative, and a good exercise for learning the basics of AJAX. Now I can go on and implement AJAX in the interface of my real web applications, which are much more complex and have a purpose other than to simply demonstrate how AJAX works.

      It's kinda like when you first start programming you might begin with a simple "hello world" program. That doesn't mean C/Perl/whatever language you're learning is useless just because the hello world application was designed as a simple programming exercise.

      So you can stop complaining everytime AJAX is mentioned. If you're not a web developer, then it might not interest you, but that doesn't make it pointless; you just don't have any use for it. Instead of looking for stupid things to complain about, just skip the article and go read your books or something.

    16. Re:This is detailed Ajax, Ken Burns style... by JM+Apocalypse · · Score: 1

      You just made my day.

      --

      - - - - - - -
      Orppf urp mf y.ppcxn. yflcbi otcnnov C am yflcbi yr n.apb Ekrpatv (Dvorak -> Qwerty)
    17. Re:This is detailed Ajax, Ken Burns style... by ClosedSource · · Score: 1

      Didn't they do they same thing at the opening credits of the "Cheers" TV show?

    18. Re:This is detailed Ajax, Ken Burns style... by m50d · · Score: 1
      Great. So now I have to sit through pointless slideshows on web sites instead of pointless Flash animations. That makes things so much better.

      Actually it does - at least now the pointless slideshow isn't sucking 60% CPU.

      --
      I am trolling
  2. Ajax and the Mr. Burns effect.... by Anonymous Coward · · Score: 5, Funny

    It's Exxxcellent.

    1. Re:Ajax and the Mr. Burns effect.... by Anonymous Coward · · Score: 0

      Exaaaactly.

    2. Re:Ajax and the Mr. Burns effect.... by Sporkinum · · Score: 1

      How about the Ken Burns Effect combined with the Alan Parsons Project?

      --
      "He's lost in a 'floyd hole"
  3. If the Web 2.0 revolution has one buzzword, it's.. by Anonymous Coward · · Score: 0

    can'tcountuptofour

  4. Re:Microsoft's MBU: The Mac's Fifth Column by ECXStar · · Score: 0, Flamebait

    And why did this article fall into the PC vs MAC thing for you??? I don't see as that and I AM a Mac user after 22+ years of PC's. They are both valid platforms.

  5. Buzzword compliance? Check by heinousjay · · Score: 3, Insightful

    The use of AJAX technique in that example is spurious, at best. It's almost sad, really, since that's probably the only reason this article was accepted.

    --
    Slashdot - where whining about luck is the new way to make the world you want.
  6. Yet another thing XML complicates... by gregmac · · Score: 3, Insightful

    Yes, AJAX is great. Of course, the XML bit of it gets in the way, it's simpler to just grab the appropriate HTML or Javascript code directly from the server. Why write something that outputs in XML, then write client-side Javascript to re-interpret it and run javascript code or create HTML? XML is just a complication for most tasks.

    --
    Speak before you think
    1. Re:Yet another thing XML complicates... by caffeination · · Score: 2, Insightful

      It's probably worth the extra effort and wasted resources just to be able to call the finished product AJAX.

    2. Re:Yet another thing XML complicates... by DarthDevilous · · Score: 2, Interesting

      Ah but you see, if HTML were used it would be called AJAH, and that doesn't sound anywhere near as buzzy as AJAX. the X(ML) makes the difference!

    3. Re:Yet another thing XML complicates... by drig · · Score: 2, Insightful

      With XML, you can return raw data that can be formatted much more flexibly on the client-side. For instance, I have a search that returns the data in XML. That way, I can update the status section, include the search results, and even zoom to the first result. If it sent back preformatted HTML, I would only be able to update the search results bit.

      --
      Citizens Against Plate Tectonics
    4. Re:Yet another thing XML complicates... by Anonymous Coward · · Score: 0

      . . . now if only there where some way to . . . html as . . . xml application . . . the circle . . .

    5. Re:Yet another thing XML complicates... by tepples · · Score: 1

      With XML, you can return raw data that can be formatted much more flexibly on the client-side.

      So what is the advantage of XML over JSON or even CSV in this case?

    6. Re:Yet another thing XML complicates... by felix9x · · Score: 2, Informative

      I agree that this example is using xml requests for no reason. The list of images could have been a plain javascript array embeded in a tag in the html page. I think this article has more useful information about how to create slideshow effects using javascript. Although xml requests could be useful for other purposes this is not one of them. One thing that could make them useful for a slideshow is if it consistat of hundreds of images so xml can be used to load the data in chunks.

    7. Re:Yet another thing XML complicates... by Anonymous Coward · · Score: 0

      . . . nah; I lost it. Ooohhh, look, a slide show! and that looks like somebody else's family! I think I'll sit through it . . .

    8. Re:Yet another thing XML complicates... by baadger · · Score: 1

      Shutup boy it has to be XML!
      Now write me out 100 lines of <deny action="question" subject="buzzwords" />

    9. Re:Yet another thing XML complicates... by Anonymous Coward · · Score: 1, Insightful
      Why write something that outputs in XML, then write client-side Javascript to re-interpret it and run javascript code or create HTML?


      Because of presentation and content separation.

    10. Re:Yet another thing XML complicates... by Anonymous Coward · · Score: 0
      Because of presentation and content separation.

      Same question from tepples: So what is the advantage of XML over JSON or even CSV in this case?

    11. Re:Yet another thing XML complicates... by Neumann · · Score: 1

      I may be wrong here, but I the thing that makes this asyncronous is the XMLHttpRequest object, which needs to have the returning data be well-formed XML.

    12. Re:Yet another thing XML complicates... by Gramie2 · · Score: 1

      Yes, you are wrong. XMLHttpRequest just gets back a chunk of text, that may or may not be XML. It could be any string at all. Sometimes it's useful to receive XML, sometimes not.

    13. Re:Yet another thing XML complicates... by JulesLt · · Score: 1

      Two reasons :
      1) The data you are using might not live on your server. (You could certainly write server side code to connect to the external server).

      2) The Asyncronous bit. You're moving away from the idea that the server creates and delivers HTML to the idea that a server delivers data and the application renders it - i.e. back towards a client-server architecture. Using the wrong tools, but we don't really have a lot of choice in that.

      --
      'Capitalists of the world, unite! Oh ... you have' (League Against Tedium)
    14. Re:Yet another thing XML complicates... by MtnMan1021 · · Score: 1

      xmlhttprequest doesn't require formatting of any sort. check out http://en.wikipedia.org/wiki/XMLHttpRequest

      enjoy!

      --
      jacob rothstein reed college
    15. Re:Yet another thing XML complicates... by PietjeJantje · · Score: 2, Interesting

      I'm using this technique to animate avatars in the project seen in the sig (that part is not out of Subversion yet). I also tried to avoid XML in the beginning, to avoid overload, for the same reasons as you point out. However, when things start to get more complex, you need to send multiple values and stuff like parameters, and XML is the answer. For really simple stuff, I agree responseText is sufficient. When more starts to get going on, for starters you need to envelop the messages with order/timestamps. At one point you get such a complex string to parse, you're better of using XML, unless you'd like to reinvent the wheel.

    16. Re:Yet another thing XML complicates... by FLEB · · Score: 1

      And this is significantly relevant to a slideshow how?

      --
      Information wants to be free.
      Entertainment wants to be paid.
      You just want to be cheap.
    17. Re:Yet another thing XML complicates... by mini+me · · Score: 1

      The X in AJAX stands for XmlHttpRequest, which, despite the name, actually has nothing to do with XML.

    18. Re:Yet another thing XML complicates... by tedgyz · · Score: 1

      Yes, AJAX is great. Of course, the XML bit of it gets in the way, it's simpler to just grab the appropriate HTML or Javascript code directly from the server. Why write something that outputs in XML, then write client-side Javascript to re-interpret it and run javascript code or create HTML? XML is just a complication for most tasks.

      For legacy sites, your argument is valid. However, given that HTML is just a rule-breaking XML, I don't quite see what the fuss is about.

      If I'm using AJAX for something useful, like streaming data that fills a table in a web page, I think well-formatted XML is useful.

      With that said, I think XML is far too overrated and far too often glibly suggested as a solution to a problem. XML is just a useful data format.

      --
      "No matter where you go, there you are." -- Buckaroo Banzai
    19. Re:Yet another thing XML complicates... by menace3society · · Score: 1

      Only if you specify which AJAX we're talking about. Remember, the one dies before the end of the war and the other soon after (so it's kind of a lose-lose situation). A better name might have been AENEAS (Asynchronous ECMAscrcipt Needing Erratic Access to Server), but what's done is done.

    20. Re:Yet another thing XML complicates... by harmic · · Score: 1

      XML is a way to represent structured information completely independantly of the reading & writing applications (ie. the reading application should not need to know anything about the writing application). The semantic meaning of the contents of a well-designed XML file is evident from the file itself.

      JSON is a way to serialise the data structures that exist within an application so that they can be sent or stored somewhere. Originally devised for Javascript (and therefore oriented towards the data structures available in javascript) implementations have since been developed for lots of other languages. If you recieve some data via JSON you can reconstitute it into an in-memory version applicable to the language you are using, but that does not help with interpreting the contents.

      CSV is just what it says - a lot of values separated by commas. There is absolutely no information there that would help you to decide what the values represent, or even to know in advance what type each value was (integer, float, string, composite structures, etc).

      Which to use: depends what you want to use it for. If you want to interchange richly structured data, possibly making the data available to a lot of different applications which are independantly developed, go for XML. If you want a simple way to transmit structured data between a small number of homogenous applications, use JSON. If you want an extremely lightweight way to save some relatively unstructured data and you are happy that the reciever of the data will have to know exactly what each field represents then why not use CSV.

    21. Re:Yet another thing XML complicates... by HotmanParisHiltonKam · · Score: 1

      Agreed - that's why some AJAX implementations use JSON instead. The JSON is directly evaluated in JavaScript, giving you the separation of data and presentation along with the speed and simplicity of a direct JS return. The best of both worlds.

    22. Re:Yet another thing XML complicates... by ergo98 · · Score: 1

      I may be wrong here, but I the thing that makes this asyncronous is the XMLHttpRequest object, which needs to have the returning data be well-formed XML.

      You are right that the object used is XMLHttpRequest. It does not, however, require grabbed data to be in XML format, and it's actually a quirk of development that HTTP get functionality even exists within its namespace.

      The reality is that the majority of so-called AJAX implementations don't use XML in any way, apart from the irrelevant naming of the object that does the GET.

    23. Re:Yet another thing XML complicates... by MrCopilot · · Score: 1
      Why write something that outputs in XML, then write client-side Javascript to re-interpret it and run javascript code or create HTML? XML is just a complication for most tasks.

      FTA The value of returning XML is that clients other than browsers can interpret the data. The choice is up to you and depends on the application.

      See?

      --
      OSGGFG - Open Source Gamers Guide to Free Games
    24. Re:Yet another thing XML complicates... by jridley · · Score: 1

      I use XML and javascript HTML creation because then I can do a lot of transforms (sorting by columns, etc) without having to hit the server again.
      Code is code. I have to write it one way or the other, and I haven't found it to be much different whether I render the HTML in the server or in the browser.

  7. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0
    ...and I AM a Mac user after 22+ years of PC's.
    switcher \'swi`ch &r\, n.
    A person who thinks that they are a Mac user but are really just trying to be. The mistake they make is to try to become a Mac user, when real Mac users are all about not trying to be anything and following your own rules. There is no fashion code to being a Mac user. There are no rules as to what applications you have to run.

    Recent converts like you are ruining the old school Mac community because you are posers. Apple releases one OS that popularizes Fitts' law and the Genie effect, and suddenly people assume being a Mac user is all about owning a Mac. But a real Mac user is born, not made. You "switchers" are misrepresenting yourselves and the Mac platform. You're giving people the wrong idea of what Macintosh is.

    switcher: shops at hot topic, thinks Firefox is a good Mac app, waiting for OS X port of PayrollPro 2000, follows any hint of a fashion trend (instead of setting them!), wouldn't know Clarus from Carl Sagan.

    real Mac user: someone true to who they are, the misfits, the rebels, the troublemakers, the round pegs in the square holes. The ones who see things differently. They're not fond of rules and they have no respect for the status quo. The ones who are crazy enough to think that they can change the world.
  8. Risk the Client PC's Limitations ? Not yet ... by unity100 · · Score: 4, Insightful

    I still definitely refrain from Ajax like hell. The concept of delivering the load to client's computer whereas being subject to limitations of the visitor pc, and the risk of not being able to deliver the content as wanted or even at all, is one too big to take. Processing everything server side, and printing out just plain old HTML formatted result to a client pc, thus bypassing all overzealous anti-virus, privacy, anti-spyware and security software and any limitation the client pc has, is the surest thing to do, dont you think ?

    1. Re:Risk the Client PC's Limitations ? Not yet ... by heinousjay · · Score: 0, Flamebait

      No, I don't think that, but I know why we disagree. You see, I understand what AJAX is and how it works, and apparently you don't. It's cool, though, if everyone was smart I wouldn't be special.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    2. Re:Risk the Client PC's Limitations ? Not yet ... by reldruH · · Score: 3, Informative

      I realize that because this is about websites, the dynamic changes slightly, but at some point you have to accept that technology has moved forward. There are industries where that happens much more quickly than in others (3d games come quickly come to mind, where they try and use every bit of performance they can get from all the newest cards), but it happens in all industries. While there are still people with Pentium 2's or older, how far back are you going to support? I think that any computer bought within the past 6-7 years (mine's up near that age) will have no problems doing the processing for something as low-weight as a web page. While you still have to deal with anti-virus/spyware/etc, I think the vast acceptance and usability of Flickr, Gmail, Google maps and all the other AJAX applications show that most people aren't having problems accessing AJAX content.

      --
      I've always pictured the color of OS zealotry as a sort of bright flamingo pinkish hue
    3. Re:Risk the Client PC's Limitations ? Not yet ... by i23098 · · Score: 2, Insightful

      Processing everything server side [...] dont you think ?

      No :p
      Available processing power of the client is the same when several clients access the web page.
      Available processing power of the server degrades with the number of clients...

      You must know you're target audience, and send most of the job you can to them (never trusting them), or by your logic, why send HTML, you better render it and send it as an image so that the client don't spend time prossecing all those HTML tags :p

    4. Re:Risk the Client PC's Limitations ? Not yet ... by caffeination · · Score: 1

      You avoid it as a developer. I avoid it as an end user. I can barely spectate from a distance on AJAX sites, thanks to my slightly-below-average connection. I'm fairly sure Blogspot's main page uses AJAX for the scrolling list of recent posts, and it maxes out my Celeron D. Digg comment pages take over a minute to load on my computer.

    5. Re:Risk the Client PC's Limitations ? Not yet ... by itp · · Score: 1

      No.

    6. Re:Risk the Client PC's Limitations ? Not yet ... by Scarblac · · Score: 1

      I'm not aware of any anti-spyware, virus etc issues with Ajax that wouldn't also impact a normal http get request or other Javascript.

      With Ajax, using it to update a part of a page instead of the whole page, you get less load on both the server, the connection and the client. I like it, in principle. Some effects just aren't possible to do in a usable way if you need to re-generate and transfer the whole page for every little update.

      It certainly has problems, though - it messes with conventional navigation (like reload a page and you're back to where you were, the 'back' button doesn't work the way you want, bookmarking doesn't work), and also on some pages you don't get enough feedback, you don't realize that your click has any effect at all until the thing updates. Of course there are also issues with accessibility, etc.

      Of course there are also issues with accessibility, etc. But all in all, I prefer Ajax to abuses of Flash, and I think that's the choice.

      --
      I believe posters are recognized by their sig. So I made one.
    7. Re:Risk the Client PC's Limitations ? Not yet ... by fireboy1919 · · Score: 1

      In this day and age, there's no reason anybody should be using Netscape 4, or any version of IE below 5.5.

      It is not unacceptable to require users to be able to view CSS2, HTML 4, Javascript 3, and DOM1. These things are all old tech at this point - with well established standards with many years to have evolved, and supported by almost all of the market.

      This isn't even about IE versus NS. You support the standard of those things I said, and your stuff will work on anything that's 6 years old or newer.

      What does this have to do with AJAX? Not much...except that it is possible to do AJAX using those techiques rather than the new ways (and many of the old ajax libraries will support those new ways).

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    8. Re:Risk the Client PC's Limitations ? Not yet ... by Bogtha · · Score: 1

      What risk are you talking about? It's perfectly possible to have fancy Ajax effects that degrade gracefully when the client can't handle them. You don't have to choose between Ajax and backwards compatibility.

      The only risk is if you're a middle manager who isn't going to be doing the actual coding, and you don't know whether your developers are in the 10% who know what they are doing or in the 90% who copy the multitude of bad examples out there. And if you're in that position, I'd say you've already taken plenty of even bigger risks.

      --
      Bogtha Bogtha Bogtha
    9. Re:Risk the Client PC's Limitations ? Not yet ... by baadger · · Score: 1

      I don't think I can foresee a time when you shall not be special.

    10. Re:Risk the Client PC's Limitations ? Not yet ... by the_duke_of_hazzard · · Score: 1

      The above got marked as insightful? Jeez. I wish I could write functional websites in plain old HTML. It would make my life a lot easier. But it's rather like saying: "Why do we bother having event loops? What's wrong with simple old single-threaded programming?"

    11. Re:Risk the Client PC's Limitations ? Not yet ... by daeg · · Score: 1

      With Ajax, using it to update a part of a page instead of the whole page, you get less load on both the server, the connection and the client.

      Just make sure your users actually want updating parts of the page. Personally, I would hate to see a news site (as an example) that updated content on the fly, it would interrupt my reading. Give the user a way to turn it on but leave it off by default. Also, load on the client goes up significantly, at least processor wise. For that reason, I still prefer to deliver raw Javascript objects and eval() them. A bit less safe, but much faster.

    12. Re:Risk the Client PC's Limitations ? Not yet ... by bigpicture · · Score: 1

      This is a mainframe mentality with dumb terminals. And we CONTROL your life and your data, and you have to kiss our ass to get at it. Been there, done that, don't want to kiss any more IT ass.

    13. Re:Risk the Client PC's Limitations ? Not yet ... by Anonymous Coward · · Score: 0

      "I realize that because this is about websites, the dynamic changes slightly, but at some point you have to accept that technology has moved forward."

      The problem is that while the PC's may be more capable, AJAX doesn't really represent a moving forward of technology, it's more like a lateral movement. As long as we continue to use HTTP and HTML as the core standards, interactive web pages will continue to be a kludge no matter how many new buzzwords are added to the mix.

      For web technologies to really move forward would require new standards that support typical interactive scenarios without the need to write boiler-plate scripts.

    14. Re:Risk the Client PC's Limitations ? Not yet ... by lysergic.acid · · Score: 1

      Exactly. There seems to be a lot of arrogant, short-sighted web developers on Slashdot who have started a trend of bashing on anything Web 2.0-related. Most of the web services/applications the term describes are of pretty high complexity having taken many years to mature, and many innovative technologies/techniques have thus been developed in the processes of creating these second generation web applications and services. But a lot of Slashdotters can't seem to get over the superficial image of the 'buzzwords' used to describe these techs, and find it fashionable to dismiss them off the bat and bash on any application which employs them.

      OK, so 'AJAX', 'Tags', 'Web 2.0', 'Blogs', 'Social Networking', etc. are all buzzwords... So are: 'P2P', 'XML', 'WiFi', 'RSS', 'OOP', 'Open Source', etc. The "trend" of using Web 2.0 buzzwords in an article (about Web 2.0 apps) isn't any more pathetic than following the trend of bashing anything Web 2.0-relate just because it's become fashionable to do so.

      Most people seem to just dismiss these techniques off hand based on their slashdot image without even investigating what their potential benefits (and potential drawbacks) are, and then try to come up with excuses as to why these ideas aren't worth considering after they've already made up their minds about it. That's why the criticisms posted usually have nothing to do with the technical merits of the technology.

      This isn't Pitchfork-Media-dot. You wouldn't judge a political candidate based on his haircut, so why would you judge a tech based on its popularity or image. Its success and widespread adoption by services like Flickr, Gmail, Google Maps should be more important than how unfashionable the use of buzzwords is. A simple look at the arguments (or lack thereof) against most of the techs these buzzwords describe should demonstrate that most of these people have no idea what they are talking about.

    15. Re:Risk the Client PC's Limitations ? Not yet ... by Aceticon · · Score: 0

      I realize that because this is about websites, the dynamic changes slightly, but at some point you have to accept that technology has moved forward

      I disagree that AJAX is "technology moving forward". CSS (especially 2.0) is technology moving forward. Javascript is technology moving forward. HTML 4 is technology moving forward.

      I've done AJAX - its just a buzzword for a way of using the advances in technology stated above together. The only thing that differenciates a website done with AJAX from any non-AJAX website out there using JavaScript, CSS2 and HMTL4 is that AJAX uses the XMLHttpRequester to dynamically retrieve data while an non-AJAX site might do it via a hidden IFRAME.

      The only reason AJAX is receiving the attention it has is that some self-proclaimed "technology investment gurus" left over from the boom are trying to go back to the old times when they could create a (new-technology) company that did exactly the same as plenty of already existing (old-technology) companies but via the Net, IPO it on the stockmarket, watch it's stock price rise to incredible heights on the backs of the greedy and ignorant masses, and then cash out. Two years later the company would long be bankrupt.

      I work as a freelancer and i've recently had an assignment on a company that does websites. From what i've seen there and since they still have plenty of customers, i now firmly believe that the Internet related part of the industry is still the most wastefull, less professional and more fashion driven part of the whole IT sector.

      When you guys stop being driven by buzzwords, stop making software design choices on the basis of "cool new thing to try" and get some managers that actually manage projects instead of being "creeping requirements pipelines", call me.

    16. Re:Risk the Client PC's Limitations ? Not yet ... by heinousjay · · Score: 1

      And here's where the market realities start to come clear: neither of the sites you mentioned are hurting for traffic, so apparently the limited client functionality problem isn't really excluding a significant part of the market. Actually, in my opinion, since it excludes the low end it's a benefit - why appeal to people who display a propensity to not spend money?

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    17. Re:Risk the Client PC's Limitations ? Not yet ... by reldruH · · Score: 1

      You make good points, but they're slightly off topic. In your original post, you made the point that you weren't willing to offload much of the processing done on the server to the clients computer. It was that point that I was refuting.

      In regards to your point about it being nothing but a buzzword, so are a lot of technologies when they first come out. Does the .NET framework allow you to do anything radically different from what you could do before? No, but it makes a lot of things easier; it's a new way of using an old technology and like it or not, AJAX is moving the internet forward. People I know who would have never been involved at all otherwise now have Gmail accounts, and because they were so impressed with that, they now use Google maps, and now they've found Wikipedia (and even contributed to an article or two) and are using Google Talk and interested in VoIP and how they can use it on more than just their computer. Without the great interfaces/usability/responsiveness (the 'ooh' and 'aah') a lot of people would never care to switch, and would still be using MS Hotmail. Using these old technologies in a new way is making people switch, is showing them what new technology can do and while there are always developers who will abuse a new technology, I think it's equally bad for people to summarily refuse to use it, when it's obviously working for millions of people just because they can't see anything new about it.

      --
      I've always pictured the color of OS zealotry as a sort of bright flamingo pinkish hue
    18. Re:Risk the Client PC's Limitations ? Not yet ... by lysergic.acid · · Score: 1

      What load is being diverted to the client by AJAX? All AJAX does is use some simple javascript to update DOM objects with XML data requested from the server. This doesn't take any more processing power than javascript form-validation. Client-side scripting is not anything new to the web. If the client can render a webpage, it should have no problems executing some simple javascript to parse XML data.

    19. Re:Risk the Client PC's Limitations ? Not yet ... by lysergic.acid · · Score: 1

      Have you never used gmail or other web apps that use AJAX in their interface? AJAX is specifically designed so that only the section of the page you're applying changes to is updated when you perform a browser action on it. AJAX interfaces act much like desktop applications in that an action on a particular section of the page does not interupt other sections of the page. So I can attach a file to an e-mail I'm composing and it won't affect the composition box that I'm still working on, or Gmail can auto-save a draft of my e-mail in progress without interrupting my typing.

      I would urge you to actually visit sites like Gmail, Flickr, Google Maps, Amazon, etc. to see what AJAX does before you start making uninformed comments about the technique.

      Also, the workload required to make an XMLHttpRequest call and parse the XML data returned from it is insignificant compared to the processing resources required to render a normal web page with images, or run a Java applet or Flash plugin. It's no more resource-intensive than javascript form-validation or drop down menus. So worrying about AJAX being a processor hog is a completely moot point.

    20. Re:Risk the Client PC's Limitations ? Not yet ... by unity100 · · Score: 1

      I still think the success of gmail lies in its simple interface and the fact that there is google behind it - a much more trusted internet presence than microsoft

    21. Re:Risk the Client PC's Limitations ? Not yet ... by daeg · · Score: 1

      I'm not talking about GMail or others. I write AJAX stuff (and rewrite, lately, taking over for past contracts) for a living these days. Gmail and related tools are very well written, but there are some horrible AJAX coding out there where the server sends back a massive XML document for a simple update, e.g., a badly designed GMail would resend the inbox.xml (figurative name) for upadting 1 item. GMail doesn't do this. XML processing can be very quick, but it can also be very slow when stupid programmers decide they need full XPath support (which generally means a massive JS library to implement XPath on older browsers) just to pull a single string out. The goal I was trying to hit (and missed, apparently) was that just because a tool (AJAX, XPath) is there doesn't mean you have to use it or that it is the best idea to do so.

    22. Re:Risk the Client PC's Limitations ? Not yet ... by unity100 · · Score: 1

      With the hype going on around the 'language', clients are requesting entire features that were otherwise done with local php/mysql operations be done with ajax. work order systems, online computer gaming bracketing systems for example are 2 examples that i have to deal with now. They do not want 'just simple form validation', they want things done entirely in ajax.

      And it is a problem to convey the realities, advantages and disadvantages of ajax to them for the projects at hand, because ajax is the 'new thing' and 'it is good' for many of them.

      You are taking javascript-remote scripting load lightly i think :

      Yes, any desktop pc can compile any web page, and even heavily javascript loaded pages relatively easily under normal circumstances. But people that browse the web never open a single firefox/ie window and browse the web on the client pc - they run media players, office programs, sometimes small games (the office crowd, as the least example), 1 or 2 instant messengers, an ever open mail client, in general.

      The combined effect of all these running at the same time, given any application has its own bugs and take on the client pc, occasionally even leads to lockups for the client pc. Which is something i experience in person when i visit heavily java loaded or ajax pages, yes, even the gmail or adwords sometimes can cause such problems.

      Youll say, and i agree that it is illogical to run such phletora of things at a time, but this is not a choice left to us developers. People have, and will do use their pcs like that - it is in the nature of people.

      In these respects, we developers are on the other side of the double edged sword - we HAVE to satisfy our clients, and at the same time we HAVE to ensure that the client's content is 100% delivered to the visitor pc.

      This is why i refrain from using any client side stuff in the code as far as i can avoid.

  9. damn you ajax by tlynch001 · · Score: 1
    One developer made a page to show how the data could be refreshed without a 'flicker' (postback). Now our customers are starting to demand that their web apps to be flicker free.

    It's annoying when suddenly a deal breaker is "I don't like the flicker when I click the button".

    1. Re:damn you ajax by hsmith · · Score: 1

      The worst is the salesman. See, they seem to (as well as the client) remember that a web app isn't the same as a desktop app. That you can't get the same functionality. Yes, it is improving, but there are still huge gaps in capabilities.

      I blame them for telling the clients "oh we can do anything" when they don't understand the limitations of the technology.

    2. Re:damn you ajax by baadger · · Score: 2, Funny

      You know what..i like the fucking flicker. i want ajax with flicker substitute. How else am i going to enjoy bashing the refresh button when a website is so god damn infuriating?

    3. Re:damn you ajax by Anonymous Coward · · Score: 0

      This can be done using double buffering, just update the backbuffer and flip it.

    4. Re:damn you ajax by Anonymous Coward · · Score: 0

      X-O ========= {&*$#AJAX@*} (barf! ajax!)

    5. Re:damn you ajax by Ciaran_H · · Score: 1

      Do browsers even have exposed functionality for rendering in a backbuffer? And even if they did, how would you use it except by using JavaScript?

    6. Re:damn you ajax by Anonymous Coward · · Score: 0

      Tell them to get with the program! It's not a flicker, it's a 9flykr!
      Sheesh. Do I have to explain Web 2.0 to everybody?

  10. Re:Microsoft's MBU: The Mac's Fifth Column by heinousjay · · Score: 1

    This is the worst copy-and-paste troll yet. Mac users, rebels indeed.

    --
    Slashdot - where whining about luck is the new way to make the world you want.
  11. The Headline Says "Ken Burns Effect" by klenwell · · Score: 5, Funny

    Where are the sepia tones, jazz soundtrack, and pedantic voiceover?

    Tom

    --
    Innovation makes enemies of all those who prospered under the old regime... -- Machiavelli
  12. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0

    A guy walks up to me and asks, "What's Macintosh?" I show him my Quadra 840av and say "That's Macintosh." So he runs out, he buys a shiny new Mac mini, and he comes back and says "That's Macintosh?" and I say "No, that's trendy!"

  13. Re:Ajax is for..... by Anonymous Coward · · Score: 1, Funny

    Your anus runs Linux?

    Now I've heard everything.

  14. Yeah right, just the one buzzword then... by Anonymous Coward · · Score: 1, Informative

    If the Web 2.0 revolution has one buzzword, it's... err, these three buzzwords, Asynchronous JavaScript and XML... hmmm, ok, scrap that.

    1. Re:Yeah right, just the one buzzword then... by Anonymous Coward · · Score: 0

      Er, Ajax?

  15. Glad that's sorted by hackwrench · · Score: 0, Redundant

    When I read "Burns" I thought some guy in that "The Simpsons" show...

  16. Re:Microsoft's MBU: The Mac's Fifth Column by Ohreally_factor · · Score: 1

    Why are you biting on an obvious copy and paste troll?

    --
    It's not offtopic, dumbass. It's orthogonal.
  17. Ken Burns effect? by Anonymous Coward · · Score: 5, Funny

    Ken Burns effect? What, it takes 10 hours to get through the thing?

    1. Re:Ken Burns effect? by Otto · · Score: 1

      Yeah, and afterwards, you feel like you've wasted your life watching it.

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    2. Re:Ken Burns effect? by Anonymous Coward · · Score: 0

      surely that would be true for those still using dial-up ;)

  18. There are a lot of "Web 2.0" buzzwords... by Jeff+DeMaagd · · Score: 2, Insightful

    ...Web 2.0 is a buzzword itself. I've seen an article that showed that many of the "Web 2.0" technologies are largely older technologies that have been renamed and rehyped, this time around, they took hold.

    1. Re:There are a lot of "Web 2.0" buzzwords... by Bastard+of+Subhumani · · Score: 0
      Web 2.0 is a buzzword itself.
      No it isn't. It's two words. Or even four. Or two-dot-zero, or four-dot-zero. And another thing, why does your name mean "The Girl"? Or are you named after a premium brand of Belgian butter?
      --
      Only three things are certain; death, taxes, and apocryphal quotations - Ben Franklin.
    2. Re:There are a lot of "Web 2.0" buzzwords... by mgblst · · Score: 1

      Wow, great post. Make sure you keep that article a secret - you know the penalty for posting a link to an article like that and sharing said information.

  19. Re:First Post by alanwj · · Score: 5, Funny
    First post :)

    This is poor advice. First you GET. Did you even look at the article?

    Alan
  20. Interesting, but distracting by Tumbarumba · · Score: 1

    This looks like an interesting technique, but I think that you would have to have a very good reason to use this feature in a real presentation, otherwise it might come across as distracting. The presenter should be trying to make some sort of point (or sale, or argument, or...). I'm sure that there are some cases where this could really make a big different to a presentation, but I'd guess that these are fairly rare.

    On the subject of web enabled presentation formats, I really like S5, Eric Meyer's Simple Standards-Based Slide Show System (see http://www.meyerweb.com/eric/tools/s5/ ). This is much more simple than the technique from the article, and there are now some very powerful Scriptalicious extenstions that can add dynamic features to S5. One of my own presentations is at http://www.exubero.com/ant/antintro-s5.html

    --
    My business: Farstrider Studios.
  21. Coolest Ajax UI Ever by Anonymous Coward · · Score: 5, Funny
    Client-side slide shows are nothing. This is the coolest Ajax UI ever. This simple yet Ajax intuitive UI:

    • was built with off-the-shelf, re-usable components
    • was assembled in minutes and required no debugging
    • has a scalable architecture
    • uses well-defined interfaces to separate objects
    • is inherently cross-browser compatible
    • runs on Windows, Linux, and OS X
    1. Re:Coolest Ajax UI Ever by d0st03vsky · · Score: 0

      Hmm, somehow I can't view this site in my browser, Lynx.

    2. Re:Coolest Ajax UI Ever by Paradise+Pete · · Score: 1

      You left off "harmful or fatal if swallowed."

    3. Re:Coolest Ajax UI Ever by djdanlib · · Score: 1

      That's the cleanest UI I've ever seen.

      It's so simple.

      Where's the source, though?

  22. Rich Corinthian Leather by hackwrench · · Score: 1

    Maybe it would help if they hired Ricardo Montalbán to say the title on account of his Star Trek background, and perhaps Fantasy Island?

  23. buzzword... by Horas · · Score: 0, Redundant

    HAS a Buzzword? Web 2.0 IS the buzzword!

  24. Sheesh... This article makes me puke... by Anonymous Coward · · Score: 0

    If the Web 2.0 revolution has one buzzword, it's Asynchronous JavaScript and XML (Ajax)

    Yeah... a buzzwords (Web 2.0 (which technically doesn't exist)) buzzwordbuzzword (AJAX)...

    Man, I'm happy to have the great hobby called programming and not actually being forced to listen to such BS every day on work before I get outsourced.

    I wonder if they use such buzzshit in India? If not, maybe that's what they're doing right!

  25. Dealing with a lack of material to work with... by Anonymous Coward · · Score: 2, Insightful

    Actually, Ken Burns has a wealth of material to work with, but none of it moves. He scowers the public records, historical accounts, and personal diaries to find these very insightful, personal accounts that really bring to life a time before universal capture of moving images. He scans and pans over static images to create a backdrop for what is essentially a book on tape. He does an excellent job considering the lack of movies and video, but not for lack of material.

    1. Re:Dealing with a lack of material to work with... by Anonymous Coward · · Score: 0

      Ah. Fair enough then. The sort of thing I'm talking about, though, is when the news takes a CCTV image and pans around as if it were a camera.

    2. Re:Dealing with a lack of material to work with... by Anonymous Coward · · Score: 0

      Wow, "scowers". Did you mean "scowrers?"

    3. Re:Dealing with a lack of material to work with... by Anonymous Coward · · Score: 0

      Feel a slight sting? That's pride fucking with you.

  26. When's the Object Oriented AJAX coming out? by Bin+Naden · · Score: 2, Interesting

    I've used Ajax a bit to develop an enterprise application and it just tends to turn into one big mess (perhaps by my own fault but nevertheless ;) ). Is there a completely object-oriented Ajax library out there because this would significantly improve the usability of ajax.

    --
    There should be a "-1:Groupthink"
    1. Re:When's the Object Oriented AJAX coming out? by Basje · · Score: 1

      Prototype:
      http://prototype.conio.net/

      It's developed for ruby on rails, but can be used with any cgi language I guess.

      --
      the pun is mightier than the sword
    2. Re:When's the Object Oriented AJAX coming out? by Anonymous Coward · · Score: 0

      yes -- yahoo has developer tools for ajax / client side javascripting available for free:

      http://developer.yahoo.com/yui/

      there are also other libraries released under license from yahoo listed at that url as well

    3. Re:When's the Object Oriented AJAX coming out? by Bin+Naden · · Score: 1

      I stand corrected...

      --
      There should be a "-1:Groupthink"
    4. Re:When's the Object Oriented AJAX coming out? by debiguana · · Score: 1

      Take a look at the xajax library (xajaxproject.org). I've used it with good success, and it's OO.

    5. Re:When's the Object Oriented AJAX coming out? by xynopsis · · Score: 1
      We've been working on a toolkit called Wt that completely hides the complexity resulting from Javascript ui logic, DHTML, XML, etc associated with creating AJAX applications. Best of all, it is pattterned from the Qt toolkit and allows you to design webapps as you would in any desktop Qt application.

      It is completely object-oriented and the event mechanism is even handled by the signal and slots approach, allowing the same programming elegance found in Qt-based software. It allows you to focus on the design and logic of your program in one place and one place only! Quite similar to how Qt hides the details of the underlying window system from the programmer.

      See this overview

      Note the familar Qt-like syntax in creating a tree widget.

      Please check it out!

  27. This is very true by SmallFurryCreature · · Score: 4, Interesting
    IF you are going to take the view that you are not going to rely on the client having certain capabilities when are you going to stop?

    Render the page server side as an image? So you presume the client has image capability?

    I think that for to long we have tried to include everyone. Bending over backwards to support crap browsers with broken functions just to make sure nobody was left behind. Well fuck it. At a given point you must just be able to say, "upgrade or our site won't run".

    If you don't the price is going to be that other people can move ahead and use new technologies while you are stuck with an ever dwindling but always present group of people who still use the same software from a decade ago.

    Ask yourselve if this is normal in the real world.

    Old cars can't run on modern petrol. Yet how many gas stations keep an old pump around for cars from before WW2? Try to get some polaroid film from your average camera store. A lp player from a highstreet electronics store.

    Get the picture? So why on earth are we still worried about people using browsers 2 generations out of date.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:This is very true by Anonymous Coward · · Score: 0

      It is just a question of economics.

      The 'upgrade or leave' philosophy makes sense at a gas station because most people are upgrading their cars anyway. Gas stations stop supporting the older fuels when it is no longer profitable. It is no longer profitable because most people have upgrade.

      The same is true for software, and rational firms will support older browsers as long as the benefits outweight the costs. The problem is, many firms are convinced they need the latest, flashiest site to sell their products and services. Some do, but I suspect most don't, and I suspect the cost of failing gracefully is probably still very low compared to the benefit of doing so.

      Yet for some reason there are hundreds of websites that fail to work if you do not have javascript, cookies, flash, or whatever else. Even websites which have no reason to require those technologies. I have no problem with a website that performs a software service using javascript. But when the site is broken because of some trivial use of javascript or cookies, that's just stupid. Take client-side validation of form variables. The only legitimate use of that is to save the server from hits that are going to result in errors anyway. Yet there are sites with forms that fail to work if javascript is disabled or unavailable. Some sites even tell you "You must have javascript enabled to use this site" when all it does it make their menu work. Or "you must have cookies enabled" when all it does is track you at their website. Do I really need javascript or cookies to get a price or product review?

      It's not even necessarily the newer technologies that are the issue. It's the cost of going for that last 10%. After all, there are many sites that still only work in IE.

    2. Re:This is very true by unity100 · · Score: 1

      However there is another catch - Everything on pcs and laptops and the like might have evolved to a state that might handle much complex web operations, but there are also a phletora of new gadgetry that is entering the world of telecommunication - we have the wap for example, a brand new and exciting new area for the net/web to expand into, however it is definite that they will have a hard time handling the fancy stuff we might be putting on the websites yet. And if, and when they wont, we will have to create two versions of the site/service, test them out and maintain them so that this new medium and the mediums that are developing alike could be able to reach out to websites.

    3. Re:This is very true by Anonymous Coward · · Score: 0

      At a given point you must just be able to say, "upgrade or our site won't run".

      Translation: "Upgrade, or go spend your money somewhere else."

    4. Re:This is very true by honkycat · · Score: 4, Insightful

      I would say that you should generally stop when you've given up enough that your web site is no longer capable of serving its purpose. If you are building a site to share photographs, then there's no real need to handle the case where the user can't render an image because your site will be worthless anyway. If, however, you're a news site with photos alongside articles, then you really ought to take the time to support text-only users.

      Also, you need to separate "backward-compatibility" from "downward-compatibility." The latter is, IMO, the more important of the two. The difference I am getting at is that backward-compatibility concerns a protocol change that breaks or is not supported by older browsers, whereas downward-compatibility concerns an interface capability requirement that can't be worked around by a software upgrade.

      There are users who can't use nifty features for a lot of reasons. Blind users have a hard time with web pages that don't render well in text mode for a screen reader or Braille "display." Users on a handheld device have limited screen area and processing power. I myself often use a text mode browser on a brand new PC before I get X up and running. If your web site can be useful to these people, then it's worth being downward compatible.

      Backward compatibility is, IMO, a bit less of a must-have, but I still would advocate maintaining it unless it's a serious hardship. Not many web sites need or are even improved by these new technologies. There are exceptions, but I find that advanced HTML rendering techniques often make sites *less* usable to me. Arguing "upgrade or die" to support something that's "cool" rather than something that's "useful" seems like a poor policy.

      Your examples of gasoline and Polaroid film fall into this backward-compatibility category. Gasoline is not a great example for this discussion because there is good reason to actively discourage people from using the older more dangerous formulations. Still, pragmatically, at some point there just isn't enough demand for something to warrant continuing to provide it. I think it's worth trying to keep things compatible if you can.

      And I don't know that I've seen many cases of people "bending over backwards" for compatibility. Most places, IMO, don't do nearly enough of it.

    5. Re:This is very true by macpeep · · Score: 1

      http://www.s60.com/browser

      I'm by no means saying that that's the level browsers in mobile devices are today. That's obviously the absolute latest and greatest. But it shows where things are headed. It's Safari based, supports HTML 4.01, XHTML 1.0, with full support for JavaScript (including AJAX-stuff), frames, forms, etc. etc.. Hell, it even supports SVG and Flash, as well as the Netscape plugin API. Most devices that will feature that browser (or feature it already) have screen resolutions of QVGA or higher and many of them have WiFi.

      The mobile world is catching up quite fast! The low-end is roughly at the level Netscape 2 was on back in 1996 / 1997 or so. The high-end is more or less caught up to the state of the art of PC browsers.

      Peppe

    6. Re:This is very true by CodeBuster · · Score: 1

      Or "you must have cookies enabled" when all it does is track you at their website. Do I really need javascript or cookies to get a price or product review?

      Perhaps not javascript, but cookies are commonly used to maintain state between requests or to keep track of the login status of the current session. There are only so many ways to maintain state in a browser session, for all the hype over browser based applications, and with URLs limited to 256 characters or less than what are you going to do? It never ceases to amaze me how people are always trying to work around the browser to badly emulate things that GUI client applications have been doing well for 20+ years. So the answer to your question is that cookies are needed to maintain state because http was originally designed to be stateless and they need some way to get around that so that they can present you with a pseudo application via a browser which was originally designed to link html pages in a stateless fashion. They opted to attach rockets and gyroscopes to a clothes dryer in an attempt to create a flying machine instead of simply designing a plane.

    7. Re:This is very true by Anonymous Coward · · Score: 0

      "So why on earth are we still worried about people using browsers 2 generations out of date."

      Becuase that's a lot of people; it's hard enough getting people to a website, no need to exclude more before they even get there. People don't upgrade in a hurry; you better support them, or lose that audience because no one will upgrade just for your site.

  28. Re:Ajax is for..... by Anonymous Coward · · Score: 0

    Linux passes through my anus when I have the runs.

  29. I admire the coding, but... by 93+Escort+Wagon · · Score: 3, Informative

    First, I will say this is a pretty slick piece of work. But the actual rendering (download the example and give it a shot) is nowhere near as smooth as what can be accomplished with an iPhoto slideshow, or with Flash.

    I'd guess this is due to inefficiencies in the browser itself. I've seen similar issues when I've played around with animating multiple text objects (moving, resizing, and changing opacity) in the past.

    --
    #DeleteChrome
    1. Re:I admire the coding, but... by Anonymous Coward · · Score: 0

      A browser can only get down to the pixel-level of whatever photo it's using. It can only shift a bitmap around in whole pixel increments and makes the movement look jerky.

      Ditigally making a bitmap move smoothly requires pre-calculating the movement vectors and speeds, and basically recalculating each pixel from pixels headed in its direction for each frame. That simulates the movement. I don't think any amount of CSS or Javascript or DHTML will do that.

  30. If you want animation, use Flash by Animats · · Score: 2, Interesting
    Javascript will never get the timing right, and it will look tacky.

    Now here's a good Flash animation. Try doing that with "Web 2.0".

    1. Re:If you want animation, use Flash by s4m7 · · Score: 1

      You're neglecting to consider the fact that flash sucks.

      --
      This comment is fully compliant with RFC 527.
    2. Re:If you want animation, use Flash by gkhan1 · · Score: 1
      Flash does not suck. It's sucks when people use it annoyingly, but it's great at doing alot of things. The grand-parents example is one of them. Google Video is another (although, I would prefer if they did that in Java, but tha's just me).

      You may dislike how people use it, but it's a great technology for embedding lightweight widgets in a web-page.

    3. Re:If you want animation, use Flash by Peganthyrus · · Score: 1

      Try using the Flash editor to make anything serious. It's pretty sucky.

      (former Flash animator/director.)

      --
      egypt urnash minimal art.
  31. Must be written by an Enginee by Alan+Reynolds · · Score: 1

    The article must be all true, since it uses engineering spelling [from the article]: "Jack Herrington..., Senior Software Enginee, Code Generation Network"

  32. Google agrees with you , this is why Gmail.... by Shohat · · Score: 4, Informative

    This is why Gmail has an alternative to the Ajax interface , and you can switck to HTML mode , and it just removes the AJAX dependant features :
    * Filter creation
    * Settings (Including Forwarding and POP)
    * Spell checker
    * Keyboard shortcuts
    * Address auto-complete
    (from http://mail.google.com/support/bin/answer.py?answe r=15049)
    Google really sets a fine example here by letting users choose what kind of interface they prefer , even though they could easily just ignore these users, as I personaly dont know anyone that uses this feature . Making a dual interface for AJAX applications on all these fluffy Web2.0 sites is a good idea , specially for mobile/light clients like that 100$ laptop

    1. Re:Google agrees with you , this is why Gmail.... by the_duke_of_hazzard · · Score: 1

      All those are dependent on AJAX? Wow, I must be really clever, cos I reckon I could do them without.

    2. Re:Google agrees with you , this is why Gmail.... by lysergic.acid · · Score: 1

      None of those features need AJAX per se, but an AJAX interface enhances their usability, and in the case of auto-complete, is the only real elegant way to implement it.

      I've developed tons of web applications without the use of AJAX too in the past, but I can recognize the potential benefits of an AJAX interface. So rather than dismissing it off hand because it's become fashionable on Slashdot to bash anything Web 2.0-related, I'm learning as much as I can about AJAX so I can implement it in my next project.

      So you're not clever, you're just arrogant and short-sighted.

    3. Re:Google agrees with you , this is why Gmail.... by Anonymous Coward · · Score: 0

      Okay, ley's see your auto-completion.

  33. its 1998 all over again by Anonymous Coward · · Score: 0


    when flash really did have to be downloaded (all 250k of it)
    now it comes as standard on Windows (since 1999)

    still its good to see IBM are catching up, maybe they will discover WebTV and WAP next

  34. Re:First Post by Anonymous Coward · · Score: 0

    Ha. Thanks for a good laugh.

  35. what is wrong with this picture? by s4m7 · · Score: 3, Insightful
    It's tough to show what this looks like in a browser without a movie. So, I took a single snapshot of the show and present it in Figure 6.

    it's tough to show you what this looks like in a browser, when i'm plainly viewing it... WITH A BROWSER?

    wtf?

    --
    This comment is fully compliant with RFC 527.
  36. Re:Microsoft's MBU: The Mac's Fifth Column by WilliamSChips · · Score: 1

    Macs have always been trendy. It's just that what was trendy 20 years ago isn't what is trendy now--that's why it's called trendy. Want to be rebellious? Come over to the Linux side.

    --
    Please, for the good of Humanity, vote Obama.
  37. It depends what you're using the web for by Anonymous Coward · · Score: 0

    I deeply resent sites that take too long to load because of all the gratuitous glitz. How about forgetting the stupid animation all together and just give me what I'm actually looking for.

    It seems to me that one of the web search engines won't let ads with graphics on their site. Lets see ... who was it again? How much money are they making these days? Hmm.

    If you actually need to show me a picture don't bother getting cute. If I want to watch animations I'll go looking for them.

    Take my advice and you'll save lots of bandwidth and cpu cycles for both of us.

  38. From TFA by Anonymous Coward · · Score: 0

    "The new model is more asynchronous, as shown in Figure 2."

    You heard it here first: 'Web 2.0' "more asynchronous" than the Web.

    Just for the record, in case the author fancies stopping his buzzword posturing:

    "asynchronous
              adj 1: (digital communication) pertaining to a transmission
                            technique that does not require a common clock between
                            the communicating devices; timing signals are derived
                            from special characters in the data stream itself
                            [ant: synchronous]
              2: not synchronous; not occurring or existing at the same time
                    or having the same period or phase [ant: synchronous]"

  39. Mac screen shots? by Hyperx_Man · · Score: 1

    Anyone notice they have MAC screen shots on this IBM web site? What is this world coming to?

    1. Re:Mac screen shots? by jasonhamilton · · Score: 1

      you mean besides the fact that ibm made powerpc chips?

      --
      SearchIRC - Now with live chat directory!
  40. AJAX does not require XML by tepples · · Score: 2, Insightful

    In practice, AJAX means Asynchronous JavaScript And XMLHttpRequest. Nothing in the XMLHttpRequest object's interface requires that the retrieved data be XML; it could be in other notations such as CSV or JSON.

  41. Ridiculous waste of my time... by brunes69 · · Score: 1

    Basically, this guy uses Ajax to download the list of images from the server, then uses DHTML to move them around the page.

    Whoop-dee-do. It's like something that could have been done in 2000.

    This is the stupidest example of Ajax I have ever seen. You use Ajax asynchronously to fetch ocuments on demand in order to reduce page reloads - you don't use it to download a 1kb list of images from the server you will only be using once during that page load.

    Ajax is a useful technology (I use it often), but this article is a horrible example of it. It saves you nothing here - he could have just had the image list inline in the page and the user would see no difference.

    The whole rest of the article is just DHTML, of which you could get much better examples at Dynamic Drive or any of another dozen sites.

    1. Re:Ridiculous waste of my time... by porneL · · Score: 1

      Yup. In 1995 we've had bunch of stupid ideas like "selling dog food on the web!". Now we have "selling dog food, on the web, with AJAX!".

    2. Re:Ridiculous waste of my time... by Anonymous Coward · · Score: 0

      a slideshow that fetches an xml file is useful for the same reason that loading points on a google map from xml is useful.

      sure, you could just put them inline in your code, but it's better to write code that is independent of the data. That way you don't have to change a single thing when the data changes.

  42. Re:Ajax is for..... by Anonymous Coward · · Score: 0

    O RLY?

  43. A policy of noscript by tepples · · Score: 1

    I'm not aware of any anti-spyware, virus etc issues with Ajax that wouldn't also impact a normal http get request or other Javascript.

    Unless, as is the case in some institutional IT installations, an overzealous proxy or group policy set on the web browser blocks all scripts from executing. What alternate content do you have in your applications' pages' noscript element?

    all in all, I prefer Ajax to abuses of Flash

    So if the user requests audio feedback for specific operations, or I want to make a slide show that contains synchronized narration, how do I provide it using AJAX?

    1. Re:A policy of noscript by orasio · · Score: 1

      You didn't understand the quote you made: the guy said that everywhere AJAX doesn't work, javascript doesn't work either (and we all know that most web applications, AJAX or not, have problems if you don't have javascript/jscript). Of course, places that don't allow javascript, will always have problem with webapps, but it's not an AJAX exclusive problem.

      HTML itself does allow for audio. It's not nice, but you could do it, without flash.

    2. Re:A policy of noscript by tepples · · Score: 1

      everywhere AJAX doesn't work, javascript doesn't work either

      Even this is not true. Some web browsers that implement script and useful parts of the HTML DOM do not have an XMLHttpRequest object. Or are you talking about requests in hidden iframe elements?

      Of course, places that don't allow javascript, will always have problem with webapps, but it's not an AJAX exclusive problem.

      Accessible web apps (under the Rehabilitation Act section 508 definition and foreign counterparts) will have to have a fallback to the traditional forms model because too many assistive technologies do not allow script.

      HTML itself does allow for audio. It's not nice, but you could do it, without flash.

      Now I'm interested. How does one do this? I'm guessing it has something to do with script turning object elements on and off; am I right? What URL or Google keywords should I use to learn more?

    3. Re:A policy of noscript by lysergic.acid · · Score: 0
      Even this is not true. Some web browsers that implement script and useful parts of the HTML DOM do not have an XMLHttpRequest object. Or are you talking about requests in hidden iframe elements?

      That has nothing to do with the discussion about anti-spyware and anti-virus programs conflicting with AJAX. The only way that security policies would conflict with AJAX is if scripting were disabled, therefore, it is a more general problem not specific to AJAX.

      Besides, all major browsers support XMLHttpRequest, XMLHTTP, or equivalent methods by now, including: Internet Explorer 5.0+, Mozilla 1.0+, Safari 1.2+, Opera 7.6+, iCab 3.0b352+, OpenLaszlo 3.1+, Konqueror 3.3+, and IceBrowser. So what popular browser supports javascript but not XMLHTTP/XMLHttpRequest?

      Whether you like it or not, AJAX is here to stay. This is apparent from the widespread adoption of AJAX interfaces by popular web applications/services. If Gmail, Google Maps, Amazon, Flickr, etc. are all implementing AJAX, then cross-browser compatibility probably isn't a huge issue. In fact, the W3C is already working on standardizing the XMLHttpRequest object API.

      It seems to have become fashionable to bitch and moan every time AJAX or some other Web 2.0 technology is mentioned on Slashdot, and usually the gripe people have is with the terms used to describe the technology/technique. But, honestly, dismissing a technology or web development technique because you think the name of the tech is stupid is like not voting for a particular political candidate because you think he has ugly hair. So what if it's become a buzzword? Shouldn't development techniques be evaluated based on their technical merits, not on whether it's become too passe to be uttered on Slashdot?

      A lot of people here like to criticize journalists/marketers for their trend of using Web 2.0 buzzwords, but how is it any less stupid to dismiss Web 2.0 tech just because it's become trendy to do so? Oh, that app implements tags? It must be lame! WEB 2.0 SUX!!! 99% of the time when AJAX is brought up in an article, it's an informative piece which actually evaluates the technique, or in this case, is a guide to AJAX development. It has nothing to do with marketing or throwing around buzzwords to fake knowledgeability, yet people are still coming up with the most strained reasons as to why AJAX is just a fad that has no practical value.

    4. Re:A policy of noscript by unity100 · · Score: 1

      If Gmail, Google Maps, Amazon, Flickr, etc. are all implementing AJAX,

      All these are in big need of distributing the load on their servers to outside - ie the client pcs. This means big operational expense cuts for them. I dont think that a publishing site with 1 million monthly uniques would need to take such measures.

    5. Re:A policy of noscript by lysergic.acid · · Score: 2, Insightful

      You're still not understanding what AJAX is. 99% of the processing load is still done by the server. All AJAX does is manipulate/update the user interface asynchronously instead of having to refresh each page. AJAX does not shift the server load to the client. I'd advise you to read the wikipedia entry on AJAX or TFA to get a better understanding of what AJAX is. These are user-interface enhancements, not a load-balancing/distributing strategy.

  44. WHERE'S THE DEMO??? by JoeCommodore · · Score: 2, Funny

    I don't get it, why do they fully detail a web cool app without a live demo??

    Are there any examples of this in action?

    --
    "Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
    1. Re:WHERE'S THE DEMO??? by baadger · · Score: 1

      What and prove AJAX is just as slashdottable as anything else and tarnish it's smooth silky sexy little image here on Slashdot? No way!

    2. Re:WHERE'S THE DEMO??? by Toveling · · Score: 5, Informative

      On my home server (may be a tad slow), http://toveling.dyndns.org/kenburns/

    3. Re:WHERE'S THE DEMO??? by JoeCommodore · · Score: 1

      Ran fine for me, thanks for putting it up!

      --
      "Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
    4. Re:WHERE'S THE DEMO??? by Anonymous Coward · · Score: 0

      Thank you. Much appreciated.

    5. Re:WHERE'S THE DEMO??? by Canis+Latrans · · Score: 2, Insightful

      Good god... no wonder he didn't put the live demo up. It looks terrible! The pictures are all over the place. Doggy's head got chopped off by the side of my browser window. The fade-out didn't even work on Opera, so I had to run it on IE to see if it looked any better. One rule of the "Burns Effect" should be "never show them where the picture ends" -- but on this demo you are constantly looking at the corners of picture with two thirds of the screen being black because it's off the edge of the picture. And the zooming looks like crap because of the poor interpolation method. And the animation is not smooth at all. So, nice try, but this is a pretty poor implementation.

      I wonder how many of these poor implementation things are due to limitations of AJAX, versus just plain poor implementation.

    6. Re:WHERE'S THE DEMO??? by Anonymous Coward · · Score: 0

      From experience, large images with fading effects run like molasses using javascript on modest machines. Obviously it's not a technical limitation on the language, but in the fact most implementations haven't been designed with this type of effects usage in mind. It's not got nothing to do with AJAX which I'm assuming is used to fetch the images (completely gratuitously, BTW)

      In contrast, I've seen the Macromedia stuff do it with ease (not that I've ever used it myself).

    7. Re:WHERE'S THE DEMO??? by Anonymous Coward · · Score: 0

      Thanks for posting a live demo!

  45. Term coined by Steve Jobs haha by AgNO3 · · Score: 2, Interesting

    The Ken Burns effect was a term coined by Steve jobs with iphoto was launched. The Pan and Scan effect as it is properly called has well been around long before Ken used it. We just associate it with him because most of his Documentaries are about subjects that had only or mostly still images to use in the show. I am Highly amussed now that a Purly Steveism is not a main stream term. If you can show me a use of Ken Burns Effect prior to iPhoto please link me up.

    --
    OMG Ponies!!! with Glitter!!!! I miss Pink :-(
    1. Re:Term coined by Steve Jobs haha by idamaybrown · · Score: 1

      When did iPhoto come out? The Ken Burns effect was used in the 1990 The Civil War documentary on PBS. And I am sure in earlier documentaries.

    2. Re:Term coined by Steve Jobs haha by AgNO3 · · Score: 1

      Uh it was not called the Ken Burns effect then. It was called a Pan and Scan. It is a Very commonly used technique that you never noticed before. It has been used in animation since, well since animation was created. If you asked the editor that did the effect for Ken Burns he would call it a Pan and Scan. It was NEVER referred to as the Ken Burns Effect until Steve added an auto Pan & Scan to iPhoto and then titled the tool the Ken Burns effect. Since this technique is being applied to still photo you just see it where as when it is done to motion footage you don't really notice. Nor should you.

      This is right from the Wiki page. Again if you can show me one use PRIOR to the release of iPhoto and not like this link a use of it since. Using the definition after the term is coined does not mean it was used to describe the effect Prior to the Steve reference.

      Wiki quote"
      This technique came to be known as the Ken Burns Effect, even though he did not originate the technique, and has become a staple of documentaries, slide shows, presentations, and even screen savers. In film editing, non-linear editing systems such as iMovie and iPhoto (from Apple Computer) often include an effect or transition called Ken Burns Effect, with which a still image may be incorporated into a film using this kind of slow pan and zoom. It is also seen in screen-savers that slowly pan and zoom through a slide show of digital photographs on a computer's hard disk."

      --
      OMG Ponies!!! with Glitter!!!! I miss Pink :-(
    3. Re:Term coined by Steve Jobs haha by tgd · · Score: 1

      Sorry, thats blatently incorrect. Apple chose to use the term, Apple did not make up the term. I studied film at Hampshire college, where they never ever fail for a moment to remind you that Ken Burns got his start in film there. Over. And. Over.

      That effect was referred to as the Ken Burns effect off and on even then, which was 12 years ago.

      The term "pan and scan" has nothing to do with the ken burns effect. Pan and scan is specifically used in the industry (and solely used, in my experience) to refer to the cropping of an image from one frame size to another, usually putting film onto TV.

      I've *never* heard it used to refer to what the "ken burns effect" is... thats just the way you shoot static material -- keep the image framing changing to draw the eye where you want it. Ken Burns just shoved it down people's throat.

    4. Re:Term coined by Steve Jobs haha by AgNO3 · · Score: 1

      Wow, I guess working on feature films, music videos, spots, pilots, or anything else we do here in Hollyweird (well Santa Monica) all day every day I wouldn't know. As for it being called the KB effect I NEVER HEARD IT CALLED THAT before Steve Jobs. The pan and scan term has been adopted by as the generic term used when converting from one crop ration to another. If you had ever done a pan and scan you would know what I am talking about and not going to go over the actual process here. Leave it to say the Wiki definition is sorely lacking in the practical application of what a Pan and Scan is. Stop by the Lustre or Assimilator booths and ask them to show you what goes on when they are CREATING the pan and scan. Needless to day you will see A LOT of panning around the image and pushes into the frame depending on how the pan affects the shot and needs to be recomposed so that the smaller ratio better show or hides the re-crop and still makes as much sense as possible.

      There is TECHIQUELLY NO difference between say the the way the cameras are used to create ANY hand animation and the KB effect. Back in the early days they when they needed to do a camera push on a hand drawn animation it would be drawn on an over-sized BG the camera whould then be pushed into the 2d scene to give the illusion of the camera moving into a 3d enviroment. The camera would then PAN around this over sized plate to create the illusion of a real life camera move. (because its a real waste of time to draw scaled figuers) Have you ever done REAL opticals? I am not going to explain optical effects here for 20 min I don't have time. So I will just end with this.

      --
      OMG Ponies!!! with Glitter!!!! I miss Pink :-(
    5. Re:Term coined by Steve Jobs haha by tgd · · Score: 1

      Boy you're smart.

      How does it matter one bit that you never heard it called that? I did frequently, so while your datapoint is interesting, it is completely irrelevant.

      But thanks for replying. Bye.

    6. Re:Term coined by Steve Jobs haha by Anonymous Coward · · Score: 1, Informative

      Urm.

      iPhoto was released on January 7th 2002.

      Here is a random post from 2000, someone asking for a "poor mans Ken Burns effect".

      Pan and Scan is only known as the proper name for the Ken Burns effect by little children playing "I can be graphical too mate". "Pan and zoom" may have been what you were looking for.

      This is like a 1 minute search using the Google. May want to try that next time before putting your foot in your mouth :)

    7. Re:Term coined by Steve Jobs haha by alienmole · · Score: 1
      Wow, I guess working on feature films, music videos, spots, pilots, or anything else we do here in Hollyweird (well Santa Monica) all day every day I wouldn't know.

      That's right, apparently you don't know. First, the term "Ken Burns effect" wasn't coined by Steve Jobs (see link provided by AC), and second, its generic is name "pan and zoom", not "pan and scan". While there's an obvious connection between the two, the latter refers specifically to a technique for converting between formats, and not to the Ken Burns effect.

      You seem to be having a problem with logical inferences, e.g. the fact that you first heard something from Steve Jobs doesn't mean it didn't exist previously (it more likely means that Jobs is aware of a wider world than you are); and the fact that when performing a pan and scan, you do something a lot like a pan and zoom, doesn't mean that the term "pan and scan" can correctly be used instead of "pan and zoom". To test your logical ability, try this ten question test.

  46. CSS2? IE fails it by tepples · · Score: 1

    It is not unacceptable to require users to be able to view CSS2 [which is] supported by almost all of the market.

    Among web user agents that run natively[1] on Microsoft Windows, a beta version of Opera is the only one that provides a reasonably complete implementation of CSS2. The others, including the latest releases of the top two (Microsoft Internet Explorer and Mozilla Firefox), fail the Acid2 test. In fact, IE fails much more basic CSS2 tests.

    [1] Here, I define "natively" to exclude cygwin1.dll, unless you can make a case that millions of users of millions of Windows machines should install Cygwin, X11, and KDE to get Konqueror.

    1. Re:CSS2? IE fails it by Anonymous Coward · · Score: 0

      but if IE didn't fail so horribly, we wouldn't have the asterisk hack at our disposal, now would we? No, instead we'd have to write a javascript to detect browser and then write up an entirely seperate stylesheet for it (because even if IE didn't fail so horribly, it would still fail pretty bad; it's just the natural order of things).

    2. Re:CSS2? IE fails it by baadger · · Score: 1

      While Opera's CSS implementation is rather golden in my opinion (*see rant below*) the Acid2 test doesn't test for compliance of CSS standards. This has been said many many many times.

      I sure wish the webstandards.org guys would place a notice atop the test page, in big red letters, "THIS IS NOT A COMPREHENSIVE STANDARDS COMPLIANCE TEST"

      *RANT* I personally suspect alot of supposed Opera breakage is just legend from old versions and poor understanding, or testing of, standards by web designers. It's annoying to read posts that imply that because a CSS webpage doesn't work quite right in Opera but does in Firefox that it is all Opera's fault. Do people not realise it is possible to have a page that utilises CSS2 (and validates) but is still incorrect?

    3. Re:CSS2? IE fails it by larry+bagina · · Score: 1

      IE provides conditional html evaluation. It's a couple extra lines of html to make IE (and only IE) import a css file (or whatever). Personally, it's a lot cleaner than exploiting css parsing bugs.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

  47. buzzphrase by tepples · · Score: 1

    No it isn't. It's two words.

    Common definitions of "buzzword" include phrases. Your pedantry fails it ;-)

  48. They do it all wrong! by Moskie · · Score: 3, Informative

    They're onto something here, but they botch a very important step: what they do with the XML once it's returned. Instead of generating the HTML through Javascript as they do, it makes much more sense to use XML transformations.

    I've taken the dive into Ajax recently to do dynamic in-page searching. For a web-app I develop for my work, on a particular page the user needs to select a client (from the thousands we have in our database). I have a spot on the page where they can provide search criteria for the client they want to select. I perform the search with Ajax, display the results, and the user selects which client they want to pick.

    I've found the the step of displaying the results can be slowest step. At first, I had the Ajax function return a JSON associative array containing the data. I would then loop through it and create the HTML I needed through Javascript (much as they do in the linked example).

    However, if something along the lines of hundreds of records were returned, the client's browser would freeze for a period of time (depending on the performance of the client's machine) while generating that HTML. This became unacceptable.

    The superior way to display the results is with XML transformations. Beleive me, it's a monumental difference, and if you're doing something like I was, you should look into it. Have the Ajax function return XML, then use an XSLT style sheet to transform those results into the HTML you want to display. It's super fast, and worth the trouble.

    1. Re:They do it all wrong! by HotButteredHampster · · Score: 1

      Do you have any tips on making this work well? I started creating a fairly complex web app that used AJAX and XSLT to transform the results, following precisely the logic you present here. Where it ran off the rails for me (no pun intended) was it meant that for any data->presentation cycle, I needed to fetch two XML documents: the REST data and the XSLT transformation. Since both were asynchronous, in order for anything to happen, both requests needed to (a) resolve and (b) be able to combine their results.

      Any thoughts, or links to more information on this? I would be very interested in learning more.

      HBH

      --
      "Smart is sexy." -- D. Scully ("War of the Coprophages")
    2. Re:They do it all wrong! by Anonymous Coward · · Score: 0

      If design allows, use the response handler of the XSLT doc to call the request for the XML data, to ensure XSLT is available when XML arrives. If that won't work (ie, when you need the same XSLT file for a variety of XML docs), have the XSLT handler set a flag to true when fully loaded, then wrap calls to dependent XML docs in functions that are called directly if the flag is true, but otherwise are diverted to a timeout/repeater/timed event that checks the flag each second or so (for a max number of seconds) until the XSLT doc is available. Most Ajax toolkits set up a kind of dependency array where you can queue pointers to the functions that are all waiting on the same condition, so that they get called in script order when the condition becomes true.

      If that makes no sense, well, it's a little off-topic, so I probably shouldn't elaborate.

      IMHO, XSLT is still not quite ready for prime time (doesn't work right in some of the major browsers) so do a sanity check in Firefox to see if it's your code that's messed up, or just a browser quirk. I have done lots of tests between XML+XSLT and subformats (XML subsets of XHTML based on microformats), and the subformats win hands down every time. For now, I'd advise holding off on client-side XSLT for at least another year. Subformats are full-fledged XML, they're just not quite as "semantic" as freeform XML can be.

      I'm not sure if there's a standard microformat for slide presentations, but I use XOXO, a general-purpose hierarchical outine system that has a lot of support (including a WYSIWYG online editor script by Les Orchard). The way I'm using XOXO, scriptless browsers see a familiar bullet list with links to slides, then use the back button to return to the list if they can't handle framesets. Ajax browsers get treated to a full-featured slideshow with cross-fading, simple animations, and an optional hierarchical floating menu to skip to any slide (same XOXO file with different CSS). With the right CSS and JS, the same XOXO-based list can auto-adapt to the client.

      I won't be adding the article's version of automatic pan-and-zoom (Ken Burns effect) because it's a little too inflexible and rudimentary. All my project's missing is a flag and a randomizer, so no need for a new approach. The article might be a decent academic tutorial for students unfamiliar with XHR. However, I wouldn't suggest using the article's ideas in any production work, as many better options are readily available.

    3. Re:They do it all wrong! by Moskie · · Score: 1

      I guess the AC was hinting at it, but one option is to load the XSLT transformation(s) into a global JS object at page load. Or at least going out of your way to make sure you get the transformation only one time at the most. The transformations I'm using aren't all that complex, and I would only need at most a couple per page, so it was reasonable for me to get the transformations at page load and use them whenever needed.

  49. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0

    I can tell some stuff about you.

    -your film didn't get into Sundance. Or Cannes. Or ResFest. Or the fucking Two Boots weekend Short Series. The tough part about it is that your film probably isn't that bad. It's probably very smart, except for the disdain you have for the very audience that has to judge your film, and view your film, and LIKE YOUR FILM. Your problem now is the problem you've always had. You don't just need to be different, you NEED EVERYONE TO KNOW YOUR ARE. And that's why you're a luser.

    -you got beat up in high school. You lost your virginity to a hooker, and you came quickly, trying to please her sexually. Oh yeah, and you ate her pussy.

    -you do some really progressive music that cycles on long timelines like every hour or so. It's probably really cool if I had a 300 year lifespan and thus a different sense of time perspective, but I don't - so that makes it lame. And again, that makes you lame, because your "genius" exists in a vacuum, completely distinct from reality for the majority of people other than you.

    -you're not as smart or ingenius as you think you are.

    -Smart Windows users treat computers as the things they are: imminently replaceable commoditized items. It's a tool. Windows users are not tool fuckers. Idiots pay double the price for REDUCED FUNCTIONALITY. Yessir, that means you. I can make movies, music, code, etc, on windows machines - and I can run a small cluster at the cost of one powerbook. And I don't have to dick around with Linsux for hours to get shit done. Nor do I pay Jobs a ridiculous tax just so I can suck his dong. Your 4+ grand can get me 4 notebooks and peripherals - and some cash left over to buy your girlfriend drinks at the bar while you lament your artistic struggles. LOL

    Tough break, buddy. Your girlfriend is kinda hot though... and the things she does after a couple of drinks. LOL

  50. Where did the Javascript Haters go? by GISGEOLOGYGEEK · · Score: 2, Interesting

    Everyone Hates Javascript, no one here would ever admit to allowing javascript run on their browsers due to the infinite number of security problems it creates ... or so says nearly everyone who has posted on this website in the last few years.

    We've read this a thousand times in a thousand stories, only fools let javascript operate despite all the incredible things it can do.

    BUT ... rename it as AJAX ... suddenly its all good.

    What a bunch of buzzword suckers you all are.

    AJAX is nothing new, its just a name for using a certain javascript technique.

    --
    George Bush + Linux = "I will not let information get in the way of the fight against Windows"
    1. Re:Where did the Javascript Haters go? by dlbornke · · Score: 1

      Amen ... too true. ... although I have to admit I always had JavaScript enabled but always told everybody its a bad thing !(TM) ... and I love GMail and Google Maps.
      Shame on me ;)

    2. Re:Where did the Javascript Haters go? by Anonymous Coward · · Score: 0

      Its not JS that's bad, its ActiveX. The problem is, you turn off ActiveX in IE, you lose XMLHttpRequest, so you lose Ajax. If you use Firefox (or any other browser) instead, there's no ActiveX to begin with and XHR doesn't use it, so scripts run in a sandbox with very little possibility to escape. We haven't been turning off JS, we've been switching browsers.

      Now, Greasemonkey (Mozilla JS postprocessor) really is a problem. It's cool at first, but don't install it-- a huge security hole and slows down Firefox tremendously.

    3. Re:Where did the Javascript Haters go? by m50d · · Score: 1

      Firstly, I'll say that I'm still disabling it. But people are no longer hating because rather than lame rollovers that could be done in CSS, redoing links so that they work the same as ordinary html but you can't open them in tabs, or scrolling annoying messages in your statusbar, here javascript is actually doing something useful for once.

      --
      I am trolling
    4. Re:Where did the Javascript Haters go? by Myria · · Score: 1

      Firefox 1.5.0.2 fixed 3 bugs that allowed JavaScript code to cause buffer overflows and execute arbitrary machine code. It's not just Internet Exploder that has this problem.

      No Execute and stack cookies FTW.

      Melissa

      --
      "Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
  51. perhaps not relevant by cinnamon+colbert · · Score: 1

    Java always slows things way down, so whenever i get to a site that does have java, i get out and look for an equivalent bit of information at some other site, or if it is a merchant, i don't buy that item.

    1. Re:perhaps not relevant by Anonymous Coward · · Score: 0

      Java != Javascript
      You lose at Geekdom

  52. Beyond My Ken by Doc+Ruby · · Score: 1

    I thought the "Ken Burns Effect" is the effect that popular US history documentaries have on US national archives. Like the Smithsonian giving Viacom's Showtime cable station a monopoly on access to the archives. Kinda like burning the public archives, without burning the money it makes a private corporation.

    --

    --
    make install -not war

  53. All The Buzzwords in Web 2.0 (First Edition) by jdbartlett · · Score: 1

    Four buzzwords and a float if you count "Web 2.0" Five if you count "revolution". Let's not count "revolution".

    However, now that AJAX is "Ajax" losing its acronym status, that's still five buzzwords.

    Then there's XML, which is really "eXtensible Markup Language", totalling 8 buzzwords.

    Then there's JavaScript, which is just one implementation of ECMAScript, the other most common one being JScript (10 buzzwords.)

    In conclusion, if the Web 2.0 revolution has any buzzwords, these are them:

    - Web
    - 2.0
    - Ajax
    - Asynchronous
    - JavaScript
    - And
    - XML
    - eXtensible
    - Markup
    - Language
    - World
    - Wide
    - Consortium
    - Standards
    - Driven
    - Rich
    - Internet
    - Application
    - XHTML
    - CSS
    - Content
    - Scrambling... no wait... I mean...
    - Cascading
    - Style
    - Sheet
    - RSS
    - Really
    - Simple
    - Syndication
    - SVG
    - Scalable
    - Vector
    - Graphics
    - XUL
    - User
    - Interface
    - Language
    - Google
    - Maps

    1. Re:All The Buzzwords in Web 2.0 (First Edition) by Guuge · · Score: 1

      Four buzzwords and a float if you count "Web 2.0"

      That's no float; it's fixed!

  54. It's called JavaScript 1.1 by jdbartlett · · Score: 1
  55. Why did you stop reading books? by maynard · · Score: 2

    Ken Burns didn't.

  56. What in the world... by Ulrich+Hobelmann · · Score: 1

    does Web 2.0 have to do with Ajax?

    Ajax is nothing special. It's a structured (HTML) document, and it's Javascript to dynamically reload or change parts of it. It's basically an extension to good old Dynamic HTML.

    Web 2.0 is about wishy-washy stuff like the Semantic Web and intelligent agents etc., all things that aren't really technological, but rather castles in the sky. Ajax is the simple application of down-to-earth technology to take static web pages a step further.

  57. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0
    ...your "genius" exists in a vacuum, completely distinct from reality...
    Yeah? Then why do we Mac users win the vast majority of the world's "Nobels and Pulitzers and Grammys and Tonys and Oscars and Pritzkers," as I mentioned above?
  58. I personally condemn Ken Burns... by hullabalucination · · Score: 1
    ...for not coming up with more contemporary motion picture archival clips from the U.S. Civil War persiod (1861-1865) so that he didn't have to pan the camera across static photos on an animation stand. Oh, well.

    Hmmmm...lack of material? I guess you never saw The Civil War: A Film by Ken Burns. It's 11 hours of documentary. In fact, it's one of the longest documentaries I can recall since Victory at Sea. He's got so much stuff packed in to this ball of wax that the average TV viewer won't hold still for all of it nor digest the majority of it. I don't recall much fat to his narrative and at times, the pace of his following the thread of two sides interacting through complex battle scenarious leaves many viewers dazed. I found it exhilarating, but at times I think he could have in places used a bit more of the "Ken Burns Effect", lingered a tad longer on a few key photos and slowed down the storytelling to let us viewers catch our breaths and let the details sink in.

    1. Re:I personally condemn Ken Burns... by caffeination · · Score: 1

      Don't take what I said too literally. I'm talking about the effect itself, not Ken Burns' work. For example, news producers pan or zoom sloooooooowly around/into things like CCTV cameras, and the only extra information it provides is that your picture hasn't frozen.

  59. But what did you think... by hullabalucination · · Score: 1

    ...of the Ken Burns Effect?

  60. You hoo... Ed Tufte? by dpbsmith · · Score: 3, Insightful

    This is the animated equivalent of chartjunk. It does not improve a bar chart to make the bars look like Cuisinaire rods instead of rectangles. It does not improve a slide show to move and zoom the pictures in random directions.

    This is a silly demonstration of technology for technology's sake.

  61. What about embedded web servers? by mustafap · · Score: 1

    >Processing everything server side, and printing out just plain old HTML formatted result to a client pc, thus bypassing all overzealous anti-virus, privacy, anti-spyware and security software and any limitation the client pc has, is the surest thing to do, dont you think ?

    What I like about AJAX is the possiblility for improving content served up by small embedded systems. I have a simple web server on a piece of telco exchange equipment ( running threadX + interniche tcp/ip & webserver ) that can just about manage serving up html and javascript. Pushing the processing down to the client PC is idea; I only have 1MB storage for code + filesystem on a 25MHz CPU. House rules dictate I may not use java, so ajax seems ideal.

    --
    Open Source Drum Kit, LPLC deve board - mjhdesigns.com
  62. sigh by Anonymous Coward · · Score: 0

    Folks, if you couldn't figure this crap out before they labeled it AJAX, do us all a favor and give up your career as a developer. JavaScript is a scripting language, its not rocket science. Its not even C++. This sort of thing is why real software engineers laugh at IT departments and Web Developers- they make a big deal of something very routine. XML is another great example of this- ooooohhh a data file that uses hierachial tags to represent structure data...how revolutionary, and how wasteful of space and bandwidth.

    If the concept of asynchronous retrieval of XML and transforming it into something useful bends your mind so much that you need an article like this one to make it simple for you, then you are a liability to your profession and your company is better off without you.

    Please, enough of the AJAX buzzword. Its Javascript, plain and simple, with a browser object to facilitate the retrieval of data. All of these 'technologies' have been around for years and I'm amazed that everyone thinks its something new.

    You guys who find this article interesting are going to crap your pants if you look at something like Wild Tangent's DOM object plugin.

  63. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0

    Why do you lump yourself into that grouping? You assume that because you use a Mac, that you have something in common with them other than the fact that you use Macs. Wrong. They have genius. You have: "I fell for Jobs marketing scheme and I go hard for baby boomers in black turlenecks!"

    Such a poorly constructed argument and blatant appeal to emotion confirm it. You aren't that bright. Good luck with everything though.

    Tough break buddy.

  64. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0

    Why do we lump ourselves into that grouping? Because we've always shared something in common. We were aesthetes before we were friends, and we were friends before we were Mac users. And we will always stick together. Bon soir.

  65. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0

    Bon soir.



    Lol. And on top of all those deficiencies, you're gay????? Lol. You should just play russian roulette with a full gun.

  66. am i blind? by ronsta · · Score: 0

    where do i see a demo to see whether something like this is even worth implementing? i looked all over the page :(. this is something i may want to take a stab at, but no clue what end product is.

  67. WAP and the like should be taken into account too by unity100 · · Score: 1

    Periodically web becomes accessible by new medium, like the WAP and upcoming new tech. Even if we were able to pass the new fancy standards to desktop and laptop pcs on the web, the new mediums will need more time until they become powerful to take on these fancy stuff easily. Which, if you think, is much visitors lost - and that is much lost potential for expansion of the web that would have been realized quicker. As it stands now the new gadgetry can keep up what we already have on the web, but if we juice our sites up, this might change. Still, it might be wiser to refrain from pumping up the sites yet.

  68. back-end engineers - end of html by Anonymous Coward · · Score: 0

    Interesting idea for an article, but the writing scares me...

    Quote from the article:
    From a career perspective, the "back-end engineers" of the Web V1.0 world, who focused just on the database and the business logic, are limited in the Web V2.0 world. It's time to realize that not all requests to the server are going to be looking for HTML. Also, Ajax and DHTML are real tools for real engineers who are paid real money for their skills. The front end isn't just for designers.

    Uhm, so backend developers don't care if their code and data are used to generate xml, javascript, or to power a think client. Also, show me a "softare enginee" that thinks "that all requests to the server are going to be looking for HTML." and i will show you a newbie PHP developer.

  69. Acid2 indicates Microsoft's attitude by tepples · · Score: 1

    the Acid2 test doesn't test for compliance of CSS standards.

    True, perfect rendering of Acid2 is necessary but not sufficient for perfect handling of CSS2. However, IE's continuing poor performance on Acid2, even in IE 7 pre-release builds, indicates Microsoft's attitude toward conforming to established open standards for the Web.

  70. If this is the Ken Burns Effect... by stam66 · · Score: 0, Redundant

    can't wait to see Monty's version!

  71. what I never hear about web 2.0... by caudron · · Score: 2, Interesting

    ...is what happens with al the people who actually need static content to particpate in this supposedly improved New Web Order.

    Think about it from the perspective of a blind man. His screen reader presents the content to him. He makes a choice or otherwise interacts with it. AJAX jumps in and dynamically changes a bit in the middle of the page. Now...how does he know it was changed? Answer? He doesn't. He's excluded by default from this whole "Web 2.0" thing.

    I'm not interested in bringing everyone's experience down to the lowest common denominator, but it's getting kinda bad for people who need 508 compliance just to be a part of this great new medium.

    If it were some remote corner of the web, I'd keep my mouth shut, but as more sites move to AJAX content, they cease being 508 compliant. And this is a very recent phenomena. Until AJAX (for the most part), the web was essentially static. Changes to a page initiated a postback event and the screen reader was thus informed that a change had occured. Not so anymore.

    This was sort brought to my attention recently as I am redoing a .com (they want it all ASP.NET 2.0-ified) for a fairly large corp and 508 compliance is a pretty big deal...and truthfully it should be. We talk about wheelchair ramps and other physical accomodations, and even computer accessibility, but AJAX is circumventing our current accessibility model.

    We need to either drastically improve the screen reader technology or make ourselves more aware of the poeple we exclude with these "advances".

    Disclaimer: Yes, I know that "Web 2.0" is not directly about AJAX but rather about collaboration, but AJAX is the preferred technology used to implement said collaboration.

    Tom Caudron
    http://tom.digitalelite.com/

    --
    -Tom
    1. Re:what I never hear about web 2.0... by Anonymous Coward · · Score: 0

      So, we should make cars work with blind people too?

      I am all for handicap access, and improving life for people with any handicap. But there is a certain point when people have to admit they cant have it all because they are handicapped.

      The web is a visual medium, and while it is a rich resource of data, it is also a source of entertainment and time wasting.

      Websites like Wikipedia or Google will want to strive to ensure that regardless of whatever version of the web we are developing for, they will want their websites easily accessible, but should it be a law or requirement that ALL websites conform to some standards?

      I have a lot of respect for people dealing with their handicaps, but I dont respect the expectation that we all have to cater to their specific needs, especially coming from people that are not handicapped. Regardless of what technology is used to drive the web, someone else will find a way of making it accessible, we shouldnt fear innovation because we are worried that some sight impared people might not be able to full experience a web page with a Ken Burns effect slideshow on it. Why would a blind person feel the need to access that website, and what do they hope to get out of it? A text description saying "picture 100034.jpg is drifting to the right a little, now 100045.jpg is fading in from the left?"

      There is a certain point when handicapped people understand that they cannot participate in the same things non-handicapped people participate it, and they accept it. Its the people that feel the world has to cater to their every needs and ensure easy access to everything non-handicapped people have access to that I find hard to agree with.

      We wont make cars that blind people can use, and there will always be web pages that exists that are simply cant be experienced by someone with a visual handicap.

    2. Re:what I never hear about web 2.0... by Bushido+Hacks · · Score: 1

      I'm using Ajax on a new project that I am working on. At the same time I am trying to find a way to make Ajax 508-compliant.

      If Web 2.0 is making some major strides in how people access the internet, then Web 2.1 should be more handicapable.

      --
      The Rapture is NOT an exit strategy.
    3. Re:what I never hear about web 2.0... by HotmanParisHiltonKam · · Score: 2, Informative

      Whether is should be so or not, it is law that blind people have access to information in all websites, in many countries.

      Having said this, people always jump on the "AJAX isn't accessible" bandwagon, which is plainly a load of crap. My AJAX apps work fine in all the popular screenreaders. How does a user know the information has changed? Provide an option for the user to turn on change notifications, which show an alert() when the page is updated.

    4. Re:what I never hear about web 2.0... by Anonymous Coward · · Score: 0
      The false assumption that Ajax always hides content is nothing short of extremely closed-minded bigotry akin to "I met this guy with a big nose and he was mean, therefore all people with big noses are mean."

      Just because many prefab Ajax script libraries are sloppy doesn't mean that the whole Ajax approach must always be sloppy. 508-compliance can actually be very easy with Ajax, so long as you roll your own and don't get sucked into using 508-ignorant code libraries.

      How?
      1. Carefully pick your XML as a subformat of XHTML (preferably from existing microformats).
      2. Use noscript tags and CSS-hidden hyperlinks to provide scriptless, synchronous access to your otherwise Ajax content (link directly to the microformat files).
      3. Test the design with scripts off to be sure navigation to all content remains possible. If content becomes inaccessible, there's usually an easy way to link to it. If you don't want Ajax users to "see" a link, hide it with CSS or script the DOM to prune it from the tree.


      Supporting 508 is really not as hard as a lot of people try to make it out to be. It just needs to be a design goal from the beginning, and you need scripters with a can-do attitude and a modicum of creative initiative. If your scripters are brain-dead or otherwise intellectually-challenged, then by all means, continue bogging down your server with the same old tedious HTML 3.2 presentation logic users are quickly learning to despise. Better a well-designed Web 1.9 site than a sloppy Web 2.0 site.
  72. Backend scripting for Web 2.0 by Regnard · · Score: 1

    Interesting that the atricle uses PHP with the AJAX-enabled slideshow.

    Now I'm wondering how do the platforms out there stack up to creating theses kind of apps (PHP, RoR, .NET, Java, etc.)

    --
    Need a color? Try 100 random colors
  73. Re:Microsoft's MBU: The Mac's Fifth Column by ECXStar · · Score: 1

    Your so full of crap troll... If it weren't for us SWITCHERS, Apple would have dried up LONG ago. Go sit on it and spin..

  74. THIS THREAD IS JUST A WEAK SOCK PUPPET TROLL by Anonymous Coward · · Score: 0

    If you're replying to your own post, your career as a troll is either just beginning or just about to end.

    And though you got a few slashbots into a lather, it has to feel hollow given the modus operandi. Keep trying.

    1. Re:THIS THREAD IS JUST A WEAK SOCK PUPPET TROLL by Anonymous Coward · · Score: 0

      Cease the crapflood, motherfucker.

  75. Ken Burn's Screensaver - iSlideshow by SamNmaX · · Score: 1

    I figure this OpenGL screensaver, iSlideshow , might be of interest given the topic. It allows you to select a set of images and play them back ken burn's style.

  76. Now I'll get my rant on . . . by Ohreally_factor · · Score: 2, Funny

    This is a troll? It's a joke, you morons. The "Ken Burns Effect" became famous when Ken Burns directed The Civil War for PBS. To think that I used to come to slashdot for the intellectual stimulation. It's like most of the smart people have left. Yeah, the curve has moved so much that I'm one of the smart ones now. Freakin' idiots.

    --
    It's not offtopic, dumbass. It's orthogonal.
    1. Re:Now I'll get my rant on . . . by Fred_A · · Score: 1

      Yes, we considered inviting you when we left for our secret moon base, but... nah.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    2. Re:Now I'll get my rant on . . . by Ohreally_factor · · Score: 1

      Still, thanks for the postcard.

      --
      It's not offtopic, dumbass. It's orthogonal.
  77. How do you destroy computers? by debiansid · · Score: 1

    You can smash 'em with a baseball bat...

    or post a link to it on ShashDot ;-)

  78. Re:Microsoft's MBU: The Mac's Fifth Column by Anonymous Coward · · Score: 0

    And I thought REAL Mac-users were the ones who were not educated enough to grasp a concept of more-than-one-button-on-a-mouse. Silly me.

    Mac is yet another computing platform. Accept it (or die).

  79. Because XML keeps the server side generic by HighOrbit · · Score: 1

    With XML, you have a standarized generic output that could be parsed by any number of clients. Thus, the AJAX/javascript browers-based client is just one of many ways to access and display the data. You could also be serving the data to a java Swing app or a MS VB app, and the server wouldn't care. By using XML, you keep everything portable and generic.

    Now, if you are writing somthing to serve your kids' photos to grandma and you know she will only view it on your webpage, then you can get away without using XML because you only expect one type of client, which you yourself will code anyway. If you are providing a web-service to serve up weather data that other people can integrate into an application, or (an even better example) grabbing third party generated weather data, you will appreciate having the data in XML because of its portablility and especially its structured organization.

    As an example, I am working on a way to grab the text of some government regulations and integrate them into a web application that will reference the appropriate regulation based upon some simple questions that the user will answer. The morons that host the reg are serving up valid but sloppy and fairly unorganzied HTML. So, if I want to zero in on, say, Part 3, subpart 301, paragraph(b)(3), I have to code a very specific parser to search and find what I want. But if they had everything in XML, I would just zero in on the named element tag that I want.

  80. NOTE: Parent post is further proof... by Anonymous Coward · · Score: 0

    ...that the PC demographic is closely aligned with NASCAR-watching trailer trash. Shouldn't you be at an evangelical revival right now? Or at a dentist's?

  81. Re:Even Nokia evaluates it... by kadnan · · Score: 1

    These guys also intrested to implement in in their sets. my Ajax based feed reader to view content of other sites.Use it and enjoy!

  82. CPU 100% by Eric+Pierce · · Score: 1

    Anyone else run this code? My CPU darts to 100% usage on my 1.5Mhz AMD. I love JavaScript, but this obviously is not a good use for it.

  83. You forgot something by bufalo_1973 · · Score: 0, Redundant

    Didn't you had to finnish saying "Jobs akbar" and burning a PC in the street?

  84. Polaroid film and LP players by dpbsmith · · Score: 1

    I call bullshit on SmallFurryCreature's comment.

    Our local CVS pharmacy, on Nahatan Street (which is the "high street" of my population-30,000 U. S. burg) does carry Polaroid film. Two kinds, in fact: Polaroid 600 and Polaroid SX70.

    The last time I checked, the local Best Buy carried not one but two LP turntables... AudioTechnica and Sony if I remember correctly. And our local Radio Shack has LP cartridges. I haven't seen an LP "player" in the flesh, but I get a number of mail-order catalogs that offer functional modern reproductions of vintage Crosley "record players."

    Polaroid film and LP players are not hard to find. And they are real physical objects that need to be manufactured.

    But SmallFurryCreature is too lazy to put in a few lines of code to ensure that customers with older PCs can access a website? I assure you that people with screen resolutions set at 800x600 or 640x480 are quite common in "the real world."

    When people with those displays can't access SmallFurryCreature's website, they are NOT going to jump up and go to CompUSA and buy a new PC. No, what they'll do is, they'll go to some other company's website. There are plenty of them on the Web that work on low-resolution screens.

    Maybe SmallFurryCreature works for a company that thinks losing, say, 1% of their customer base to the competition is no big deal. Good luck to him and his company: they're going to need it.

  85. Wrong. by brunes69 · · Score: 1
    Sperating code from data is a good thing. But having the data loaded from an XML file and inlined in the page would be the exact same as this example, avoid the complexities of AJAX, and actually be more performant, because you would get all the information in one request rether than two.

    Your comparison is like apples and oranges. The reason AJAX is good for Google Maps is because it allows you to interact with the map in real time. There is no need to interact with a slideshow in real time, other than to pause / rewind/ fast-forward it, none of which would involve trips to the server anyways.

    Stupid use of AJAX.

  86. Re:This is detailed Ajax, Ken Burns style.WEB-1.0 by pileated · · Score: 1

    do you think there's some sort of connection between perl sigs and a preference for literacy over flashy effects, namely preferring book reading to slide shows?

    next new trend: WEB -1.0.??

  87. Nope, sorry by Anonymous Coward · · Score: 0

    It turns out flash sucks.

  88. (...)Web 2.0 (...) has one buzzword (...) ajax by mlopes · · Score: 1

    What? A buzzword that has one buzzword!?!?!? How amusing!

  89. Ajax is upon me, as i feared, inevitably ... by unity100 · · Score: 1

    I'd known this would happen sooner or later, and it did.

    I am going to devise a tournament system in Ajax for a client of one of my contractors.

    I do not get why the client is too enthusiastic about this new 'collection of scripting languages'. All in all, his site wont be getting any considerable number of users at a given time for justifying the delegation of the server load to client pcs', there is nothing s/he cannot have done with the server side applications, via PHP, MySQL etc, but the client is still very interested in having that way.

    The fact that ActiveX is already used to plant rootkits in home pcs, the load, even if it is a small one, that happens while compiling ajax pages in the visitor pc and the way it occasionally leads to lock-ups in client pc because clients often have 5-6 windows and applications active at the same time, and the idea of scaling down and down the applet further to be fit into operation windows that might get smaller with the number of applications open in a client pc are stuff that can not be taken lightly ...

    I admit that i wonder to undertake such a mid-sized project for testing out and getting accustomed to this new much-hyped technique however. Its good to know, even if you do oppose the disadvantages it brings.

    But my belief still is that, in 1-1.5 years time, many system adminstrators, users, anti-virus, security and privacy programs will be barring or filtering out many functions that comes with the Ajax combination, or allow omly prominent sites like gmail to run in the client pc, due to security concerns. The fact that you can get procedures performed in the remote pc is already an open door to many malicious activity, and the 'black' crowd i guess wouldnt wait long to jump in to the new ride to spread a phletora of malicious stuff. So shortly, best way for many security software, and adminstrators would be to directly filter ajax content coming out from non-prominent sites, ie small sites, to make sure no harm is done on the clients' pc.

    Taking into account the fact that the main advantage of ajax is the delegation of the server load to the client pc - which is something big guys sorely need, but almost maybe 80% of the sites on the internet does not -, and combining it with the possibility of being filtered/barred by the security software/adminstrators as not being a 'big guy', takes me into the conclusion that Ajax is a 'big boys'' tool.