1) Well, we should be aiming for a windows 2000 look and feel. UI
Enhancements should be a 3rd party addon, not bundled with ROS, or at
least not the default. Changing the way a proven UI works is a recipe
for disaster.
mf wrote:
Mikko Tikkanen wrote:
Aye. I'm still in. Just have been a tad busy.
I've been watching my
mail but that's about it but since I started my school few weeks ago I
have more time on my hands. At least when project deadlines aren't
pushing too close.
Great.
The school also has new advantages; since I'm
studying UI/usability
design I could do some actual user testing, with live subjects. I
could also get artists involved as the schools also has art teaching.
Be careful not to make ReactOS into some kind of guinea pig for
eccentric design though. One of the most important goals for ReactOS,
interface-wise, is not requiring any retraining for people switching
from Windows.
Max Well wrote:
As you said, there are already two UI designer,
so I would like to
redesign the setup.
I believe the setup is already being UI-ified. Contact Alex Ionescu for
details. See also:
http://www.reactos.org/wiki/index.php/Alex_Ionescu/RosGooeySetup
Richard Campbell wrote:
I don't think i quite understand this...Are
you saying we should develop
a new UI? I don't think so. The Windows UI is standard, and several
million users KNOW this UI. Our UI should be kept as close as possible
to windows without breaking any laws.
I honestly don't know where you got this idea from, but we will be
staying close to the Windows feel, as I explained above.
jwalsh(a)bigpond.net.au wrote:
Richard is correct.
I understand the statement below as a recipe for suicide.
If you are having trouble getting skills on the ground now, this will
make sure you never do.
Being SLAPP'ed by a multibillion business is
no picnic.
What's this, chinese whispering? What exactly did I say we're going to
do which is going to make msft get interested in SLAPPing us? I'm
calling for help to improve our UI which currently is somewhere in the
pre-win95 age.
Martin Fuchs wrote:
Yes, that's the best way: Write down what you
intend to implement
exactly on the Wiki or in Bugzilla. I will help in explorer, winefile
and ibrowser as far as possible. But my available time is limited.
Branching the code is possible, if you want to change explorer
completely. But I would prefer to maintain only one code base. The
already existing "lean-explorer" branch may be enough. ;-)
First off, PLEASE reply ONLY in ros-general. My initial mail states:
Please reply to this mail only on the general
list or to me in person
(if you're not on the list and only get digests), it is only
crossposted in ros-dev to get a wider range of attention.
Keeping track of conversation on multiple lists is only confusing.
Thanks.
As for your suggestion, I'd like to say that I personally dislike
indirect communication like the wiki or bugzilla. Stuff gets done in a
fraction of the time if you can reach a quick concensus by means of word
exchange. I don't know why you seem to avoid IRC, but mailing list seems
alright with me as well. Seeing that you're as "in charge" of the look
of explorer as you currently are, maybe it would be beneficial if you
would join the UI Team yourself? Just a suggestion :).
Cheers,
mf.
_______________________________________________
ros-general mailing list
ros-general(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-general