Specification Filter control property

Specification Status
Author	Christoph Lukasiak (Clu)
Last Change	19 Jan. 2010
Status (Help)	Preliminary

Abstract

The 'filter control property' will provide an additional fast and easy way of searching data sets from a database, inside a database form. Therefore every control, which is connected to a data field, get the possibility to became a filter control. After that it can filter corresponding data sets in a database. This additional property can be set in the 'control property browser' dialog.

References

Reference Document	Check	Location (URL)
Prerequisites	[passed/failed]	n/a
Product Requirement, RFE, Issue ID (required)	[available/not available]	<PLEASE ENTER LOCATION HERE>
Accessibility Check (required)		See accessibility section for check list
Test case specification (required)	[available/not available]	<PLEASE ENTER LOCATION HERE>
IDL Specification	[available/not available]	<PLEASE ENTER LOCATION HERE>
Software Specification Rules	n/a	n/a
Other, e.g. references to related specs, Product Concept Document		<PLEASE ENTER LOCATION HERE>

Contacts

Role	Name	E-Mail Address
Developer	Frank Schoenheit	Frank Schoenheit
Quality Assurance	Marc Neumann	Marc Neumann
Documentation	Uwe Fischer	Uwe Fischer
Icon Design	Stella Schulze	Stella Schulze
User Experience	Christoph Lukasiak	Christoph Lukasiak

Acronyms and Abbreviations

Acronym / Abbreviation	Definition
<WYSIWYG>	<What You See Is What You Get>

User scenario

By creating forms there is to consider that you have mostly two completly different groups of user: 1. the form designer who is, in the most of cases, a well experienced professionell and 2. the form user which can be totally unexperienced, but have to serve the created form afterwards, maybe several or more times.

1. the form designer create a form, containing a filter field and can previously define what he propose to search and how it looks like. In example he can use listboxes wich contains already filter contents like names (smith, barnes, morrison) or similar stuff what improves the search and is not possible with the current filter tools. He can design how it looks like, define the label text or add a run button and so fit his form to his user group and data.

2. the form user is in many cases rather unexperienced and will not understand easyly how to use the current form tools in a proper way. With this additional filter field he get the possibility to filter, how the form designer has arranged it, inside the form he actually use (not in toolbars, dialogs etc.). This allows a fast and easy way of getting the desired data out of a database form. If the form contains a search field he just have to click into it, insert filter phrase and return (or select one from listbox) to start the filter and get the result row set.

Detailed Specification

1. 'run filter' button (navigation bar & form navigation toolbar or action button)
2. possibility to make a 'run filter' button from any button
3. info text 'Find' (grey) inside control
4. Filter field: in control property browser on tabpage 'data', second field after 'Data field', named: 'Filter field' (yes/no) -> 'no' as default
5. lifefiltering: in form property browser on tabpage 'data', after 'Sort', named: 'Allow lifefiltering' (yes/no) -> 'yes' as default

additional features:
- run with return or 'run filter button'
- remove filter button removes all filter
- input text parts or search conditions (meye.., like meyer, >3 ..) possible
- all fields (if you have more than one filter field) and filters are 'and' combined (also already in use 'autofilter' or 'form based' filter)

Help | User Interface Element Templates | Example Spec

Accessibility

Accessibility is the responsibility of the I-Team, beginning with UX, DEV and QA, to ensure that the following requirements are fulfilled:

1. Is the feature fully keyboard accessible?
   (Ex: "I can go everywhere and use every function using the keyboard only"
   <START TYPING HERE>
2. Have I specified visual alternatives for the case that the specified feature includes audio as output?
   <START TYPING HERE>
3. Are text alternatives for all icons and graphics available?
   <Start typing here>
4. Don't provide important information in colors alone
   (Ex: marking important information hard coded in red)
   <START TYPING HERE>
5. Does the specified feature respect system settings for font, size, and color for all windows and user interface elements?
   <START TYPING HERE>
6. Have I ensured that flash rates do not exceed 2 hertz for blinking text, objects, or other elements? In any case, try to avoid flashing UI elements
   <START TYPING HERE>
7. Ensure that assistive technology (AT) (like ZoomText or Orca) is able to read everything.
   <START TYPING HERE>

QUESTIONS?

If you need help while designing, implementing or testing the accessibility of the UI, ask/visit:

1. The accessibility check list at the OpenOffice.org Wiki
2. accessibility@ui.openoffice.org (The accessibility mailing lists, preferred)
3. For specific implementation details, architecture: mt@openoffice.org (Malte Timmermann)
4. For specific UX and testing questions: es@openoffice.org (Éric Savary)

Migration

<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>

Configuration

<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>

Help | Configuration Table Template

File Format

<START TYPING HERE --- If this part is irrelevant state a reason for its absence.> Help

Help | File Format Table Template

Open Issues

<State a bulleted list of issues Issue here>