Apache OpenOffice Wiki - User contributions [en]

Issue Tracker

2006-04-28T08:24:34Z

DavidFraser: added start of description of lifecycle

[[Category:Quality Assurance]]
'''Issue Tracker''', formerly '''IssueZilla''', is the software used for tracking bugs and feature requests for [[OpenOffice.org]]. It was forked long ago by [[CollabNet]] from Mozilla's [[Wikipedia:Bugzilla|Bugzilla]].

== External links ==

* [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]
* [http://qa.openoffice.org/issue_handling/pre_submission.html#duplicates Simple Search]
* [http://qa.openoffice.org/issues/query.cgi Advanced Search]
* [http://qa.openoffice.org/issue_handling/pre_submission.html Submit an issue]

== Lifecycle ==

* [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Lifecycle] explains what the Resolved and Status fields mean.
* [http://qa.openoffice.org/issuelinks.html Issue Quick Links] enables you to track a issue and which CWS it belongs to.
* "FIXED" means that an issue is resolved in a CWS, not neccessarily integrated into a master workspace / release build.

Impress multiple display support

2006-03-30T14:51:19Z

DavidFraser: need ppt, link to Linux workaround

= Impress Multiple Display Support =

This is the current status of the implementation of [[Impress simple multiple display specification]] for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719].

== For Developers Only ==

There is a patch available on the bug which will enable using a different monitor on Windows inside vcl. If somebody desperately needs this functionality, they could possibly start from there and produce a build that has no user interface to control the output, but always shows the presentation on the secondary display. Note that no such build currently exists...

There are some stabs at patches for a UI, but that needs more specification work.

== For Users ==

There is no end-user functionality available for this feature yet

=== Workarounds ===

==== Windows ====

You can dispay presentations on a different monitor wihtout requiring Microsoft Office by combining Microsoft's free-as-in-beer [http://www.microsoft.com/downloads/details.aspx?FamilyID=428d5727-43ab-4f24-90b7-a94784af71a4&displaylang=en PowerPoint Viewer] and [http://www.mediachance.com/free/multimon.htm multimon].

For this to work you will need to save your presentation in Microsoft's proprietary PowerPoint format (.PPT).

* Download PowerPoint viewer from http://www.microsoft.com/downloads/details.aspx?FamilyID=428d5727-43ab-4f24-90b7-a94784af71a4&displaylang=en (or search for PowerPoint viewer if that no longer works) and install
* Download multimon from http://www.mediachance.com/free/multimon.htm and install
* Start multimon
* Right click on the multimon task bar (that appears on the secondary display), and select Properties
* Tick "Auto Hide" and "Use Ctrl-Alt Arrows", and untick "Insert Caption Button" and "Add Multi-Text Clipboard"
* Start PowerPoint viewer and select the presentation. It will appear on the primary screen
* With the presentation window focused (in the foreground), press Ctrl-Alt-Right and it will move to the secondary display
* You can then proceed as normal.

Note: The multimon web page says Ctrl-Shift, but its Ctrl-Alt. Ctrl-Alt-Left will move it back.

==== Linux / Unix ====

There is a workaround on Linux that enable you to cunningly reposition the presentation on the secondary display.

You can view instructions on using Xinerama on Linux to do this here: http://documentation.openoffice.org/HOW_TO/misc/multiple_screens.pdf

Impress multiple display support

2006-03-30T14:47:40Z

DavidFraser: added workaround instructions for windows

= Impress Multiple Display Support =

This is the current status of the implementation of [[Impress simple multiple display specification]] for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719].

== For Developers Only ==

There is a patch available on the bug which will enable using a different monitor on Windows inside vcl. If somebody desperately needs this functionality, they could possibly start from there and produce a build that has no user interface to control the output, but always shows the presentation on the secondary display. Note that no such build currently exists...

There are some stabs at patches for a UI, but that needs more specification work.

== For Users ==

There is no end-user functionality available for this feature yet

=== Workarounds ===

==== Windows ====

You can dispay presentations on a different monitor wihtout requiring Microsoft Office by combining Microsoft's free-as-in-beer [http://www.microsoft.com/downloads/details.aspx?FamilyID=428d5727-43ab-4f24-90b7-a94784af71a4&displaylang=en PowerPoint Viewer] and [http://www.mediachance.com/free/multimon.htm multimon].
* Download PowerPoint viewer from http://www.microsoft.com/downloads/details.aspx?FamilyID=428d5727-43ab-4f24-90b7-a94784af71a4&displaylang=en (or search for PowerPoint viewer if that no longer works) and install
* Download multimon from http://www.mediachance.com/free/multimon.htm and install
* Start multimon
* Right click on the multimon task bar (that appears on the secondary display), and select Properties
* Tick "Auto Hide" and "Use Ctrl-Alt Arrows", and untick "Insert Caption Button" and "Add Multi-Text Clipboard"
* Start PowerPoint viewer and select the presentation. It will appear on the primary screen
* With the presentation window focused (in the foreground), press Ctrl-Alt-Right and it will move to the secondary display
* You can then proceed as normal.

Note: The multimon web page says Ctrl-Shift, but its Ctrl-Alt. Ctrl-Alt-Left will move it back.

==== Linux / Unix ====

There are some workarounds on the bug mentioned above on Linux that enable you to cunningly reposition the presentation on the secondary display.

Impress multiple display support

2006-03-30T14:00:35Z

DavidFraser: added current status

NLC

2006-03-29T21:03:03Z

DavidFraser: changed URLs to internal links

{{NLC}}
== Welcome to the Native-Language Confederation Wiki ==
There is a [[List_of_N-L_Projects_Wiki_Pages|long list]] of the Native-Lang projects with wiki pages full of information !

[[NLC:whatshot|What's hot in the NLC?]]

= "''United in Diversity''" =

Here you will find some useful information concerning the Native-Language Confederation (NLC) and Projects.

''How to propose a new Native-Language project''
* Visit [http://native-lang.openoffice.org] for administrative information

* Learn how to differentiate between level 1 and 2 native-language projects
Level 2 projects are "regular" native-language projects, while level 1 projects are mostly localization projects (See [http://l10n.openoffice.org] for more info on localization projects] for whose it makes sense to have some web space on OpenOffice.org . These projects are not supposed to design their web site, manage mailing lists, write documentation, but they are encouraged to work on QA.

* Once you have decided what level your project should choose, you have to:
** Assess your resources (human, material, time to devout to the project)
** Check if your language is not already being localized or considered for localization. See [http://http://l10n.openoffice.org/languages.html] for a comprehensive list of the OpenOffice.org localizations
** Draft and post a proposal on the dev@native-lang.openoffice.org and discuss@openoffice.org lists. Your proposal should describe your goals, your resources and introduce yourself and your team. Please mention what level you wish to give to your project

* Once your project has been accepted by the NLC leads and by the consensus of the native-lang projects' leads, please follow these instructions:
** Indicate the desired domain name for your project: it should be the two or three letters corresponding to the ISO code of your language. BEWARE: Native-Lang projects are based on languages, not on countries!
** Indicate your OpenOffice.org username and if necessary your co-lead's username
** Register yourself to the NLC
** Indicate if you signed and sent/faxed the JCA See: [http://www.openoffice.org/FAQs/faq-licensing.html]
** The NLC leads will open an issue that may take some time to be approved (not more than 10 days) then your project will be set up.

''Now you need to submit your ssh keys and work with CVS''

Whether it is for editing your website or contribute code, OpenOffice.org uses CVS. It is actually the same CVS platform that is being used for both the website and the development platform. In order to be able to use OpenOffice.org's CVS and access your new native-lang project's website you need to:
* Open an issue (separate from the issue opening your new native-language project) and file it as follows: component "www" and subcomponent "openoffice.org website general issues" with your key in attachment. Assign it to "ssh2key". Also make sure to specify what part of the website you want to work with. In the NLC case, that would be your new native-lang project, so specify the two letters forming the domain name of your new project. For example, if your project is http://xy.openoffice.org, specify "xy". If your project is http://xyz.openoffice.org, specify "xyz"
* Read [http://www.openoffice.org/scdocs/ddCVS.html.en] to learn how to use the CVS.

You are ready to go!

'' Initiatives of the Native-Lang Confederation ''

''' Wiki Pages of Native-Lang Projects'''

Some of Native-Lang Confederation Projects started to use this wiki for organizing parts of their work. You can access these wiki pages from the
[[List of N-L Projects Wiki Pages]]

Impress multiple display support

2005-12-19T13:00:10Z

DavidFraser: added status page

Impress multiple display specification

2005-12-19T13:00:03Z

DavidFraser: added lnik to status page

Impress simple multiple display specification

2005-12-19T12:59:21Z

DavidFraser: added link to status page

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification is for a simple enhancement to Impress that would allow selecting the display for full-screen presentations. A related specification for enabling better control of the presentation from another screen is [[Impress presenter mode specification]].

Any discussion of the specification should happen in the issue, or on the discussion pages.

Current status of the implementation is at [[Impress multiple display support]].

= Simple support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. Especially for presentation it would be preferable for the user to be able to configure on which single monitor or on which range of monitors his presentation should be played.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| David Fraser
| davidf@sjsoft.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|-
| 1.2
| split into simple and presenter mode specs
| DF
| 2005-12-15
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Currently Impress will always display a full-screen presentation on the primary display. If there is a secondary display such as a video presenter, it is often required to display on this display, which is currently difficult or impossible.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the standard document editor window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

== Goals ==
Provide a robust and easy-to-use dialog, to allow the user to both select which monitor to display the "main" presentation on.

== Requirements and Dependencies ==

=== Requirements ===
Many requirements are already met, but someone needs to put the pieces together...

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

In order to be complete, the presenter view would be required as well, but simply being able to select the display for now would allow output onto a video projector from laptops, which would make it at least feasible to use OOo in this scenario.

== Detailed Specification ==
This feature includes a dropdown box in the "presentation options" dialog in which the user can choose on which display the presentation is to be shown. This box contains values like "Screen 1" and "Screen 2". The choosable values are adjusted to meet the present situation, e.g. when the second screen is disabled, the user can only select "Screen 1". The selection only matters for fullscreen presentation.

The consequence of the user's selection in the above mentioned dropdown box is that the presentation is shown on the selected screen/display device, but still in fullscreen mode.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
Not required

=== G11n ===
Nothing known.

=== Error Conditions ===
If the secondary screen was selected, but afterwards the user edited the system settings to have only one screen, the presentation is shown on this primary screen. No error message needed.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

Impress presenter mode specification

2005-12-15T12:09:07Z

DavidFraser: No need to link to the original page

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification is for an enhancement to Impress to create a presentation view for controlling a presentation on another display in a multi-display environment. A related specification for being able to display the presentation on another screen is [[Impress simple multiple display specification]]. This is a follow-on to that and requires it before it can be implemented.

Any discussion of the specification should happen in the issue, or on the discussion pages. It will probably be neccessary to create a separate issue for this specification.

= Support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. When displaying presentations on video projectors or alternate displays it would be preferable for the user to be able to include a separate display for the presenter to see and control what is being displayed, along with ancillary (but important) information.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|-
| 1.2
| split into simple and presenter mode specs
| DF
| 2005-12-15
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Would need to specify the exact layout and functionality of the presenter view. Then would require implementation of that mode in Impress.

=== Technical Dependencies ===
Requires the implementation of the [[Impress simple multiple display specification]].

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

== Detailed Specification ==
In the Impress options, there should be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
Nothing known.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

http://www.apple.com/iwork/keynote/presenter.html
Apple's implementation of this feature.

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
An article about Microsoft's implementation of this feature.

Impress simple multiple display specification

2005-12-15T12:08:48Z

DavidFraser: No need to link to the original page

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification is for a simple enhancement to Impress that would allow selecting the display for full-screen presentations. A related specification for enabling better control of the presentation from another screen is [[Impress presenter mode specification]].

Any discussion of the specification should happen in the issue, or on the discussion pages.

= Simple support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. Especially for presentation it would be preferable for the user to be able to configure on which single monitor or on which range of monitors his presentation should be played.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| David Fraser
| davidf@sjsoft.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|-
| 1.2
| split into simple and presenter mode specs
| DF
| 2005-12-15
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Currently Impress will always display a full-screen presentation on the primary display. If there is a secondary display such as a video presenter, it is often required to display on this display, which is currently difficult or impossible.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the standard document editor window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

== Goals ==
Provide a robust and easy-to-use dialog, to allow the user to both select which monitor to display the "main" presentation on.

== Requirements and Dependencies ==

=== Requirements ===
Many requirements are already met, but someone needs to put the pieces together...

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

In order to be complete, the presenter view would be required as well, but simply being able to select the display for now would allow output onto a video projector from laptops, which would make it at least feasible to use OOo in this scenario.

== Detailed Specification ==
This feature includes a dropdown box in the "presentation options" dialog in which the user can choose on which display the presentation is to be shown. This box contains values like "Screen 1" and "Screen 2". The choosable values are adjusted to meet the present situation, e.g. when the second screen is disabled, the user can only select "Screen 1". The selection only matters for fullscreen presentation.

The consequence of the user's selection in the above mentioned dropdown box is that the presentation is shown on the selected screen/display device, but still in fullscreen mode.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
Not required

=== G11n ===
Nothing known.

=== Error Conditions ===
If the secondary screen was selected, but afterwards the user edited the system settings to have only one screen, the presentation is shown on this primary screen. No error message needed.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

Impress multiple display specification

2005-12-15T12:02:15Z

DavidFraser: Have split this into two, reduced to links

Impress simple multiple display specification

2005-12-15T12:01:32Z

DavidFraser: spelling

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification is for a simple enhancement to Impress that would allow selecting the display for full-screen presentations. A related specification for enabling better control of the presentation from another screen is [[Impress presenter mode specification]]. (These were originally together in [[Impress_multiple_display_specification]])

Any discussion of the specification should happen in the issue, or on the discussion pages.

= Simple support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. Especially for presentation it would be preferable for the user to be able to configure on which single monitor or on which range of monitors his presentation should be played.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| David Fraser
| davidf@sjsoft.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|-
| 1.2
| split into simple and presenter mode specs
| DF
| 2005-12-15
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Currently Impress will always display a full-screen presentation on the primary display. If there is a secondary display such as a video presenter, it is often required to display on this display, which is currently difficult or impossible.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the standard document editor window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

== Goals ==
Provide a robust and easy-to-use dialog, to allow the user to both select which monitor to display the "main" presentation on.

== Requirements and Dependencies ==

=== Requirements ===
Many requirements are already met, but someone needs to put the pieces together...

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

In order to be complete, the presenter view would be required as well, but simply being able to select the display for now would allow output onto a video projector from laptops, which would make it at least feasible to use OOo in this scenario.

== Detailed Specification ==
This feature includes a dropdown box in the "presentation options" dialog in which the user can choose on which display the presentation is to be shown. This box contains values like "Screen 1" and "Screen 2". The choosable values are adjusted to meet the present situation, e.g. when the second screen is disabled, the user can only select "Screen 1". The selection only matters for fullscreen presentation.

The consequence of the user's selection in the above mentioned dropdown box is that the presentation is shown on the selected screen/display device, but still in fullscreen mode.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
Not required

=== G11n ===
Nothing known.

=== Error Conditions ===
If the secondary screen was selected, but afterwards the user edited the system settings to have only one screen, the presentation is shown on this primary screen. No error message needed.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

Impress presenter mode specification

2005-12-15T12:01:13Z

DavidFraser: Created presenter mode specification

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification is for an enhancement to Impress to create a presentation view for controlling a presentation on another display in a multi-display environment. A related specification for being able to display the presentation on another screen is [[Impress simple multiple display specification]]. This is a follow-on to that and requires it before it can be implemented. (These were originally together in [[Impress multiple display specification]])

Any discussion of the specification should happen in the issue, or on the discussion pages. It will probably be neccessary to create a separate issue for this specification.

= Support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. When displaying presentations on video projectors or alternate displays it would be preferable for the user to be able to include a separate display for the presenter to see and control what is being displayed, along with ancillary (but important) information.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|-
| 1.2
| split into simple and presenter mode specs
| DF
| 2005-12-15
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Would need to specify the exact layout and functionality of the presenter view. Then would require implementation of that mode in Impress.

=== Technical Dependencies ===
Requires the implementation of the [[Impress simple multiple display specification]].

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

== Detailed Specification ==
In the Impress options, there should be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
Nothing known.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

http://www.apple.com/iwork/keynote/presenter.html
Apple's implementation of this feature.

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
An article about Microsoft's implementation of this feature.

Impress simple multiple display specification

2005-12-15T11:53:57Z

DavidFraser: created simple multi-display specification from Impress_multiple_display_specification

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification if for a simple enhancement to Impress that would allow selecting the display for full-screen presentations. A related specification for enabling better control of the presentation from another screen is [[Impress presenter mode specification]]. (These were originally together in [[Impress_multiple_display_specification]])

Any discussion of the specification should happen in the issue, or on the discussion pages.

= Simple support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. Especially for presentation it would be preferable for the user to be able to configure on which single monitor or on which range of monitors his presentation should be played.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| David Fraser
| davidf@sjsoft.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|-
| 1.2
| split into simple and presenter mode specs
| DF
| 2005-12-15
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Currently Impress will always display a full-screen presentation on the primary display. If there is a secondary display such as a video presenter, it is often required to display on this display, which is currently difficult or impossible.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the standard document editor window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

== Goals ==
Provide a robust and easy-to-use dialog, to allow the user to both select which monitor to display the "main" presentation on.

== Requirements and Dependencies ==

=== Requirements ===
Many requirements are already met, but someone needs to put the pieces together...

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

In order to be complete, the presenter view would be required as well, but simply being able to select the display for now would allow output onto a video projector from laptops, which would make it at least feasible to use OOo in this scenario.

== Detailed Specification ==
This feature includes a dropdown box in the "presentation options" dialog in which the user can choose on which display the presentation is to be shown. This box contains values like "Screen 1" and "Screen 2". The choosable values are adjusted to meet the present situation, e.g. when the second screen is disabled, the user can only select "Screen 1". The selection only matters for fullscreen presentation.

The consequence of the user's selection in the above mentioned dropdown box is that the presentation is shown on the selected screen/display device, but still in fullscreen mode.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
Not required

=== G11n ===
Nothing known.

=== Error Conditions ===
If the secondary screen was selected, but afterwards the user edited the system settings to have only one screen, the presentation is shown on this primary screen. No error message needed.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

Impress multiple display specification

2005-12-15T11:38:05Z

DavidFraser: added link to specification template, removed categories at end

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719]. (Other specifications can be created using the [[Specification template]])

This specification needs to be split into two - [[Impress simple multiple display specification]] and [[Impress presenter mode specification]].

Any discussion of the specification should happen in the issue, or on the discussion pages.

= Support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. Especially for presentation it would be preferable for the user to be able to configure on which single monitor or on which range of monitors his presentation should be played Ideally, this should also include a separate display for the presenter to see what is being displayed, along with ancillary (but important) information.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support, at minumum, the ability to have a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow the user to both select which monitor to display the "main" presentation on, and to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Many requirements are already met, but someone needs to put the pieces together...

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

== Detailed Specification ==
This feature includes a dropdown box in the "presentation options" dialog in which the user can choose on which display the presentation is to be shown. This box contains values like "Screen 1" and "Screen 2". The choosable values are adjusted to meet the present situation, e.g. when the second screen is disabled, the user can only select "Screen 1". The selection only matters for fullscreen presentation.

The consequence of the user's selection in the above mentioned dropdown box is that the presentation is shown on the selected screen/display device, but still in fullscreen mode.

There should also be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
If the secondary screen was selected, but afterwards the user edited the system settings to have only one screen, the presentation is shown on this primary screen. No error message needed.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

http://www.apple.com/iwork/keynote/presenter.html
Apple's implementation of this feature.

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
An article about Microsoft's implementation of this feature.

Specification Template

2005-12-15T11:37:24Z

DavidFraser: remove link to self

Specifications should be made using this template based on the official [http://specs.openoffice.org/collaterals/Specification_template.stw Specification Template in stw format]. Wiki pages should be able to be created based on this template, then they should be converted back to a document using the official template.
This header text should be removed from the Specification, and the document footer should have the HTTP Link to the specification included.

= Specification Title =
= Project =

{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| <Author Name>
| <Date>
| <Draft or Final>
|-
| Conforms to
|
|
|
|-
| Applies to
| <Required - List of modules or applications affected.>
|
|
|-
| Task ID(s)
| <Required - Tasklist comma separated.>
|
|
|-
| Category
| <Feature or Bug Fix>
|
|
|}

=== Abstract ===
<The Abstract is a formal summary of the completed specification. An abstract is an important tool for several different usage scenarios for example it can be reused as an information source for a What's new guide. Abstracts are typically 150 to 250 words long and shall cover the main points of the specification.>

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| <Name + Initials>
|
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
|
|
| <Date>
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| <Term 1>
|
|}

== Motivation ==
<What is the reason for pursuing this project?>

== User Scenarios ==
<A user scenario is a idealized description of a specific interaction. This description shall be written short and specific. User scenarios can describe a leak of functionality, or based on the requirements, a solution.>

== Goals ==
<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 Development, Quality Assurance and Documentation guidance.>

== Requirements and Dependencies ==

=== Requirements ===
<State the requirement(s) of this feature here.>

=== Technical Dependencies ===
<Are there any technical dependencies for this feature? Does the implementation of this feature create any technical dependencies to other program parts? Or very important any issues for automatedd GUI Testing?>

== Competitive Analyses ==
<Describe or reference to solutions which are already on the market. Describe what is done well or what is done bad.>

== Detailed Specification ==
<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.>

<String Lists>

<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 have to provide a caption too, if possible the mockups shouldn't be scaled.For making Screen shots use Alt+Print on Window to capture only the dialog. On JDS, launch from a Terminal window the 'gnome-panel-screenshot' tool. This tools shoots the whole desktop, so you have to crop out the dialog with a tool like Gimp for example.>

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Button
| ~Delete
| ~Entfernen
|
|
|}

==== Tab Order ====
<If necessary Describe or visualize the tabbing order. The description of the tab order has to contain which control has the initial focus.>

==== Key Board Shortcuts ====
<Key Board shortcuts used in dialogs have to be listed in a table with a small description.>

=== G11n ===
<Globalization related topics should be stated here. A globalization related topic is for example when a feature needs to be enhanced to satisfy special regional needs.>

=== Error Conditions ===
<List all error conditions, and the action the system takes about them. If an alert box comes up, which kind is it? Include exact text of messages, or say what points need to be covered. Error Messages need a string list>

=== Migration ===
<Any migration issues have to be stated here. For example how can users migrate from one version of a database to another?>

== Future Tasks ==
<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.>

== Notes ==
<Questions will arise during the writing of the specification. State these in here.>

== References ==
<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.>

Specification Template

2005-12-15T11:36:34Z

DavidFraser: Created templates for specifications made on the wiki

Specifications should be made using this [Specification template] based on the official [http://specs.openoffice.org/collaterals/Specification_template.stw Specification Template in stw format]. Wiki pages should be able to be created based on this template, then they should be converted back to a document using the official template.
This header text should be removed from the Specification, and the document footer should have the HTTP Link to the specification included.

= Specification Title =
= Project =

{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| <Author Name>
| <Date>
| <Draft or Final>
|-
| Conforms to
|
|
|
|-
| Applies to
| <Required - List of modules or applications affected.>
|
|
|-
| Task ID(s)
| <Required - Tasklist comma separated.>
|
|
|-
| Category
| <Feature or Bug Fix>
|
|
|}

=== Abstract ===
<The Abstract is a formal summary of the completed specification. An abstract is an important tool for several different usage scenarios for example it can be reused as an information source for a What's new guide. Abstracts are typically 150 to 250 words long and shall cover the main points of the specification.>

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| <Name + Initials>
|
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
|
|
| <Date>
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| <Term 1>
|
|}

== Motivation ==
<What is the reason for pursuing this project?>

== User Scenarios ==
<A user scenario is a idealized description of a specific interaction. This description shall be written short and specific. User scenarios can describe a leak of functionality, or based on the requirements, a solution.>

== Goals ==
<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 Development, Quality Assurance and Documentation guidance.>

== Requirements and Dependencies ==

=== Requirements ===
<State the requirement(s) of this feature here.>

=== Technical Dependencies ===
<Are there any technical dependencies for this feature? Does the implementation of this feature create any technical dependencies to other program parts? Or very important any issues for automatedd GUI Testing?>

== Competitive Analyses ==
<Describe or reference to solutions which are already on the market. Describe what is done well or what is done bad.>

== Detailed Specification ==
<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.>

<String Lists>

<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 have to provide a caption too, if possible the mockups shouldn't be scaled.For making Screen shots use Alt+Print on Window to capture only the dialog. On JDS, launch from a Terminal window the 'gnome-panel-screenshot' tool. This tools shoots the whole desktop, so you have to crop out the dialog with a tool like Gimp for example.>

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Button
| ~Delete
| ~Entfernen
|
|
|}

==== Tab Order ====
<If necessary Describe or visualize the tabbing order. The description of the tab order has to contain which control has the initial focus.>

==== Key Board Shortcuts ====
<Key Board shortcuts used in dialogs have to be listed in a table with a small description.>

=== G11n ===
<Globalization related topics should be stated here. A globalization related topic is for example when a feature needs to be enhanced to satisfy special regional needs.>

=== Error Conditions ===
<List all error conditions, and the action the system takes about them. If an alert box comes up, which kind is it? Include exact text of messages, or say what points need to be covered. Error Messages need a string list>

=== Migration ===
<Any migration issues have to be stated here. For example how can users migrate from one version of a database to another?>

== Future Tasks ==
<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.>

== Notes ==
<Questions will arise during the writing of the specification. State these in here.>

== References ==
<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.>

Impress multiple display specification

2005-12-15T11:31:15Z

DavidFraser: Updated date, fixed syntax

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719].

This specification needs to be split into two - [[Impress simple multiple display specification]] and [[Impress presenter mode specification]].

Any discussion of the specification should happen in the issue, or on the discussion pages.

= Support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. Especially for presentation it would be preferable for the user to be able to configure on which single monitor or on which range of monitors his presentation should be played Ideally, this should also include a separate display for the presenter to see what is being displayed, along with ancillary (but important) information.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support, at minumum, the ability to have a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow the user to both select which monitor to display the "main" presentation on, and to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Many requirements are already met, but someone needs to put the pieces together...

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

== Detailed Specification ==
This feature includes a dropdown box in the "presentation options" dialog in which the user can choose on which display the presentation is to be shown. This box contains values like "Screen 1" and "Screen 2". The choosable values are adjusted to meet the present situation, e.g. when the second screen is disabled, the user can only select "Screen 1". The selection only matters for fullscreen presentation.

The consequence of the user's selection in the above mentioned dropdown box is that the presentation is shown on the selected screen/display device, but still in fullscreen mode.

There should also be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
If the secondary screen was selected, but afterwards the user edited the system settings to have only one screen, the presentation is shown on this primary screen. No error message needed.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

http://www.apple.com/iwork/keynote/presenter.html
Apple's implementation of this feature.

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
An article about Microsoft's implementation of this feature.

----
CategorySpecifications CategoryIssues

Impress multiple display specification

2005-12-15T11:29:37Z

DavidFraser: removed link to old wiki page (migrated) - improved note on splitting spec

This page exists to make a spec for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 issue 12719].

This specification needs to be split into two - [Impress simple multiple display specification] and [Impress presenter mode specification].

Any discussion of the specification should happen in the issue, or on the discussion pages.

= Support for multiscreen displays (dual monitors) =

= Impress =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-06-10
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. Especially for presentation it would be preferable for the user to be able to configure on which single monitor or on which range of monitors his presentation should be played Ideally, this should also include a separate display for the presenter to see what is being displayed, along with ancillary (but important) information.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support, at minumum, the ability to have a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow the user to both select which monitor to display the "main" presentation on, and to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Many requirements are already met, but someone needs to put the pieces together...

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
MS PowerPoint has this feature and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

== Detailed Specification ==
This feature includes a dropdown box in the "presentation options" dialog in which the user can choose on which display the presentation is to be shown. This box contains values like "Screen 1" and "Screen 2". The choosable values are adjusted to meet the present situation, e.g. when the second screen is disabled, the user can only select "Screen 1". The selection only matters for fullscreen presentation.

The consequence of the user's selection in the above mentioned dropdown box is that the presentation is shown on the selected screen/display device, but still in fullscreen mode.

There should also be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
If the secondary screen was selected, but afterwards the user edited the system settings to have only one screen, the presentation is shown on this primary screen. No error message needed.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
To come.

== References ==
http://www.openoffice.org/issues/show_bug.cgi?id=12719

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
(and many other forum posts over the whole web)

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
(temporary workaround for Linux users)

http://www.apple.com/iwork/keynote/presenter.html
Apple's implementation of this feature.

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
An article about Microsoft's implementation of this feature.

----
CategorySpecifications CategoryIssues

HSQLDB Localization

2005-11-28T14:20:17Z

DavidFraser: added info on using PO files for properties files.

In an effort to provide OpenOffice.org users with localized [[HSQLDB]] error messages (in the form [[HSQLDB Integration|shipped with OOo 2.0]], all error messages are English), a [http://dba.openoffice.org/servlets/ReadMsg?list=users&msgNo=3029 call was made] to the community to volunteer for translating the error messages from the [http://sourceforge.net/project/showfiles.php?group_id=23316&release_id=339171 HSQLDB source] into other languages.

So far, we have volunteers for the following languages:

(The initial list was stolen from [http://qa.openoffice.org/issue_handling/submission_gateway.html#language here], feel free to add your own language/name if you want to participate.)

<pre>
[ ] Basque
[ ] Brazilian(Pt)
[ ] Catalan
[ ] Chinese
[ ] Czech
[ ] Danish
[ ] Finnish
[X] French: Jérôme Paschoud
[X] German: Thomas Kellerer
[ ] Greek
[ ] Hindi
[ ] Hungarian
[ ] Japanese
[ ] Korean
[ ] Laotian
[ ] Malaysian
[ ] Netherlands
[ ] Norwegian
[ ] Portugese
[ ] Romanian
[ ] Russian
[ ] Serbian
[ ] Slovak
[ ] Slovenian
[ ] Spanish
[ ] Tamil
[ ] Thai
[ ] Turkish
</pre>

Note that you can use prop2po.py from the [http://translate.sourceforge.net/ translate toolkit] to convert properties files to PO files. For example,

<pre>
prop2po.py -P sql-error-messages.properties -o po/sql-error-messages.pot
prop2po.py -t sql-error-messages.properties sql-error-messages_it.properties -o po/it.po
</pre>

this yield files like this:

<pre>
#: 001
msgid "08001 The database is already in use by another process"
msgstr "08001 L'archivio Ã¨ in uso da un altro processo"

#: 002
msgid "08003 Connection is closed"
msgstr "08003 Connessione chiusa"
</pre>

Samples from hsqldb 1.8 [http://davidf.sjsoft.com/files/hsqldb-po/ here]

OOoRelease201

2005-11-28T08:28:43Z

DavidFraser: /* possible Showstoppers (needs update!) */ fixed wrong label for 2.0 release page

=== Release Plan for 2.0.1 release===

{| border = "1"
|-
! Task !! Who !! Deadline !! Comments
|-
! last cws integration for first RC / SRC680_m1xx
| mh, RE || 2005-11-10 || SRC680 is closed
|-
! release notes
| mh || 2005-11-23, done || http://development.openoffice.org/releases/2.0.1.html
|-
! Setup Guides
| || 2005-11-13 ||
|-
! Upload of RC builds
| mh || 2005-11-18, delayed, new estimate 2005-11-25 || full install sets for: en-US, fr, es, it, sv, nl, de, pt-BR, ja, ko, th, zh-CN, zh-TW;<br>full install sets with JRE for: en-US, fr, es, it, sv, nl, de, pt-BR, ja, ko, th, zh-CN, zh-TW;<br> lang packs for: en-US, en-GB, en-ZA, fr, es, it, sv, nl, de, pt-BR, ja, ko, zh-CN, zh-TW, af, be-BY, bg, bs, ca, cs, cy, da, el, et, fi, gu-IN, hi-IN, hr, hu, km, lt, nb, nn, ns, pa-IN, pl, ru, rw, sh-YU, sk, sl, sr-CS, st, sw-TZ, th, tr, vi, zu<br>.../contrib/2.0.1rc1
|-
! Update of 680 pages to RC1
| || 2005-11-28||
|-
! Trigger QA of final builds
| (aschnabel) || 2005-11-25 ||
|-
! Track Status of localized builds
| (aschnabel) || 2005-11-25 || http://qa.openoffice.org/localized/status.html
|-
! QA of English RC builds
| (ja) || 2005-11-25 ||
|-
! move RC to final
| mh || 2005-12-01 ||
|-
! press release?
| (craig) || 2005-12-01 ||
|-
! msg to annouce@ooo content
| (craig) || 2005-12-01 ||
|-
! Update of SDK 2.0
| mh || 2005-12-01 ||
|-
! Upload of URE 1.0.1
| mh || 2005-12-01 ||
|-
! Upload of src tarball
| mh || 2005-12-01 ||
|-
! download pages
| st || 2005-12-02 || download.o.o/2.0.1/*, incl. staticization
|-
! upload of solver tarballs
| mh || 2005-12-02 ||
|-
! notification of mirrors
| st || 2005-12-02 ||
|-
! Update of Bittorrents
| (mike!) || 2005-12-02 ||
|-
! Update of P2P page
| (deepankardatta) || 2005-12-05 ||
|-
! press kit update
| (jacqueline) || 2005-12-05 || http://www.openoffice.org/press/2.0/index.html
|-
! homepage
| (louis) || 2005-12-05 ||
|-
! release
| all || 2005-12-05 ||
|-
|}

==== possible Showstoppers (needs update!)====
Check and update:
http://development.openoffice.org/releases/OOo_2_0_timetable.html

* [[Main_ReleaseOOo20|Release 2.0]]

User:DavidFraser

2005-11-14T09:17:24Z

DavidFraser: created user page

===== David Fraser =====

I mostly do stuff for localization - I work for [http://www.translate.org.za/ translate.org.za].

Here's [http://www.translate.org.za/blogs/david/ my blog].