RSS

Scrolling Trackpad

Hands-down (pun intended), the design feature with the largest impact for me on the MacBook Pro has been the scrolling trackpad.

I have disabled the trackpad on every notebook computer I have owned. I was looking for the setting to disable it on the MBP when I found the “Use two fingers to scroll” setting on the same pane. I checked, tried it, and I will certainly not be uncomfortable without a mouse on the MacBook Pro again.

It shouldn’t surprise anyone that the company who brought us the solid state touch pad of the 3rd generation iPod scroll wheel (the one that didn’t have to move, it just sensed where your finger went) would bring an innovation like this.

Update: It drives me crazy now when I switch back over to the Dell to grab a few files that were left behind. I don’t have a mouse plugged in over there, so I use the track-pad. It drives me nuts when I drag two fingers down and it doesn’t scroll for me. I appreciate this new feature more and more each time I switch back to the old machine.

 
Leave a comment

Posted by on April 11, 2006 in fribble

 

Tags:

boot camp vs. parallels — early findings

UpdateIt seems the unresponsive mouse issue has a very simple fix. Simply trun down the acceleration a notch as described below. I tried it quickly today and it seemed to improve the performance. I’ll try it out for a day to see if it it’s enough for an everyday environment or not.

In XP, go to Display Properties, Settings, Advanced, Troubleshoot, and slide the slider down one notch, things speed up considerably, particularly mouse tracking and menu hiliting.

Here are two pics snapped with the Treo to satisfy the obligatory “pictures of Windows running on the MacBook Pro.”. Nothing that you haven’t seen in the past week already, but this is a significant milestone in computing, and it’s fun to be a part of it.

Windows will make the MacBook Pro faster and more reliableAs I mentioned in the previous post I had no issues with the installation in either Parallel’s virtual machine nor on Boot Camp’s new partition. Boot Camp was slick, creating the driver disc automatically. And I fully support the marketing claim that Boot Camp offers the “most elegant hard drive utility ever” to create the new partition.

This message during the installation cracked me up during both installations: Your computer will be faster and more reliable.

Windows Partition Option
Apple provides many disclaimers along the journey that this isn’t a supported product. But those are the only hints that this isn’t ready for prime-time. The experience exceeded my expectations on how easy the task would be.

After installing Windows I inserted the Apple drivers CD and everything installed quickly and easily. The only effort required on my part was the continual reasurance that it was OK to install these drivers that weren’t signed by Microsoft. After all the drivers were on board, everything worked as I hoped it would. It took forever on my Dell to get the Bluetooth PCMCIA card to work, but it was only a few clicks to get the MacBook Pro to recognize a Bluetooth mouse. The wireless almost instantly recognizes my router at home, whereas the D800 can take up to 2 minutes to get an IP address after it finds the signal. Performance has been great. The only downside is the inability to see the OS X volume on the same drive.

Parallels Virtual Machine Option
After increasing the RAM to the highest recommended level of 616MB (this machine only has 1GB) the sluggish mouse response disapeared. The speed was actually much better than connecting to servers remotely. The problem is that the rest of the environment became sluggish and when it started to bog, so did the VM. Maybe with another stick of memory inside it could handle both loads simultaneously.

Ebony and Ivory live to gether in perfect harmony side by side on my MacBook Pro

I need to spend a little more time on the Parallel forums to see if there are other tips to creating a stable environment. My true needs in Windows are really only to get to Exchange through Outlook (webmail is no good for those of us that practice GTD and need to empty our inboxes efficiently into local folders) and test our web apps in the IE browser. I’d much rather do all my development work in tools back here in OS X.

Until a tweak is discovered for the settings in Parallels, I’ll continue to live a split life between partitions.

 
4 Comments

Posted by on April 10, 2006 in fribble

 

Tags:

switch

The switch is in progress …

MacBook ProI purchased a MacBook Pro today and I’m in the process of moving in. If you follow my del.icio.us “noteworthy” feed, you’ll know that I was just waiting for the Windows XP dual-boot (or even better VM-ware like) solution to become more stable than a hack. Anyone interested in such things has seen the promising news on both fronts. The ultimate goal is to use a MacBook Pro at home and at work in the Windows-dominated environment of my clients.

So tonight I am just getting settled in on the Mac side; setting up email, moving my iTunes library, and installing all the essential applications. Then this weekend, I’ll take on evaluating the differences between Boot Camp (the dual boot option direct from Apple) and Parallels (the WM-ware option from third-party Parallels). In a perfect world WM-ware would be great as I could live in OSX and just tab out to Windows when I needed to. But I’ve read about performance issues in Parallels (which makes sense). And I have less confidence in a beta from a third-party than I do in a beta from Apple.

I’ll post my findings this weekend. But there’s no need to wait for me. There’s lots of folks out there that have done this testing already.

 
1 Comment

Posted by on April 6, 2006 in fribble

 

Tags:

Prototype generation packages

Until I heard about Axure last week I didn’t know about any tools out there for creating prototypes. But in the last week, I’ve learn the names of two others. The list I’m keeping currently includes:

How did I miss all these before? Please leave a comment if you think there are others that should be added.

I have not spent much time looking at each of these. From what I have seen so far they offer high-fidelity prototypes to make sure that the sponsors/potential users understand how the application will work, look and feel.

I am very curious to see how well it generates code. The other side of the protokit benefit is that developers can also see an authentic design. Ideally, a high-fidelity prototype should look real both on the screen and under the hood. Developers should see all of the presentation assets (images and css) and exactly what mark-up their code (jsp, asp, php, etc.) should generate.

If you’ve had experience with any of these tools (or have examples online that they generated) please leave a comment below. I’m very interested to look at the output.

Ironically, these packages also automatically generate all the document debts that high-fidelity prototypes help eliminate the need for.

 
1 Comment

Posted by on March 31, 2006 in prototyping

 

Freeware color-picker for Windows

For years I used an old version of Tiger Color’s application Color Impact to grab colors from the screen (like the eyedropper in Fireworks or Photoshop). But a few years ago they increased the price to $40, which IMHO is way too much to pay for a feature that should have already been included in MS Office.

Enter Color Cop, a freeware eyedropper for Windows. In the spirit of “Getting Real” (and unlike the bloated Color Impact app) it does just what you need and nothing else. Using this small, light app keeps me from firing up Fireworks when I just need to grab a hex or RGB for some pixel on my screen.

Props to Lifehacker, the source of many great tips.

 
Leave a comment

Posted by on March 28, 2006 in code

 

Anyone used Axure RP before?

If anyone has used Axure for prototyping, I’d be interested in hearing about your experience. I’m particularly interested in the ability to use a library of templates (like protokit) as a base.

 
Leave a comment

Posted by on March 24, 2006 in prototyping

 

Workflow is dead! Long-live workflow!

James Robertson and my co-worker Jeff Potts have a great discussion running on the problems with workflow in content management applications.

Workflows can be infinitely flexible when they are modeled the way work is really done. What’s needed is a model that more accurately reflects how people naturally work.

I think linear workflows are inherently flawed by design. Even in the most extreme example of linear work, a manufacturing assembly line, workers typically have the ability to stop the line and reject an item outright or request rework. But often the rework is something more complex than simply passing the item back to have it worked again.

When these kinds of exceptions occur in most workflow systems today, users create workarounds to the system to get their work done.

About 8 years ago I used a different kind of workflow engine at KMPG when Kevin Parker and I were helping creating an HR outsourcing center. We used a product called Action Workflow to handle all of the transactional items in and out of the center. Action is based on the ActionWorks Business Interaction Model which more realistically models how work is really done. Take a look at the model to see how different it is than the standard linear approach.

The Action model treats work the way it really lives, organically in a cycle of negotiations and performance. New cycles can organically recur in the parents. It’s a completely different (more effective and realistic) way to look at workflow.

I know James and Jeff were trying to keep this product-agnostic. But Action is the only example I know that’s using the cycle-approach. Everything else I know of is linear.

We need ways to systematically track the work that we do. The more accurately they model the way we do work, the less people will use workarounds, and the happier everyone will be.

 
1 Comment

Posted by on March 24, 2006 in process

 

UI Design is more than a pretty face

Luke Wroblewski discusses the benefits and drawbacks of “mockups” (or we could assume “prototypes” as well) in his latest article on UX Matters, Live by the Mockup, Die by the Mockup. The article is a nice summary of ideas many of us have been discussing about the benefits and drawbacks of prototyping. But his conclusion is great, tying these ideas back to the real role of the UI designer:

When interface designers focus too much on mockups rather than product solutions, the design profession may suffer. This type of dilemma already exists for visual designers, who are routinely called upon just to “make things pretty.â€? As a result, every interface designer should focus on building a reputation as a problem solver and communicating that through the language of design and business. The presentation medium will change, the need to solve problems will not.

I often use this quote from Elizabeth Boling at Indiana University because it’s the most consice phrase I’ve found to dispell the too common misconception:

“Designer” does not mean “artist” — though lots of people want to think it does. The job of a designer is not self-expression, it’s problem solving. 

A powerful portfolio then for a UI designer/architect would include business problems with the designer’s solutions. I hope to have such a portfolio posted sometime soon.

 
1 Comment

Posted by on February 17, 2006 in prototyping

 

Champagne Prototyping

Glenn passed along this link to a paper on a new technique for researching end-user functions for complex applications. Their focus seems to be on adding functionality to an existing complex application, but many of their findings support the need for the likes of protokit to develop rich prototypes quickly.

Unlike classic Wizard of Oz, Champagne Prototyping gives the user access to a rich interactive environment that genuinely can be executed on the computer—but the core feature of interest is not actually executable by the computer or even by the researcher. The rich executable context allows the user to interact with the system in order to understand the circumstances in which the new feature would be applied and the effects it will have, but finesses the fact that the feature itself has not been implemented.

Read the Champagne Prototyping: A Research Technique for Early Evaluation of Complex End-User Programming Systems by Alan Blackwell, Margaret Burnett, Simon Peyton Jones for more details.

 
Leave a comment

Posted by on February 7, 2006 in prototyping

 

Navigator Acquired by Hitachi Consulting

So, the conversation I have had with several friends lately regarding Navigator’s aquisition goes like this:

Me: Navigator was bought last week. Now I work for Hitachi Consulting.

Firend: Hitachi? Don’t they make harddrives and TVs? Can you get me an HDTV? 

Yes, they are the same company, but it’s a very big company (think the GE of Japan, they are both very diversified). Hitachi Consulting is a global consultancy that’s the services division of the Hitachi parent company. They now have offices worldwide with bases of operation in Japan, the US, and Europe

I’m excited that Navigator is now part of Hitachi Consulting. We’re contributing our depth of experience in Business Intelligence and Content Management to Hitachi’s larger national presence and broader consulting services. I know it sounds cliche, but it really is a win-win-win for Navigator, Hitachi Consulting, and our collective clients. Read the full press release at the Navigator website.

 
Leave a comment

Posted by on February 6, 2006 in business