summaryrefslogtreecommitdiff
path: root/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri
diff options
context:
space:
mode:
Diffstat (limited to 'old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri')
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-article-icon.jpgbin5290 -> 0 bytes
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-more.txt1
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-calc.jpgbin50578 -> 0 bytes
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-writer.jpgbin12949 -> 0 bytes
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice-logo.jpgbin7676 -> 0 bytes
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice.txt1
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/reboot.txt1
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/recap.txt1
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/tutorial-accessibility.txt1
9 files changed, 0 insertions, 5 deletions
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-article-icon.jpg b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-article-icon.jpg
deleted file mode 100644
index fa5ce13..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-article-icon.jpg
+++ /dev/null
Binary files differ
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-more.txt b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-more.txt
deleted file mode 100644
index 8b70894..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/ms-more.txt
+++ /dev/null
@@ -1 +0,0 @@
-Just for the record -- Microsoft is not evil. Microsoft is a publicly traded company run by non-evil human beings who work to protect the company's market share and profitability just like any other company. I recently wrote an article for Wired.com [criticizing][2] Microsoft's attempt to foist a "open" standard on office software users, but in spite of what many readers seem to think, I don't think Open Office XML (OOXML) is a deliberate attempt to screw over users. The problem is that Microsoft's best interests and users best interests do not always overlap. For our tech-savvy Monkey Bites readers who'd like a more detailed explanation of how and why OOXML is not good for users, Rob Weir has an excellent post entitled [*How to hire Guillaume Portes*][1] that digs into some of the problems with OOXML in more detail. From Weir's article: >It is quite possible to write a standard that allows only a single implementation. By focusing entirely on the capabilities of a single application and documenting it in infuriatingly useless detail, you can easily create a "Standard of One." ... As I've stated before, if this were just a Microsoft specification that they put up on MSDN for their customers to use, this would be par for the course, and not worth my attention. But this is different. Microsoft has started calling this a Standard, and has submitted this format to ISO for approval as an International Standard. It must be judged by those greater expectations. [1]: http://www.robweir.com/blog/2006/01/how-to-hire-guillaume-portes.html "How to hire Guillaume Portes" [2]: http://www.wired.com/news/technology/software/0,72403-0.html?tw=wn_index_2 "MS Fights to Own Your Office Docs" \ No newline at end of file
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-calc.jpg b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-calc.jpg
deleted file mode 100644
index 9296484..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-calc.jpg
+++ /dev/null
Binary files differ
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-writer.jpg b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-writer.jpg
deleted file mode 100644
index 0c82407..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neo-writer.jpg
+++ /dev/null
Binary files differ
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice-logo.jpg b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice-logo.jpg
deleted file mode 100644
index 9c1b736..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice-logo.jpg
+++ /dev/null
Binary files differ
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice.txt b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice.txt
deleted file mode 100644
index 24c296d..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/neooffice.txt
+++ /dev/null
@@ -1 +0,0 @@
-Mac users are traditionally not big fans of Microsoft and any die-hard Mac fan can argue until they're blue in the face that it's possible to get by without using MS products. But there is one field in which Microsoft software unquestionably dominates -- Office documents. However [competition in the Office field is heating up][1] and more robust alternatives to the MS Office suite are now available. The most obvious alternative to office is [OpenOffice.org][3], but so far there hasn't been a true native Mac port. As it stands now, there is an OS X port but it requires the X11 windowing system to be installed. However, if you're like me and you don't want to mess with X11, there is another alternative -- [NeoOffice][2]. NeoOffice is based on the OpenOffice.org office suite, but it incorporates many native Mac features like Aqua menus, OS X fonts and integration with Apple's mail.app. Die-hard Mac fans will no doubt love the native Aqua look and feel and NeoOffice does a good job adhering to the Apple UI guidelines. In short, if it looks like a duck and quacks like a duck, it's probably a duck, even it it uses Java here and there to take advantage of Aqua widgets. Naturally NeoOffice offers the full set of applications you'd expect in an office suite (including word processing, spreadsheet, presentation, and drawing programs) and it can import, edit, and exchange files with other popular office programs such as Microsoft Office. So how does it stand up in everyday use? Well it depends on what your needs are. For most people the word processing app, Writer, will ably do just about anything you want and exports to MS .doc files with ease. As for reading MS Office files from other people, Writer handled everything I threw at, but some people have reported problems with complex double column formats with embedded images and the like. Also note that at this time Writer does not support the new MS Word format .docx, but a recent update to the NeoOffice homepage says that .docx support will be available later this quarter. If for some reason you need to embed video or other multimedia materials in your documents, you'll want to look elsewhere since those features haven't been implemented yet NeoOffice. I also tested Calc, NeoOffice's spreadsheet program and found it to be slightly less stable (it crashed once while importing a very very large .csv file), but it did an excellent job of importing Ms Excel files. So can NeoOffice replace MS Office? I would say yes for the casual user like myself. If you regularly have to deal with complex MS Office documents your mileage may vary. [2]: http://www.planamesa.com/neojava/en/index.php "NeoOffice" [3]: http://www.openoffice.org/ "OpenOffice.org" [1]: http://www.wired.com/news/technology/software/0,72403-0.html?tw=wn_index_2 "MS Fights to Own Your Office Docs" \ No newline at end of file
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/reboot.txt b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/reboot.txt
deleted file mode 100644
index 04d9e18..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/reboot.txt
+++ /dev/null
@@ -1 +0,0 @@
-<img alt="Any_key_3" title="Any_key_3" src="http://blog.wired.com/photos/uncategorized/any_key_2.jpg" border="0" style="float: right; margin: 0px 0px 5px 5px;" />The Morning Reboot: * OpenOffice.org has [released a patch][1] for a security flaw involving Windows Metafile files. The vulnerability would allow unauthorized code to run, were the unsuspecting user to open an infected file. Although there were no known public exploits or even proof of concept examples, the patch is recommended for all OpenOffice users. [1]: http://news.yahoo.com/s/pcworld/20070104/tc_pcworld/128396 "Patch Issued for Critical OpenOffice.org Flaw" * Speaking of office suites, CNN has a review [slamming MS Word 2007][2]. From the review: "after four weeks of side-by-side comparative testing, I could discern no significant improvement in functionality over Word 2003." [2]: http://money.cnn.com/2007/01/04/technology/wordreview_fsb.fsb/index.htm?postversion=2007010509 "Microsoft's four-letter #&!? Word" * We generally eschew rumor sites like ThinkSecret, but it's a slow week and this one has got screenshots, so what the heck. <b>RUMOR</b>: ThinkSecret [has some screenshots][3] of what *could* be an Apple spreadsheet app to be bundled with iWork '07. We'll know for sure next week. [3]: http://www.thinksecret.com/news/0701iwork.html "Apple Spreadsheet App?" * Running out of room for your movie downloads? Good news, Hitachi just [announced][4] a one terabyte drive aimed at the desktop market. [4]: http://searchstorage.techtarget.com/originalContent/0,289142,sid5_gci1237560,00.html "Hitachi unveils 1 TB drive for retail" \ No newline at end of file
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/recap.txt b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/recap.txt
deleted file mode 100644
index a0fe6f3..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/recap.txt
+++ /dev/null
@@ -1 +0,0 @@
-The Week in Review, in which we recap the more popuar Monkey Bites posts: * We [looked at BitTyrant and BitThief][1], two new torrent clients that emphasize a selfish streak. BitThief, which downloads without sharing is just plain wrong, but the jury is still out on BitTyrant. * On Wednesday we asked if [Apple was the new Microsoft][2]. You can imagine how that went over with the fanboys. * We tried to get in the spirit of the holidays and offered up a bunch of [new year's resolutions for coders][3]. *I will stop making crontab entries to scripts I end up deleting.* D'oh! * Microformats made the news with Firefox [announcing][4] that version three of the popular browser would offer some kind of support. Naturally we [rounded up][5] some tutorials to help you get started. * We declared January "Mac Month" and have been [reviewing][6] [software][7] and of course next week we'll be coming to you live from MacWorld. Personally, I had no idea that the weird little symbol on the corner of the Mac "command" key [is called][8] a *severdighet*. [1]: http://blog.wired.com/monkeybites/2007/01/bittorrent_bull.html "BitTorrent Bullies: BitTyrant and BitThief" [2]: http://blog.wired.com/monkeybites/2007/01/is_apple_the_ne.html "Is Apple The New Microsoft?" [3]: http://blog.wired.com/monkeybites/2007/01/new_years_resol.html "New Year's Resolutions for Coders" [4]: http://blog.wired.com/monkeybites/2007/01/firefox_3_to_su.html "Firefox 3 to support microformats" [5]: http://blog.wired.com/monkeybites/2007/01/tutorial_o_the__2.html "Tutorial 'O The Day: XHTML Microformats" [6]: http://blog.wired.com/monkeybites/2007/01/mac_month_neoof.html "Mac Month: NeoOffice The Aqua Friendly MS Office Alternative" [7]: http://blog.wired.com/monkeybites/2007/01/mac_month_image.html "Mac Month: Imagewell Review" [8]: http://blog.wired.com/monkeybites/2007/01/mac_month_the_c.html "Mac Month: The Command Key" \ No newline at end of file
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/tutorial-accessibility.txt b/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/tutorial-accessibility.txt
deleted file mode 100644
index 1d2eba7..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/01.01.05/Fri/tutorial-accessibility.txt
+++ /dev/null
@@ -1 +0,0 @@
-Wednesday's tutorial touched on [how semantically correct XHTML helps][4] search engine spiders "read" your pages, but spiders aren't the only reason for semantics. Semantics also help people with disabilities by making an elements context clear to assistive devices like [JAWS][6]. But while semantics are a good start, they aren't the end of the story when it comes to accessibility. There is in fact an entire [W3C spec][5] on accessibility and there are many ways that you can improve your sites accessibility (note that these tips are good whether you're using HTML or XHTML). The best and most comprehensive tutorial I know of that deals with accessibility is Mark Pilgrim's [Dive Into Accessibility][1], which isn't actually a tutorial it's an entire book downloadable as html or pdf as well as readable online. Another excellent book-length tutorial is Joe Clark's [*Building Accessible Websites*][3]. While I highly recommend Pilgrim's book, if you don't feel you have the time for something that long, there's also an excellent tutorial on A List Apart called [*What Is Web Accessibility*][2], that will get you acquainted with the basics and point you to a number of other helpful tutorials. [3]: http://joeclark.org/book/sashay/serialization/ "Building Accessible Websites" [2]: http://alistapart.com/articles/wiwa "What Is Web Accessibility?" [1]: http://www.diveintoaccessibility.org/ "Dive Into Accessibility" [4]: http://blog.wired.com/monkeybites/2007/01/tutorial_o_the__1.html "Tutorial 'O The Day: XHTML Semantics" [5]: http://www.w3.org/WAI/ "W3C Accessibility Initiative" [6]: http://en.wikipedia.org/wiki/Job_Access_With_Speech "Wikipedia definition - JAWS" \ No newline at end of file