Vermeer/FrontPage lives in Sharepoint Wiki

This is a story of recursion and the rise and fall and rise of software. I'm one of the few people that could spot this particular example.

It began with Vermeer, later known as Microsoft FrontPage. I knew it well, even the Macintosh versions. Once, before it started drinking sterno and snorting meth, FrontPage was a software classic. I still use FP 98 on my XP box, there's never been anything better at creating hypertext documents.

FrontPage had a terribly swift decline after FP 98, but even in its debauched state it was the forgotten father of two bits of software - the early versions of Sharepoint and today's version of Sharepoint Designer.

I don't use SP Designer, but I use Sharepoint 2007 - a lot. Even on deep inspection there doesn't seem to be much of FrontPage left in the newest version. SP 2007 is an unspeakably awful document management system and file server, and a very clever implementation of a list/table manager.

Oh, and it includes a Wiki built on extensions to the list manager.

The Wiki is where the recursion comes in. As I worked with it, stringing together hypertext documents and switching between list and web views, the deja vu hit. I'd worked this way before.

The Sharepoint Wiki, I realized, maps very easily onto the actions and interactions of Vermeer/FrontPage. It's not as powerful or as quick to use as FP 98, but it's more approachable for novices and it doesn't require a thick client on each desktop.

So a shadow of FrontPage lives on, buried deep within Sharepoint.

Oh, and now I can explain to young folk the appeal of the original Vermeer/FrontPage. It's the super-powerful toolkit you wish you had for your Wikipedia writing.

Update 9/26/08: I had occasion to copy and paste a very long FrontPage document into a Wiki item. It rendered suspiciously well. I know Sharepoint Designer is a descendant of FrontPage, and that Sharepoint Wiki articles are editable using SharePoint Designer -- so maybe it's not surprising that Sharepoint Wiki is very accepting of FP HMTL. You really do feel the inheritance.

Access 2003 and bugs with special characters and escape sequences

Microsoft Access has some curious behaviors with certain characters. They can be very hard to reference in searches or text operations. Most software (ex. grep) uses “escape sequences” or delimiters for characters like #-()[]?* etc that may have special meaning, but Access struggles here.

From the Access Help files (which are impressive, but often like reading the scrolls of a long lost civilization), we can see that even the expected behavior is very obscure:

• Wildcard characters are meant to be used with text data types, although you can sometimes use them successfully with other data types, such as dates, if you don't change the Regional Settings properties for these data types.
• When using wildcard characters to search for an asterisk (*), question mark (?), number sign (#), opening bracket ([), or hyphen (-), you must enclose the item you're searching for in brackets. For example, to search for a
  question mark, type [?] in the Find dialog box.
• If you're searching for a hyphen and other characters simultaneously, place the hyphen before or after all the other characters inside the brackets. (However, if you have an exclamation point (!) after the opening bracket, place the hyphen after the exclamation point.)
• If you're searching for an exclamation point (!) or closing bracket (]), you don't need to enclose it in brackets.
• You can't search for the opening and closing brackets ([ ]) together because Microsoft Access interprets this combination as a zero-length string. You must enclose the opening and closing brackets in brackets ([[ ]]).
• A Microsoft Access project uses different wildcard characters than an Access database uses. For more information, search the Microsoft SQL Server Books Online index for "wildcard characters"…

I love the last bit, where Microsoft hints that even the odd rules Access once used won’t necessarily keep working.

As of June 2008 though things are worse in a patched version of Access 2003. I couldn’t get search on a [ character to work at all, and I had to escape a single quote using: """".

I think software ages at dog speeds, and Access is well into senescence.

Microsoft Access 2GB file size limitation and the Invalid Argument error message

Every time I ran “Make Table” in Access 2003 I got an “Invalid Argument” error message.

Google found the explanation in seconds:

Error message when you run an append query, run a make-table query, or import data in a large Access database file: "Invalid argument"

In Microsoft Access, when you try to run an append query, to run a make-table query, or to import data in a large Microsoft Access database file, you may receive the following error message:

Invalid argument.

This problem occurs when the size of the Access database file approaches the 2 gigabyte (GB) size limitation.

The limitation still exists in Access 2007.

Shades of the old DOS 640kb memory limits. Will we never escape those old 2**n boundaries?

Of course these kinds of meaningless error messages were impossible to decipher in the days before Google. It’s getting hard to remember how things worked back then …

iPhoto strips Finder metadata from image files on import in OS 10.4, fixed in 10.5

I've rewritten this post since original publication.

You can trace the evolution through this Apple Discussion thread: When you drop an image into iPhoto in 10.4.11 the Finder metadata (extended attributes – Spotlight comments, Labels, etc are not copied.

I thought this was an iPhoto bug, and I bemoaned the lack of attention to Finder metadata.

Apparently it's an OS bug! In 10.5 metadata, including Spotlight comments, is preserved.

So I can't blame the iPhoto engineers, but that's a pretty amazing OS bug.

OS X file renaming utilities: alternatives to ABFR

There are hundreds of splogs that claim to review software, but there's a simple trick to getting to the good stuff.

Once you come up with two product names, search for the two in combination. Then when you get to three, search for the three in combination.

Splogs can't auto-generate inter-product comparisons, so this blows away the junk.

I did this as I looked for an alternative to A Better Finder Rename for file renaming. I like ABFR, but I need to pay up again since my version won't work in Leopard (this is why OS updates are so expensive, the OS cost is the least of it).

Before I pay up, I need to scan the free alternatives. TUAW has a good quick review or 3-4 solutions - Name Mangler: batch rename your files,
and Renamer4Mac mentions 2-3.

I like paying for quality products, so I'll probably still pay for ABFR, but I'll at least try the best seeming of the freebies.

Managing video files with the Finder and Spotlight

Imagine, for a moment, you have been engaged in months of ugly struggle with PureDigital's Flip Camcorder, 3ivx's codecs, QuickTime, AppleScript, Automator, OS X, iMovie HD, iMovie '08 and too many other bits of software to name.

Imagine then that QuickTime 7.45, OS X 10.4.11 and the 3ivx codecs PureDigital's Flip camera uses stop working together. (thank you Perian)

It's not just me. Apple's been making lots of customers miserable. I think we're all entitled to free versions of OS X, by hook or crook, for all eternity.

So I was ready to try something very simple for managing our video fragments (there's no equivalent of EXIF for video btw):

Here's how it works with the Flip camcorder:

1. Drag them off the camcorder into my custom video folder (see custom Finder column settings in image below, the built-in software no longer works since I had to remove the official non-functioning Flip codec).
   
   
2. Using 'A Better Finder Rename' I rename the videos to the form: YYMMDD HH MM_##.AVI where the YYMMDD is their last modified date (basically the time Flip stopped writing to the AVI file).
   
   
3. As per Image 1 (below) I click on file and then do cmd-opt-I to open the "Inspector". Now when I go from image to image I can see a thumbnail of the video, click to play the video in the Inspector, and type descriptive comments that Spotlight will search (Spotlight Comments in Inspector). These are part of the standard OS X file metadata. I can also rename the image from the Inspector. No extra clicks or delays. Videos I don't want get a "d" in comments, I delete them later. (It's not shown here, but I've since customized my labels to correspond to the usual 1-5 star rating, renamed labels with the ratings in Finder options, and display the label name in the custom folder view.)
   
   
4. My spotlight searches (Image 2) use the comments. Spotlight (sigh) doesn't show comments in search results (argh), but the Inspector works on Spotlight results. I just open it and view details as I go from result to result.

It's a pretty darned simple workflow, and it's not dependent on any special software functionality. Just QuickTime, Perian, and OS X. I don't file the videos, I toss them into the folder and rely on search. If I end up storing them in some future OS X app the metadata will still be around, and potentially scriptable into some future repository.

Image 1: View of the video folder with inspector open. Files where comment = "d" will be deleted.


Image 2: Results of a Spotlight search, with Inspector open so I can click on a search result and see image and comments.



Update 6/6/08: When you drop an AVI file to iPhoto, iPhoto does not copy the extended attributes. In particular, it doesn't copy the Spotlight comments or the labels. I'm going to go and drink now.

Update 6/6/08b: The loss of extended attributes was a 10.4 defect. It's fixed in 10.5.3.

Nisus Writer Professional - the manual is a work of love

Nisus Writer Professional is not cheap for families. The license covers a single user at a time, so a family like ours with 5 users would need to spend $200 for use on a single machine. Other software has similar policies, but Nisus is very explicit about this during installation. Word and Pages leave such details to the imagination.

On the other hand, some testing shows NWP doesn't enforce the license (though for all I know NWP reports violations). They also have a generous upgrade policy for past licensees.

What else can I criticize about NWP/Nisus Writer Express?

• HTML export is pretty darned unimpressive
• I'm annoyed that NWE didn't survive the migration from 10.4 to 10.5.3. Many of my old apps run fine in 10.5.3, but NWE locked up when I tried to import a simple Word 97 document.
• NWP can't translate a Word Table of Contents into a NWP Table of Contents and vice-versa.
• NWP doesn't do image compression! Word has fabulous image compression, so a 2MB Word document can balloon into a 32MB NWP/NWE document.
  

I'll have more to say about the good things after I play with NWP a bit more. NWE has been my word processor of choice, and, even with the family licensing costs, we're staying with Nisus.

I'll point out one marvelous sign that most everyone else will miss. Nisus has a 400 page work-of-love PDF manual, which is sold as a bound book for $25.

These people love their product. That's a very encouraging sign.

There are some other things, from my time with Nisus Writer Express, that I expect