[TYPO3-hci] Hello everyone!
Sudara Williams
sudara at web-crossing.com
Thu Apr 5 09:39:15 CEST 2007
> THX Sudara! It is only the first step to write down the Ideas.
> This is far far away from been "something" or better "real" :(
>
@ Jens: Not true! Not only are requirements and sketching a large
part of the process, but one of the most important, and one that has
been lacking in the T3 Dev Cycle for a long time.
> Well.. Anyway.. What can we currently do about getting this project
> further? It seems like the coders of T3 don't have much interest in
> hci.. :-/
@ Andreas: I code and treat usability as just as important as
functionality.
As a newbee to this list, I'm curious about workflow:
Is there much communication and/or feedback with the Core and other
teams?
Are we expected to not only innovate and improve the UI, but
implement it?
Is there any guarantee that the code will be included if we do
implement UI changes?
If so, how much flexibility exists?
Is it worth innovating within the tight constraints of 4.x, or better
to focus on 5.x ?
In my experience building larger web-apps, UI requirements are
collected with the feature set, then the designer and programmers sit
down to find a good balance between clean, understandable feature set
and kick-ass functionality. There are two separate roles - success
comes when both innovate and communicate their needs.
Ideally, with a large product like Typo3 they would wait to build the
feature set (at least in the view) until they receive sketches and
can think about how to implement. The process is smoothed a bit if
the framework of the app is MVC, which most of it is not at present -
I'm not sure about future plans.
Sudara
More information about the TYPO3-team-hci
mailing list