Rockbox mail archive
Subject: RE: The UI design
From: Nielsen Linus (ext) (Linus.Nielsen_at_elema.siemens.se)
> So far, most of the UI interface has been lifted from ideas
> in the original Archos firmware, requested on this list, or
> a product of the intuition of the developers.
That is true. It is also a product of technical limits, like the display and
the buttons. The buttons, for example, already have symbols and text on
them, making it difficult to reassign them to something else. But no, nobody
has given the UI a real thought.
> I think heuristics is fascinating, and that it could be very
> helpful to know what we want our end product to look and act
> like before we finish coding.
This implies that we have a final goal, an "end product", and that we will
finish coding when we reach that goal. I don't think that is the case.
> I think some sort of flowchart or process diagram would be a
> good way to communicate the user interface to each other.
That sounds good. However, the Rockbox is in many aspects a moving target,
so trying to establish some kind of specification may be a tough task.
> Does anyone else think this is a good idea? If so, I
> volunteer to be a focal point for developing this into
> an actuality. I don't know if anyone has concatenated
> a list of UI-specific requests so far, so any help (from
> the list and Sourceforge archives, perhaps) would be good.
You will have to dig through the mail archives and the Sourceforge feature
requests. I guess your mail will generate a discussion as well.
I would like an effort like the one you suggested. It is also very useful
for documentation purposes, and even a possible future user's manual...
Page was last modified "Jan 10 2012" The Rockbox Crew