Apache OpenOffice Wiki - User contributions [en]

EIS

2010-02-01T18:52:40Z

Mox: /* Overview */ fix broken link

[[Category:Quality Assurance]][[Category: Development]][[Category: Specification]][[Category:CWSTooling]][[sl:SL/EIS]]
== Overview ==
[http://eis.services.openoffice.org EIS (Environment Information System)] consists of a database keeping information about [[MWS | MasterWorkspaces (short MWS)]] and [[CWS | ChildWorkspaces (short CWS)]] as well as some additional things, a web-frontend used by everyone involved with work on [[CWS | ChildWorkspaces]] ( eg. [http://development.openoffice.org/ developer], [http://qa.openoffice.org/ QA] member, [http://documentation.openoffice.org/ Documentation] writer, member of [[User_Experience_Community | User Experience Team]], those working on [http://l10n.openoffice.org/#l10n localization] and [http://l10n.openoffice.org/#i18n internationalization] etc. ) and a [http://en.wikipedia.org/wiki/SOAP SOAP] interface used by a bunch of [http://tools.openoffice.org/dev_docs/ooo-cws-tools-doc.sxw commandline tools] which are used by developers to create and maintain [[CWS | ChildWorkspaces]].

You can [http://eis.services.openoffice.org/EIS2/Logon log into] the web frontend at [http://eis.services.openoffice.org http://eis.services.openoffice.org] with your OOo email address (including @openoffice.org) and your OOo password. A [http://eis.services.openoffice.org/EIS2/GuestLogon read-only anonymous access] is also available there.

[http://eis.services.openoffice.org EIS] is also needed if you want to write [[feature announcement]] mails or [http://eis.services.openoffice.org/EIS2/servlet/changesmails.ShowAPIChangesMails api changes] to inform developers, Quality Assurance (QA) engineers, localization- (L10N) and documentation-people about changes in the office code or if you want to [http://eis.services.openoffice.org/EIS2/guide.CheckSpecification check] [http://specs.openoffice.org/ Specifications].

Additionally [http://eis.services.openoffice.org EIS] provides a few [http://en.wikipedia.org/wiki/RSS_(file_format) RSS feeds] with information about [[CWS | ChildWorkspaces]] and [[MWS | MasterWorkspaces]]. The [http://eis.services.openoffice.org/EIS2/cws.rss.CWSAnnounceNewsFeed/MWS feed that informs about new milestones on MasterWorkspaces] for example is [http://en.wikipedia.org/wiki/Web_syndication syndicated] on [http://go-oo.org/planet Planet OpenOffice.org]. These can also be found on the [http://eis.services.openoffice.org main EIS page].

Recently results of [[tinderbox]] have also been integrated into the [http://eis.services.openoffice.org EIS] web frontend.

== Background and general Information ==
Development on [[OpenOffice.org]]/[[StarOffice]] is using [http://tools.openoffice.org/dev_docs/OOo_cws.html branches] in the source code repository (currently [http://en.wikipedia.org/wiki/Subversion_(software) SubVersion] previously [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]) a set of [http://tools.openoffice.org/dev_docs/ooo-cws-tools-doc.sxw commandline tools] and the tool called
[http://eis.services.openoffice.org EIS]. [http://eis.services.openoffice.org EIS] is the acronym for Environment Information System and also the german word for the english word ice bye the way. The idea behind [[MWS | MasterWorkspaces (short MWS)]] and [[CWS | ChildWorkspaces (short CWS)]] is that no development is done on the [[MWS]]. Instead all work is performed on a copy of the [[MWS]], this copy then is referred to as a [[CWS]]. Only if the [[CWS]] is at least as good as the [[MWS]] (it may contain no regressions and newly introduced features must be fully operational) it will be [[Merging | merged]] ([[Integration|integrated]]) back into the [[MWS]]. Ideally this would mean that the [[MWS]] can be released at any time as a fully working drop. However, this only works in theory. Still the concept of [[MWS]]/[[CWS]] greatly reduces the number of new issues introduced in the [[MWS]].

[http://development.openoffice.org/releases/index.html Codelines for releases] use different [[ MWS | MasterWorkspaces]] and for minor releases also a new [[MWS | MasterWorkspace]] is usually introduced to stabilize the code for this minor release on a separate branch.

To work with [[CWS | ChildWorkspaces]] and [[MWS | MasterWorkspaces]] means:
* To do all development work on a copy of the product code
* To thoroughly test and check the developed code before re-integrating it into the product code.
* Only fully tested source code gets into production code, so fewer regression bugs will occur.
* All [http://eis.services.openoffice.org/EIS2/cws.MilestoneData milestones] on the [[MWS | MasterWorkspace]] (the product code) are potentially in a condition to be published
* Bugs are more often discovered around the time they are introduced, and by the people who introduced them.
* Because code is better checked and tested before integrating it into the product, the developer has greater freedom to work

[[CWS | ChildWorkspaces]] in [http://eis.services.openoffice.org EIS] do have a status which reflects what is currently being done on the [[CWS | ChildWorkspace]] and if the [[CWS]] has already gone into production code or the [[CWS]] is still being worked on. Which next status can be set depends on the current status.

There is a set of [[CWS_Policies|ChildWorkspace Policies]] which regulates how work on a [[CWS | ChildWorkspace]] is done eg. how issues in OpenOffice.org's bugtracking system issuezilla are usually assigned to [[CWS | ChildWorkspaces]] and how the different kinds of people involved in the lifecycle of a [[CWS | ChildWorkspace]] interact with each other. [http://eis.services.openoffice.org EIS] knows about two different kinds of [[CWS | ChildWorkspaces]]: public [[CWS]] and [http://www.sun.com Sun] internal [[CWS]]. For [http://www.sun.com Sun] internal [[CWS]] only a limited set of information is being shown on [http://eis.services.openoffice.org http://eis.services.openoffice.org] For example the description, which might contain internal information about a [http://www.sun.com Sun] customer, is not being shown. [http://www.sun.com Sun] internally there exists a different incarnation of the [http://eis.services.openoffice.org EIS] web-frontend which does show this information. Most [[CWS | ChildWorkspaces]] being worked on by [http://www.sun.com Sun] developers are public, only those few containing [[StarOffice]] only modules or features or those which do contain confidential information about a [http://www.sun.com Sun] customer are private [[CWS | ChildWorkspaces]].
[[CWS | ChildWorkspaces]] always have an "Owner" and a "QA representative" which usually should be two distinct persons ;-). Other types of information kept in [http://eis.services.openoffice.org EIS] are for example relevant source code modules, feature and/or bug-fix issues being worked on in the [[CWS]], the release for which the [[CWS]] is planned to be integrated and flags to indicated wether changes on that [[CWS]] are relevant for Documentation and Translation. [http://eis.services.openoffice.org EIS] also offers some statistics about [[CWS | ChildWorkspaces]]. Some fields in the Edit page for a [[CWS]] are required to be set at least when the status is changed to '''ready for QA''' and you will not be able to change to that state without setting those also. Besides the "Owner" and the "QA representative" EIS also provides the role of a "Member" of a ChildWorkspace. Members can be added on the [[CWS]] edit page. All [[CWS]] where you are either "Owner", "QA representative" or "Member" are shown on list provided by the ChildWorkspaces/MyCWS list. The "''ChildWorkspaces/Browse''" submenu provides some treeviews to show [[CWS | ChildWorkspaces]] in the database using different selection criterias. Which entries in this treeviews are shown is limited by a setting. The default is to show only [[CWS]] of the last 6 month. This can be changed by using the Settings link in the right corner and than using the CWS tab page where you will find a field "months displayed in treeviews" which can be set to a new value.

Additionally to the handling of [[CWS | ChildWorkspaces]] and [[MWS | MasterWorkspaces]] another feature of [http://eis.services.openoffice.org EIS] is the handling of [http://eis.services.openoffice.org/EIS2/servlet/changesmails.ShowAPIChangesMails API Changes] and [http://eis.services.openoffice.org/EIS2/servlet/changesmails.ShowFeatureMails Feature Announcements], which are entered into [http://eis.services.openoffice.org EIS] by developers and than mailed to [http://www.openoffice.org/mail_list.html OpenOffice.org mailing lists] and stored in the [http://eis.services.openoffice.org EIS] database. [http://eis.services.openoffice.org/EIS2/servlet/changesmails.ShowAPIChangesMails API Changes] inform other developers about code changes which might be relevant to them and [http://eis.services.openoffice.org/EIS2/servlet/changesmails.ShowFeatureMails Feature Announcements] as well as [http://specs.openoffice.org/ Specifications] are essential for those working on documentation or QA. [http://eis.services.openoffice.org/EIS2/servlet/changesmails.ShowFeatureMails Feature Announcements] and [http://specs.openoffice.org/ Specifications] are also used for semi-automated Release Notes creation and are thus important for informing everyone about changes in new releases, see [http://development.openoffice.org/releases/2.0.4rc3.html OpenOffice.org 2.0.4 Release Notes] for example. [http://specs.openoffice.org/ Specifications] must be created using a [http://specs.openoffice.org/collaterals/template/OpenOffice-org-Specification-Template.ott standard template] and [http://eis.services.openoffice.org EIS] can [http://eis.services.openoffice.org/EIS2/guide.CheckSpecification check] wether documents can be used for the Release Notes creation process or break that process because they do contain changes that make the document unusable for the [http://www.w3.org/TR/xslt XSLT] being used for that or because they are not based on the correct template.

== List of statuses know to [http://eis.services.openoffice.org EIS] ==

# '''planned''': A [[CWS]] with this state is planned, but not physically existend. Thus no code has been changed, it´s not even yet decided from which milestone the CWS will be created. Having this state available is useful for long term planning, resource aquisition etc.
# '''new''': [[CWS]] with this state have been created, they do have a physical representation somewhere and development is currently working on it. The '''cwscreate''' [http://tools.openoffice.org/dev_docs/ooo-cws-tools-doc.sxw commandline tool] is used to create directory for source code of a new [[CWS | ChildWorkspace]]. If a [[CWS | ChildWorkspace]] with state '''planned''' and the name given as argument to '''cwscreate''' already exists this one is propagated to state '''new''' in [http://eis.services.openoffice.org EIS] otherwise a new entry is created in [http://eis.services.openoffice.org EIS]. If you create a [[CWS | ChildWorkspace]] using '''cwscreate''' please use the [http://eis.services.openoffice.org web frontend] afterwards and add as much additional information as possible.
# '''ready for qa''': The developers think they are ready. They have prepared installation sets and hand the [[CWS]] over to QA by changing to this state. Depending on how the [[CWS]] handling for the [[MWS | MasterWorkspace]] is configured QA can now either set the state to '''nominated''' or '''approved by QA''' if QA accepts the changes on the [[CWS | ChildWorkspace]]. If changes on the [[CWS]] are note accepted QA sets the state back to '''new'''.
# '''approved by QA''': This is a special intermediate state used when a more controlled approach is active for the [[MWS | MasterWorkspace]] the [[CWS]] was created on. In this case QA approves a [[CWS]] but program management has the final say if and when something goes into the [[MWS | MasterWorkspace]]. That is program management will set the state to '''nominated''' after QA has set this state.
# '''nominated''': The [[CWS]] is being handed over to Release Engineering which can now start to integrate the [[CWS]] into the [[MWS |MasterWorkspace]]
# '''integrated''': all work on the [[CWS]] is finished and the changes on the [[CWS | ChildWorkspace]] have been integrated into the [[MWS | MasterWorkspace]].
# '''canceled''': A canceled [[CWS]] has been abandoned, no more work will be done on it. This state is for [[CWS]] which where once in state '''new''' but are not needed anymore.
# '''deleted''': similar to '''canceled''' this is for [[CWS]] which are not needed any more. The difference is that the '''deleted''' state can only be set for '''planned''' [[CWS]] which never made it to being actually physically created and thus to the state '''new'''.
# '''fixed on master''': this is used to reflect changes in [http://eis.services.openoffice.org EIS] done by Release Engineering directly on the Master usually to fix a very special urgent problem or a merge conflict. [[CWS]] in this state are not really existing physically these are just entries in [http://eis.services.openoffice.org EIS] keeping information about changes done directly on the source code repository branch of the [[MWS | MasterWorkspace]].
# '''finished''': This is a special state used for Special-Product-Release [[CWS | ChildWorkspaces]] which will never get integrated into a [[MWS | MasterWorkspace]] but represent a Special Release Version, eg. some version done for a single customer with a change that will never get into the [[MWS | MasterWorkspace]].
# '''pre-nominated for PP''': a historic state used for special Product Patch [[CWS]] handling, no longer used.
# '''cloned''': There are times when changes for a [[MWS | MasterWorkspace]] created to stabalize a minor release must also be integrated into a [[MWS | MasterWorkspace]] for the current main release trunk or vice versa. In this case [[CWS | ChildWorkspaces]] are being cloned. Eg. there can be a [[CWS | ChildWorkspace]] xyz created on the [[MWS | MasterWorkspace]] SRC680 and to integrate the same changes also into the OOE680 [[MWS | MasterWorkspace]] a clone xyz_OOE680 will be created. Release Engineering has a special commandline tool to create such clones.

== EIS Entry Points ==
The main webpage for [http://eis.services.openoffice.org EIS] is [http://eis.services.openoffice.org http://eis.services.openoffice.org]. There you can find a link to [http://eis.services.openoffice.org EIS] [http://eis.services.openoffice.org/EIS2/Logon logon] where you must use your OpenOffice.org email address as username. There is also an [http://eis.services.openoffice.org/EIS2/GuestLogon anonymous guest logon link] on this page for those who do not have an [http://www.openoffice.org/servlets/Join OpenOffice.org account] and the [http://en.wikipedia.org/wiki/RSS_(file_format) RSS feeds] [http://eis.services.openoffice.org EIS] provides can also be found on that page. Besides, the "[http://eis.services.openoffice.org/EIS2/cws.InfoForTask Find] a ChildWorkspace (CWS) name for a given IssueTracker issue ID", "[http://eis.services.openoffice.org/EIS2/wsm.FixedTasks List] integrated issues within the most current master build" and "[http://eis.services.openoffice.org/EIS2/wsm.FixedTasksExplorer Show] treeview of all integrated master builds" features on [ http://qa.openoffice.org/issuelinks.html http://qa.openoffice.org/issuelinks.html] are also features provided by EIS. At http://specs.openoffice.org there is a Specification Checking Tool link, which is also a feature offered by [http://eis.services.openoffice.org EIS]. You may find direct links to [[CWS | ChildWorkspace]]information in some [http://en.wikipedia.org/wiki/RSS_(file_format) RSS feeds] and webpages like [http://go-oo.org/planet Planet OpenOffice.org] or in some documentation on [http://www.openoffice.org http://www.openoffice.org]. If you need to create such a direct link to [[CWS | ChildWorkspace]] information on some webpage yourself you can use something like the following:

[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fcwsqueryenhance http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fcwsqueryenhance ]

where 'cwsqueryenhance' is the name of the [[CWS | ChildWorkspace]] and 'SRC680' is the [[MWS |MasterWorkspace]] it was created on without milestone information. The general formular for such URLs is

http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=<MasterWorkspace>%2F<ChildWorkspace>

Such links and also the features on the [http://qa.openoffice.org/issuelinks.html QA issuelinks page] and the [http://eis.services.openoffice.org/EIS2/guide.CheckSpecification Specification Checking Tool] can be used without [http://eis.services.openoffice.org/EIS2/Logon logon].
The [http://en.wikipedia.org/wiki/SOAP SOAP] interface of [http://eis.services.openoffice.org EIS] is at [https://eis.services.openoffice.org/soap/servlet/rpcrouter https://eis.services.openoffice.org/soap/servlet/rpcrouter]. The [http://tools.openoffice.org/dev_docs/ooo-cws-tools-doc.sxw CWS commandline tools] authenticate there using [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS] username and crypted [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS] password. This must be configured in a .cwsrc file, details about this .cwsrc file can be found on the [[CWS]] Wiki entry. The [http://en.wikipedia.org/wiki/SOAP SOAP] interface is currently not yet documented, but with [http://tools.openoffice.org/source/browse/tools/solenv/bin/modules/Cws.pm CWS.pm] there is a [http://en.wikipedia.org/wiki/Perl perl] module for using it available in the OpenOffice.org source code.

== Tips & Tricks ==
* You can change the menu to being displayed at the left side instead of on top via using the Settings link in the right corner and than using the Menu-Style radio buttons on the "Frames" tab page.
* If you are a member of QA and you want to find [[CWS | ChildWorkspaces]] which do not yet have a QA representative use the "''ChildWorkspaces / Seek QA''" menu entry.
* to find out what the latest milestone on a given [[MWS|MasterWorkspace]] is you can either look at [http://eis.services.openoffice.org EIS (Environment Information System)] using the menu entry "''MasterWorkspaces / MasterWorkspace Info''" or use the command "'''cwsquery latest'''".
* {{LinkBanner}}

== Contact ==
[http://eis.services.openoffice.org EIS] is a service operated by [http://www.sun.com Sun] and currently maintained by [[User:bei|Bernd Eilers]]. If you have found a bug in [http://eis.services.openoffice.org EIS] or a feature request for it you can [http://qa.openoffice.org/issue_handling/pre_submission.html submit an issue] in issuezilla under Category tools and with target DevTools to him.

== related Links ==
* [http://tools.openoffice.org/dev_docs/child_workspace_policies.html ChildWorkspace Policies]
* [http://tools.openoffice.org/dev_docs/ooo-cws-tools-doc.sxw CWS commandline tools documentation]
* [http://tools.openoffice.org/servlets/ReadMsg?list=dev&msgNo=5044 The email which introduced CWS commandline tools]
* [http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf TX 20 Report] - A document provided by [http://eric.bachard.free.fr/news/ Eric Bachard] including amongst other things some very good stuff about [http://eis.services.openoffice.org EIS] and [[CWS | ChildWorkspace]] handling, eg. Screenshots of the EIS web-frontend, an explanation about ChildWorkspace statuses and an example of typical CWS commandline tool usage for developers.
* [[RedTinderboxStatusInEIS]]

Writer/Paste Unformatted Shortcut Specification

2009-06-24T19:43:45Z

Mox: /* Writer */ It's much better to use weblinks that are accessible to also others than Sun employees.

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
|
|
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| [http://www.openoffice.org/issues/show_bug.cgi?id=17563 i17563], [http://www.openoffice.org/issues/show_bug.cgi?id=103070 i103070]
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste Unformatted text''' command exists in OpenOffice.org, but lacks direct shortcut. This specification specifies associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way. The chosen shortcut is already used in Mac OS X platform, and equivalent shortcut is chosen for Windows/Linux for cross-platfrom consistency.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| Éric Savary
| es@openoffice.org
|-
| Documentation
| UFI
| ufi@openoffice.org
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-06-13

|}

== Motivation ==
To make the important text handling UI flow more fluent and more efficient.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling (using existing document style) Just Works. No additional work needed.

== Goals ==
Make it efficient to use pasting so that target document style consistent through-out the target document.

== Requirements and Dependencies ==

=== Requirements ===
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Mac OS X platfrom (including Apple's iWork, TextEdit, Safari) has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste Unformatted Text
| Einsetzen Unformatierter Text
| Coller texte non formaté
| Pegar texto sin formato
|
|}

(this menu item is not enabled by default, but user must enabled it for the shortcut to work on Mac OS X)

=== Error Conditions ===
Existing Unformatted text dimming.

=== Migration ===
Not needed.

== Notes ==
None at this time.

== References ==

[[Category:Writer]]

Writer/Paste Unformatted Shortcut Specification

2009-06-13T18:09:22Z

Mox: /* Abstract */

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
|
|
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
|
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste Unformatted text''' command exists in OpenOffice.org, but lacks direct shortcut. This specification specifies associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way. The chosen shortcut is already used in Mac OS X platform, and equivalent shortcut is chosen for Windows/Linux for cross-platfrom consistency.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| ES
| es@openoffice.org
|-
| Documentation
| UFI
| ufi@openoffice.org
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-06-13

|}

== Motivation ==
To make the important text handling UI flow more fluent and more efficient.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling (using existing document style) Just Works. No additional work needed.

== Goals ==
Make it efficient to use pasting so that target document style consistent through-out the target document.

== Requirements and Dependencies ==

=== Requirements ===
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Mac OS X platfrom (including Apple's iWork, TextEdit, Safari) has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste unformatted text
| Einsetzen Unformatierter Text
| Coller texte non formaté
| Pegar texto sin formato
|
|}

(this menu item is not enabled by default, but user must enabled it for the shortcut to work on Mac OS X)

=== Error Conditions ===
Existing Unformatted text dimming.

=== Migration ===
Not needed.

== Notes ==
None at this time.

== References ==

[[Category:Writer]]

Writer/Paste Unformatted Shortcut Specification

2009-06-13T18:09:02Z

Mox: New page: = Writer = {| border=1 cellspacing=0 cellpadding=5 | Document - ID | Specification Owner | Last Change | Status |- | | | | Draft |- | Conforms to | | | |- | Applies to | sw, officecfg...

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
|
|
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
|
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste Unformatted''' command exists in OpenOffice.org, but lacks direct shortcut. This specification specifies associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way. The chosen shortcut is already used in Mac OS X platform, and equivalent shortcut is chosen for Windows/Linux for cross-platfrom consistency.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| ES
| es@openoffice.org
|-
| Documentation
| UFI
| ufi@openoffice.org
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-06-13

|}

== Motivation ==
To make the important text handling UI flow more fluent and more efficient.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling (using existing document style) Just Works. No additional work needed.

== Goals ==
Make it efficient to use pasting so that target document style consistent through-out the target document.

== Requirements and Dependencies ==

=== Requirements ===
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Mac OS X platfrom (including Apple's iWork, TextEdit, Safari) has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste unformatted text
| Einsetzen Unformatierter Text
| Coller texte non formaté
| Pegar texto sin formato
|
|}

(this menu item is not enabled by default, but user must enabled it for the shortcut to work on Mac OS X)

=== Error Conditions ===
Existing Unformatted text dimming.

=== Migration ===
Not needed.

== Notes ==
None at this time.

== References ==

[[Category:Writer]]

User:Mox

2009-06-13T17:40:26Z

Mox:

*[[Paste Unformatted shortcut Specification]]
*[[Paste and Match Style Specification]]

Stuff I work on:
* [[Mac OS X Porting - User Experience]]
* [[Mac OS X Porting - Canvas]]
* [[Mac OS X Porting - Separate apps (OOoRunner -framework)]]
* [[Mac OS X Porting - Native Audio and Video]]
* [[Mac OS X Porting - Native Spellchecking]]
* [[Mac OS X Porting - Keyboard Shortcuts]]

* [[Mac OS X Porting - Code Documentation]]
* [[Mac OS X Porting - Comparison to Toolkit Ports]]

* Clipboard + image byte re-ordering [https://bugzilla.mozilla.org/attachment.cgi?id=240960 mozilla patch] and [http://hsivonen.iki.fi/kesakoodi/clipboard/ clipboard fun details]

* Including extensions to installation packages - [[Extensions Integration into Installation Set]]

* [[UI Layout]] > [[Platform UI Differences]] ... [[Chrome Again]], hmm???

* People who can create CWSs (the CVS checkbox): [[DomainDeveloper]]

Interested in:
* [[User Experience Community]]

I want to see as much collaboration as possible:
* [[Mac OS X Porting - contributions from NeoOffice]] & history [http://www.openoffice.org/editorial/edp_and_danw.html OOo in 2002]

Read more about this:
* [[Drawing framework]]

Other interesting stuff:
* [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 OOoCon2006/XCanvas]
* [http://wiki.services.openoffice.org/wiki/Category:MacOSX Mac OS X related Wiki pages]
* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

Wishes:
* Get rid of [http://mydatapages.com/quickdraw.html Quickdraw], or we will have broken application in the near future Mac OS X releases: [http://wiki.mozilla.org/Mac:NPAPI_Drawing_Models Porting Quickdraw to CoreGraphics]

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]

SVN

2009-06-13T17:35:28Z

Mox: /* SVN - Subversion */

#REDIRECT [[Subversion]]

Writer/Paste and Match Style Specification

2009-04-04T07:47:31Z

Mox:

= THIS DOCUMENT IS NOT VALID ANYMORE - IT IS STORED ONLY FOR ARCHIVAL REASONS =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
|
|
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
|
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17
|-
| 1.1
| updated dimming/functionality definition
| mox
| 2009-03-31
|-
| 1.2
| OBSOLETE
| mox
| 2009-04-02

|}

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Unformatted text", it is highly cumbersome and hard to discover. "Unformatted text" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "unformatted text" functionality (i.e. SOT_FORMAT_STRING paste type). However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if this kind of pasting is not possible. Same rules as with the OOo 3.1 command: Edit -> Paste Special -> '''Unformatted text'''.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

== References ==

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-04-04T07:42:53Z

Mox:

= THIS DOCUMENT IS NOT VALID ANYMORE - IT IS STORED ONLY FOR ARCHIVAL REASONS =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
|
|
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
|
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17
|-
| 1.1
| updated dimming/functionality definition
| mox
| 2009-03-31
|-
| 1.2
| OBSOLETE
| mox
| 2009-04-02

|}

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Unformatted text", it is highly cumbersome and hard to discover. "Unformatted text" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality (i.e. SOT_FORMAT_STRING paste type). However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if this kind of pasting is not possible. Same rules as with the OOo 3.1 command: Edit -> Paste Special -> '''Paste Unformatted'''.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

== References ==

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-03-31T18:45:15Z

Mox: /* Error Conditions */

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17
|-
| 1.1
| updated dimming/functionality definition
| mox
| 2009-03-31

|}

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality (i.e. SOT_FORMAT_STRING paste type). However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if this kind of pasting is not possible. Same rules as with the OOo 3.1 command: Edit -> Paste Special -> '''Paste Unformatted'''.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-03-31T18:44:58Z

Mox: /* Error Conditions */

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17
|-
| 1.1
| updated dimming/functionality definition
| mox
| 2009-03-31

|}

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality (i.e. SOT_FORMAT_STRING paste type). However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if this kind of pasting is not possible. Same rules as with the OOo 3.1 command Edit -> Paste Special -> '''Paste Unformatted'''.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-03-31T18:44:36Z

Mox: /* Detailed Specification */

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17
|-
| 1.1
| updated dimming/functionality definition
| mox
| 2009-03-31

|}

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality (i.e. SOT_FORMAT_STRING paste type). However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if this kind of pasting is not possible. Same rules as with the OOo 3.1 command Edit -> Paste Special -&gr; '''Paste Unformatted'''.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-03-31T18:39:46Z

Mox: /* Glossary */

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17
|-
| 1.1
| updated dimming/functionality definition
| mox
| 2009-03-31

|}

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality. However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-03-31T18:39:28Z

Mox: /* Document Change History */

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17
|-
| 1.1
| updated dimming/functionality definition
| mox
| 2009-03-31

|}

== Glossary ==

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

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality. However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-03-17T20:46:03Z

Mox:

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Enhancement
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17

|}

== Glossary ==

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

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this functionality and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality. However, in the future this functionality could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this functionality could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]

Writer/Paste and Match Style Specification

2009-03-17T20:23:56Z

Mox: /* Detailed Specification */

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17

|}

== Glossary ==

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

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this feature and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality. However, in the future this feature could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this feature could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]
[[Category:Features]]

Writer/Paste and Match Style Specification

2009-03-17T20:23:34Z

Mox: /* Future Tasks */

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17

|}

== Glossary ==

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

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this feature and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality. However, in the future this could feature could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this feature could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]
[[Category:Features]]

Writer/Paste and Match Style Specification

2009-03-17T20:23:06Z

Mox:

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17

|}

== Glossary ==

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

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this feature and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality. However, in the future this could feature could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
In the future this could feature could be improved beyond the simple unformatting of the source content.

== Notes ==
None at this time.

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

[[Category:Writer]]
[[Category:Features]]

Writer/Paste and Match Style Specification

2009-03-17T20:22:17Z

Mox:

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17

|}

== Glossary ==

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

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this feature and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See also requirements.

Menu item "Paste and Match Style" in "Edit" menu
* Below "Paste" menu item
* Above "Paste Special" menu item (if it exists)

Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

Initial implementation relies fully on the functionality provided by the existing "paste unformatted" functionality. However, in the future this could feature could be improved beyond the simple unformatting of the source content.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
None at this time.

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

[[Category:Writer]]
[[Category:Features]]

Writer/Paste and Match Style Specification

2009-03-17T20:17:15Z

Mox: initial revision

This specification is for describing the UI additions and functionality of the Paste and Match Style.

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

= Paste and Match Style =

= Writer =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Mox
| 2009-03-17
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sw, officecfg
|
|
|-
| Task ID(s)
| 17563
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The '''Paste and Match Style''' command and associated keyboard shortcut (CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac) makes it possible to use the styling of OpenOffice.org documents more efficiently and in powerfully consistent way.

The greatest advantage is that no matter where the copied content originated from (web page, another office program, ...) the styling of the document being worked on is maintained by using the styling of the target document also in the pasted content.

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

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mox Soini
| mox@openoffice.org
|-
| Development
| Mox Soini
| mox@openoffice.org
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
| mox
| 2009-03-17

|}

== Glossary ==

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

== Motivation ==
While it is technically possible to achieve a similar functionality via "Paste Special -> Paste Unformatted", it is highly cumbersome and hard to discover. "Paste Unformatted" does not truly express what a powerful tool it can be.

== User Scenarios ==
User copies text from a web page and pastes it to the document he works on. Styling Just Works. No additional work needed.

== Goals ==
Make powerful pasting functionality understandable to users. Make it efficient to use pasting so that target document style consistent through-out the document.

== Requirements and Dependencies ==

=== Requirements ===
Menu item "Paste and Match Style" under "Paste" menu item in "Edit" menu
Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux, Cmd-Option-Shift-V on Mac

=== Technical Dependencies ===
Not known.

== Competitive Analyses ==
Apple's iWork has this feature and it's extremely useful and efficient for those interested in high quality documents.

== Detailed Specification ==
See requirements. The placement of the command is between Paste and Paste Special in Edit menu.

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| French
| Spanish
| Comments
|-
| Menu item
| Paste and Match Style
| Einsetzen und Stil anpassen
| Coller et appliquer le style
| Pegar con el mismo estilo
|
|}

=== Error Conditions ===
Menu item is dimmed if pasting is not possible. Same rules as with Paste Special.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==
None at this time.

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

[[Category:Writer]]
[[Category:Features]]

User:Mox

2009-03-17T19:30:48Z

Mox:

*[[Paste and Match Style Specification]]

Stuff I work on:
* [[Mac OS X Porting - User Experience]]
* [[Mac OS X Porting - Canvas]]
* [[Mac OS X Porting - Separate apps (OOoRunner -framework)]]
* [[Mac OS X Porting - Native Audio and Video]]
* [[Mac OS X Porting - Native Spellchecking]]
* [[Mac OS X Porting - Keyboard Shortcuts]]

* [[Mac OS X Porting - Code Documentation]]
* [[Mac OS X Porting - Comparison to Toolkit Ports]]

* Clipboard + image byte re-ordering [https://bugzilla.mozilla.org/attachment.cgi?id=240960 mozilla patch] and [http://hsivonen.iki.fi/kesakoodi/clipboard/ clipboard fun details]

* Including extensions to installation packages - [[Extensions Integration into Installation Set]]

* [[UI Layout]] > [[Platform UI Differences]] ... [[Chrome Again]], hmm???

* People who can create CWSs (the CVS checkbox): [[DomainDeveloper]]

Interested in:
* [[User Experience Community]]

I want to see as much collaboration as possible:
* [[Mac OS X Porting - contributions from NeoOffice]] & history [http://www.openoffice.org/editorial/edp_and_danw.html OOo in 2002]

Read more about this:
* [[Drawing framework]]

Other interesting stuff:
* [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 OOoCon2006/XCanvas]
* [http://wiki.services.openoffice.org/wiki/Category:MacOSX Mac OS X related Wiki pages]
* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

Wishes:
* Get rid of [http://mydatapages.com/quickdraw.html Quickdraw], or we will have broken application in the near future Mac OS X releases: [http://wiki.mozilla.org/Mac:NPAPI_Drawing_Models Porting Quickdraw to CoreGraphics]

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]

Mac OS X Porting - Keyboard Shortcuts

2009-02-21T22:49:02Z

Mox:

==Contributors==
* Ismael Merzaq: [[User:Ismael|Ismael]]
* Mox Soini: [[User:Mox|Mox]]
* Eric Bachard: [[User:ericb|ericb]]
* Graham Perrin: [[User:grahamperrin|grahamperrin]]

==Introduction==
For most of the keyboard shortcuts in OpenOffice.org, the Mac OS X port will follow the other OpenOffice.org platforms, to maintain consistency and allow people to use several platforms without much re-learning.

However, there are some special cases that require Mac OS X port to make exceptions in shortcuts, compared to the other platforms:
* Mac OS X System has global keyboard shortcuts that override existing OpenOffice.org shortcuts
* Apple Human Interface Guidelines (AHIG) requires that all Mac OS X applications define certain common set of shortcuts. That common set might cause a change for shortcut to have different functionality.

'''Example:'''

When the user press F9 in OpenOffice.org (native version or X11 version), the fields are not refreshed,
because the Mac OS X function Exposé is launched and catches the key accelerator (to refresh the fields, go to
Tools>Refresh>Fields in the menu.

What we have to do is to change the conflicting key accelerators for OpenOffice.org.

== Apple Developer Connection (ADC) Reference Library: highlights ==

===[http://developer.apple.com/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXKeyboardShortcuts/chapter_6_section_1.html Accessibility Overview: Appendix A: Accessibility Keyboard Shortcuts]===
* keyboard shortcuts that are reserved for use with various Universal Access features in Mac OS X

===[http://developer.apple.com/documentation/userexperience/Conceptual/AppleHIGuidelines/XHIGKeyboardShortcuts/chapter_950_section_1.html Apple Human Interface Guidelines: Keyboard Shortcuts Quick Reference]===
* system-reserved and commonly used keyboard shortcuts

===[http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_4.html#//apple_ref/doc/uid/TP30000361-TPXREF30 Apple Human Interface Guidelines: Selecting]===
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_4.html#//apple_ref/doc/uid/TP30000361-TPXREF21 Selection Methods]
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_4.html#//apple_ref/doc/uid/TP30000361-TPXREF26 Selections in Text]
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_4.html#//apple_ref/doc/uid/TP30000361-TPXREF31 Selections in Spreadsheets]
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_4.html#//apple_ref/doc/uid/TP30000361-TPXREF30 Selections in Graphics] … with the mouse alone or a combination of the mouse and the keyboard…

===[http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_3.html Apple Human Interface Guidelines: The Keyboard]===
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_3.html#//apple_ref/doc/uid/TP30000361-TPXREF61 The Functions of Specific Keys] … [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_3.html#//apple_ref/doc/uid/TP30000361-TPXREF17 Extending Text Selection With the Shift and Arrow Keys]
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_3.html#//apple_ref/doc/uid/TP30000361-CHDIGFBH Keyboard Shortcuts]
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_3.html#//apple_ref/doc/uid/TP30000361-BJCFCJAF Keyboard Focus and Navigation]
* [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/chapter_12_section_3.html#//apple_ref/doc/uid/TP30000361-TPXREF19 Type-Ahead and Key-Repeat]

===[http://developer.apple.com/documentation/Cocoa/Conceptual/AppArchitecture/Concepts/AppFeatures.html Application Architecture Overview: Features of a Cocoa Application]===
* … Menu Management … The application takes care of … accelerator keys …

===[http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSTextView_Class/Reference/Reference.html NSTextView Class Reference]===
* [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSTextView_Class/Reference/Reference.html#//apple_ref/doc/uid/20000373-BBCFEJEH complete] — invokes completion in a text view … By default invoked using the F5 key, this method provides users with a choice of completions for the word currently being typed. May be invoked programmatically if autocompletion is desired by a client of the text system. You can change the key invoking this method using the text system’s key bindings mechanism; see “Text System Defaults and Key Bindings" for an explanation of the procedure.

===[http://developer.apple.com/documentation/Cocoa/Conceptual/SysServices/Concepts/properties.html System Services: Services Properties]===
* [http://developer.apple.com/documentation/Cocoa/Conceptual/SysServices/Concepts/properties.html#//apple_ref/doc/uid/20000852-97498 Property Definitions] ([http://www.diigo.com/04tvf highlights])

===[http://developer.apple.com/documentation/Cocoa/Conceptual/EventOverview/TextDefaultsBindings/chapter_9_section_1.html Text System Defaults and Key Bindings]===
* [http://developer.apple.com/documentation/Cocoa/Conceptual/EventOverview/TextDefaultsBindings/chapter_9_section_2.html Key Bindings]
* [http://developer.apple.com/documentation/Cocoa/Conceptual/EventOverview/TextDefaultsBindings/chapter_9_section_3.html Standard Action Methods for Selecting and Editing]
* [http://developer.apple.com/documentation/Cocoa/Conceptual/EventOverview/TextDefaultsBindings/chapter_9_section_4.html Text System Defaults]

==Mac OS X Shortcuts (under construction)==

===Introduction===

This new section marked with '''under construction''' will contain as many as possible shortcuts available on Mac OS X. All these shortcuts are Apple HIG compliant and we should check them in OO.o and fix them if they do not work as expected.

====Sections====
Please, split shortcuts to smaller sections to make it easily editable. It's a pain to edit one long table. Thanks.

====How to edit====
Copy complete specification of shortcuts from Apple HIG to this wiki page and add red comments if something's wrong. If we use this way, we can have idea how it should work, how it works and what to fix.

You can find duplicates in tables below. That's because they are duplicated in Apple's HIG documentation. I do not want to remove them to avoid mistakes.

====Synonyms and distinctions====

=====accelerate, bind and shortcut=====

In Apple terms:
* a key may be ''bound''
* there may be ''multiple keystroke bindings''
* the expression ''accelerator'' is not always used
* the expression ''shortcut'' is not always used.

=====command key=====

ADC Reference Library tends to refer to the ''command'' key. The command key is also known as:
* cmd
* Apple
* [http://film.art.columbia.edu/wiki/index.php/Keyboard_shortcut_and_other_symbols open Apple]

On a British keyboard the command key is labelled with a ''place of interest sign'':

⌘

plus either of the following labels:

cmd


=====completion of text=====

In Apple terms: the user may invoke ''completion'', typically using the F5 key.

Completion may be invoked programmatically if ''autocompletion'' is desired by a client of the text system.

OpenOffice.org uses terms such as:
* Auto-complete
* AutoInput
* Word completion

=====option key=====

ADC Reference Library tends to refer to the ''option'' key. The option key is also known as:
* opt
* alt

On a British keyboard the option key is usually labelled:

alt
⌥

===Roadmap===

====CWS====

=====[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fmacshortcuts01 macshortcuts01]=====

CWS created, based on m41. This CWS should fix all menu items and shortcuts. Only these they are easily fixable - change shortcut. Shortcuts with additional effort (new menu item, deepeter changes, ...) should be fixed in macshortcuts02 (planned).

Feel free to add tasks to this CWS and fix shortcuts.

Plan is to have this CWS integrated in 3.2. This needs to be discussed on IRC meeting.

Note: there's list of proposed fixes in the table below. There's no detailed description. To see why this proposal is taken into account, look at tables below with Apple HIG shortcuts with comparison to OO.o shortcuts.

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="4" | Shortcuts for macshortcuts01
|-
! style="background:#abcdef" | App !! style="background:#abcdef" | Current !! style="background:#abcdef" | Proposal !! style="background:#abcdef" align="left" | Shortdesc
|-
| OO.o || Cmd-L || Cmd-{ || Left alignment - Writer [http://www.openoffice.org/issues/show_bug.cgi?id=99170], Calc [http://www.openoffice.org/issues/show_bug.cgi?id=99178], Impress, Draw [http://www.openoffice.org/issues/show_bug.cgi?id=99179]
|-
| OO.o || Cmd-R || Cmd-} || Right alignment - Writer [http://www.openoffice.org/issues/show_bug.cgi?id=99170], Calc [http://www.openoffice.org/issues/show_bug.cgi?id=99178], Impress, Draw [http://www.openoffice.org/issues/show_bug.cgi?id=99179]
|-
| OO.o || Cmd-E || Cmd-(pipe) || Center alignment - Writer [http://www.openoffice.org/issues/show_bug.cgi?id=99170], Calc [http://www.openoffice.org/issues/show_bug.cgi?id=99178], Impress, Draw [http://www.openoffice.org/issues/show_bug.cgi?id=99179]
|-
| OO.o || Cmd-M || Ctrl-M || Default formatting - Writer [http://www.openoffice.org/issues/show_bug.cgi?id=98951], Calc [http://www.openoffice.org/issues/show_bug.cgi?id=98950], meta [http://www.openoffice.org/issues/show_bug.cgi?id=98949]
|-
| Writer || F9 || ?? || Fields - Writer [http://www.openoffice.org/issues/show_bug.cgi?id=99171]
|-
| Calc || F9 || ?? || Recalculate - Calc [http://www.openoffice.org/issues/show_bug.cgi?id=99172]
|-
| OO.o || F11 || Cmd-T || Styles and formatting 
Needs discussion, because I'd rather display Context menu - Character instead of stylist window. Which is what is displayed in Pages for example.
|-
| Writer || F12 || ?? || Numbering On/Off - Writer [http://www.openoffice.org/issues/show_bug.cgi?id=99174]
|-
| Calc || F12 || ?? || Group - Calc [http://www.openoffice.org/issues/show_bug.cgi?id=99175]
|-
| OO.o || Cmd-Y || Cmd-Shift-Z || Redo - All [http://www.openoffice.org/issues/show_bug.cgi?id=99177]
|}

=====macshortcuts02=====

Planned CWS.

This CWS should include fixes for shortcuts not included in 01.

===Common shortcuts===

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="2" | Description
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Description
|-
| style="color:green" | OK || OpenOffice.org shortcut works as expected or Mac OS X reserved shortcut is not used by the OpenOffice.org.
|-
| style="color:red" | EE || Shortcut doesn't work and can be fixed
|-
| style="color:blue" | II || To implement this shortcut we need to enhance OO.o because of missing menu items, ...
|}

====Moving the insertion point with the arrow keys====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Moving the insertion point
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Key !! style="background:#abcdef" align="left" | Moves insertion point
|-
| style="color:green" | OK || Right Arrow || One character to the right
|-
| style="color:green" | OK || Left Arrow || One character to the left
|-
| style="color:green" | OK || Up Arrow || To the line above, to the nearest character boundary at the same horizontal location
|-
| style="color:green" | OK || Down Arrow || To the line below, to the nearest character boundary at the same horizontal location
|-
| style="color:red" | EE || Option–Right Arrow || To the '''end''' of current word, then to the '''end''' of the next word 
It moves to the '''beginning''' of next word, then to the '''beginning''' of the next word
|-
| style="color:green" | OK || Option–Left Arrow || To the beginning of the current word, then to the beginning of the previous word
|-
| style="color:green" | OK || Option–Up Arrow || To the beginning of the current paragraph, then to the beginning of the previous paragraph
|-
| style="color:red" | EE || Option–Down Arrow || To the end of the current paragraph, then to the end of the next paragraph (not to the blank line after the paragraph, if there is one) 
Blank line is not skipped
|-
| style="color:red" | EE || Command–Right Arrow || To the next semantic unit, typically the end of the current line, then the end of the next line 
Doesn't work for next lines. It jumps to the end of the current line, but not to the ends of next lines.
|-
| style="color:red" | EE || Command–Left Arrow || To the previous semantic unit, typically the beginning of the current line, then the previous unit 
Doesn't work for previous lines. It jumps to the beginning of the current line, but not to the beginnings of previous lines.
|-
| style="color:green" | OK || Command–Up Arrow || Upward in the next semantic unit, typically the beginning of the document
|-
| style="color:green" | OK ||Command–Down Arrow || Downward in the next semantic unit, typically the end of the document
|}

'''Exception:''' For non-Roman script systems, '''Command–Left Arrow''' and '''Command–Right Arrow''' are reserved for changing the direction of keyboard input.

====Extending selection with Shift and the arrow keys====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Extending selection
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Key !! style="background:#abcdef" align="left" | Extends selection
|-
| style="color:green" | OK || Shift-Right Arrow || One character to the right
|-
| style="color:green" | OK || Shift-Left Arrow || One character to the left
|-
| style="color:green" | OK || Shift-Up Arrow || To the line above, to the nearest character boundary at the same horizontal location
|-
| style="color:green" | OK || Shift-Down Arrow || To the line below, to the nearest character boundary at the same horizontal location
|-
| style="color:red" | EE || Shift-Option–Right Arrow || To the '''end''' of current word, then to the '''end''' of the next word 
It moves to the '''beginning''' of next word, then to the '''beginning''' of the next word
|-
| style="color:green" | OK || Shift-Option–Left Arrow || To the beginning of the current word, then to the beginning of the previous word
|-
| style="color:green" | OK || Shift-Option–Up Arrow || To the beginning of the current paragraph, then to the beginning of the previous paragraph
|-
| style="color:red" | EE || Shift-Option–Down Arrow || To the end of the current paragraph, then to the end of the next paragraph (not to the blank line after the paragraph, if there is one) 
Blank line is not skipped
|-
| style="color:red" | EE || Shift-Command–Right Arrow || To the next semantic unit, typically the end of the current line, then the end of the next line 
Doesn't work for next lines. It jumps to the end of the current line, but not to the ends of next lines.
|-
| style="color:red" | EE || Shift-Command–Left Arrow || To the previous semantic unit, typically the beginning of the current line, then the previous unit 
Doesn't work for previous lines. It jumps to the beginning of the current line, but not to the beginnings of previous lines.
|-
| style="color:green" | OK || Shift-Command–Up Arrow || Upward in the next semantic unit, typically the beginning of the document
|-
| style="color:green" | OK || Shift-Command–Down Arrow || Downward in the next semantic unit, typically the end of the document
|}

==== Reserved shortcuts ====

Don’t use the keys and key combinations in Table below for actions other than those listed in the table.

Shortcuts below are Mac specific and they are not passed to application.

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Reserved shortcuts
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Keys !! style="background:#abcdef" align="left" | Action
|-
| style="color:green" | OK || Esc || Cancel the current action
|-
| style="color:green" | OK || Command-Tab || Activate the most recently used open application
|-
| style="color:green" | OK || Command-Shift-Tab || Activate the least recently used open application
|-
| style="color:green" | OK || Command-Option-D || Show or hide the Dock
|-
| style="color:green" | OK || Command-H || Hide the active application
|-
| style="color:green" | OK || Command-Option-H || Hide other applications (all but the active one)
|-
| style="color:red" | EE || Command-Shift-Q || Log out 
OO.o: Interrupt Macro
|-
| style="color:green" | OK || Command-Shift-Option-Q || Log out without confirmation
|-
| style="color:green" | OK || Command-Shift-Option-Control-Q || Force log out without confirmation
|-
| style="color:green" | OK || Command–Space bar || Show or hide Spotlight search field
|-
| style="color:green" | OK || Command-Option-Esc || Open the Force Quit dialog
|-
| style="color:red" | EE || Command-F5 || Turn VoiceOver on or off 
OO.o: Control Focus
|-
| style="color:green" | OK || Control-F1 || Turn full keyboard navigation on or off
|-
| style="color:green" | OK || Control-F7 || Toggle keyboard navigation in windows and dialogs
|-
| style="color:red" | EE || F9 || Tile or untile all open windows 
Writer: Fields 
Calc: Recalculate 
Impress: Slideshow, F5 is also assigned, but F9 should be removed, see [http://www.openoffice.org/issues/show_bug.cgi?id=99173]
|-
| style="color:green" | OK || F10 || Tile or untile all open windows in current application
|-
| style="color:red" | EE || F11 || Hide or show all open windows 
Writer, Calc, Impress, Draw: Styles and Formatting
|-
| style="color:red" | EE || F12 || Display or hide Dashboard 
Writer: Numbering On/Off 
Calc: Group
|}

==== Reserved shortcuts for international systems ====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Reserved shortcuts for international systems
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Keys !! style="background:#abcdef" align="left" | Action
|-
| ? || Command–Space bar || Rotate through enabled script systems
|-
| ? || Command–Option–Space bar || Rotate through keyboard layouts and input methods within a script
|-
| ? || Command–modifier key–Space bar || Apple reserved
|-
| ? || Command–Right Arrow || Change keyboard layout to current layout of Roman script
|-
| ? || Command–Left Arrow || Change keyboard layout to current layout of system script
|}

==== Recommended shortcuts using Shift to complement other commands ====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="4" | Recommended shortcuts using Shift to complement other commands
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Keys !! style="background:#abcdef" align="left" | Command !! style="background:#abcdef" align="left" | Complemented command
|-
| style="color:blue" | II || Command-Shift-A || Deselect All || Command-A (Select All) 
There's no Edit - Deselect All
|-
| style="color:blue" | II || Command-Shift-G || Find Previous || Command-G (Find Again) 
There's no Find Again / Previous. These should be assigned in Find & Replace dialog?
|-
| style="color:blue" | II || Command-Shift-P || Page Setup || Command-P (Print) 
This should be probably assigned to File - Printer Settings
|-
| style="color:green" | OK || Command-Shift-S || Save As || Command-S (Save)
|-
| style="color:green" | OK || Command-Shift-V || Paste as (Paste as Quotation, for example) || Command-V (Paste)
|-
| style="color:red" | EE || Command-Shift-Z || Redo || Command-Z (Undo) 
OO.o has Cmd-Y as Redo
|}

'''Note:''' Command-Shift-Z would be used for Redo only if Undo and Redo are separate commands (rather than toggled using Command-Z).

====Accessibility shortcuts - zooming ====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Screen zooming
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Keys !! style="background:#abcdef" align="left" | Action
|-
| style="color:green" | OK || Option-Command-8 || Turns screen zooming on or off
|-
| style="color:green" | OK || Option-Command-= || Zooms in
|-
| style="color:green" | OK || Option-Command-- (hyphen) || Zooms out
|-
| style="color:green" | OK || Command-Option-Control-8 || Inverts the screen colors
|-
| style="color:green" | OK || Command-Option-Control-, || Reduces contrast
|-
| style="color:green" | OK || Command-Option-Control-. || Increases contrast
|}

====Accessibility shortcuts - moving focus====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Focus moving in full keyboard access mode
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Keys !! style="background:#abcdef" align="left" | Action
|-
| ? || Control-F1 || Turns full keyboard access on or off
|-
| ? || Control-F2 || Moves focus to the menu bar
|-
| ? || Control-F3 || Moves focus to the Dock
|-
| ? || Control-F4 || Moves focus to the active (or next) window
|-
| ? || Shift-Control-F4 || Moves focus to the previous window
|-
| ? || Control-F5 || Moves focus to the toolbar
|-
| ? || Control-F6 || Moves focus to the first (or next) utility window
|-
| ? || Shift-Control-F6 || Moves focus to the previous utility window
|-
| ? || Control-F7 || Toggles the keyboard access mode in windows and dialogs between all controls and just text fields and scrolling lists
|-
| ? || Control-Tab || Moves focus to the next grouping of controls in a dialog or the next table (when Tab moves to next cell)
|-
| ? || Shift-Control-Tab || Moves focus to the previous grouping of controls
|-
| ? || Command-Tab || Moves focus to the first (or next) open application’s Dock icon
|-
| ? || Command-Shift-Tab || Moves focus to the previous open application’s Dock icon
|-
| ? || Arrow key || Moves focus to the next or previous value in a text field or certain controls, such as menus; also opens Dock menus
|-
| ? || Control–arrow key || Moves focus to another value or cell within a control such as a table
|-
| style="color:green" | OK || Command-` (grave accent) || Activates the next open window in the frontmost application
|-
| style="color:green" | OK || Command-Shift-` (grave accent) || Activates the previous open window in the frontmost application
|-
| ? || Command-Option-` (grave accent) || Moves focus to the window drawer
|-
| ? || Space bar || Selects the highlighted control (equivalent to clicking the mouse button)
|-
| style="color:green" | OK || Return (Enter) || Selects the default button
|-
| style="color:green" | OK || Esc || Cancels a dialog or a selection in a pop-up menu or list; in a Dock menu, Esc closes the menu and moves the focus to the frontmost window
|}

====Quick Reference Shortcuts====

Here's a list of shortcuts from Quick Reference [http://developer.apple.com/documentation/userexperience/Conceptual/AppleHIGuidelines/XHIGKeyboardShortcuts/chapter_950_section_1.html#//apple_ref/doc/uid/TP40002725-CHDIGFBH] from Apple. Table below doesn't contain all shortcuts from this page, only reasonable ones and those not listed above.

=====Alphabet keys=====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Alphabet shortcuts
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Keys !! style="background:#abcdef" align="left" | Action
|-
| style="color:green" | OK || Cmd-Z || Reverse the effect of the user's previous operation (Undo)
|-
| style="color:red" | EE || Cmd-Shift-Z || Reverse the effect of the last Undo command (Redo) 
OO.o uses Cmd-Y
|-
| style="color:green" | OK || Cmd-X || Remove selection and store on the Clipboard (Cut)
|-
| style="color:green" | OK || Cmd-W || Close the active window (equivalent to the Close command)
|-
| style="color:red" | EE || Shift-Cmd-W || Close a file and its associated windows 
This should be associated with File - Close command
|-
| style="color:red" | EE || Option-Cmd-W || Close all windows in the application 
There's no File - Close All or Window - Close All menu item
|-
| style="color:green" | OK || Cmd-V || Insert the Clipboard contents at the insertion point (Paste)
|-
| style="color:blue" | II || Option-Cmd-V || Apply the style of one object to the selected object (Paste Style) 
AFAIK no Paste Style in OO.o
|-
| style="color:blue" | II || Option-Shift-Cmd-V || Apply the style of the surrounding text to the insert object (Paste and Match Style) 
not exactly implemented in OO.o, but in the "Paste Special" menu there's "Paste Unformatted", which is almost the same
|-
| style="color:blue" | II || Ctrl-Cmd-V || Apply formatting settings to the select object (Paste Ruler) 
Probably Format brush, need more info
|-
| style="color:green" | OK || Cmd-U || Underline the selected text or turn underlining on or off
|-
| style="color:red" | EE || Cmd-T || Display the Fonts window 
OO.o uses F11, which is captured by Mac OS X.
|-
| [[http://www.openoffice.org/issues/show_bug.cgi?id=99204 bug 99204]] || Alt-Cmd-T || Mac OS X: show or hide the Character Palette. (Show or hide a toolbar. 
As we have more than one toolbar, we should save all visible toolbars and hide / show them.)
|-
| style="color:green" | OK || Cmd-S || Save
|-
| style="color:green" | OK || Shift-Option-S || Save As
|-
| style="color:green" | OK || Cmd-Q || Quit the application
|-
| style="color:green" | OK || Cmd-P || Display the Print dialog
|-
| style="color:red" | EE || Shift-Cmd-P || Display a dialog for specifying printing parameters 
This should be probably assigned to File - Printer Settings
|-
| style="color:green" | OK || Cmd-O || Open a new document
|-
| style="color:green" | OK || Cmd-N || Open a new document
|-
| style="color:red" | EE || Cmd-M || Minimize the active window to the Dock 
Window is minimized, but Writer, Calc, ... use this shortcut for default formatting
|-
| style="color:red" | EE || Option-Cmd-M || Minimize all windows of the active application to the Dock 
Doesnt' work, beeps only
|-
| style="color:green" | OK || Cmd-J || Scroll to a selection
|-
| style="color:green" | OK || Cmd-I || Italicize the selected text or toggle italic text on or off
|-
| style="color:red" | EE || Option-Cmd-I || Display and inspector window 
This should display Character ... dialog in Writer for example. Same as right mouse click - Character ... This is for what Inspector window is used in other applications.
|-
| style="color:green" | OK || Cmd-H || Hide the windows of the currently running application
|-
| style="color:green" | OK || Option-Cmd-H || Hide the windows of all other running applications
|-
| style="color:red" | EE || Cmd-G || Find the next occurence of the selection 
This should be assigned to Find button in the Find & Replace dialog at least
|-
| style="color:red" | EE || Shift-Cmd-G || Find the previous occurence of the selection 
This should be assigned to Find button in the Find & Replace dialog at least and search direction should be set to backwards.
|-
| style="color:green" | OK || Cmd-F || Open a Find window
|-
| style="color:blue" | II || Option-Cmd-F || Jump to search field control 
There's no search field control
|-
| style="color:red" | EE || Cmd-E || Use the selection for a find operation 
OO.o uses this shortcut to center text/object. This shortcut should open Find & Replace dialog and put selected text into the search for field. Cmd-| (pipe) should be used for centering.
|-
| style="color:green" | OK || Cmd-D || Double underline - it's not HIG, but it not violates HIG too
|-
| style="color:green" | OK || Cmd-C || Duplicate the selected data and store on the Clipboard (Copy)
|-
| style="color:blue" | II || Shift-Cmd-C || Display the Colors window 
Does it make sense to display floating window with colors? Probably not yet
|-
| style="color:blue" | II || Option-Cmd-C || Copy the style of the selected text (Copy Style) 
We can probably enhance clipboard and add additional style object, so, user can copy style and paste it to objects with Option-Cmd-P?
|-
| style="color:blue" | II || Ctrl-Cmd-C || Copy the formatting settings of the selected item and store on the Clipboard (Copy Ruler) 
Same as for the previous one. No Style, but hardcoded formatting combined with Style?
|-
| style="color:green" | OK || Cmd-B || Boldface the selected text or toggle boldfaces text on or off
|-
| style="color:green" | OK || Cmd-A || Select all
|}

=====Special keys=====

{| border="1" cellpadding="5" cellspacing="0" align="center" valign="top" style="width:800px"
! style="background:#59e;" colspan="3" | Alphabet shortcuts
|-
! style="background:#abcdef" | Status !! style="background:#abcdef" | Keys !! style="background:#abcdef" align="left" | Action
|-
| style="color:green" | OK || Option-Cmd-8 || Turn screen zooming on or off
|-
| style="color:green" | OK || Option-Ctrl-Cmd-8 || Invert the screen colors
|-
| style="color:green" | OK || Shift-Cmd-4 || Capture a selection to a file
|-
| style="color:green" | OK || Shift-Ctrl-Cmd-4 || Capture a selection to the Clipboard
|-
| style="color:green" | OK || Shift-Cmd-3 || Capture the screen to a file
|-
| style="color:green" | OK || Shift-Ctrl-Cmd-3 || Capture the screen to the Clipboard
|-
| style="color:red" | EE || Shift-Cmd-= || Increase the size of the selected item 
Normally, font size is increased. Other applications use this shortcut to zoom in page.
|-
| style="color:green" | OK || Option-Cmd-= || Zoom in when screen zooming is on
|-
| style="color:green" | OK || Option-Cmd-/ || Turn font smoothing on or off
|-
| style="color:red" | EE || Cmd-? || Open the application's help viewer 
OO. uses F1
|-
| style="color:green" | OK || Option-Ctrl-Cmd-. || Increase screen contrast
|-
| style="color:green" | OK || Option-Ctrl-Cmd-, || Decrease screen contrast
|-
| style="color:green" | OK || Cmd-, || Open the application's preferences window
|-
| style="color:red" | EE || Cmd-; || Find mispelled words in the document 
FIXME - proposal
|-
| style="color:red" | EE || Cmd-(pipe) || Center-align a selection 
OO.o uses Cmd-E, which should be used for something else.
|-
| style="color:red" | EE || Cmd-} || Right-align a selection 
OO.o uses Cmd-R
|-
| style="color:red" | EE || Cmd-{ || Left-align a selection 
OO.o uses Cmd-L
|-
| style="color:green" | OK || Option-Cmd-- (hyphen) || Zoom out when screen zooming is on
|-
| style="color:red" | EE || Cmd-- (hyphen) || Decrease the size of the selected item 
It should decrease font size of selection. Other applications use this shortcut to zoom out whole page.
|-
| style="color:green" | OK || Cmd-` || Activate the next open window in the frontmost application
|-
| style="color:green" | OK || Shift-Cmd-` || Activate the previous open window in the frontmost application
|-
| ?? || Option-Cmd-` || Move focus to the window drawer
|-
| ... || ... || To be done
|}

==Mac OS X Shortcuts==
The following table describes the differences in keyboard shortcuts and the reasons for the changes. For detailed information, see: [http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/chapter_1_section_1.html Apple Human Interface Guidelines], [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGKeyboardShortcuts/chapter_20_section_1.html AHIG for key accelerators and menus] and [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGMenus/chapter_16_section_4.html for menu examples]

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''OpenOffice.org Mac OS X shortcuts'''
|-
! style="background:#59e;" colspan="4" | Generic OpenOffice.org
|-
! style="background:#abcdef;width:100px;" | Functionality !! style="background:#abcdef;width:150px;" | Ideal OpenOffice.org !! style="background:#abcdef;width:150px;" | OpenOffice.org Aqua !! style="background:#abcdef;width:300px;" | Reason
|-
| '''Main command key''' || Command (CMD) ''the "Apple" key'' || Command (CMD) ''the "Apple" key'' (implementation in progress) || In Mac OS X, the ''Command'' -modifier is the logical equivalent of ''Control'' modifier in Windows and Linux
|-
| '''Function keys''' || F1 - F12 || - || Function keys in Mac OS X have system-wide functionality (like F9 for Exposé)
|-
| '''Spotlight search''' || CMD-Space || - || This shortcut is used system-wide in Mac OS X
|-
| '''Apple reserved''' || CMD-Shift-Space || - || This shortcut is used system-wide in Mac OS X (see [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGKeyboardShortcuts/chapter_20_section_1.htmlbreaking Apple shortcut documentation])
|-
| '''Preferences...''' ''access to settings'' || CMD-, ''i.e. comma''||CMD-, same shortcut || AHIG, system-wide standard. Mac OS X: ''Preferences... in (System-wide) Application menu, i.e. the "Apple-menu"'' OOo: ''Tools > Options''
|-
| '''Help''' || CMD-? ''i.e. question mark'' || F1 || AHIG, system-wide standard
|-
| '''Undo''' || CMD-Z || CMD-Z || AHIG, system-wide standard
|-
| '''Redo''' || CMD-SHIFT-Z || CMD-Y || AHIG, system-wide standard
|-
| '''Spellcheck''' || CMD-; ''i.e. semicolon'' || F7 || AHIG, system-wide standard. Mac OS X: ''Edit > Spellcheck''
|-
| '''Non-breaking space''' || Option-Space || CTRL-Space || conflicts with Mac OS X System. See also [http://en.wikipedia.org/wiki/Non-breaking_space Wikipedia:Non-breaking space]
|-
| '''Close''' || CMD-W ''Close in File -menu'' || CTRL-F4 and CTRL-W || AHIG, system-wide standard. OOo: ''window > Close window'' with the key accelerator and ''File > Close'' without key accelerator.
|-
| '''Minimize''' ''minimize window'' || CMD-M ''Minimize in Window -menu'' || ?? || AHIG, system-wide standard.
|-
| '''Hide''' ''hide window'' || CMD-H ''Hides the Window '' ||CMD-H ''Hides the Window ''|| AHIG, system-wide standard.
|-
| '''Copy''' ''copy'' || CMD-C ''Copy '' ||CMD-C ''Copy''|| AHIG, system-wide standard.
|-
| '''Paste''' ''paste'' || CMD-V ''paste '' ||CMD-V ''paste ''|| AHIG, system-wide standard.
|-
| '''Paste and Match style''' || CMD-SHIFT-OPTION-V ''Paste and Match style in Edit -menu'' || - ''Paste Special -> Unformatted text in Edit -menu'' || There is no direct command in OOo. CTRL-SHIFT-V activates the paste special dialog. However, the "Paste and Match style" should have shortcut as the text is more intuitive and is very handy when copy-pasting between different documents.
|-
| '''Open''' ''open' || CMD-O ''Open '' ||CMD-O ''Open''|| AHIG, system-wide standard.
|-
| '''Print''' ''print'' || CMD-P ''print '' ||CMD-P ''print ''|| AHIG, system-wide standard.
|-
| '''Save ''' || CMD-S ''save''|| CMD-S ''save'' || AHIG, system-wide standard.
|-
| '''Save As''' || CMD-SHIFT-S || - || AHIG, system-wide standard.
|-
| '''Left-align''' || CMD-{ ''i.e. left bracket'' || CTRL-l || AHIG, system-wide standard
|-
| '''Right-align''' || CMD-} ''i.e. right bracket'' || CTRL-r || AHIG, system-wide standard
|-
| '''Align to center''' || <nowiki>CMD-|</nowiki> ''i.e. pipe'' || CTRL-e || AHIG, system-wide standard
|-
| '''Decrease size''' of the selected item || CMD-- || ?? || AHIG, system-wide standard. Apple Pages: ''Format > Font > Smaller'' Equivalent of the Smaller command in OpenOffice.org
|-
| '''Increase size''' of the selected item || CMD-+ || ?? || AHIG, system-wide standard. Apple Pages: ''Format > Font > Bigger'' Equivalent of the ?? command in OpenOffice.org
|-
| '''Conditional hyphen''' || ?? || CTRL-- || conflicts with AHIG
|-

! style="background:#59e;" colspan="4" | OpenOffice.org Writer
|-
! style="background:#abcdef;" | Functionality !! style="background:#abcdef;" | OpenOffice.org Mac OS X !! style="background:#abcdef;" | OpenOffice.org !! style="background:#abcdef;" | Reason
|-
| '''Refresh fields''' || ?? || F9 || Conflicts with Mac OS X system. OOo: ''Tools > Refresh > Fields''
|-
| '''Style dialog''' || CMD-SHIFT-T || F11 || Conflicts with Mac OS X system. Apple Pages: ''View > Show Styles Drawer''
|-
| '''Default format''' ''in Format -menu'' || - || CTRL-SHIFT-Space || Conflicts with Apple reserved shortcut, see [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGKeyboardShortcuts/chapter_20_section_1.htmlbreaking Apple shortcut documentation] Apple Pages: ''Format > Reapply Defaults to Selection'' OOo: ''Format > Default format''
|-

! style="background:#59e;" colspan="4" | OpenOffice.org Calc
|-
! style="background:#abcdef;" | Functionality !! style="background:#abcdef;" | OpenOffice.org Mac OS X !! style="background:#abcdef;" | OpenOffice.org !! style="background:#abcdef;" | Reason
|-
| '''Recalculate''' the cell content || ?? || F9 || Conflicts with Mac OS X system. OOo: ''Tools > Cell content > Recalculate''
|-
| '''Group (data)''' || ?? || F12 || Conflicts with Mac OS X system. OOo: ''Data > Plan > Group''
|-

|-

|}
==Keyboard Viewer in Mac OS X==
* [http://docs.info.apple.com/article.html?path=Mac/10.5/en/9024.html English]
* [http://docs.info.apple.com/article.html?path=Mac/10.5/fr/9024.html Français]
===Screen shots===
====British====
* http://www.brighton.ac.uk/centrim/Members/gjp4/ooo/qa/92224

==See also==
===[[Auto-completion]]===
* … list all parts of OpenOffice.org providing some kind of auto-completion feature, then compare and discuss their respective user interfaces …
===[[AutoInput]]===
* … will discuss the user interface for the AutoInput feature in Calc (also known as auto-completion.) …
===[[Word_Completion|Word completion]]===
* … behavior of the Word Completion feature in Writer (sometime called auto-completion.) …
===GullFOSS===
* [http://blogs.sun.com/GullFOSS/entry/framework_team_and_community_contributions The framework project and community contributions for OpenOffice.org 3.1 – Part 1]
* [http://blogs.sun.com/GullFOSS/entry/the_framework_project_and_community The framework project and community contributions for OpenOffice.org 3.1 – Part 2] … "Extensions are part of the different configuration layers and therefore can provide accelerators easily with a configuration file within their extension package.".

[[Category:Porting]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]
[[Category:User Experience]]
[[Category:To-Do]]

SVN

2008-10-09T19:35:19Z

Mox: SVN usage guide for OpenOffice.org sources

== SVN - Subversion ==

Once things settle down, this page will hopefully contain FAQ and instructions for using SVN with OpenOffice.org sources, a bit similar to [[CVS]] and [[Getting It]].

In the meantime, take a look at [[OOo and Subversion]] page.

Main Page

2008-10-09T19:31:04Z

Mox: /* Hot Topics */

<div style="float:right; padding-left:5px;">
{| style="text-align:left; border:1px solid #aaaaaa; background-color:#f9f9f9;font-family: Verdana, sans-serif;"
|- padding:5px;padding-top:0.5em;font-size: 95%;
|
<div style="border:1px solid #ccc; background: #fff; border-right:3px solid #ccc; border-bottom:3px solid #ccc; text-align: center; padding:3px; float:right; font-size: smaller; line-height: 1.3; margin-right: 4px;">
<div style="width:100%">{{CURRENTDAYNAME}}</div>
<div style="width: 100%;">{{CURRENTYEAR}}</div>
<div style="width: 100%;"> {{CURRENTMONTH}}</div>
<div style="font-size: x-large; width: 100%;">{{CURRENTDAY}}</div>
<div style="background: #aaa; color: #000;">'''{{CURRENTTIME}}''' [[wikipedia:UTC|UTC]]</div>
</div>
|}
</div>


== Welcome to the OpenOffice.org wiki ==
__NOTOC__
This wiki is for all projects associated with OpenOffice.org (OOo). It has a good focus on resources for developers. Also other projects work more and more on the wiki. (Most...) are listed here. Click a link to go directly to the page you want.
* [[Certification]]
* [[Community_Council|Community Council]]
* [[#Getting started with OOo development|Development]] (see below)
* [[Documentation]]
* [[Education Project]]
* [[Marketing]]
* [[NLC]] ''Native-Language Confederation''
* [[Product_Release|Product Releases]]
* [[Quality Assurance]]
* [[Security]]
* [[User_Experience|User Experience (UX)]]
* User Interface ([[Accessibility]], [[Visual Design]])
* [[#Finding general OpenOffice.org user help|User Resources]]
* [[Website]]
* [[List_of_wishes]]
Join in contributing to the OpenOffice.org Wiki. Please use your OOo login name for the wiki account. Some functionality is available only if you are logged in to avoid [[MediaWiki_Configuration#AntiSPAM_Measures43q5|SPAM]]. Additionally your email address has to be validated. We might be able to avoid the separate user administration later and log you in with the OpenOffice.org site credentials.

To get started editing the wiki see [[Help:Editing]].

== Getting started with OOo development ==
<div style="float:right; background-color:lightyellow; border: 1px solid black; margin:0 1em 0 0.5em; padding:0 0.5em 0 0.5em; ">
Get Started from Scratch 
you most likely need to:
# [[Getting It|Get it]]
# [[Building|Build it]]
# [[Installing|Install it]]
# [[Running|Run it]]
Click for instructions on 
each step!
</div>

[[Building]] and [[hacking]] on [http://www.openoffice.org OpenOffice.org] (OOo) entails climbing a fairly lengthy and steep incline. Hopefully, this wiki will make the learning curve less steep and less abrupt, and will give you a walking stick to help you out.

Much of our documentation assumes that you'll be using a reasonably current Linux system, as this is the easiest environment to start. On Linux, all prerequisites are available as [http://www.gnu.org Free software]. There is also some information on developing on [[Windows]].

[[Education_Project |Education Project]] aims to welcome Students or Teachers who are interested to contribute for code, or whatever concerning Educational system ( see e.g. [[Education_Project/Effort |Education Project Effort]] )

For help setting up your editor or environment to search/edit/compile OOo easily, please refer to the [[:Category:Developer_Tools|developer tools]] area.

Note that you can build either the plain 'up-stream' OOo or use an [[ooo-build]] release which adds some patches & fixes. However, the ooo-build process is destined to being gradually phased out as the various up-stream issues it solves go away.

Remember that learning UNO components development is not an easy task. To help you there is an Eclipse plugin and tutorial. You can install the Eclipse plugin by using the following update site: http://cedric.bosdonnat.free.fr/ooeclipseintegration. The tutorial on how to create a UNO component in Java is available in the [http://api.openoffice.org/files/documents/22/3216/JavaComponentTuto.odt api project docs & files sections]. The document will even be wikified on this page: [[JavaEclipseTuto | Java Tutorial using Eclipse]]

There exists also an [[OpenOffice_NetBeans_Integration|OpenOffice.org API plugin for NetBeans]] that helps a lot to get started with the API and with developing with and for OpenOffice.org. The plugin provides several wizards that simplify the first steps and help to create full working code skeletons for extensions. Try it out and have fun when you want to develop a Java extension for OpenOffice.org. Feedback is always welcome, help us to improve the plugin and send us new ideas what we can do better!

== Going Further ==

* [[I want to be an OpenOffice.org developer]] - the basic what & where
* [[IRC Communication|Meet the team on IRC]]
* [[Tutorials]] - hacker tutorials to get the hang of the code
* [[Debugging]] - for when it all goes wrong
* [[Tinderbox]] - test new [[CWS|child workspaces]] and show your build logfile to others
* [[Environment Variables]] - a description of handy environment variables used at runtime
* [[Source code directories| A description of the source directories]]
* [[Contributing Patches]] - for when you have something to fold back
* [[Commit Rights]] - An overview of how to attain commit rights, and what to do with them once you get them
* [[Tips]] - misc. hints & tips.
* [[FAQ]] - some infrequently asked questions
* [[Using_Cpp_with_the_OOo_SDK|Using C++ with OOo SDK]]
* [[Extensions_development|Extensions development]] (Python, Basic, Java and C++)
* [[Extensions_development#Ideas|Extensions Ideas]] An ideas section for new extensions '''(NEW)'''
* [[:Category:Localisation|Localisation of OpenOffice.org (under construction)]]
* [[OpenOffice_NetBeans_Integration|OpenOffice.org NetBeans Integration]] - program, extend, and customize OO.org in Java with a modern IDE
* [[OpenOffice_Eclipse_Integration|OpenOffice.org Eclipse Integration]] - program, extend, and customize OOo in Java with Eclipse
* [[Extra Software]] - other open source programs

== Hot Topics ==
* [[SVN]]: [[OOo_and_Subversion|OpenOffice.org migrates to Subversion]] '''(NEW)'''
* [[Marketing/OnlineConferenceSessions|Online Conference Sessions]] '''(NEW)'''
* [[Extensions development#Ideas|Extensions Ideas]] '''(NEW)'''
* [[To-Dos]]
* [[Performance]]
* [[User:Ericb|Native Mac OS X port]] or for everything related to OpenOffice.org and [[:Category:MacOSX|Mac OS X]]
* [[SVG_Import_Filter|SVG import]]
* [[Product Release|Product release data]]
* [[Java_and_OpenOffice.org|Java related functionality]]
* [[Cpp Coding Standards|C++ Coding Standards]], [[Writing_warning-free_code|Warning-free Code]] and [[Writing_correct_Cplusplus|Correct C++]]
* [[Syndication|Syndication]] Of OOoAnnouncements
* [[Mono Integration|details on how to get Mono working with OOo]]
* [[Porting_to_x86-64_%28AMD64%2C_EM64T%29|64bit porting]]
* [[VBA|MS Office VBA interoperability]]
* [[Digital Signatures]]
* [[Bibliographic| Bibliographic Project Developer and Documentation pages]]
* [[QA Metrics]]
* [[BuildSpeedup| Make the OO.o build process the coolest on the planet]]
* [[Chart2 | Chart2: The new chart implementation]]
* [[Firefox ODFReader extension]]
* [[Firefox OpenOffice.org extension]] Menu extension with useful OO.o links
* [[Compiler versions used by port maintainers and release engineers]]
* [[Effort/Revise OOo Multi-Threading|Revise OOo Multi-Threading]].
* [[Uno]] on the Wiki.
* [[Framework]] on the Wiki.
* [[Summer_of_Code_2007]] and [[OpenOffice.org_Developer_Article_Contest]]
* [[BetterDatabaseDrivers | Better and simpler infrastructure for database drivers]]
* [http://www.openoffice.org.br/?q=lancamento_do_cogroo Cogroo] grammatical checker in Portuguese
* [[Architecture]] - Description of OOos software architecture.
* [[Metalink]] - An XML format used by OOo for file distribution that stores mirror/P2P locations.
* [[Convert2MediaWiki]] - Informations to convert from OOo to media wiki
* [[Object Inspector]] - Description of an extension to inspect Uno-Objects
* [[OOoCon 2007]] - The OpenOffice Conference 2007

== Finding general OpenOffice.org user help ==

* [[OOoHelpOutline|OpenOffice.org Help Outline]]
* [[OOo OnlineHelp]]
* [http://plan-b-for-openoffice.org/ Technical support] for non technical users
* Free and commercial [[OpenOffice.org_Solutions|Solutions]] to assist in the adoption of OpenOffice.org
* [[Press coverage on OpenOffice.org]]
* [[Wikipedia:List_of_applications_supporting_OpenDocument|List of applications supporting OpenDocument]] from Wikipedia
* [[OASIS]] and [[OpenDocument]]
* The office suite components: [[Writer]], [[Calc]], [[Impress]], [[Base]], [[Math]], [[Draw]], and [[Chart]].
* [http://www.kegel.com/openoffice/triage.html OpenOffice.org Needs YOU! (OLD)]

[[:Category:MainIndex|Main Index of Articles]]

<center>
{|style="border: 1px solid #cfcfbf; padding: .0em .25em .0em; background-color: #f0f0ff; text-align: center;"
|
|-
|


| style="font-size: 95%;"|You loaded this Main Page on {{CURRENTDAYNAME}}, {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}} ''T'' {{CURRENTTIME}} '''[[wikipedia:UTC|UTC]]'''.
|-
|style="font-size: 95%;"|
|}
</center>
{{InterWiki Languages}}

Getting the source

2008-10-09T19:29:55Z

Mox: /* Vanilla up-stream */

{|
|
=== Source code ===

The source code can be downloaded as tarballs, e.g. [http://download.openoffice.org/2.2.1/source.html here for OOo2.2.1]. In case there are newer releases or for developer snapshots please see the [http://download.openoffice.org/ Download Central] ''Development'' section. The source is huge, so it was split to several files: for newer releases than OOo2.1 substitute OOo_2.1.0_ accordingly:

* OOo_2.1.0_src_core.tar.bz2 - the necessary part for each build, the other tarballs depend on this one.
* OOo_2.1.0_src_binfilter.tar.bz2 - the filters for old binary [[StarOffice]] formats.
* OOo_2.1.0_src_l10n.tar.bz2 - translations to other languages than English and German.
* OOo_2.1.0_src_sdk.tar.bz2 - OOo SDK (Software Development Kit).
* OOo_2.1.0_src_system.tar.bz2 - libraries that usually are on a standard Linux system and it's not necessary to build own version on Linux. For a Windows build this package is usually required.

For a full build you need them all. For development, <tt>src_core</tt> is usually all you need.

Download them to one directory and unpack them. Information how to checkout from CVS follows.

=== Vanilla up-stream ===

You might be interested particularly in the [http://tools.openoffice.org/dev_docs/build_linux.html#GetTheSourceCode Get the source code] section in the build guide. It is written for Linux, but it is quite similar for all the platforms.

export 'CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs'
cvs login
(CVS password: anoncvs)
cvs co -r <milestone> OpenOffice2

The tool to browse project [http://tools.openoffice.org/source/browse/tools/ source code online] has some [http://tools.openoffice.org/servlets/ProjectSource additional hints].

If you want just to test development releases, you can download already compiled builds from [http://download.openoffice.org/680/]. List of available Mac builds is in [[Mac OS X Development Builds]].

SVN: See also [[OOo and Subversion]]

=== ooo-build ===

There are loads of versions of OO.o, and several choices of branch, with multiple outstanding patch sets.
I recommend you build from up-stream CVS HEAD milestones (SRC680 milestones), with patch sets to make them easier to build from [http://go-ooo.org/packages/SRC680]

The very latest ooo-build (a small ~1.5Mb build wrapper) can be got from SVN thus:

<pre>
svn co http://svn.gnome.org/svn/ooo-build/trunk ooo-build
</pre>

Note: You are going to need to download an additional ~150Mb of compressed source, and have ~3Gb
of space to unpack and build it in.

== Checking out a CWS through CVS ==

''This section is a draft!''

First, find the CWS name such as picom. Then, lookup the CWS name in EIS (e.g., [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=5112&logon=true&OpenOnly=false&Section=All picom]). Notice "Milestone (current)" is m222 (in this example as of time of writing): that is the base milestone. Then, notice the affected modules listed under "Modules & Files."

You will checkout the base milestone from CVS. The convention for base milestone is SRC680_m### (later DEV300_m###?). Then in each affected module (where a module is basically a directory), you will update the module with CVS. The convention for the revision tag for the CWS is cws_src680_####.

Here is a script.

<code>
#!/bin/bash
# configure these variables according to the particular CWS
AFFECTED_MODULES="basebmp basegfx canvas comphelper cppcanvas \
desktop filter goodies offapi offuh psprint sal \
slideshow solenv testshl2 tools unotools vcl xpdf"
BASE_MILESTONE_TAG=SRC680_m222
CWS_TAG=cws_src680_picom
export CVSROOT=':pserver:anoncvs@anoncvs.services.openoffice.org:/cvs'
echo 'Enter the password is anoncvs'
cvs login
cvs co -r $BASE_MILESTONE_TAG OpenOffice2
for d in $AFFECTED_MODULES
do
echo "updating module $d"
pushd $d
cvs up -dP -r $CWS_TAG
popd
done
</code>

'''If''' you have a working [[CWS#cws_config_file_.28.cwsrc.29 | ~/.cwsrc configuration file]] setup '''and''' the SOLARENV environment variable is set to an already existing <tt>solenv</tt> directory of a previously checked out OOo tree, e.g. <code>export SOLARENV="$HOME/ooo/SRC680/src.m222/solenv"</code>, '''and''' <tt>PATH</tt> contains the <tt>solenv/bin</tt> directory, e.g. <code>export PATH="$SOLARENV/bin:$PATH"</code>, '''then''' the list of affected modules may be automatically obtained using
<code>
AFFECTED_MODULES="$(cwsquery -m src680 -c picom modules)"
</code>

You also may use <tt>cwsquery</tt> to obtain the current milestone of the CWS with
<code>
BASE_MILESTONE_TAG="SRC680_$(cwsquery -m src680 -c picom current)"
</code>

When scripting this it is a good idea to check the exit code of <tt>cwsquery</tt> commands in case your <tt>~/.cwsrc</tt> is broken or the environment prerequisites aren't met or the EIS database isn't reachable, so add the following after each <tt>cwsquery</tt> command:
<code>
if [ $? -ne 0 ]; then
echo 'cwsquery unsuccessful.'
exit 1
fi
</code>

If you already have <tt>~/.cwsrc</tt> working and a milestone master build ready and want to work on a CWS based on that milestone see [[Tuning in to a CWS]], which offers a method that does not require to rebuild the entire tree.

External links
* [http://cedric.bosdonnat.free.fr/wordpress/?p=78 Getting an OOo CWS] Cedric's blog (May 2008)

== See also ==

*[[Building]]
| valign="top" |
{{Getting_It|Languages}}
|}

[[Category:Development]]

Mac OS X Porting - Work Areas/Todo's

2008-09-14T11:05:45Z

Mox: /* Areas and ToDos X11 Version */

This page is intended to serve as a living ToDo list for the OpenOffice.org Mac OS X port. To keep things simple it contains the ToDos for both the X11 version and the upcoming Aqua version of OpenOffice.org for Mac OS X. The page is divided into different work areas which either assigned to a person in charge or are unassigned yet. Below each area there is a detailed list of todos which has to be maintained by the respective people himself.
Persons who are in charge of a certain area are responsible for keeping their respective part of the page up-to-date.
<noinclude>[[Category:Porting]] [[Category:Aqua]] [[Category:MacOSX]] [[Category:To-Do]]</noinclude>

If you're interested in contributing to the project please coordinate with [mailto:ericb@openoffice.org Eric Bachard]

== Areas and ToDos Aqua Version ==
 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Messaging || [mailto:tra@openoffice.org Tino Rachui]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement messaging infrastructure || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Windowing || [mailto:tra@openoffice.org Tino Rachui]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement salframe.cxx || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Drawing || [mailto:ssa@openoffice.org Stephan Schaefer]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement drawing support || In progress || [mailto:ssa@openoffice.org Stephan Schaefer]
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native Printing support || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Make some docs || Done || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|-
| Native look & feel for Print and Print Setup || In progress || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|-
| Panel for OpenOffice.org specific options || New || Unassigned
|-
| Implement native Print support || New || Unassigned
|-
| Implement native Print setup || New || Unassigned
|}

Work in progress, see: [[Mac OS X Porting - Native Printing]]

Description:

'''OpenOffice.org side''':

AquaSalPrinter class is located in aqua/source/gdi/salprn.cxx

Headers are in:
vcl/inc/salinst.hxx
vcl/inc/salgdi.hxx
vcl/inc/salprn.hxx

Aqua implementation:
aqua/inc/salprn.h (AquaSalPrinter class implementation, inherits from SalPrinter)

'''Mac OS X API side''':

Todo: implement missing methods, using Carbon API

Link for Mac OS X API documentation:

http://developer.apple.com/documentation/Carbon/Reference/CarbonPrintingManager_Ref/index.html

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Key input || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| accelerators for native menu || In progress || Ismael
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native sound support ||
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement native sound support || Started || [mailto:ericb@openoffice.org Eric Bachard]
|}

New page has been updated.

See: [[Native Sound Implementation on Mac OS X]]

Estimation of code remaining to write: 40% (macosxplayer.cxx mainly)

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Image Acquisition || [mailto:ericb@openoffice.org Eric Bachard]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement Image Acquisition || In progress || [mailto:ericb@openoffice.org Eric Bachard]
|}

'''See''': [[Mac OS X Porting - Data Acquisition]]

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native font support || [mailto:ericb@openoffice.org Eric Bachard]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| ATS || Started || [mailto:ericb@openoffice.org Eric Bachard]
|}

salatslayout.cxx License origin is justified here: http://qa.openoffice.org/issues/show_bug.cgi?id=23283]

'''OpenOffice.org side''':

See : [[Mac OS X Porting - Native Fonts]]

Carbon API implementation (binding) is made in salatslayout.cxx

ATS and ATSUI starting point: http://developer.apple.com/documentation/Carbon/Conceptual/ATS_Concepts/atsfonts_intro/chapter_1_section_1.html

Apple's starting page leading to deeper docs: http://developer.apple.com/documentation/TextFonts/Typography-date.html

'''Todo-list for native font implementation:'''

- missing methods (to be implemented):

'''bool ATSLayout::GetGlyphOutlines()'''
'''ATSLayout::InitFont()'''
'''ATSLayout::MoveGlyph()'''
'''ATSLayout::DropGlyph()'''
'''ATSLayout::Simplify()'''

- Fix known bugs:
MultiLine does not work (writer cannot be used, because)
Bad keyboard/charset ? (missig chars)
When redrawing, everything is redrawn using the most little font size -> even the dialog boxes on menu bars
Bad values returned

- Implement MultiSalLayout
- Complete implementation
- read Apple API [ Work in progress]
- describe current implementation: organisation / design [work in progress]
- design of new implementation [FIXME] find examples

Estimation of code remaining to write ~40 %

'''Done''' (mainly Stephan Schaefer, with initial salatslayout.cxx file written by Herbert Duerr)

'''Work in progress''' : understand MultiSalLayout

'''Resources''': use sample code to test/initialize ATS server (using e.g. ATSUIDirectAccessDemo)

For more informations, see: [[Mac OS X Porting - Native Fonts]]

== Areas and ToDos X11 Version ==

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Packaging Packaging related tasks || [mailto:obr@openoffice.org Oliver Braun]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Improved packaging for OOo || Done || [mailto:obr@openoffice.org Oliver Braun]
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Installation Installation related tasks || [mailto:obr@openoffice.org Oliver Braun]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Provide an improved installer for OOo || New || [mailto:obr@openoffice.org Oliver Braun]
|-
| Error messages during installation when no X11 is installed || Started (messages need to be localised and more info supplied) || Unassigned
|-
| Support language pack instalation || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Desktop Integration Desktop integration related tasks || [mailto:obr@openoffice.org Oliver Braun]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
|Allow opening of documents with path names that need to be escaped for shell scripts || Integrated for 2.1 see [http://www.openoffice.org/issues/show_bug.cgi?id=69143] || [mailto:smsm1@openoffice.org Shaun McDonald]
|-
| Save documents in ~/Documents by default || New || Unassigned
|-
| Use the Mac OS X key chain for document signing || New || Unassigned
|-
| Read proxy settings and user information from the system settings || New || Unassigned
|-
| Mac OS X address book integration || New || Unassigned
|-
| Make use of the Mac OS X spell checker || New || Unassigned
|-
| Improved clipboard support || New || Unassigned
|-
| Support for standard Mac OS X shortcuts according to HI guideline || New || Unassigned
|-
| Integrate native FileOpen/FileSave dialog into OOo || Started || [mailto:fheckl@openoffice.org Florian Heckl]
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Printing || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Improved printing support (CUPS) || Done || Oliver Braun
|-
| Use the native print dialog in OOo || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Ease of use || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Reduce visible toolbars || New || Unassgined
|-
| Suppress icons in OOo menus by default || New || Unassigned
|-
| Suppress xterm window when launching OOo || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Implement NeoLight plugin || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement NeoLight (spothlight plugin) in OpenOffice.org 2.0. For more informations, please have a look at [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1328&sid=9fb65afa5ca4232a6f8fae420424a3fe]|| New || Unassigned
|}

 

== Assurance Quality and Mac OS X port ==
 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Mac OS X QA || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Collect informations and manage Mac OS X QA on the wiki || New || Unassigned
|}

Mac OS X Porting - Work Areas/Todo's

2008-09-14T11:05:26Z

Mox: /* Areas and ToDos Aqua Version */

This page is intended to serve as a living ToDo list for the OpenOffice.org Mac OS X port. To keep things simple it contains the ToDos for both the X11 version and the upcoming Aqua version of OpenOffice.org for Mac OS X. The page is divided into different work areas which either assigned to a person in charge or are unassigned yet. Below each area there is a detailed list of todos which has to be maintained by the respective people himself.
Persons who are in charge of a certain area are responsible for keeping their respective part of the page up-to-date.
<noinclude>[[Category:Porting]] [[Category:Aqua]] [[Category:MacOSX]] [[Category:To-Do]]</noinclude>

If you're interested in contributing to the project please coordinate with [mailto:ericb@openoffice.org Eric Bachard]

== Areas and ToDos Aqua Version ==
 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Messaging || [mailto:tra@openoffice.org Tino Rachui]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement messaging infrastructure || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Windowing || [mailto:tra@openoffice.org Tino Rachui]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement salframe.cxx || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Drawing || [mailto:ssa@openoffice.org Stephan Schaefer]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement drawing support || In progress || [mailto:ssa@openoffice.org Stephan Schaefer]
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native Printing support || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Make some docs || Done || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|-
| Native look & feel for Print and Print Setup || In progress || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|-
| Panel for OpenOffice.org specific options || New || Unassigned
|-
| Implement native Print support || New || Unassigned
|-
| Implement native Print setup || New || Unassigned
|}

Work in progress, see: [[Mac OS X Porting - Native Printing]]

Description:

'''OpenOffice.org side''':

AquaSalPrinter class is located in aqua/source/gdi/salprn.cxx

Headers are in:
vcl/inc/salinst.hxx
vcl/inc/salgdi.hxx
vcl/inc/salprn.hxx

Aqua implementation:
aqua/inc/salprn.h (AquaSalPrinter class implementation, inherits from SalPrinter)

'''Mac OS X API side''':

Todo: implement missing methods, using Carbon API

Link for Mac OS X API documentation:

http://developer.apple.com/documentation/Carbon/Reference/CarbonPrintingManager_Ref/index.html

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Key input || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| accelerators for native menu || In progress || Ismael
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native sound support ||
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement native sound support || Started || [mailto:ericb@openoffice.org Eric Bachard]
|}

New page has been updated.

See: [[Native Sound Implementation on Mac OS X]]

Estimation of code remaining to write: 40% (macosxplayer.cxx mainly)

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Image Acquisition || [mailto:ericb@openoffice.org Eric Bachard]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement Image Acquisition || In progress || [mailto:ericb@openoffice.org Eric Bachard]
|}

'''See''': [[Mac OS X Porting - Data Acquisition]]

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native font support || [mailto:ericb@openoffice.org Eric Bachard]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| ATS || Started || [mailto:ericb@openoffice.org Eric Bachard]
|}

salatslayout.cxx License origin is justified here: http://qa.openoffice.org/issues/show_bug.cgi?id=23283]

'''OpenOffice.org side''':

See : [[Mac OS X Porting - Native Fonts]]

Carbon API implementation (binding) is made in salatslayout.cxx

ATS and ATSUI starting point: http://developer.apple.com/documentation/Carbon/Conceptual/ATS_Concepts/atsfonts_intro/chapter_1_section_1.html

Apple's starting page leading to deeper docs: http://developer.apple.com/documentation/TextFonts/Typography-date.html

'''Todo-list for native font implementation:'''

- missing methods (to be implemented):

'''bool ATSLayout::GetGlyphOutlines()'''
'''ATSLayout::InitFont()'''
'''ATSLayout::MoveGlyph()'''
'''ATSLayout::DropGlyph()'''
'''ATSLayout::Simplify()'''

- Fix known bugs:
MultiLine does not work (writer cannot be used, because)
Bad keyboard/charset ? (missig chars)
When redrawing, everything is redrawn using the most little font size -> even the dialog boxes on menu bars
Bad values returned

- Implement MultiSalLayout
- Complete implementation
- read Apple API [ Work in progress]
- describe current implementation: organisation / design [work in progress]
- design of new implementation [FIXME] find examples

Estimation of code remaining to write ~40 %

'''Done''' (mainly Stephan Schaefer, with initial salatslayout.cxx file written by Herbert Duerr)

'''Work in progress''' : understand MultiSalLayout

'''Resources''': use sample code to test/initialize ATS server (using e.g. ATSUIDirectAccessDemo)

For more informations, see: [[Mac OS X Porting - Native Fonts]]

== Areas and ToDos X11 Version ==

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Packaging Packaging related tasks || [mailto:obr@openoffice.org Oliver Braun]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Improved packaging for OOo || Done || [mailto:obr@openoffice.org Oliver Braun]
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Installation Installation related tasks || [mailto:obr@openoffice.org Oliver Braun]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Provide an improved installer for OOo || New || [mailto:obr@openoffice.org Oliver Braun]
|-
| Error messages during installation when no X11 is installed || Started (messages need to be localised and more info supplied) || Unassigned
|-
| Support language pack instalation || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Desktop Integration Desktop integration related tasks || [mailto:obr@openoffice.org Oliver Braun]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
|Allow opening of documents with path names that need to be escaped for shell scripts || Integrated for 2.1 see [http://www.openoffice.org/issues/show_bug.cgi?id=69143] || [mailto:smsm1@openoffice.org Shaun McDonald]
|-
| Save documents in ~/Documents by default || New || Unassigned
|-
| Use the Mac OS X key chain for document signing || New || Unassigned
|-
| Read proxy settings and user information from the system settings || New || Unassigned
|-
| Mac OS X address book integration || New || Unassigned
|-
| Make use of the Mac OS X spell checker || New || Unassigned
|-
| Improved clipboard support || New || Unassigned
|-
| Support for standard Mac OS X shortcuts according to HI guideline || New || Unassigned
|-
| Integrate native FileOpen/FileSave dialog into OOo || Started || [mailto:fheckl@openoffice.org Florian Heckl]
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Printing || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Improved printing support (CUPS) || Done || Mox Soini, Oliver Braun
|-
| Use the native print dialog in OOo || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Ease of use || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Reduce visible toolbars || New || Unassgined
|-
| Suppress icons in OOo menus by default || New || Unassigned
|-
| Suppress xterm window when launching OOo || New || Unassigned
|}

 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Implement NeoLight plugin || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement NeoLight (spothlight plugin) in OpenOffice.org 2.0. For more informations, please have a look at [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1328&sid=9fb65afa5ca4232a6f8fae420424a3fe]|| New || Unassigned
|}

 

== Assurance Quality and Mac OS X port ==
 

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Mac OS X QA || [mailto:???@openoffice.org Unassigned]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Collect informations and manage Mac OS X QA on the wiki || New || Unassigned
|}

Mac OS X Porting - Canvas

2008-04-22T20:39:57Z

Mox: /* Tasks */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

 

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

Now there are cairo-based Canvas backends for Unix/X11, Windows and Mac/Quartz. The text rendering, however, is always directed back to VCL. To take the full advantage of cairo library, and it's support for cross-platform text layout and rendering, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvasFont.html XCanvasFont] and [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XTextLayout.html XTextLayout] interfaces need to be implemented "natively" with cairo.

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=88613 issue 88613])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T19:54:19Z

Mox: /* Tasks */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

 

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

Now there are cairo-based Canvas backends for Unix/X11, Windows and Mac/Quartz. The text rendering, however, is always directed back to VCL. To take the full advantage of cairo library, and it's support for cross-platform text layout and rendering, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvasFont.html XCanvasFont] and [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XTextLayout.html XTextLayout] interfaces need to be implemented "natively" with cairo.

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=690xx issue 690xx])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T19:53:51Z

Mox: /* Tasks */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

 

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

Now there are cairo-based Canvas backends for Unix/X11, Windows and Mac/Quartz. The text rendering, however, is always directed back to VCL. To take the full advantage of cairo library, and it's support for text layout and rendering, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvasFont.html XCanvasFont] and [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XTextLayout.html XTextLayout] interfaces need to be implemented "natively" with cairo.

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=690xx issue 690xx])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:48:46Z

Mox: /* Contributors */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

 

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=690xx issue 690xx])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:47:51Z

Mox: /* Contributors */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Berens [[User:thb|thb]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

 

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=690xx issue 690xx])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:46:53Z

Mox: /* Introduction */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

 

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=690xx issue 690xx])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:46:37Z

Mox: /* Introduction */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=690xx issue 690xx])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:46:10Z

Mox:

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=690xx issue 690xx])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:45:34Z

Mox:

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend.

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:39:56Z

Mox: /* Status */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Tasks==

The main task currently, is to understand and document the various APIs and how they interact with each other. The pieces are there ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], [http://developer.apple.com/cocoa/ Cocoa] etc.), but more details are needed to understand how they fit together.

TODO:
* cairo implementation of XCanvas (in OOo) lacks function documentation
* quartz implementation of cairo (in Cairo) lacks function documentation (look at other implementations)
* Create visual explanations of the API structure
* port the code, in [http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066]. Work started.

PERFORMANCE:
* OpenOffice.org VCL uses a lot of XOR-based (win32-like, bitmap-oriented) graphics functions. Mac OS X does not have this concept and uses compositing, canvas and layers instead. To get good performance of OOo on Mac OS X, OOo needs to be gotten rid of heavy use of XOR functions
* 32-bit -images: OOo internally uses non-32bit images, whereas Cocoa/Carbon require 32-bit images for native graphics operations. OOo should be converted to use 32-bit images internally.

DOCS:
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:36:48Z

Mox: /* Tasks */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Tasks==

The main task currently, is to understand and document the various APIs and how they interact with each other. The pieces are there ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], [http://developer.apple.com/cocoa/ Cocoa] etc.), but more details are needed to understand how they fit together.

TODO:
* cairo implementation of XCanvas (in OOo) lacks function documentation
* quartz implementation of cairo (in Cairo) lacks function documentation (look at other implementations)
* Create visual explanations of the API structure
* port the code, in [http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066]. Work started.

PERFORMANCE:
* OpenOffice.org VCL uses a lot of XOR-based (win32-like, bitmap-oriented) graphics functions. Mac OS X does not have this concept and uses compositing, canvas and layers instead. To get good performance of OOo on Mac OS X, OOo needs to be gotten rid of heavy use of XOR functions
* 32-bit -images: OOo internally uses non-32bit images, whereas Cocoa/Carbon require 32-bit images for native graphics operations. OOo should be converted to use 32-bit images internally.

DOCS:
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:36:09Z

Mox: /* Roadmap for Canvas in Mac OS X */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Tasks==

The main task currently, is to understand and document the various APIs and how they interact with each other. The pieces are there ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], [http://developer.apple.com/carbon/ Carbon] etc.), but more details are needed to understand how they fit together.

TODO:
* cairo implementation of XCanvas (in OOo) lacks function documentation
* quartz implementation of cairo (in Cairo) lacks function documentation (look at other implementations)
* Create visual explanations of the API structure
* port the code, in [http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066]. Work started.

PERFORMANCE:
* OpenOffice.org VCL uses a lot of XOR-based (win32-like, bitmap-oriented) graphics functions. Mac OS X does not have this concept and uses compositing, canvas and layers instead. To get good performance of OOo on Mac OS X, OOo needs to be gotten rid of heavy use of XOR functions
* 32-bit -images: OOo internally uses non-32bit images, whereas Cocoa/Carbon require 32-bit images for native graphics operations. OOo should be converted to use 32-bit images internally.

DOCS:
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:34:34Z

Mox: /* Introduction */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

Currently the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas (somewhat works, handled by the [[AquaBuild|Aqua port]]).

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Tasks==

The main task currently, is to understand and document the various APIs and how they interact with each other. The pieces are there ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], [http://developer.apple.com/carbon/ Carbon] etc.), but more details are needed to understand how they fit together.

TODO:
* cairo implementation of XCanvas (in OOo) lacks function documentation
* quartz implementation of cairo (in Cairo) lacks function documentation (look at other implementations)
* Create visual explanations of the API structure
* port the code, in [http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066]. Work started.

PERFORMANCE:
* OpenOffice.org VCL uses a lot of XOR-based (win32-like, bitmap-oriented) graphics functions. Mac OS X does not have this concept and uses compositing, canvas and layers instead. To get good performance of OOo on Mac OS X, OOo needs to be gotten rid of heavy use of XOR functions
* 32-bit -images: OOo internally uses non-32bit images, whereas Cocoa/Carbon require 32-bit images for native graphics operations. OOo should be converted to use 32-bit images internally.

DOCS:
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-04-22T17:28:03Z

Mox: /* Debugging */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11 and upcoming [[AquaBuild|Native Mac OS X port using Carbon]].

The future rendering framework in OpenOffice.org (OOo) is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a well designed API (easier to port, easier to use) and a more strong isolation of the API from the rest of the OOo (One of the big problems of the current VCL is that also the internals of the VCL are used from many places in the OOo code).

To facilitate easier migration, one of the OOo XCanvas API implementations is based on VCL. This means that once the VCL part of OOo has been ported, also the XCanvas API works for that platform. This approach has made it possible to start the conversion from VCL to XCanvas, even though some of the non-VCL XCanvas implementations are missing.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OpenOffice, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

Currently native (non-VCL) implementations of XCanvas exist only for Windows and Linux.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI-part of things is unsolved. For some ideas, see [http://ooocon-arnes.kiberpipa.org/media/XUL_Gecko_Stephan_Schaefer/slide.pdf XUL presentation at OOoCon 2005]

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas (somewhat works, handled by the [[AquaBuild|Aqua port]]).

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Tasks==

The main task currently, is to understand and document the various APIs and how they interact with each other. The pieces are there ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], [http://developer.apple.com/carbon/ Carbon] etc.), but more details are needed to understand how they fit together.

TODO:
* cairo implementation of XCanvas (in OOo) lacks function documentation
* quartz implementation of cairo (in Cairo) lacks function documentation (look at other implementations)
* Create visual explanations of the API structure
* port the code, in [http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066]. Work started.

PERFORMANCE:
* OpenOffice.org VCL uses a lot of XOR-based (win32-like, bitmap-oriented) graphics functions. Mac OS X does not have this concept and uses compositing, canvas and layers instead. To get good performance of OOo on Mac OS X, OOo needs to be gotten rid of heavy use of XOR functions
* 32-bit -images: OOo internally uses non-32bit images, whereas Cocoa/Carbon require 32-bit images for native graphics operations. OOo should be converted to use 32-bit images internally.

DOCS:
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

User:Mox

2008-02-25T15:00:02Z

Mox:

Stuff I work on:
* [[Mac OS X Porting - User Experience]]
* [[Mac OS X Porting - Canvas]]
* [[Mac OS X Porting - Separate apps (OOoRunner -framework)]]
* [[Mac OS X Porting - Native Audio and Video]]
* [[Mac OS X Porting - Native Spellchecking]]
* [[Mac OS X Porting - Keyboard Shortcuts]]

* [[Mac OS X Porting - Code Documentation]]
* [[Mac OS X Porting - Comparison to Toolkit Ports]]

* Clipboard + image byte re-ordering [https://bugzilla.mozilla.org/attachment.cgi?id=240960 mozilla patch] and [http://hsivonen.iki.fi/kesakoodi/clipboard/ clipboard fun details]

* Including extensions to installation packages - [[Extensions Integration into Installation Set]]

* [[UI Layout]] > [[Platform UI Differences]] ... [[Chrome Again]], hmm???

* People who can create CWSs (the CVS checkbox): [[DomainDeveloper]]

Interested in:
* [[User Experience Community]]

I want to see as much collaboration as possible:
* [[Mac OS X Porting - contributions from NeoOffice]] & history [http://www.openoffice.org/editorial/edp_and_danw.html OOo in 2002]

Read more about this:
* [[Drawing framework]]

Other interesting stuff:
* [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 OOoCon2006/XCanvas]
* [http://wiki.services.openoffice.org/wiki/Category:MacOSX Mac OS X related Wiki pages]
* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]

Wishes:
* Get rid of [http://mydatapages.com/quickdraw.html Quickdraw], or we will have broken application in the near future Mac OS X releases: [http://wiki.mozilla.org/Mac:NPAPI_Drawing_Models Porting Quickdraw to CoreGraphics]

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]

UI Layout

2008-02-25T14:58:00Z

Mox: /* Goals */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction and History==
This page concerns itself with current and possible future UI Layout in OpenOffice.org, meaning the code methods and file formats used to programmatically create the locations, style and contents of Graphical User interface - the buttons, text boxes, toolbars, menus, dialogs etc.

Historically the UI layout has been hard-coded in individual applications (Writer, Impress, Calc etc.). Later this evolved into slightly de-coupled with the creation of [http://gsl.openoffice.org/vcl/ VCL]. While VCL makes porting easier for different platforms, such as Linux (KDE & Gnome) and Mac OS X, it also makes it very hard to get platform specific features and style into the UI. Some of this difficulty was lessened by the introduction (Since march 2003) of [http://people.redhat.com/dcbw/ooo-nwf.html Native Widget Framework], which allows to glue the native widgets (e.g. the blue buttons in Mac OS X) over the OpenOffice.org's default widgets. This is accomplished by copying the look of the native button, while the interaction and the "feel" (how the button behaves) are coming from openoffice.org.

Before Native Widget Framework (pre-2003), OpenOffice.org more or less looked like Windows 95 on all platforms. Between 2004-2006 OpenOffice.org has begun to look more like native application, although purely in the look of widgets. The UI Layout (including menu structures, menu labels, location of widgets etc is all Windows-centric legacy).

==Complementary and Related projects==

The differences between different platforms are tracked in:
* [[Platform UI Differences]]

The possible future UI Layout work is complementary and not overlapping with:
* Graphics Rendering re-work: [[Mac_OS_X_Porting_-_Canvas|OOo Canvas]]
* [[Uno/Effort/Uno_Runtime_Environment|UNO Runtime environment]]
* [http://odftoolkit.openoffice.org/ ODF Toolkit] and
* OOo Runner [[Mac_OS_X_Porting_-_Separate_apps_%28OOoRunner_-framework%29|Separate Apps on Mac OS X]]

==Goals==

Most work in OpenOffice.org (in general) will concentrate on '''platform independent''' OpenOffice.org, meaning that the all the UI and Layout will be the same on different platforms (except the widgets). The reasoning for this is simpler effort, consistency and easy-to-use between different platforms. [http://porting.openoffice.org/servlets/ReadMsg?listName=mac&msgNo=4438 See this mailing].

Parallel to the platform independent effort, a '''platform specific''' effort is suggested. This would work towards taking the most advantage of each platform - similarly as advanced rendering would use DirectX on Windows, OpenGL on Linux and Quartz on Mac OS X, also the advanced UI concepts and widgets could be used on each platform, to create a more powerful office suite, not just the lowest common denominator.

However, to accomplish such feat, much of the underlying architecture and structure would need to be changed. A cross-platform (instead of platform independent) UI framework would have to be created, to make platform-specific modifications easy and possible. One of the sources for inspiration in this area is Mozilla's XUL [http://ooocon-arnes.kiberpipa.org/media/XUL_Gecko_Stephan_Schaefer/slide.pdf XUL in OOo concept test report], [http://www.mozilla.org/projects/xul/ Developer information]

Very ambitious goal, long journey, big rewards.

=== The middle road? ===
There are pieces of OpenOffice.org being worked on, which would allow OOo to be much more "native" to each platform while still keeping some of the UI platform independent, where needed.
* a relatively simple XML layout infrastructure, see [[VCL_UI_Rework]]
* a separated graphics rendering module (hopefully sharing as much code as possible --> Cairo backend), see [[Mac OS X Porting - Canvas]]
* a properly isolated font searching/matching versus font rendering
* Using CSS for styling/theming (similar to Mozilla Firefox)

The advantages of this approach would be: 1) dynamic layout allowing UI to adapt to varying lengths of localized strings, and varying screen sizes, 2) Ability to change the UI layout/style files in plain text and have changes appear while the program is running.

==Tasks==

Research: [[Mac OS X Porting - Comparison to Toolkit Ports]]

==UI Examples and Comparison==
The following lists the typical applications used on various platforms and the comparison screenshots from OpenOffice.org. The aim is to show that while there are similarities in these platform-specific applications, and much of the actual functionality is quite similar, the actual UI (i.e. '''how''' you accomplish those functions) has differences both on surface and in deeper levels.

{| border="0" cellpadding="5" cellspacing="0" align="center"
! style="width:300px;" |   !! style="width:40px;" |   !! style="width:300px;" |  
|-
! style="margin:0" colspan="3" | '''Comparison between OpenOffice.org and platform-specific UI Layouts'''
|-
! valign="top" align="left" | [[Image:Kword-tn.png]]
Kword (development version) on Linux (KDE). 
Note the Photoshop-like toolbar/sidebar on the left. 
[http://mox.fidisk.fi/opensource/UI/kword.png Full view]
|  
! valign="top" align="left" | [[Image:Linuxooo-tn.png]]
OpenOffice.org 2.0 on Linux. [http://mox.fidisk.fi/opensource/UI/linuxooo.png Full view]
|-
! style="color: #FFF" |   !! style="color: #FFF" |   !! style="color: #FFF" |  
|-
! valign="top" align="left" | [[Image:Vistaword-tn.png]]
Latest Microsoft Office on Windows Vista. 
Note the task oriented layout and the merged menu/toolbars (Ribbon UI).
[http://mox.fidisk.fi/opensource/UI/vistaword.png Full view]
|  
! valign="top" align="left" | [[Image:Winooo-tn.png]]
OpenOffice.org 2.0 on all Windows versions. 
[http://mox.fidisk.fi/opensource/UI/winooo.png Full view]
|-
! style="color: #FFF" |   !! style="color: #FFF" |   !! style="color: #FFF" |  
|-
! valign="top" align="left" | [[Image:Macword2008-tn.png]]
Latest Microsoft Office (development version) on Mac OS X. 
Note the layout and the new "modes" that are remarkably different from Windows version. 
[http://mox.fidisk.fi/opensource/UI/macword2008.png Full view]
|  
! valign="top" align="left" | [[Image:Macooo-tn.png]]
OpenOffice.org 2.0 (Aqua development version) on Mac OS X.
[http://mox.fidisk.fi/opensource/UI/macooo.png Full view]
|-
! style="color: #FFF" |   !! style="color: #FFF" |   !! style="color: #FFF" |  
|-
! valign="top" align="left" | [[Image:Pages-tn.png]]
Apple's Pages (part of iWork) on Mac OS X. 
Note the design oriented, very clean layout and the powerful floating "Inspector" -toolbar/toolbox. 
[http://mox.fidisk.fi/opensource/UI/pages.png Full view]
|  
! valign="top" align="left" | [[Image:Macooo-tn.png]]
OpenOffice.org 2.0 (Aqua development version) on Mac OS X.
[http://mox.fidisk.fi/opensource/UI/macooo.png Full view]
|-
|-

|}

[[Category:Porting]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Architecture]]
[[Category:Features]]
[[Category:User Experience]]
[[Category:To-Do]]

File:Vistaoffice-toolbar-tn.png

2008-02-25T14:32:17Z

Mox:

File:Vistaoffice-toolbar-customize-tn.png

2008-02-25T14:32:11Z

Mox:

File:Aqua-toolbar-tn.png

2008-02-25T14:32:05Z

Mox:

File:Aqua-toolbar-customize-tn.png

2008-02-25T14:31:57Z

Mox:

Platform UI Differences

2008-02-25T14:29:18Z

Mox: /* Differences */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
While the [[UI Layout]]-page shows the conceptual differences between the platforms, it is not possible to create good UI by just high-level changes. This page aims to document the differences in details in the UI (and report the status in Ooo).

Since the current OOo is more-or-less carbon copy of Windows XP GUI on '''all''' platforms, this page will not document that GUI at all. Focus is put to the platforms that differ from Windows XP GUI.

==Complementary and Related projects==

The possible future UI Layout work is complementary and not overlapping with:
* [http://indiehig.com/wiki/Main_Page Indie HIG] The Missing manuals on the Mac OS X User Interface
* Graphics Rendering re-work: [[Mac_OS_X_Porting_-_Canvas|OOo Canvas]]
* [[Uno/Effort/Uno_Runtime_Environment|UNO Runtime environment]]
* [http://odftoolkit.openoffice.org/ ODF Toolkit] and
* OOo Runner [[Mac_OS_X_Porting_-_Separate_apps_%28OOoRunner_-framework%29|Separate Apps on Mac OS X]]

==Goals==

Document the differences in Platform specific UIs (e.g. Aqua/Mac OS X, Aero/Vista, Gnome/Linux, KDE/Linux Win32/Windows XP).

Follow the implementation progress with status-tables.

The focus is in stuff expressed in GUI guidelines (e.g. Aqua HIG, Aero xxx, Gnome UI SG,...) and stuff that is ''standard'' or ''preferred'' way of doing things, as exemplified by high quality applications on each platform (e.g. Apple Pages (iWork) on Mac OS X, MS Word (Vista Office), and Abiword on Gnome)

==Differences==

The following lists and documents the differences in the typical applications used on various platforms, compared to OpenOffice.org. The aim is to show that while there are similarities in these platform-specific applications, and much of the actual functionality is quite similar, the actual UI (i.e. '''how''' you accomplish those functions) has differences both on surface and in deeper levels.

Stuff to add (Mac OS X):
* ok/cancel buttons: ok on the right side
* ...

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''Platform specific UI differences'''
|-
! style="width:100px;" |   !! style="background:#59e;width:210px;" | Mac OS X (Aqua) !! style="background:#59e;width:210px;" | Windows Vista (Aero) !! style="background:#59e;width:210px;" | Ubuntu Gnome Linux
|-
! style="background:#abcdef;" colspan="4" | Application Menu
|-
| '''Location''' ''Where the menu is located'' || [[Image:Aqua-menu.png]] System wide menu in the top of the screen. Contents of the menu depend on which is the active window || [[Image:Vistaoffice-menu.png]] '''Vista Office''' (Ribbon UI): Merging of menus and toolbars, resulting in tabbed toolbars. '''Vista''' (Aero): In the top of the application window. || In the top of the application window
|-
| '''Icons''' || [[Image:Aqua-menu-no-icons.png]] No icons in the menu || '''Ribbon:''' No (regular) menus. '''Aero:''' No icons in the menu || typically(?) icons in the menu
|-
| '''Main structure''' ''what are the top-level menu items'' || Apple-button (systemwide), Pages (i.e. the application menu), File, Edit, Insert, Format, Arrange, View, Window, Help. In total: 10 || '''Ribbon/Word:''' Office-button (similar to "File" -menu), Home, Insert, Page Layout, References, Mailings, Review, View. In total: 8. ''Note: Clearly task-oriented structure'' || ???
|-
| '''Preferences''' ''Where the settings are located and what they are called'' || [[Image:Aqua-menu-preferences.png]] '''Preferences...''' in the "'''Application menu'''" e.g. Pages -menu, accessible with CMD-, || '''Options...''' in Tools -menu?? || '''Preferences''' in Edit -menu
|-
! style="background:#abcdef;" colspan="4" | Toolbars
|-
| '''Icons''' ''The default setting'' || [[Image:Aqua-toolbar-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/aqua-toolbar.png full size] 10-15 icons (large: 30x30px) with text underneath || [[Image:Vistaoffice-toolbar-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/vistaoffice-toolbar.png full size] '''Ribbon:''' three sizes. Amounts per tab - ''Main actions:'' 3-11 icons, (large: 35x35px) with text underneath. ''Important actions:'' 3-19 icons, (small: 20x20px) with text on the right side. ''Other actions:'' 0-29 icons, (small: 20x20px) without text. || 10-15 icons (large: 30x30px)? with text underneath
|-
| '''Customization''' ''How the toolbars are customized'' || [[Image:Aqua-toolbar-customize-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/aqua-toolbar-customize.png full size] Main toolbars are customizable through right clicking, selecting '''Customize...''' and then drag-and-dropping. ''Much of the toolbar functionality in'' '''Inspector''' ''-tool instead.'' || [[Image:Vistaoffice-toolbar-customize-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/vistaoffice-toolbar-customize.png full size] '''Ribbon:''' Main toolbars are NOT customizable. The Quicklaunch toolbar is customisable from its toolbar and from "Customize" in ??? > Options -menu. Shows a dialog. || Not editable / occasionally the same style as Mac OS X. ''NOTE: Also in Mozilla applications''
|-
| '''Style''' ''What the toolbar icons/buttons look like'' || '''No surrounding 3D "button" around the icon''', colors used sparingly, as few metaphors as possible. Icons have subtle shadow. || ??? || No button borders, richer colors, icons in 3D perspective
|-
| '''Highlight''' ''What the toolbar icons/buttons look like, when clicked'' || '''No highlight''' ''No visual change in the button'' || '''Light-bulb highlight''' ''buttons look like they are shining'' || Highlights with dark color to show the full button area
|-

! style="background:#abcdef;" colspan="4" | Dialogs (and Sheets)
|-
| '''Customize Toolbar''' ''What kind of UI is used?'' || Opens a '''Sheet''' || Opens a '''Dialog''' || N/A or Opens a '''Sheet'''
|-
! style="background:#abcdef;" colspan="4" | Workflow (Task vs. other)
|-
! style="background:#abcdef;" colspan="4" | Interaction styles
|-
! style="background:#abcdef;" colspan="4" | Design goals
|-
| '''Target users''' ''What kind of people are the applications designing for?'' || Normal people who want to do well designed documents with good layout. '''Not just word processing''' || Word processing for the average Joe, lots of functionality || Usability important, cleaned up UI
|-
| '''Templates''' ''What is the purpose of the templates?'' || To learn/get ideas for good style/design, '''professional quality''' || To have all the templates for all the possible occasions || Get the templates you want from the internet repositories

|-

|}

[[Category:Porting]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Architecture]]
[[Category:Features]]
[[Category:User Experience]]
[[Category:To-Do]]

File:Vistaoffice-menu.png

2008-02-25T14:24:34Z

Mox:

File:Aqua-menu-no-icons.png

2008-02-25T14:23:52Z

Mox:

File:Aqua-menu.png

2008-02-25T14:23:46Z

Mox: