Gallery and Data Source Panel Layout

OpenOffice.org 1.1 / Geordi

Task ID(s)

iBIS #110432, #110433

Category	Specification Affects

<Other>

Abstract

The panels for the Gallery and for Data Sources are not pinned by default anymore. This document specifies the default layout of Gallery and Data Source panels.

i-Team

Specification Owner	Matthias Müller-Prove	mprove@sun.com
Marketing (MA)		
User Experience (UX)	Matthias Müller-Prove	
Development(DEV)	Kai Ahrens	
Quality Assurance (QA)		
Documentation (DOC)		

Specification Reviews

Version	Reviewer	Comment
Reviewed by UX 06/24/03	Frank Loehamann	<Comment>
	Lutz Höger	
UI String Review <Date>		
Reviewed by QA <Date>		
Reviewed by DOC <Date>		

Document History

Version	Author	Comment
Draft 06/24/03	Matthias Müller-Prove	<Comment>
Final 06/24/03	MMP	
6/25/03	MMP	clarification in 2.1
6/31/03	MMP	4.3 Future Tasks

Contents

Glossary	1

References	1

1	Motivation	1

2	Goals	1

2.1	How does this feature meet the requirements	1

2.2	How does this feature improve the program architecture	1

3	Dependencies	1

3.1	Technical Dependencies / Requirements	1

4	Detailed Specification	1

4.1	Gallery Panel	1

4.2	Data Source Panel	3

4.3	Future Tasks	3

5	Legal Issues	4

6	Notes	4

Glossary

Term	Description
<Term 1>	

References

<Required - Give references to related documentation, such as engineering designs, technical specs, and other sources for related units. Also include links to documents that other sections in this spec need to refer to, such as user opinions usability test reports.>

Motivation

<Required - What is the reason for pursuing this project?>

Goals

The new default size of the Gallery and Data Source panel should be smaller than in OpenOffice.org 1. It has to be made sure that the ratio between the panel and the content area of the document is in good shape, i.e. the major part of the window is still reserved for the content area of the document.

How does this feature meet the requirements

The new default height is about 30% smaller than before.

How does this feature improve the program architecture

n.a.

Dependencies

Technical Dependencies / Requirements

none

Detailed Specification

Gallery Panel

The gallery tiles have a size of 80x80 pixels, with 8 pixel margin between the tiles. Top and left border is 3 pixels. OpenOffice.org 1 opens at a size that displays 2½ rows. OpenOffice.org 1.1 displays 1½ rows by default. The height of the visible content area of the gallery is 3 + 80 + 8 + 40 = 131 pixels. The entire gallery panel takes 187 pixels.

This default size is the same for all OpenOffice.org modules that provide a gallery.

Illustration 1 OpenOffice.org Writer without Gallery

Illustration 2 OpenOffice.org 1 with Gallery in default size

Illustration 3 OpenOffice.org 1.1 with Gallery in default size

Data Source Panel

The Data Source panel has the same default height as the Gallery panel. This makes sure that the data tree to the left can contain 7 rows without the need for scrolling.

Illustration 4 OpenOffice 1.1 with Data Source panel in default size

Future Tasks

MMP-1 Issue. The position of the panels is between Function Bar and Object Bar. It is desirable not to divide the toolbar area into an upper and lower part and to display the panels in the middle. This problem will be tackled for OpenOffice.org 2, because the concept of toolbars will be redesigned from scratch.

MMP-2 Issue. The DataSource panel has to store its size. OpenOffice.org 1.1 opens it always with the default measurements regardless of previous changes by the user.

MMP-3 Issue. Measurement in pixel are kind of useless because text height is measured in appfont. (ask CJ for a definition)

Legal Issues

none

Notes

<Recommended - Questions will arise during the writing of the specification. State these in here.>

<Required – This paragraphs gives the audience idea of what to aspect from this document. It should be described shortly what problem will be solved.>

The source of software product implementation and change is the I-Team (Implementation Team). I-Teams are typically comprised of people who have skills in the areas of Product Marketing, Development Engineering, Technical Publications, and Test Engineering. I-Teams define the features or set of changes (based on input from SCs, customers, Engineering, or Marketing), plan the implementation project, perform the implementation and testing...

Recommended - Please list of technical terms or specialized field of knowledge here.

Required - Give references to related documentation, such as engineering designs, technical specs, and other sources for related units. Also include links to documents that other sections in this spec need to refer to, such as user opinions usability test reports.

<Required - What is the reason for pursuing this project?>

<Required - The goals section must be short but also provide a clear statement of the goals, to achieve with this feature, project or task. A clear statement in this section gives the Development, Quality Assurance and Documentation guidance.>

<Recommended - Describe how this feature will meet expected requirements>

<Recommended - Descripe how this feature will improve the program architecture.>

<Recommended - Are there any requirements or dependencies for this feature? Does the implementation of this feature create any requirements/dependencies to other program parts?>

<Required - First of all the concept section should give the audience an overview of how the new feature will work. When this is done this section has to cover the necessary things to finish this feature. This is the crucial part of the specification. If images are used in the concept, it is very important that these images provide a caption. The caption should be short and has to describe shortly the image. UI Mockups has to provide a caption too, if possible the mockups shouldn't be scaled and our standard user interface font, Andale Sans UI has to be used for strings on dialogs.>

<Recommended - If there are features which couldn't be implemented but have to be implemented in the future. State these in here with a description why the feature couldn't be implemented right now.>

<Recommended - If there are any legal issues to deal with the should be described here. Legal issues could be for example we have to redistribute third party technology. This section can also contain links the Legal Review Tool.If the Specification will be published on OpenOffice.org this section has to be removed.>

<Recommended - Questions will arise during the writing of the specification. State these in here.>

Gallery and Data Source Panel Layout

Page 4

http://ui.openoffice.org/proposals/GallerynDataSourcePanels.sxw

Matthias Müller-Prove

2003-06-24T13:45:55