Slashdot Mirror


Early AJAX Office Applications

prostoalex writes "Perhaps many, who viewed Zimbra presentation from yesterday, thought about other office-related applications they would like to see moved to the Web. Richard McManus on ZDNet provides a list of the currently available AJAX apps. Did you know there was AJAX word processor, AJAX spreadsheet, AJAX calendar, AJAX presentation-building software, AJAX e-mail client, AJAX note-taking software and some other interesting applications, which, deployed on your local server, do not need installation and "just work" in a browser window?"

9 of 426 comments (clear)

  1. Web Applications by MadX · · Score: 4, Interesting

    I really like the way that Web apps are starting to make a comeback.
    Yes, it's true that there will always be problems with compatibility in browsers,
    but at the end of the day, to make the underlying OS insignificant, it makes the adoption of alternate OS's become easier.

    Who knows, maybe the pressure will cause other proprietary companies to start looking at the way they
    do business ? A pipe dream now ... but so was flying to the moon !!

    1. Re:Web Applications by trentrez · · Score: 4, Interesting

      Forgive me for saying this, as my understanding of the X Windows model is limited, but aren't rich web applications like this moving towards a server client model similar to how X works. Except in this instance we have the web server serving the applications' content and the browser acting as the client.

      It's quite ironic that all this talk of the OS becoming insignificant is just yet us piling another layer on top of our systems. Shouldn't more effort be focused on making a standard and open windowing system so that developers have one windowing GUI to think about when making their apps (instead of the current big three, namely MS Windows, X Windows and Mac OS X). Yes web apps address this, but in my opinion the way they are approaching the solution is completely backwards.

      Fair enough these web apps allow you to access your program on the move, allowing you to only worry about whether the terminal you are sat at has a nice browser that supports JavaScript, but think about Exchange server when coupled with Outlook Web Access - we suddenly see that these rich AJAX apps are nothing new and are in fact a step in the wrong direction. We should be focused on bringing everything down a level - not piling everything inside a web browser.

      Imagine an OS model where you have a server running at a nice secure location with all your applications running 24/7 then you have a standard windowing desktop client OS that connects to your server to bring up your apps and data where ever you are, be it at work, home or sat on a train on your PDA. I think having a windowing system that would allow this would be far more advantageous than using either remote desktop (VNC etc) or rich web apps (Java, AJAX etc).

  2. Webservices gone mad by ReformedExCon · · Score: 4, Interesting

    Webservices were going to rule the computing world. You'd download apps as you needed them from vendors, then they would automatically bill you for the rental, but only for the time spent using the actual product.

    That idea died a horrible death, despite Microsoft's best efforts to make the Network the Computer.

    Now webservices are back, but instead of building miniature application control building blocks, the entire application interface is downloaded to your browser. Everything immediate runs client-side and anything that needs a backend is sent upstream to the server. No more trying to keep a network connection alive between the client PC and the network server. Everything can be kept very asynchronous.

    It's no surprise that this is the way things are evolving. Even the first CGI programs foretold this type of usage pattern. You'd get an interface on the client side and the heavy processing would be done on the server. But now with faster connections and the ability to run more stuff on the client side, a lot of processing can be and has been pushed off the server and onto the client browser.

    It's very interesting, and quite a pleasant break from the barrage of boring sysadmin-specific stories here.

    --
    Jesus saved me from my past. He can save you as well.
    1. Re:Webservices gone mad by trezor · · Score: 4, Interesting

      ASP.Net are an initiative of what? An awkward merging of two technologies so that ASP developers won't be frightened away?

      Say again? I've done all sorts of programming from Motorola assembly to php and java, both professionaly and purely on a hobby-basis, so I consider my sellf a more than competent and experienced enough developer. I've also worked quite a bit with ASP.NET.

      Sure ASP.NET may not be the right tool for every job, but then again what is? Making web-applications with ASP.NET feels like breeze compared to doing the same stuff in say php. The fact that it's event-based with a solid foundation making that the underlying protocols and technology transparent to developer, actually means that you can immidiately focus on the application logic, and doesn't have to worry about every god damn thing involving web-communication.

      Sure, I know how that works, I know the low-level protocols, I can implement it if I have to, but the fact that I don't need to feels damn good. The .NET Framework supplies tons of goodies for those who know how to take advantage of it.

      For instance, directly coupled database to webpage data-linking, including the ability to manipulate date with next to no programming. Please tell me how this can be done in less than 10 lines of code in php. As a developer, I'm really happy that I don't have to rewrite the same DB-logic, reference the same db-field names, link them to similary named html-controls, and vice-verce for updates. It makes my life simpler. What's wrong with that?

      Dismissing ASP.NET as something that only unskilled developers would use is ignorant at best.

      --
      Not Buzzword 2.0 compliant. Please speak english.
  3. Well... by omgpotatoes · · Score: 4, Interesting

    ..hello GoogleOS! Platfrom-independent, all online, all the applications you need. Who cares if it's viewed out of IE?

  4. Re:Network failures. by Simon+Brooke · · Score: 4, Interesting
    I'd like this if they sold $20 dumb terminals to use it, but I paid a lot of money for a computer that can run applications locally without constantly going to the network.

    Most people - the overwhelming majority - are not competent to use a general purpose computer. They don't understand about basic things like security and backups. Consequently their machines are crawling with viruses and trojans, and when eventually they have a hardware problem they lose, in many cases, months or even years of work.

    For these people, a thin client web appliance using applications hosted remotely on machines maintained by competent people makes a huge amount of sense. And, frankly, that's 90+% of the whole population, so this is potentially a very big market.

    --
    I'm old enough to remember when discussions on Slashdot were well informed.
  5. XMLHttpRequest security issues by Dogtanian · · Score: 4, Interesting

    The problem with Java applets is they require too much to be installed on the client side. This has big security and performance implications

    Security? XMLHttpRequest is very cool, but (albeit for reasons not the same as those you gave for Java), it's likely to fall off its pedestal very soon in the face of these security problems.

    In short, assuming you have the functionality turned on (I assume there is a way to turn it off in present browsers, though I haven't checked), XMLHttpRequest breaks the assumption that web pages only record what you're doing when you "submit" a request (don't think this applies to Flash, but it's normally obvious when a flash app is being used).

    In short, it's theoretically possible for a site to be receiving information about pretty much every action you carry out within a browser window, and practically *quite* possible (and likely) for less than trustworthy sites to be receiving information you'd rather they didn't (if you knew about it); I could go further, but the article pretty much explains it well.

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    1. Re:XMLHttpRequest security issues by Bogtha · · Score: 4, Interesting

      In short, it's theoretically possible for a site to be receiving information about pretty much every action you carry out within a browser window, and practically *quite* possible (and likely) for less than trustworthy sites to be receiving information you'd rather they didn't (if you knew about it); I could go further, but the article pretty much explains it well.

      This is a problem with Javascript in general, not a problem with AJAX per se. It's been possible to leak information in this manner since Netscape 2.0 - you just swap in an image with the URL http://www.example.com/image.gif?timestamp-mysensi tiveinformation.

      Basically, if you don't want a website to know how you are interacting with a page on that website, you need to switch off Javascript altogether.

      --
      Bogtha Bogtha Bogtha
    2. Re:XMLHttpRequest security issues by sheriff_p · · Score: 4, Interesting

      Well before the advent of AJAX, I build javascript to monitor a user's mouse trail and keypresses over a website. It would take this information from event handlers, and serialize it into a cookie, which would be read by the next page they visited on the site, stored, and could then be played back easily through an admin interface.

      If you've been assuming this isn't possible, or in use (the company I built it for still uses it, I believe), you're missing a point here.

      More details in a back copy of TPJ, who I wrote it up for.

      +Pete

      --
      Score:-1, Funny