Please excuse the accuracy of this post, I don't actually have all of the core codenames remebered, or the versioning thats part of the joke: who on earth can?
I can !!
I would think you are looking for something more like this:
Sunday - Pentium 4 Monday - Celeron Tuesday - Pentium D Wednesday - Centrino Thursday - Core Duo Friday - Pentium 4 Extreme Edition Saturday - Core 2 Duo
The Core Duo is not a Pentium, as the Core series is supposed to replace the Pentium line. Pentium D was a replacement for the Celeron, but not part of the Pentium 4 line.
You will probably be able to do your work locally with your browser since it is possible for AJAX application to delay data sending. Therefore it shouldn't be a problem for Spreadsheet or Word like application.
Ahh, but now you're talking about Google developing non-web-based applications. The whole purpose of "AJAX" style application development is that you can have the advantages of server-side processing while maintaining what appears to be a fluid working environment on the client side. As we all know a standard web page is maintained through links and posts, each one sends a request and processes some data which is then responded to with another page. In Ajax this same thing happens, but JavaScript is used to send the request to the server and then only a portion of the page is updated / changed.
For AJAX to work in this way though it requires that it to connect to a server for more input. By isolating it away from the server, you are talking about downloaded an application module, we'll call this a "Javlash" or maybe a "Flava". In any case, we're talking about a completely different application structure, as all of its processing would have to be local in order to "turn off" the internet connection to type a word document. In order to hand more complicated procedures "like file saving" it just isn't possible to do this in JavaScript. Or at least it is not plausable.
The other piece of the equation which dictates that an Internet connection would be necessary is that on the initial page load, in order for the application to load, it would need to connect to the Internet at least once, so what is the point of designing a dynamic web app that connects only once at the beginning. That's just more hassle then it is worth. Might as well just use a client side only application that will connect to the Google servers for collaboration features if you want a standalone mode.
Personally, as a developer of dynamic web apps, I would never want to run mission critical applications out of a web browser, as I know just how unstable all of the major browsers are, from Firefox to Safari to Internet Explorer, especially when running heavily JavaScripted pages that persist for extended periods of time. I would rather use something like OO.o that gives me all of the features I need and allows me to keep track of my own data.
Slashdot Mirror
I can !!
I would think you are looking for something more like this:
Sunday - Pentium 4
Monday - Celeron
Tuesday - Pentium D
Wednesday - Centrino
Thursday - Core Duo
Friday - Pentium 4 Extreme Edition
Saturday - Core 2 Duo
The Core Duo is not a Pentium, as the Core series is supposed to replace the Pentium line. Pentium D was a replacement for the Celeron, but not part of the Pentium 4 line.
Ahh, but now you're talking about Google developing non-web-based applications. The whole purpose of "AJAX" style application development is that you can have the advantages of server-side processing while maintaining what appears to be a fluid working environment on the client side. As we all know a standard web page is maintained through links and posts, each one sends a request and processes some data which is then responded to with another page. In Ajax this same thing happens, but JavaScript is used to send the request to the server and then only a portion of the page is updated / changed.
For AJAX to work in this way though it requires that it to connect to a server for more input. By isolating it away from the server, you are talking about downloaded an application module, we'll call this a "Javlash" or maybe a "Flava". In any case, we're talking about a completely different application structure, as all of its processing would have to be local in order to "turn off" the internet connection to type a word document. In order to hand more complicated procedures "like file saving" it just isn't possible to do this in JavaScript. Or at least it is not plausable.
The other piece of the equation which dictates that an Internet connection would be necessary is that on the initial page load, in order for the application to load, it would need to connect to the Internet at least once, so what is the point of designing a dynamic web app that connects only once at the beginning. That's just more hassle then it is worth. Might as well just use a client side only application that will connect to the Google servers for collaboration features if you want a standalone mode.
Personally, as a developer of dynamic web apps, I would never want to run mission critical applications out of a web browser, as I know just how unstable all of the major browsers are, from Firefox to Safari to Internet Explorer, especially when running heavily JavaScripted pages that persist for extended periods of time. I would rather use something like OO.o that gives me all of the features I need and allows me to keep track of my own data.