March 07, 2009
The logic beyond my design for Totem
In fact, there are three reasons beyond my design for timing bar:
- User doesn't focus by his eyes on a media player in the same way he
focus on a word processor.
Word processors have a 'side-focus-angle' which is the start reading/writing point, which is in the top-left side
of the application window (or top-right in middle-eastern languages).
While in media players, there is no language-context. instead, there is a 'black board' hides a lot of events and
surprises waiting to appear once in 'the middle of the screen', so it has a 'central-focus-point', and the whole
application should have this spirit; the spirit of centralization, that's why the timing information shouldn't be
considered as 'status' in a regular status bar in a regular language-context-based application, but it should
appear in a 'central black board' screen, just like the original video central black board! - There is a wide unused area under the 'seek bar', and timing information
appears in a small silly corner in the
application window.
The solution: taking the advantage of this unused area, and putting the timing information in a 'respected board'
in this area, in as size that deserves. - By this suggested design we can make timing board richer, and more
interactive.
Rich: arranging timing information in distributed areas instead of putting it in a one simple line makes it more readable.
Interactive: for example, double clicking on the time numbers to offer the time left with (-) sign, just like XMMP/Winamp.
Categories: Desktop
