User Experience
I’d like to show you some of the mockups that have been done so far. They are quite early and are expected to drastically change during the feedback gathering stage.
Mockup | Dashboard (Click to Load Video)
(Contains both text and voice-over)
This is how we envision the Dashboard. It is a combination of a Launcher and event handling. It should provide the user of latest events, similar to how we read the newspaper each morning, along with the ability to launch applications under the proper working-context. The Dashboard is the hub upon which all of Pipi is built.
In this mockup, I’m using the Creator (called “Editor” since more recently) to edit some metadata of an entity within a project.
Mockup | Editor
Metadata can be text-based, or of any data-type such as video, images or sound. I’ve made a clear distinction between two types of metadata and how they relate to Pipi. One category is the time-based metadata. This includes feedback, scheduling or comments. The other type is the content-based metadata. Including shot-lengths, reference images or asset descriptions. Pipi deals only with content-based metadata as it has no concept of time or tasks. In short, content-based metadata is what would be used in automation scripts such as when pointcaching or publishing whereas time-based metadata is used by humans (coordinators).
Prototype | Dashboard (Click click)
Prototype | Editor (Click click)
[HR][/HR]
What do you think of the Dashboard so far?
Jargon
Some of the words used in these and following videos that might seem mysterious.
Entity
Shots, assets, events, users are all referred to as being entities within Pipi. They are the building blocks of production.
Variant
An asset, such as a character, may contain multiple variants. Models, rigs, texture, shaders are all examples of a variant of a single asset.
Job
Projects are referred to as jobs within Pipi
Channel
Groups of metadata inside an entity are referred to as being channels of metadata. Physically, they are different files on disk.