Interface of The MediaBook CD for Director

Date:    Tue, 11 Apr 1995 00:36:08 -0600
From:    Chris Malley <cvm@BHI.COM>
Subject: review of The MediaBook CD for Director
Now that my latest product has shipped, I've finally had a chance to dive into The MediaBook CD for Director (herein referred to as TMB). Since enough people have seemed interested, and since Terry Schussler solicited feedback from this list, I decided to do a review of the interface. Note that this is a review of the interface only -- there is a lot of stuff on the disc that looks interesting, particularly the Toolbox, that I am still in the process of exploring.

Summary

Here is a summary of my feelings about TMB's interface. (Details and specific examples follow.)

For me personally, the interface isn't very useful, mainly because of the lack of depth, sparse links, and lack of keyword search. It may be ok for a novice who's doing their first serious Director project, but I can recite the Lingo manual in my sleep (scares the hell out of my wife) and have committed most of the Macromedia tech notes to memory. I would have been more satisfied if given only the Toolbox folder and asked to send in $50. Hopefully I'll get my $256-worth out of plowing through the Director samples.

Platform & reviewer

I've been using 2 Macs to explore TMB: Performance was adequate on both machines, but more "wait cursor" type feedback would be useful, especially when opening MIAWs. I also intended to give it a spin under Windows, but decided I had enough feedback to provide based on my Mac experience.

I spent about 8 hours exploring the interface and making notes, then another 3 hours writing up this review. So if anyone's going to flame me or take offense, take a deep breathe first and remember that I put in $600 of my time and $256 of my cash to do this. I'm doing this because I give a shit, not because I want to trash someone's product. I think gray matter design is genuinely interested in helping the Director community. If I didn't believe that, I'd be whining for my money back instead of writing review notes.

As for qualifications, I've been a serious Lingo programmer for 5 years, and a UNIX programmer and UI designer for 15 years. I've done products with pretty traditional interfaces and some with pretty far out ones. (Not to infer that I know it all...)

Interface overview

For those of you who haven't seen TMB, here's a brief overview of the interface.

TMB is divided into 6 sections, all accessible only from the main screen:

Interactive Lingo Dictionary
(detailed info on Lingo keywords)
Reference Library
(article covering general topics)
Lingo Library
(ready-to-use handlers)
Director Toolbox
(suite of development tools)
XObject Studio
(collection of XObjects)
Resource Directory
(directory of additional resources)

There is also a Help section, which is likewise available only from the main screen. (So if you need help, back to the main screen you go.)

Each section operates in the same basic way. When you're in a section, you choose from a list of items and get two things: a scrolling list of text describing the chosen item, and a scrolling list of related items (or "links").

What's visible in the list of related items is controlled by 3 buttons labelled as follows:

Since the related items list is generally pretty short, it probably would have been better to do away with these buttons and show all related items at once, color-coded to indicate which ones where Topics/Examples/Lingo.

In addition to the sections, there are 4 omnipresent "tabs" along the left edge of the screen. These tabs pull out to reveal additional features. (The documentation calls them "additional navigation features", but some of them have nothing to do with navigation.) Here are the contents of the tabs:

Utilities tab:
Copy To Folder
Copy To File
Print
Mark Code
Bookmarks tab:
Define
Remove
Access
Clear All
Indicies:
General
Lingo Keywords
Lingo Library
XObjects
Options:
Font Size
Sound Level
Copy To Volume
Default Links

The rest of this review is going to consist of detailed observations about the sections and tabs. (Some of this may be of interest only to Terry, and might not even be comprehensible if you don't have TMB.)

"Sections"

Some general comments on the "sections" part of the interface:

This is close, but there are a few things that are bringing the usability down. To elaborate...

When you enter a "section", you're presented with 2 scrolling lists. Initially, the left list contains your choices and the right list contains some instructions. When you select a an "entry" from the left list, things suddenly flip-flop -- the left list contains details about the entry, and the right list is a set of related choices (or "links"). To get back to the first list of choices, you have to press a brain icon. To get back to the main screen, you have to press the brain icon twice. You cannot go from an entry immediate back to the main screen. The implications of this are:

My suggestions for improvement are as follows:

Advantages to this approach:

Specific comments:

  1. Interactive Lingo Dictionary

  2. Reference Library

  3. Lingo Library

  4. Director Toolbox

  5. XObject Studio

  6. Resource Directory

  7. Help

"Tabs"

Some comments on tabs:

My biggest beef is best described by an example. Bookmarks>Add can be pushed at any time, but it's only appropriate to push it when you're viewing an entry in one of the sections. Yet the feedback is the same whether pushing Add was effective or not. Why expose a feature in circumstances where it doesn't do anything?

It's also not obvious what object the actions in the tabs are being applied to. You have to learn by trial and error. Interfaces usally follow an object-action or action-object behavior. TMB tries to be object-action, but you're never really sure what the object is, or if you were successful.

Tab buttons don't behave consistently. When a tab is retracted, it exhibits rolloff behavior (sort of -- the button hilite doesn't toggle as you move on and off the button.) When it's extended, it doesn't exhibit rolloff behavior. None of the feature choices exhibit rolloff behavior.

Specifics:

  1. Utilites>Copy To Folder
    This displays a dialog that prompts you for a filename. The text field looks like it's about 60 chars wide and allows you to type in a huge number of chars. This name is truncated to the Mac filename limit. (Hmmm... wonder what happens on Windows.)

  2. Utilites>Copy To File

  3. Utilities>Print
    Not much to say here, except the feedback for "successfully printed" and "didn't do a thing" is the same. This should kill quite a few innocent trees.

  4. Utilites>Mark Code

  5. Bookmarks>Define

  6. Bookmarks>Remove

  7. Bookmarks>Access

  8. Bookmarks>Clear All
    no icon to signify level of alert. See the standard caution alert box in the Apple HIG.

  9. Indicies
    selecting any one of these causes any similar MIAW to be closed. If I can't have multiple MIAWs, then you might as well move the button on the Indicies tab (and the Bookmark list) into the MIAW and handle the selection there so you don't get the performance hit of opening/closing MIAWs.

  10. Options>Font Size

  11. Options>Sound Level

  12. Options>Copy To Volume

  13. Options>Default Links

Other stuff

  1. As noted by others, the opening movie plays in the upper left corner of the screen, then jumps to the center of the screen. As a result, my first impressions were: rush job, questionable QA process, Is the important stuff going to work if stuff like this is broken? I paid big bucks for this? (This impression was somewhat tempered by the fact that I was prepared for this -- I read a report on the DIRECT-L list, as well as Terry's response.)
  2. Dialogs are pretty crude looking. No visual distinction between title and message text, and the title is often different than the label on the button that was pushed to open the dialog. Lack of Cancel buttons makes many dialogs harder to use. No use of icons to signify level of alert. See the Apple HIG.
  3. Credits: inconsistent use of fonts between the different entries.
  4. Text: A good portion of the text could stand proof reading and/or editing by a Lingo-literate technical writer.