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?"
Remember java applets?! They were suppose to do these kind of things...
Stop with the acronyms for goodness sakes.
AJAX is a floor cleaning product.
I'm sorry to say this, but there are too many people who think something is cool because it uses the latest hip technology. Nobody cares that it is AJAX, they just care that it works well and does what they want.
The sooner OSS and other people writing software out there realise this the better.
Rant over
Great, so now the network being down means I can get absolutely no work done.
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.
And just in case they mentioned that that's not a concern in one of those 40 linked pages, no, I didn't read all the articles, so feel free to yell at me now.
The Ajax apps all look extremely impressive, but I do believe inconsistent UI will eventually plateau the adoption. Developers love to play the artist when there's a clean slate, and everyone will have their own set of icons and widgets.
Developers need to understand that once you're over 25 years old, you don't care to learn brand new interfaces all over again. The closer it looks to something familiar (your Windows/Mac OS UI), the better. For God's sake, if it doesn't look at Windows, at least make the metaphors intuitive.
My recent pet peeve is tiny little icons, just for the sake of tiny little icons. I'm familiar with the standard "Open", "Save", "Copy", "Cut", "Paste", and "Print" icons. That saves real estate over text, and saves me time.
However, With monitors getting bigger and bigger, unique icons will NO LONGER OFFER THE SAME BENEFIT. I'm not going to hover my mouse pointer over every single 8-pixel-by-8-pixel icon you have, just to forget it the next time around because you lined up 50 of them on the toolbar like lucky charms. If there's room for text, and if that saves time, put the text in!
Things where one user needs to access an application from many locations (email for example), or where a group of distributed users need have instant access to shared information (calendar, notes) .. great idea to have a remotely hosted application or data store.
.. I'm not sure of course, but I rather doubt the capability of a javascript based spreadsheet. It might be ok for holding a small set of data and a handful of equations, but I wouldn't much like to view the last 10 years of accounts of a medium sized company with one. It'd be considerably slower than a properly compiled and optimized application.
But for word processing? Spreadsheets? That seems like a waste of bandwidth, and an unnecessary security risk. I've been working remotely for the last 2 years (300 miles from the company office). I've never encountered a situation where a remote service text editor would be preferable to a local app. Given my flaky internet connection that would really be a very bad thing. Whatsmore
http://twitter.com/onion2k
Having only just managed to ween my co-workers off a ton of needless javascript in their applications 'improvements' in web technologies such as AJAX are a concern to me. Having read all about 'Web 2.0' technologies, I'm left to wonder where the business case for all this while STILL maintaining standards in accessibility comes from?
Please note: accessibility means equal access for ALL, it is not a term to differentiate disabled internet users from their able-bodied peers.
So now we have we have to use libraries that work for IE and every other browser separately, we then have rewrite it all for people using accessibility aids that often use scraping techniques to get content from the page and wont update unless the page refreshes, so we have to write a legacy version anyway (of course, you can make the call that the chance of getting sued is low enough not to bother).
Before people say we have to write a ton of code to account for different browsers and accessibility combinations, I work supplying web apps to public sector education bodies and none of my applications require wild cul-de-sacs of code for special scenarios.
We have only just started mastering equal access for all in web applications as it is, the last thing we need is a new generation of web developers who think that "omg cool functionality kthx" > accessibility
Yes. For rather obvious security reasons, XMLHttpRequest is limited to making requests to the host the script originated from. Also it would be way slower than a normal web browser. Plus completely inaccessible, which is illegal in many places.
That falls apart when the browser that isn't the "latest and most popular" doesn't support the technologies your AJAX browser uses.
Bogtha Bogtha Bogtha
Everyone seems to be running around raving about AJAX applications. Why do you all think AJAX is so good? Really? It's cool if you need to update a webpage without reloading (and particularly for server-push), but why do I want server-push functionality in a word processor, spreadsheet, calendar, presentation-building software or note-taking software (note, I've taken e-mail client out of that list, as server push is actually useful there)?
Sure, if these were tools to allow multiple people to work on the same document simultaneously, but these all seem to share data only after it's been saved back to the server. As someone else pointed out, the presentation application doesn't even use AJAX!
Would people please stop using AJAX to mean "Really cool looking Javascript application"? If Javascript applications excite you, fine, you're welcome to them, but please get the terms right...