That's exactly my point. Almost everywhere you see a timeline—YouTube, Quicktime, etc.—it is sized to fill the available space.
YouTube doesn't stick to some "1 second = 1 pixel" rule, they resize to match the UI to its content. And that's the crux of the issue: currently, the UI does not adapt to fit the needs of users. There is no technical reason it can't. if you'd like an example of how confusing the UI can be, just fire up a new installation and try to use the timeline. Or, even take a look at mine: http://skitch.com/arthus/b3fmh/dock It's basically just a jumble of letters and numbers overlaid on top of each other, making the whole thing pretty useless. And this is after from months of blogging. On Jul 27, 2009, at 8:15 PM, Caius Durling wrote: > > On Mon, Jul 27, 2009 at 6:22 PM, Owen Winkler<[email protected]> > wrote: >> We have existing components, and users are familiar with major >> applications' interfaces that scroll automatically when you drag >> contents (like the loupe) near their edges. They are also familiar >> with >> interfaces that allow you to grab the background and scroll the >> entire >> interface. >> > > Major apps with timelines also start off "zoomed in" to the content > that exists, and then "zoom out" to a predefined level as the content > grows longer. Video in iMovie, or sound in Quicktime Player for > example. Users don't have any issue with comprehending this, its using > all of the available screen space to present the current data. > > C > --- > Caius Durling > [email protected] > +44 (0) 7960 268 100 > http://caius.name/ > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
