> We could require people to submit an
>outline of the parts they intend to create for the UI, and if we (everyone
>on the list who'd like to vote) like it and we think it'll work, we tell
>Scott this person should really have an MC licence.
Uli,
I bit my tongue & kept my keyboard quiet when you posted this originally;
but seeing it a second time prompts me to respond. There MUST be an
overall pattern and logic to the UI; otherwise it will come out looking
like a collection of seperate computer science class projects like the Unix
CLI.
This means a group collaborates in advance to set up a basic metaphore and
interface style to be followed throughout the UI. Letting individuals move
forward to implement their ideas for one part of the UI without having a
basic framework of guidelines in place will, IMFO, doom us to something of
lesser quality that we can achieve if we do it right.
In short, I don't see UI development as a collection of small projects that
can be "glued" to gether to produce a whole. People will have to work more
closely together and MUST have an agreed-upon metaphore and approach in
advance.
Rob Cozens, CCW
http://www.serendipitysoftware.com/who.html
"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."
from "The Triple Foole" by John Donne (1572-1631)
