Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Wednesday January 24 2018, @08:14PM   Printer-friendly
from the film-at-11 dept.

I regularly read the Knowing and Doing blog of Eugene Wallingford who is Associate Professor and Head, Department of Computer Science at the University of Northern Iowa. In a sequence of blog posts, he artfully raises some concepts of film editing to a much wider application than just films.

We start with a blog post 95:1 that introduces a book he is currently reading:

This morning, I read the first few pages of In the Blink of an Eye, an essay on film editing by Walter Murch. He starts by talking about his work on Apocalypse Now, which took well over a year in large part because of the massive amount of film Coppola shot: 1,250,000 linear feet, enough for 230 hours of running time. The movie ended up being about two hours and twenty-five minutes, so Murch and his colleagues culled 95 minutes of footage for every minute that made it into the final product. A more typical project, Murch says, has a ratio of 20:1.

He continues this thread with a later entry The Cut:

Walter Murch, in In the Blink of an Eye:

A vast amount of preparation, really, to arrive at the innocuously brief moment of decisive act: the cut -- the moment of transition from one shot to the next -- something that, appropriately enough, should look almost self-evidently simple and effortless, if it is even noticed at all.

[...] Reading Murch has given me a new vocabulary for thinking about transitions visually. In particular, I've been thinking about two basic types of transition:

  • one that signals motion within a context
  • one that signals a change of context

These are a natural part of any writer's job, but I've found it helpful to think about them more explicitly as I worked on class this week.

And, more recently, Footnotes, expands on that concept and by noting:

While discussing the effective use of discontinuities in film, both motion within a context versus change of context, Walter Murch tells a story about... bees:

A beehive can apparently be moved two inches each night without disorienting the bees the next morning. Surprisingly, if it is moved two miles, the bees also have no problem: They are forced by the total displacement of their environment to re-orient their sense of direction, which they can do easily enough. But if the hive is moved two yards, the bees become fatally confused. The environment does not seem different to them, so they do not re-orient themselves, and as a result, they will not recognize their own hive when they return from foraging, hovering instead in the empty space where the hive used to be, while the hive itself sits just two yards away.

This is fascinating, as well being a really cool analogy for the choices movies editors face when telling a story on film. Either change so little that viewers recognize the motion as natural, or change enough that they re-orient their perspective. Don't stop in the middle.

I am still digesting this, but it leads me to wonder if the applications with which I've had the most difficulty might be guilty of failing to properly handle these transitions. In some cases the "language" is verb, noun (e.g. Open, File...) and in other cases it is Noun, Verb (e.g. Select text, Italicize). Have you run into this? What are the best/worst examples you have encountered?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Informative) by Anonymous Coward on Wednesday January 24 2018, @11:12PM

    by Anonymous Coward on Wednesday January 24 2018, @11:12PM (#627445)

    The best menus seem to be object oriented.

    Pull down the menu and you will notice that it is designed for you to select a noun - an object - and then, secondarily, tpo select a verb - an action to apply to that object.

    I've tried to explain this to people but at the time that I present this concept to them they are usually struggling to wrap their heads around 'what is a file' and don't have a lot of bandwidth left for design philosophy.

    However, it's clear to me that the original programmers who conceived of this menu structure - perhaps at Xerox PARC? - were religiously applying object orientation to everything - even menu design - and I applaud them for this.

    Object orientation is a huge topic. I don't think normal people understand how much it influences the design of software or databases because it doesn't involve them, but when it comes to menus, it seems to me that, somewhere along the line, we lost something of value, and have spent decades struggling to get along without it, and that we would do better to spend some time introducing people who want to understand computers, to, not just the abstractions we use, but to the very process of identifying those abstractions - IE, Warnier-Orr Analysis or something similarly flexible.

    My $0.02, YMMV, etc.

    ~childo

    Starting Score:    0  points
    Moderation   +2  
       Informative=2, Total=2
    Extra 'Informative' Modifier   0  

    Total Score:   2