Hi Jacqueline,

Jacqueline Rahemipour wrote:
Hi Oliver,

better late than never :-) Sorry...


Oliver-Rainer Wittmann - Software engineer - Sun Microsystems Inc schrieb:
Hi Jacqueline,

(...)

- page 4, line 34: Scrollbars become visible in the fields dialog,
if needed. I suppose, that the dialog is not big enough to show the
 headings in proper way, even if tooltips are implemented. I tried
to visualize how it looks like if we have 4 or more levels (see
screenshot http://projects.ooodev.org/qa/crossreferences.jpg). The
feature will be used in large documents with many headings and
levels. Is it possible to implement the dialog resizable?

We also notice this usability issue.
As far as I know resizable dialogs aren't possible in OOo. We also
thought about the width of the selection list box. But, because the
other panes of this dialog uses the same respectively a similar layout, we didn't want to confuse the user.
A colleague has made the following suggestion:
type:        format:
+----------+  +----------+  name
|          |  |          |  +----------+
|          |  |          |  +----------+
|          |  |          |
|          |  |          |  value
|          |  |          |  +----------+
|          |  |          |  +----------+
+----------+  +----------+

selection:
+--------------------------------------+
|                                      |
|                                      |
|                                      |
|                                      |
|                                      |
|                                      |
+--------------------------------------+

Then, we keep the three columns from the other panes and we got a big
list box for the selections.

Yes, this is a possible solution. As you already mentioned, an argument against this structure of the dialog could be the consistency to the other panes.

An alternative could be a similar design to the pane "database". I would prefer, if the boxes for type and selection are placed in the first row, to get the focus on the most important parts in the correct order: First I choose the type, then I choose a reference and after that I choose a format.

In the above example we have this order, this could be confusing:

1    3    4

          5

2

What about that:

type:         selection:
+-----------+  +-------------------------+
|           |  |                         |
|           |  |                         |
|           |  |                         |
|           |  |                         |
|           |  |                         |
|           |  |                         |
|           |  |                         |
|           |  |                         |
|           |  +-------------------------+
|           |  format:        name
|           |  +-----------+  +----------+
|           |  |           |  +----------+
|           |  |           |  value
|           |  |           |  +----------+
+-----------+  +-----------+  +----------+

This example would allow this order:

1    2

     3    4

          5

This is also not the best solution, I suppose. May be it would be helpful to ask the ux-experts.



Thx for your response and your alternative sugesstion.

I will prepare the preliminary specification with both suggestions. Then I will discuss them with the iTeam.


Regards, Oliver.

--
=======================================================================
Sun Microsystems GmbH    Oliver-Rainer Wittmann
Nagelsweg 55             Software Engineer - StarOffice/OpenOffice.org
20097 Hamburg
Germany
http://www.sun.de        mailto:[EMAIL PROTECTED]
----------------------------------------------------------------------
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
----------------------------------------------------------------------
     Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
                  D-85551 Kirchheim-Heimstetten
                Amtsgericht Muenchen: HRB 161028
     Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer
        Vorsitzender des Aufsichtsrates: Martin Haering


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  • [sw-disc... Jacqueline Rahemipour
    • Re:... Oliver-Rainer Wittmann - Software engineer - Sun Microsystems Inc
      • ... Jacqueline Rahemipour
        • ... Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems
          • ... Ian Laurenson
            • ... Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems

Reply via email to