Friday, August 19, 2005

Blogger for Word: a mixed bag

Blogger: Download Blogger for Word

On the one hand, this sounds great. On the other hand, I hate Word and I don't want to buy a copy. Fortunately it supports my ancient version of Word 2000.
Now you can use Blogger right within Microsoft Word. Just download and install the Blogger for Word add-in and a Blogger toolbar will be added to Word allowing you to:

* Publish to your blog
* Save drafts
* Edit posts
I hope there's an API someone else can use ...

Logitech mm50 Portable Speakers for iPod

Logitech Products > Speakers > Stereo - 2.0 and 2.1 > Logitech mm50 Portable Speakers for iPod

A quite competitive portable or small room iPod speaker solution. Good for the kitchen. Cheaper than some of the Altec Lansing solutions and has its own LiOn rechargeable batteries.

Thursday, August 18, 2005

Exotic OS X knowledge: unifying data and resource forks

Mac OS X 10.4.2 (Part 29)

I once spent a few days looking for a way to unify data and resource forks. I didn't come up with anything. So this Macintouch discussion really caught my attention:
I haven't tried this as I don't have any files on a FAT32 volume, but I believe that this technique should work. Obviously, don't throw out the component files until you've tested this solution.

1) Identify the files which are the actual resource and data forks. In Scott's case he seems to understand which is which.

2) Copy the data fork file onto an HFS volume. Let's assume that the copy will be called /Users/me/test.

3) Open the terminal app.

4) Here's the slightly tricky part. You can use the 'cp' command to copy into the resource fork directly. Assuming the resource fork's file name is

/Volumes/Fat32/file/resource.frk, use this command:
cp /Volumes/Fat32/file/resource.frk /Users/me/test/rsrc

Even though /Users/me/test is a file, not a directory, the syntax above is valid (on OS X, not other Unixes). Actually, I think as of Tiger, it's being deprecated in favor of a more extensible fork naming scheme (/Users/me/test/..namedfork/rsrc), but this still works and it's easier.

5) If you (or your applications) care, use a utility to set the new file's Creator and Type. If you're not sure what they are, just open the finder info file in a text editor- they ought to jump out at you. Alternatively, make a new data file with the relevant application, and copy the info from there. I'd probably do this step just to be sure, but most OS X apps don't care about this. The Finder won't care if the file extension is correct and unique. /Developer/Tools/SetFile is a command-line tool that will work, but there are zillions available, some for free.

File Buddy for OS X has some interesting features - creating packages

The most popular file utility for the Macintosh

This Macintouch reference suggests FB is worth a look:
Use some file-system tool (SkyTag's FileBuddy for instance) to tell the MacOS that a certain folder is actually a Package. If File-Names were not ruined in the copying process, and multi-fork resource-files were not part of the deal (they are quite rare these days), then this trick will work for you.

The following FileBuddy screenshot contains an "info" window for file-system objects. Note the "Package" checkbox. That's the one you'll need to set up for the folders that "forgot" they were packages.

Wednesday, August 17, 2005

Wi-Fi Protected Access: where Windows XP SP2 meets OS X

Setting up an encrypted wireless LAN with both Windows and OS X clients used to be very ugly. There was no implemented standard for WEP passphrases, so one had to work around cryptic hex keys. Well, at least if you're using XP SP2 and OS X 10.3.x or later the bad old days are history. Wi-Fi Protected Access (WPA) just works.

My AirPort Extreme is running WPA (my iBook doesn't seem to support WPA2, not sure if that's a Panther issue or a G3 issue). My XP SP2 laptop connecs using the same passphrase my Mac clients use. No problems at all. Apparently since May 2005 XP SP2 also supports WPA2.

This is so much better than WEP -- although I fear my aged iBook doesn't like the CPU burden ...

MacDevCenter.com: Automated Backups on Tiger Using rsync

MacDevCenter.com: Automated Backups on Tiger Using rsync

OS X Pages - A warm and fuzzy feeling

Apple - Support - Pages

I fired up my free trial vesion of OS X Pages (I'm keeping my Office trial in reserve until I really need Office -- if nothing happens in 6 months I'll remove it). I've no idea if it's any good, but there are some things that give me a warm and fuzzy feeling.

For one, the files are Packages. I opened one and found gzipped document, I opened that and found XML I could open in a text editor. Transparent file formats. Very good.

For another, I really liked the strong styles support and the elegant templates. How refreshing after Word's utterly bodged up style sheets and exceptionately ugly templates (Microsoft is clearly unwilling to hire anyone with taste).

Ok, so the first thing I got was a missing font error message. I know it's got to be as buggy as all get out. I'm still going to give it a try.

PS. It probably helps to know that "Pages are actually sections with section breaks." In other words, pages are document components with associated styles, a template is a set of such components. Once you know Pages are really "sections" (in Word parlance) then this document fills in the rest of the pieces (sections/Pages inherit from the currently selected section/Page):
If you want different parts of a document to have different margins, headers or footers, numbers of columns, master objects, or page-numbering schemes, you can divide the document into sections by inserting a section break. Section breaks are useful when dividing a document into distinct parts, such as title pages, chapters, and indices.

When you add a section break, the new section always starts on a new page.

To insert a section break:

1. Click where you want the new section to begin.

2. Choose Insert > Section Break.

The new section has the same formatting as the previous section until you change it...

To remove a section break, click at the beginning of the line that follows the break and press the Delete key.

Tip: You can see where breaks occur in your document by showing formatting characters (also called "invisibles"). To show formatting characters, choose View > Show Invisibles.