Comments on: Living Off of a G3 http://schwarztech.us/articles/living-off-of-a-g3 Fri, 20 Jan 2012 16:28:41 +0000 hourly 1 http://wordpress.org/?v=3.2 By: John Stalberg http://schwarztech.us/articles/living-off-of-a-g3/comment-page-1#comment-626349 John Stalberg Mon, 07 Dec 2009 04:48:19 +0000 http://schwarztech.us/?p=978#comment-626349 I jusr want to mention that Microsoft has a plug-in for older versions of its Office suite for Windows wich when installed makes it possible to open these new xml office file formats (the new file formats have an x at the end of the name). I don't know if they have done a similar plug for the Mac version but if not I would guess it's on the way. I also belive OpenOffice.org can open the new formats. Googles web apps might be able to open them as well. I belive both th OO.org and Googles web apps matching the Office programs aims at being MS compatible and should therefore be considered as a tools fto use for existing MS Office files. For a more Macish experiense with the OOo functionallity there are the NeoOffice.app. In this perspective I find the Apple programs you mention unnessesary crippled frontwards compatibillity wise. I once made a web site with iWeb. Later, after having updated my OS and iLife I discovered that I would need to have some files from the site project stored on my local machine. to be able to open the site in IWeb. That was so unbelievably stupid (if nessecary at all it could go with the site files and be stored on the web server) I made it to be my first and last experience with iWeb. If an entry level web design application adds complexity and uncompabillity to something that not even the entire Adobe CS Web Premium über suite need, I say it has implemented stupidity in its design. MS Office is a great example of bloat ware but the iLife or iWork stuff seem to be crippled instead. Of course if you know this or put in an effort to read the documentation you can avoid some of this but the unplanned frontwards compatibillity issue is in Apples hands. For once it is MS that has shown how to do it right! Maybe one should consider saving files in an uncomplex file format beside the ordinary format for back up reaspns!? One day it might turn out that you would be happy just to be able to extract the information from a file. The looks and the rest of the bells and whistles isn't always nessesary and could be added again to the plain text, picture, video and other information carrying files, when implemented in some new or different program. I jusr want to mention that Microsoft has a plug-in for older versions of its Office suite for Windows wich when installed makes it possible to open these new xml office file formats (the new file formats have an x at the end of the name). I don’t know if they have done a similar plug for the Mac version but if not I would guess it’s on the way.

I also belive OpenOffice.org can open the new formats.

Googles web apps might be able to open them as well. I belive both th OO.org and Googles web apps matching the Office programs aims at being MS compatible and should therefore be considered as a tools fto use for existing MS Office files.

For a more Macish experiense with the OOo functionallity there are the NeoOffice.app.

In this perspective I find the Apple programs you mention unnessesary crippled frontwards compatibillity wise. I once made a web site with iWeb. Later, after having updated my OS and iLife I discovered that I would need to have some files from the site project stored on my local machine. to be able to open the site in IWeb. That was so unbelievably stupid (if nessecary at all it could go with the site files and be stored on the web server) I made it to be my first and last experience with iWeb. If an entry level web design application adds complexity and uncompabillity to something that not even the entire Adobe CS Web Premium über suite need, I say it has implemented stupidity in its design.

MS Office is a great example of bloat ware but the iLife or iWork stuff seem to be crippled instead. Of course if you know this or put in an effort to read the documentation you can avoid some of this but the unplanned frontwards compatibillity issue is in Apples hands. For once it is MS that has shown how to do it right! Maybe one should consider saving files in an uncomplex file format beside the ordinary format for back up reaspns!? One day it might turn out that you would be happy just to be able to extract the information from a file. The looks and the rest of the bells and whistles isn’t always nessesary and could be added again to the plain text, picture, video and other information carrying files, when implemented in some new or different program.

]]>