[Usability] HIG - Human Interaction Guide
- From: "Nickolay V. Shmyrev" <nshmyrev yandex ru>
- To: usability gnome org
- Subject: [Usability] HIG - Human Interaction Guide
- Date: Fri, 03 Jun 2005 04:58:59 +0400
Hi all.
There is one thing I was always wondering. HIG nicely specifies how
Gnome Application should look, but it says almost nothing about not less
important thing - how application should behave. And a bit's of helpful
information about behavior are deeply hidden.
Just quick review of gnomefiles application shows that they all are
different, even if the look similar, they work in completely different
ways. There are a lot of moments that can and should be cleared, let me
point to some of them:
How application should save it's geometry - on per-document basis or
globally. What to do on document overwrite or input-output error. How
application should work with document metadata. How to provide document
navigation (browser-like style or another way, I have no ideas). How
handle multiple documents, what to do if users request tabs. Should
application provide file menu or something like this. What should task-
based application do, or do non-document application allowed. When
developer should write applet and when use notification area. Should applications
be spatial.
Is it possible to append such chapters to HIG or it should be standalone
document?
I know, that without appropriate support of development platform it
would be hard to reach consistency in application behavior, but HIG
experience shows that just writing a standard of something similar helps a lot,
supporting libraries would be much easier to write if there will be
document with detailed description.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]