Could the stand-alone rich client learn from a Web app technique?

Via Scoble, I saw this item on another blog by Matt Raible that talks about what he calls the Fade Anything Technique (based on 37 Signals own Yellow Fade Technique). Basically, when you are updating content on a page/web form (he uses the Basecamp example), he has some script that highlights your new entry and then lets it fade after three seconds.

In a way, it's not a BIG deal because you know you made the update, and the highlight-and-fade script lets you visually, yet unobtrusively see what you did. Nonetheless, it's a subtle thing, a sign of polish and maturity. I like it.

Could we use this kind of thing in a non-Web app? What about Word? I regularly paste huge chunks of text in my documents, and I have trouble quickly ascertaining the limits of what I just inserted. It might well be very helpful to have a temporary background on that text so I can get a better picture of what just happened in my insert. I'm going to spin up some VBA code in the morning to see if I can mimic their experience.

This may be a case where the Web is providing a richer experience than the traditional stand-alone app.

BTW: I used BlogJet before it was a real product, and I liked its features. I thought I would give it a try now that it is all grown up. Turns out it has trouble negotiating proxy servers. Uninstalled. Still looking for a mature .Text compliant blog editor. BlogJet failed. Any suggestions?

 Rock Thought for the Day: Have not yet listened to Audioslave's new album. My colleague next door, Andrew May was jamming to Everlast this morning. Nice.

Comments (3)

  1. Shane Wright says:

    You may find SubEthaEdit interesting:

    The focus is different (its a programming editor, built for collaboration), but it uses the ‘highlight added/edited text’ idea quite well.

    I use it (minus the collaboration), and the highlighting of what I’ve changed is very very useful!

  2. "I’m going to spin up some VBA code in the morning to see if I can mimic their experience."


    What, not .NET?


    <grinning, ducking and running>

    Seriously though, how do *you* choose between doing something in VBA vs VB.NET/C#? Why did you choose VBA in this case?


    Stephen Bullen

Skip to main content