Apache OpenOffice Wiki - User contributions [en]

ReleaseStatus Minutes

2011-04-11T23:29:56Z

Saperski: Undo revision 195941 by Hrithik (Talk)

The various functional groups of OpenOffice.org (Quality Assurance, Development, User Experience, Documentation, Release Engineering, Marketing, Localization, etc.) are represented here.
On every Monday 3pm German time ([http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=2&year=2008&hour=15&min=0&sec=0&p1=307 see here to convert to other time zones]) this meeting will track the status and the detailed schedule of deliveries for the upcoming releases.

The members of this meeting review critical issues and deliverables for the releases and agree on the appropriate handling of those issues. They coordinate the actual release schedule.

== Agenda for next meeting ==

=== Review OOo 3.4 release status ===

*...

=== Review OOo 3.4 issues ===

*In general we currently have about [http://openoffice.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=regression&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=regressions&query_based_on=regressions&columnlist=priority%2Cassigned_to%2Cbug_status%2Cresolution%2Cop_sys%2Cvotes%2Cshort_desc&field0-0-0=noop&type0-0-0=noop&value0-0-0= 10] open regression issues and around [http://openoffice.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&target_milestone=OOo+3.4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=P2+usability%2C+accessibility&query_based_on=P2+usability%2C+accessibility&field0-0-0=noop&type0-0-0=noop&value0-0-0= 110] issues overal on target "3.4". <br>''(''[http://blogs.sun.com/ratte/entry/some_changes_for_the_openoffice ''which are still too much release relevant issues'']'')''

=== General topics ===
* none

==== Issue queries and release schedule ====
* Meta Issues: {{Bug|117745}} for 3.4 final version
* [http://openoffice.org/bugzilla/showdependencytree.cgi?id=117745&hide_resolved=1 Dependency list for 3.4 final issues]
* [http://openoffice.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&target_milestone=OOo+3.4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=P2+usability%2C+accessibility&query_based_on=P2+usability%2C+accessibility&field0-0-0=noop&type0-0-0=noop&value0-0-0= Issues with generic target 3.4]
* [[OOoRelease34 | Release Schedule for OOo 3.4]]

== 2011-04-11 ==
Participants: Kai Ahrens, Stefan Baltzer, Rafaella Braconi, Oliver Craemer, Martin Damboldt, Helge Delfs, Olaf Felka, Pavel Janik, Kami, Marcus Lange, Marc Neumann, Fridrich Štrba

=== 3.4 Status ===

*DEV300m106 was used for the branch off. Now the development for the 3.4 release will go on with the new OOO340 codeline.
*The announcement for OOo 3.4 Beta is prepared as draft.
*The Beta release is scheduled for tomorrow.
*The 3.4 is in good shape but still there are a couple of issues open that need to be fixed before the final release.
*Nearly all issues that were suggested for a possible OOo 3.3.1 are already fixed in the upcoming 3.4 Beta release.
*Please raise stopper candidates as usual on the releases mailing list. BUT only in case they <u>don't</u> already match the release criteria - e.g. being a regression, data loss, etc. which would obviously need to be fixed on 3.4 target.<br>
*To calm the OOO340 code line down a little, we will switch to longer milestone cycles on the way to the 3.4 release. For now these will be three week cycles as already mentioned at [http://blogs.sun.com/ratte/entry/some_changes_for_the_openoffice http://blogs.sun.com/ratte/entry/some_changes_for_the_openoffice]. So in case you are addressing further 3.4 issues and you are eager to get early feedback from submitter of an issue or whom ever, please use the established and well known methods like qa-upload (FTP) to provide separate CWSs / patches for early feedback on fixes.<br>

=== Other items ===
* None

=== RE duties this week ===
DEV300m107 by Vladimir Glazunov (vg)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-04-11_IRC_log|ReleaseStatus Minutes 2011-04-11 IRC log]]

== 2011-04-04 ==
Participants: Kai Ahrens, Stefan Baltzer, Oliver Craemer, Helge Delfs, Olaf Felka,
Pavel Janik, Martin Hollmichel, Kami, Marcus Lange, Marc Neumann,
Fridrich Štrba, Ruediger Timm

=== 3.4 Status ===
* The upcoming DEV300m106 will now be used for the branch off.
* The OOo 3.4 Beta Release is scheduled for this week.

=== Other items ===
* None

=== RE duties this week ===
DEV300m106 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-04-04_IRC_log|ReleaseStatus Minutes 2011-04-04 IRC log]]

== 2011-03-28 ==
Participants: Stefan Baltzer, Oliver Craemer, Martin Damboldt, Helge Delfs, René Engelhard, Olaf Felka, Martin Hollmichel, Pavel Janik, Kami, Uwe Luebbbers, Marc Neumann, Fridrich Štrba, Ruediger Timm

=== 3.4 Status ===
* The release relevant issues are now low enough to do the branch off. So this will be the next step.
* The planned beta release will be done with one of the next milestones in April.

=== Other items ===
* None

=== RE duties this week ===
DEV300m105 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-03-28_IRC_log|ReleaseStatus Minutes 2011-03-28 IRC log]]

== 2011-03-21 ==
Participants: Stefan Baltzer, Oliver Craemer, Martin Damboldt, Helge Delfs, René Engelhard, Olaf Felka, Pavel Janik, Kami, Marcus Lange, Uwe Luebbbers, Marc Neumann, Heiner Rechtien, Fridrich Štrba, Ruediger Timm

=== 3.4 Status ===
* We still have a bit too many open issue that are release relevant, but the decreasing trend is clearly visible:
** 25 with [http://openoffice.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=regression&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&emailassigned_to1=1&emailtype regressions]
** 6 with [http://openoffice.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=data_loss&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&emailassigned_to1=1&emailtype1 data loss]
** 185 with [http://openoffice.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&target_milestone=OOo+3.4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring& overall 3.4 target]
** Next possible branch off date is still scheduled for March, 28th.

=== Other items ===
* The listed issues for a 3.3.1 review are mostly fixed, only 2 are open. The respective CWSs will be integrated into one of the next DEV300 milestones. So it's a good idea to take the next builds for testing these issues.

=== RE duties this week ===
DEV300m104 by Vladimir Glazunov (vg)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-03-21_IRC_log|ReleaseStatus Minutes 2011-03-21 IRC log]]

== 2011-03-14 ==
Participants: Kai Ahrens, Stefan Baltzer, Oliver Craemer, Martin Damboldt, Helge Delfs, Olaf Felka, Pavel Janik, Martin Hollmichel, Kami, Marcus Lange, Uwe Luebbbers, Marc Neumann, Heiner Rechtien, Enoki Shinji, Mechtilde Stehmann, Fridrich Štrba, Ruediger Timm

=== 3.4 Status ===
* None

=== Other items ===
* None

=== RE duties this week ===
DEV300m103 by Oliver Bolte (obo)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-03-14_IRC_log|ReleaseStatus Minutes 2011-03-14 IRC log]]

== 2011-03-07 ==
Participants: Kai Ahrens, Stefan Baltzer, Oliver Craemer, Helge Delfs, Olaf Felka, Pavel Janik, Kami, Marcus Lange, Uwe Luebbbers, Marc Neumann, Heiner Rechtien, Enoki Shinji, Fridrich Štrba

=== 3.4 Status ===
* Regarding the [http://wiki.services.openoffice.org/wiki/OOoRelease34 release schedule] today would be the branch off day. As the number of [http://wiki.services.openoffice.org/wiki/OOoRelease34#Release_relevant_issues release relevant issues] is too high we have to shift this date to March, 28th.
* We will see end of March if we need another Alpha version.
* A couple of issues have been raised as candidates for a bugfix release. It was not yet possible to gather all needed data for today's meeting (complexity, efforts, risks of regressions, backporting, etc.). So, we will about them next Monday.

=== 3.3 Status ===
* For the OOo 3.3.0 release we have now 70 languages online with >900 files. This is the biggest release ever.

=== Other items ===
* None

=== RE duties this week ===
DEV300m102 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-03-07_IRC_log|ReleaseStatus Minutes 2011-03-07 IRC log]]

== 2011-02-28 ==
Participants: Kai Ahrens, Stefan Baltzer, Gilles Bignebat, Oliver Craemer, Martin Damboldt, Helge Delfs, Olaf Felka, Pavel Janik, Kami, Marcus Lange, Marc Neumann, Fridrich Štrba, Ruediger Timm

=== 3.4 Status ===
* The queries for the [http://wiki.services.openoffice.org/wiki/OOoRelease34#Release_relevant_issues release relevant issues] were updated to point now to the new issue tracking tool BugZilla.
* The developer snapshot DEV300m101 will be released as Alpha version soon.

=== Other items ===
* The migration of the OpenOffice.org infrastructure to [http://kenai.com/projects/ooo-migration/pages/Home "Project Kenai"] was successfully finished.
* Marcus told that this week the additional OOo 3.3 builds will be released on the mirrors, after the Kenai migration we now can also update the download webpages.

=== RE duties this week ===
DEV300m102 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-02-28_IRC_log|ReleaseStatus Minutes 2011-02-28 IRC log]]

== 2011-02-21 ==
Participants: Kai Ahrens, Stefan Baltzer, Rafaela Braconi, Oliver Craemer, Martin Damboldt, Helge Delfs, René Engelhard, Olaf Felka, Martin Hollmichel, Kami, Uwe Luebbers, Marc Neumann, Heiner Rechtien, Fridrich Štrba

=== 3.4 Status ===
* None

=== Other items ===
* None

=== RE duties this week ===
DEV300m101 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-02-21_IRC_log|ReleaseStatus Minutes 2011-02-21 IRC log]]

== 2011-02-14 ==
Participants: Kai Ahrens, Stefan Baltzer, Rafaela Braconi, Oliver Craemer, Martin Damboldt, Helge Delfs, René Engelhard, Olaf Felka, Martin Hollmichel, Kami, Marcus Lange, Uwe Luebbers, Marc Neumann, Heiner Rechtien, Fridrich Štrba

=== 3.3 Review ===
* Marcus reported that since the OOo 3.3 release from January, 26th we now have 29 languages with released files.
* Rafaella explained the detailed plan how to go on with the remaining files:
** NL teams that haven't released install builds will be included in the automatic process.
** NL teams that have released all or partly builds will be left-out.
** A separate Wiki page with more information will be created and linked on the download webpage.

=== 3.4 Status ===
* The branch off date for [http://wiki.services.openoffice.org/wiki/OOoRelease34 OOo 3.4] was originally scheduled for today but as the release criteria aren't fulfilled yet the branch off had to be deferred until March 7th.
* Therefore we will release a Alpha version which is planned with developer snapshot DEV300m101 next week.
* Milestone DEV300m101 or DEV300m102 (depends on RE and amount of conflicts) will be the last with feature integrations, after this the branch off will take place.

=== Other items ===
* None

=== RE duties this week ===
DEV300m100 by Jens-Heiner Rechtien (hr) <br>
DEV300m101 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-02-14_IRC_log|ReleaseStatus Minutes 2011-02-14 IRC log]]

== 2011-02-07 ==
Participants: Kai Ahrens, Stefan Baltzer, Rafaela Braconi, Oliver Craemer, Martin Damboldt, Helge Delfs, René Engelhard, Shinji Enoki, Olaf Felka, Pavel Janik, Kami, Marcus Lange, Uwe Luebbers, Marc Neumann, Mechtilde Stehmann, Rüdiger Timm

=== 3.3 Status ===
* Marcus reported that since the OOo 3.3 release from January, 26th we have 24 languages with 278 files in "released" status, tomorrow additionally Vietnamese with 14 files.
* Compared with the 3.2.1 release (29 languages with 294 files) this is again a satisfying release.
* Deadline for further releases from the the NLC is February, 10th.
* However, there are still ~700 files in RC status, how to get the remaining files released as stable for download?
* Rafaella suggests to test the files automatically if the builds install.
* As there was a general agreement in the chat, she will post a proposal on the l10n and qa mailing lists.

=== Other items ===
* None

=== RE duties this week ===
DEV300m100 by Jens-Heiner Rechtien (hr)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-02-07_IRC_log|ReleaseStatus Minutes 2011-02-07 IRC log]]

== 2011-01-31 ==
Participants: Kai Ahrens, Stefan Baltzer, Oliver Craemer, Martin Damboldt, Helge Delfs, René Engelhard, Olaf Felka, Kami, Marcus Lange, Uwe Luebbers, Fridrich Štrba

=== 3.3 Status ===
* OOo 3.3 is out and released with press announcement
* currently 14 native lang teams have approved their language builds
* the testing time frame will run until February, 8th

=== Other items ===
* After nomination of some DEV300 CWSs the next milestone build will start later this week

=== RE duties this week ===
DEV300m99 by Vladimir Glazunov (vg)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-01-31_IRC_log|ReleaseStatus Minutes 2011-01-31 IRC log]]

== 2011-01-25 ==
Participants: Rafaella Braconi, Martin Damboldt, René Engelhard, Shinji Enoki, Hirano Kazunari, Heiner Rechtien

=== Review of issues for OOo 3.3.0 if any ===
{{Bug|111112}} for tracking 3.3 Release issues

=== Other items ===
* 3.3 Status
** no new stopper issues were reported until today
** OOo 3.3.0 RC 10 (build OOO330m20) is now declared as OOo 3.3.0 final
** the builds will be distributed through the mirror network
** download webpages will be changed when builds are available
** press announcement is in preparation
** a few NL teams have already sent requests to distribute localized builds
** the other teams have a time frame of 2 weeks for final testing and approval

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-01-25_IRC_log|ReleaseStatus Minutes 2011-01-25 IRC log]]

== 2011-01-24 ==
Participants: Kai Ahrens, Stefan Baltzer, Chris Cheney, Oliver Craemer, Martin Damboldt, Helge Delfs, Shinji Enoki, Olaf Felka, Martin Hollmichel, Pavel Janik, Kami, René Engelhard, Marcus Lange, Marc Neumann, Heiner Rechtien, Mechtilde Stehmann, Fridrich Štrba, Ruediger Timm

=== Review of issues for OOo 3.3.0 if any ===
{{Bug|111112}} for tracking 3.3 Release issues

=== Other items ===
* 3.3 Status
** no new stopper issues were reported until now
** we assume a release GO for the special meeting scheduled tomorrow

=== RE duties this week ===
DEV300m99 by Vladimir Glazunov (vg)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-01-24_IRC_log|ReleaseStatus Minutes 2011-01-24 IRC log]]

== 2011-01-17 ==
Participants: Stefan Baltzer, Chris Cheney, Oliver Craemer, Martin Damboldt, René Engelhard, Shinji Enoki, Olaf Felka, Pavel Janik, Kami, Marcus Lange, Uwe Luebbers, Heiner Rechtien, Fridrich Štrba, Ruediger Timm

=== Review of issues for OOo 3.3.0 if any ===
{{Bug|111112}} for tracking 3.3 Release issues

=== Other items ===
* 3.3 Status
** RC 10 (build OOO330m20) has been started today.
** It's expected to see the first files on the mirrors for end of this week.
** The build will contain the following stoppers which were accepted already last week:
*** {{Bug|116318}} axial gradient has wrong border in presentation mode
*** {{Bug|116371}} PDF-Export: background color of hatching not exported
*** {{Bug|116439}} Content of worksheet disappear when move or copy from one spreadsheet to another
** New stopper candidates will be reviewed very closely if they really meet the criteria.

=== RE duties this week ===
OOO330m20 by Oliver Bolte (obo) <br>
DEV300m98 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-01-17_IRC_log|ReleaseStatus Minutes 2011-01-17 IRC log]]

== 2011-01-10 ==
Participants: Kai Ahrens, Stefan Baltzer, Gilles Bignebat, Chris Cheney, Oliver Craemer, Martin Damboldt, Helge Delfs, René Engelhard, Shinji Enoki, Olaf Felka, Martin Hollmichel, Pavel Janik, Kami, Marcus Lange, Uwe Luebbers, Volker Merschmann, Marc Neumann, Heiner Rechtien, Mechtilde Stehmann, Fridrich Štrba, Ruediger Timm

=== Review of issues for OOo 3.3.0 if any ===
{{Bug|111112}} for tracking 3.3 Release issues

=== Other items ===
* 3.3 Status
** Upload of RC 9 (build OOO330m19) is in progress.
** Currently there are 5 new stopper nominated on the releases@ooo mailing list:
*** {{Bug|108961}} Paper size is ignored while Printing (DL becomes A4)
*** {{Bug|116035}} msvcr90.dll not found, nothing works until manually copied DLL into ooo_path/program
**** This issue was reject as it is occurring on Windows 2000, this OS is too old and already given up by Microsoft.
*** {{Bug|116318}} axial gradient has wrong border in presentation mode
*** {{Bug|116339}} OOo freezes for minutes on slide change
*** {{Bug|116371}} background color of hatching not exported
*** More details are needed to decide if these stoppers are acceptable and if another RC is necessary

=== RE duties this week ===
DEV300m97 by Vladimir Glazunov (vg) <br>
<i> DEV300m98 by Ivo Hinkelmann (ihi) </i>

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-01-10_IRC_log|ReleaseStatus Minutes 2011-01-10 IRC log]]

== 2011-01-03 ==
Participants: Gilles Bignebat, Chris Cheney, Martin Damboldt, Helge Delfs, René Engelhard, Olaf Felka, Pavel Janik, Kami, Marcus Lange, Heiner Rechtien, Mechtilde Stehmann, Ruediger Timm

=== Review of issues for OOo 3.3.0 if any ===
{{Bug|111112}} for tracking 3.3 Release issues

=== Other items ===
* 3.3 Status
** Build of RC 8 (OOO330m18) is available since December last year.
** Currently there are 3 new stopper nominated on the releases@ooo mailing list:
*** {{Bug|110384}} Extremely slow scrolling in calc when charts are displayed
*** {{Bug|115944}} Can't open pptx in Impress
*** {{Bug|116164}} File to show 8192 discontinuities crashes Calc
*** More details are needed to decide if these stoppers are acceptable and if another RC is necessary

=== RE duties this week ===
OOO330m19 by Kurt Zenker (kz) <br>
DEV300m97 by <i> tbd </i>

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[[ReleaseStatus_Minutes_2011-01-03_IRC_log|ReleaseStatus Minutes 2011-01-03 IRC log]]

== Historic Minutes ==
=== [[ReleaseStatus_Minutes_2010_07-12]] ===
=== [[ReleaseStatus_Minutes_2010_01-06]] ===
=== [[ReleaseStatus_Minutes_2009_08-12]] ===
=== [[ReleaseStatus_Minutes_2009_01-07]] ===
=== [[ReleaseStatus_Minutes_2008_05-12]] ===
=== [[ReleaseStatus_Minutes_2008_01-04]] ===
=== [[ReleaseStatus_Minutes_2007_09-12]] ===
=== [[ReleaseStatus_Minutes_2007_05-08]] ===
=== [[ReleaseStatus_Minutes_2007_04]] ===
=== [[ReleaseStatus_Minutes_2007_03]] ===
=== [[ReleaseStatus_Minutes_2007_02]] ===
=== [[ReleaseStatus_Minutes_2007_01]] ===
=== [[ReleaseStatus_Minutes_2006_12]] ===
=== [[ReleaseStatus_Minutes_2006_11]] ===
=== [[ReleaseStatus_Minutes_2006_10]] ===

[[Category:Release Meeting]]
[[Category:Releases]]

Release criteria

2011-04-11T23:29:22Z

Saperski: Undo revision 195942 by Hrithik (Talk)

[[Product Release]]s of OpenOffice.org are downloaded by millions of users, are integrated into complex business solutions and are published by different Linux distributions around the world. Therefore a Release of OOo has to fulfill a lot of requirements. Over the past years many requirements came up and this should be a collection.

= Meaning =
Release Criteria should address the most critical aspects which are important for a Release of [[OpenOffice.org]]. Many areas have to be checked by the [[Release Manager]] or others before a release approval can be given. All items on this page are needed to be fulfilled before a release approval. But it is possible that one or more items are not fulfilled and a release is approved. Then the Release Status Meeting has given the approval.

= Responsibilities =
* The Release Managers and the [http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes Release Status Meeting] approve the general Release of OOo. This means that the English version and the source of OOo is approved. Then there isn't planned any further build for such release. All other languages have to be released on such code base.
* Other languages are approved by the corresponding [http://projects.openoffice.org/native-lang.html Localization teams] (L10N). If this isn't done, a language build will stay in unstable status of a Release Candidate and isn't available via the [http://download.openoffice.org general download link].

= Guidelines/Criteria =
== Quality requirements ==
=== Automated testing [http://quaste.services.openoffice.org QUASTe] ===
* The 'required' tests have to run without any error and warning in the English version (more languages are welcome)
* The 'optional' tests should run without any error and warning in the English version (more languages are welcome)

=== General testing ===
* [http://wiki.services.openoffice.org/wiki/Test_Case_Management TCM] testing should be finalized for one or more languages without any [[Stopper]] issue
* All installation sets are checked generally (MD5 checksums etc. are available)
* There is not any issues in [http://qa.openoffice.org/issues/query.cgi IssueTracker] open for the corresponding release target
* There is not any [[ChildWorkSpace|CWS]] in [http://eis.services.openoffice.org EIS] open for the corresponding release target

=== [[Stopper]] issues ===
* There is not any opened and known <b>Stopper</b> issues for this release
* The last <b>Release Candidate</b> is available for longer than 5 days (including one weekend) and there is not any new announced and approved <b>Stopper</b> in the Releases mailing list (releases @openoffice.org)

== Localization requirements==
===Conditions===
* English is source language and has to be 100% translated in User Interface (UI) and Online Help (Help)
* Translation and the testing of the localized builds has to be finished before the first Release Candidate will be published
* Official installation sets for localized builds will be provided when
** 100% in UI and Help is translated <b>but</b>
** <b>Full install sets</b> for a language can be requested when UI and Help are at least 80% translated
** [[Languagepack | Language packs]] can be requested when only UI is at least 80% translated
** <b>Language packs</b> will be done when full install sets are built, too

===References===
* As reference the percent values from the Pootle servers will be used (see section [https://tools.services.openoffice.org "Translation Pootle Server"]). Depending on the language Pootle or Pootle2 has to be used.
* Information about the [http://wiki.services.openoffice.org/wiki/NLC:ReleaseChecklist Release Process of a localized build] can be found in the Native Language Confederation ([[NLC]]) category.

== Legal requirements ==
* All legal requirements for the product have been cleared (3rd party software etc.)

== Technical requirements ==
* [http://www.collab.net Collab.net] is informed about the release early enough
* Installation sets are linked to the final place for download
* Links are working on the [http://download.openoffice.org general download website]

== Marketing requirements ==
* Release notes are ready
* Websites for the Release are ready and present

[[Category:Releases]]

Product Release

2011-04-11T23:28:38Z

Saperski: Undo revision 195943 by Hrithik (Talk) - vandalism

== Product Releases of OpenOffice.org ==

For release information please see the technical [http://development.openoffice.org/releases/index.html Release Notes] and a detailed [http://www.openoffice.org/dev_docs/features/index.html feature overview].

Released OpenOffice.org versions have passed QA tests. In case that you are missing a recent version for your language or platform, please help the [mailto:dev@qa.openoffice.org QA team] to perform tests those releases.

For a list of uploaded Developer Snapshots and Release Candidates/Releases see the [[Product_Release/builds_uploaded | table of uploaded builds]]. The most recent builds can be downloaded on the [http://download.openoffice.org download webpage].

For guidance on announcing new releases see [[PolicyMirrorLinking]].

<br>

=== Upcoming OpenOffice.org 3.x.x ===

* [[ReleaseSchedule|Release Schedule OOo 3.x.x]]
* [[OOoRelease34|Release Schedule OOo 3.4.0]]

=== Released OpenOffice.org 3.x.x ===

* [[OOoRelease33|OpenOffice.org 3.3.0]] (January 26th, 2011)
* [[OOoRelease321|OpenOffice.org 3.2.1]] (June 4th, 2010)
* [[OOoRelease32|OpenOffice.org 3.2.0]] (February 11th, 2010)
* [[OOoRelease311|OpenOffice.org 3.1.1]] (August 31st, 2009)
* [[OOoRelease31|OpenOffice.org 3.1.0]] (May 7th, 2009)
* [[OOoRelease301|OpenOffice.org 3.0.1]] (January 27th, 2009)
* [[OOoRelease30|OpenOffice.org 3.0.0]] (October 13th, 2008)

=== Released OpenOffice.org 2.x.x ===

* [[OOoRelease243|OpenOffice.org 2.4.3]] (September 04th, 2009)
* [[OOoRelease242|OpenOffice.org 2.4.2]] (October 28th, 2008)
* [[OOoRelease241|OpenOffice.org 2.4.1]] (June 10th, 2008)
* [[OOoRelease24|OpenOffice.org 2.4]] (March 27th, 2008)
* [[OOoRelease231|OpenOffice.org 2.3.1]] (December 4th, 2007)
* [[OOoRelease23|OpenOffice.org 2.3]] (September 17th, 2007)
* [[OOoRelease221|OpenOffice.org 2.2.1]] (June 12th, 2007)
* [[OOoRelease22|OpenOffice.org 2.2]] (March 29th, 2007)
* [[OOoRelease205|OpenOffice.org 2.1]] (December 12th, 2006)
* [[OOoRelease204|OpenOffice.org 2.0.4]] (October 13th, 2006)
* [[OOoRelease203|OpenOffice.org 2.0.3]] (June 29th, 2006)
* [[OOoRelease202|OpenOffice.org 2.0.2]] (March 8th, 2006)
* [[OOoRelease201|OpenOffice.org 2.0.1]] (December 21st, 2005)
* OpenOffice.org 2.0.0 (October 21st, 2005)

=== OpenOffice.org 1.1 ===

* OpenOffice.org 1.1.5 (September 9th, 2005)
* OpenOffice.org 1.1.4 (December 22th, 2004)
* OpenOffice.org 1.1.3 (October 4th, 2004)
* OpenOffice.org 1.1.2 (June 18th, 2004)
* OpenOffice.org 1.1.1
* OpenOffice.org 1.1.0 (October 1st, 2003)

=== OpenOffice.org 1.0 ===

* OpenOffice.org 1.0.3 (April 10th, 2003)
* OpenOffice.org 1.0.2 (January 20th, 2003) (tag "OpenOffice_1_0_2")
* OpenOffice.org 1.0.1 (July 17th, 2002) (tag "OpenOffice_1_0_1")

<br>

Older releases can be retrieved via the [ftp://archive.services.openoffice.org/pub/openoffice-archive/stable Archive Server].

[[Category:Releases]]
[[Category:Quality Assurance]]

LoadICUBreakIterator

2008-05-01T01:39:48Z

Saperski: add discussion links and bugs

=Breaking encapsulation of ICU BreakIterator=

Because of {{Bug|84467}} (duplicate of the {{Bug|81519}}) we are using <code>RuleBasedBreakIterator() constructor</code> and then we want to <code>setBreakType()</code> there.

ICU code:
* [http://www.icu-project.org/apiref/icu4c/classBreakIterator.html BreakIterator] reference
* [http://www.icu-project.org/apiref/icu4c/classRuleBasedBreakIterator.html RuleBasedBreakIterator] reference

OpenOffice.org code:
* [http://l10n.openoffice.org/source/browse/l10n/i18npool/source/breakiterator/breakiterator_unicode.cxx?rev=1.34&view=markup BreakIterator_Unicode::loadICUBreakIterator] function

Mailing list discussions:
* [http://www.nabble.com/Minor-changes-needed-to-ICULanguageBreakFactory-(ICU4C)-td10069414.html Discussion] about [http://bugs.icu-project.org/trac/ticket/5695 ICULanguageBreakFactory]
* [http://www.freebsd.org/cgi/query-pr.cgi?pr=121787 ports/121787] FreeBSD problem report
* [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448745 Debian bug 448745]
* [http://sourceforge.net/mailarchive/forum.php?thread_name=200804301825.10247.mi%2Bicu%40aldan.algebra.com&forum_name=icu-support icu-support]

Example reasons to use custom rules:
* {{Bug|72868|Writer/Impress: line does not break after Chinese punctuation and before Latin letters}}
* {{Bug|80891|character in the forbidden list sometimes appears at the home of line}}
* {{Bug|83229|wrong hyphenation when word does contain a hyphen}}
* {{Bug|83649|Line break should be between typographical quote and left bracket}}
* {{Bug|83464|line brake between letter and $}}
* {{Bug|81448|slash and backslash make non-braking spaces of preceding spaces}}

=Use cases of <code>loadICUBreakIterator</code>=

Questions:
*Why does <code>wordRule</code> need to be static and preserved across the calls?
*Is rulestring <code>word</code> used at all? Other WordTypes?

{|class="wikitable"
!public method
!loadICU call
!resulting rule text
|-
|
nextCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)

prevCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)
|loadICUBreakIterator(rLocale, LOAD_CHARACTER_BREAKITERATOR, 0, "char", Text)
|<code>char</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, ANYWORD_IGNOREWHITESPACES, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, ANYWORD_IGNOREWHITESPACES, NULL, Text)
|<code>edit_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, DICTIONARY_WORD, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, DICTIONARY_WORD, NULL, Text)
|<code>dict_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, WORD_COUNT, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, WORD_COUNT, NULL, Text)
|<code>count_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, another_word_type)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, another_word_type)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, another_word_type, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, another_word_type NULL, Text)
|<code>word</code> '''(???)'''
|-
|
beginOfSentence( const OUString& Text, sal_Int32 nStartPos, rLocale)

endOfSentence( const OUString& Text, sal_Int32 nStartPos,rLocale)
|loadICUBreakIterator(rLocale, LOAD_SENTENCE_BREAKITERATOR, 0, NULL, Text);
|NULL
|-
|
getLineBreak(
const OUString& Text, sal_Int32 nStartPos,
const lang::Locale& rLocale, sal_Int32 nMinBreakPos,
const LineBreakHyphenationOptions& hOptions,
const LineBreakUserOptions& /*rOptions*/ )
|loadICUBreakIterator(rLocale, LOAD_LINE_BREAKITERATOR, 0, "line", Text);
|<code>line</code>
|}

# Figure out if locale BreakIteratorRules (<code>{edit_word, dict_word, count_word, char, line}</code>) gives something for the requested locale
# If not, try to load ''rule''+<code>_</code> + ''lang'' string anyway.

LoadICUBreakIterator

2008-05-01T00:27:41Z

Saperski: another word type

=Breaking encapsulation of ICU BreakIterator=

Because of {{Bug|84467}}, we are using <code>RuleBasedBreakIterator() constructor</code> and then we want to <code>setBreakType()</code> there.

ICU code:
* [http://www.icu-project.org/apiref/icu4c/classBreakIterator.html BreakIterator] reference
* [http://www.icu-project.org/apiref/icu4c/classRuleBasedBreakIterator.html RuleBasedBreakIterator] reference

OpenOffice.org code:
* [http://l10n.openoffice.org/source/browse/l10n/i18npool/source/breakiterator/breakiterator_unicode.cxx?rev=1.34&view=markup BreakIterator_Unicode::loadICUBreakIterator] function

=Use cases of <code>loadICUBreakIterator</code>=

Questions:
*Why does <code>wordRule</code> need to be static and preserved across the calls?
*Is rulestring <code>word</code> used at all? Other WordTypes?

{|class="wikitable"
!public method
!loadICU call
!resulting rule text
|-
|
nextCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)

prevCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)
|loadICUBreakIterator(rLocale, LOAD_CHARACTER_BREAKITERATOR, 0, "char", Text)
|<code>char</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, ANYWORD_IGNOREWHITESPACES, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, ANYWORD_IGNOREWHITESPACES, NULL, Text)
|<code>edit_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, DICTIONARY_WORD, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, DICTIONARY_WORD, NULL, Text)
|<code>dict_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, WORD_COUNT, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, WORD_COUNT, NULL, Text)
|<code>count_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, another_word_type)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, another_word_type)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, another_word_type, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, another_word_type NULL, Text)
|<code>word</code> '''(???)'''
|-
|
beginOfSentence( const OUString& Text, sal_Int32 nStartPos, rLocale)

endOfSentence( const OUString& Text, sal_Int32 nStartPos,rLocale)
|loadICUBreakIterator(rLocale, LOAD_SENTENCE_BREAKITERATOR, 0, NULL, Text);
|NULL
|-
|
getLineBreak(
const OUString& Text, sal_Int32 nStartPos,
const lang::Locale& rLocale, sal_Int32 nMinBreakPos,
const LineBreakHyphenationOptions& hOptions,
const LineBreakUserOptions& /*rOptions*/ )
|loadICUBreakIterator(rLocale, LOAD_LINE_BREAKITERATOR, 0, "line", Text);
|<code>line</code>
|}

# Figure out if locale BreakIteratorRules (<code>{edit_word, dict_word, count_word, char, line}</code>) gives something for the requested locale
# If not, try to load ''rule''+<code>_</code> + ''lang'' string anyway.

LoadICUBreakIterator

2008-05-01T00:26:51Z

Saperski: add rulestring

=Breaking encapsulation of ICU BreakIterator=

Because of {{Bug|84467}}, we are using <code>RuleBasedBreakIterator() constructor</code> and then we want to <code>setBreakType()</code> there.

ICU code:
* [http://www.icu-project.org/apiref/icu4c/classBreakIterator.html BreakIterator] reference
* [http://www.icu-project.org/apiref/icu4c/classRuleBasedBreakIterator.html RuleBasedBreakIterator] reference

OpenOffice.org code:
* [http://l10n.openoffice.org/source/browse/l10n/i18npool/source/breakiterator/breakiterator_unicode.cxx?rev=1.34&view=markup BreakIterator_Unicode::loadICUBreakIterator] function

=Use cases of <code>loadICUBreakIterator</code>=

Questions:
*Why does <code>wordRule</code> need to be static and preserved across the calls?
*Is rulestring <code>word</code> used at all? Other WordTypes?

{|class="wikitable"
!public method
!loadICU call
!resulting rule text
|-
|
nextCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)

prevCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)
|loadICUBreakIterator(rLocale, LOAD_CHARACTER_BREAKITERATOR, 0, "char", Text)
|<code>char</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, ANYWORD_IGNOREWHITESPACES, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, ANYWORD_IGNOREWHITESPACES, NULL, Text)
|<code>edit_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, DICTIONARY_WORD, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, DICTIONARY_WORD, NULL, Text)
|<code>dict_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, WORD_COUNT, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, WORD_COUNT, NULL, Text)
|<code>count_word</code>
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, another_word_type)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, another_word_type)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, another_word_type, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, WORD_COUNT, NULL, Text)
|<code>word</code> '''(???)'''
|-
|
beginOfSentence( const OUString& Text, sal_Int32 nStartPos, rLocale)

endOfSentence( const OUString& Text, sal_Int32 nStartPos,rLocale)
|loadICUBreakIterator(rLocale, LOAD_SENTENCE_BREAKITERATOR, 0, NULL, Text);
|NULL
|-
|
getLineBreak(
const OUString& Text, sal_Int32 nStartPos,
const lang::Locale& rLocale, sal_Int32 nMinBreakPos,
const LineBreakHyphenationOptions& hOptions,
const LineBreakUserOptions& /*rOptions*/ )
|loadICUBreakIterator(rLocale, LOAD_LINE_BREAKITERATOR, 0, "line", Text);
|<code>line</code>
|}

# Figure out if locale BreakIteratorRules (<code>{edit_word, dict_word, count_word, char, line}</code>) gives something for the requested locale
# If not, try to load ''rule''+<code>_</code> + ''lang'' string anyway.

LoadICUBreakIterator

2008-04-30T23:59:14Z

Saperski: tab

=Breaking encapsulation of ICU BreakIterator=

Because of {{Bug|84467}}, we are using <code>RuleBasedBreakIterator() constructor</code> and then we want to <code>setBreakType()</code> there.

ICU code:
* [http://www.icu-project.org/apiref/icu4c/classBreakIterator.html BreakIterator] reference
* [http://www.icu-project.org/apiref/icu4c/classRuleBasedBreakIterator.html RuleBasedBreakIterator] reference

OpenOffice.org code:
* [http://l10n.openoffice.org/source/browse/l10n/i18npool/source/breakiterator/breakiterator_unicode.cxx?rev=1.34&view=markup BreakIterator_Unicode::loadICUBreakIterator] function

=Use cases of <code>loadICUBreakIterator</code>=

{|class="wikitable"
|
nextCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)

prevCharacters(Text, nStartPos, rLocale,
SKIPCELL, sal_Int32 nCount, nDone)
|loadICUBreakIterator(rLocale, LOAD_CHARACTER_BREAKITERATOR, 0, "char", Text)
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, ANYWORD_IGNOREWHITESPACES)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, ANYWORD_IGNOREWHITESPACES, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, ANYWORD_IGNOREWHITESPACES, NULL, Text)
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, DICTIONARY_WORD)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, DICTIONARY_WORD, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, DICTIONARY_WORD, NULL, Text)
|-
|
nextWord( const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

previousWord(const OUString& Text, sal_Int32 nStartPos,
rLocale, WORD_COUNT)

getWordBoundary( const OUString& Text, sal_Int32 nPos,
rLocale, WORD_COUNT, sal_Bool bDirection)
|loadICUBreakIterator(rLocale, LOAD_WORD_BREAKITERATOR, WORD_COUNT, NULL, Text)
|-
|
beginOfSentence( const OUString& Text, sal_Int32 nStartPos, rLocale)

endOfSentence( const OUString& Text, sal_Int32 nStartPos,rLocale)
|loadICUBreakIterator(rLocale, LOAD_SENTENCE_BREAKITERATOR, 0, NULL, Text);
|-
|
getLineBreak(
const OUString& Text, sal_Int32 nStartPos,
const lang::Locale& rLocale, sal_Int32 nMinBreakPos,
const LineBreakHyphenationOptions& hOptions,
const LineBreakUserOptions& /*rOptions*/ )
|loadICUBreakIterator(rLocale, LOAD_LINE_BREAKITERATOR, 0, "line", Text);
|}

LoadICUBreakIterator

2008-04-30T23:36:20Z

Saperski: Initial page

User talk:Ccornell

2008-04-29T20:22:12Z

Saperski: /* SVG support on a Wiki */ thanks

Hello,

I tried to setup the menu structure for the [[Documentation/OOoAuthors User Manual/Getting Started/Starting OpenOffice.org|second chapter]]. But I seem to run into trouble in that I can't figure out how to get the pages within the chapter to show up in the menu. Could you check to see what I'm doing wrong?

--[[User:Kirk|Kirk]] 00:45, 18 July 2007 (CEST)

:Nevermind, I seem to have figured it out. --[[User:Kirk|Kirk]] 00:35, 19 July 2007 (CEST)

:: It's a little complex to begin with, but once you see the pattern of how the TOC works, it starts to make sense :-) I made a small change to the template - changed max-width to just width. Internet Explorer is a broken browser, and does not respect CSS standards very well. It doesn't know max-width, so the easy solution is just to use a fixed width for the TOC. --[[User:Ccornell|Ccornell]] 08:41, 19 July 2007 (CEST)

==New Template problem==

I'm having a bit of difficulty getting the revised template to show the next page in a document. Could you have a look at [[Template:Documentation/ImpressFormattingTOC]]? Everything else seems to be working okay, I just can't seem see what I'm missing on that part. --[[User:Kirk|Kirk]] 03:24, 13 December 2007 (CET)

: You have implemented the TOC correctly. When you look at the TOC page itself, you will see it shown as you see it on the link above (the raw TOC, not the TOC as it is shown when included in a content page). The Next and Previous page parts of the TOC will show (in the raw TOC) as <nowiki>[[{{{PrevPage}}}|< Previous Page]]</nowiki> and <nowiki>[[{{{NextPage}}}|Next Page >]]</nowiki> on the TOC page itself - this is because the variables for the Next and Previous pages have not yet been given to the template.
: When the TOC is included in a content page and you pass the Next and Previous variables, the links will be created on the content page. --[[User:Ccornell|Ccornell]] 11:49, 2 January 2008 (CET)

== Syntax Highlighting for the Color Blind ==

Hey,

I couldn't find an appropriate place to bring this up elsewhere, so I decided to contact you. I'm color blind, and I'm having a very hard time reading source code which is syntax-highlighted. I wind up having to select text, and read the selected text, or paste to another program.

The cyan (I think?) syntax color is nearly invisible for me, and entirely unreadable. See for example:

<source lang="cpp">
// 4-parameter template
class RNG_impl : public ::cppu::WeakImplHelper4<
::org::openoffice::sheet::addin::XRNG,
::sheet::XAddIn,
lang::XServiceName,
lang::XServiceInfo >
</source>

:Good point! It is a horrible color for anyone to have to try and read. We need to look at the colors used for the syntax highlighting. Right now it is simply using the defaults. Changing the default colors means editing the CSS for GeSHI - so not too difficult. The old syntax highlighter had some color customizations that I can refer to as a place to start.
:The best place to discuss this is on the dev@website.openoffice.org mailing list. I will post updates and information there. --[[User:Ccornell|Ccornell]] 20:44, 25 March 2008 (CET)

== SVG support on a Wiki ==

I would like to upload two rather large SVG graphs. Currently I have put them online as [[Image:Module dependency graph without external.odg‎]]
and [[Image:Module dependency graph.odg‎]].
First, this Wiki does not support SVG upload. Second, are there any extensions to display them conveniently? (Something like [http://meta.wikimedia.org/wiki/SVG_image_support] and [http://meta.wikimedia.org/wiki/Inline_SVG_extension]).  « <span style="font-family: monospace, courier; font-size:90%">[[User:Saperski|Saperski]]<span style="font-size: 70%"> // </span>[[User talk:Saperski|@talk]]</span> »  03:14, 29 April 2008 (CEST)
: I added SVG to the image whitelist, so you should be able to upload SVG images now.
: There are issues with using SVG as a display image... mainly because people still using IE will need to install an extension to view them. The rest of us who use real browsers will not have any issues, but sadly... a lot of people still use non-compliant browsers. Adding functionality that requires end-users to install yet another plugin to use/view content is... undesirable.
: It is possible to render the SVG images to PNG so that any browser can display them (eg IE) but this requires additional software (such as Batik) to be installed server side (for example [http://meta.wikimedia.org/wiki/User:Coffman/SVG_Extension Coffman/SVG_Extension]).
: For now, with SVG whitelisted, you can upload SVG images. If you wish to argue a case for SVG rendering, then take it to the dev@website mailing list. If there is consensus/agreement that it's a good thing, then we can take the next step of enabling SVG rendering. --[[User:Ccornell|Ccornell]] 10:10, 29 April 2008 (CEST)
::Thanks, that enough for now. I think we can live with "Error creating thumbnail:" message (see [[:Image:Module_dependency_graph.svg]]).  « <span style="font-family: monospace, courier; font-size:90%">[[User:Saperski|Saperski]]<span style="font-size: 70%"> // </span>[[User talk:Saperski|@talk]]</span> »  22:22, 29 April 2008 (CEST)

File:Module dependency graph.odg

2008-04-29T20:18:44Z

Saperski: SVG

Openoffice.org module dependency graph based on build.lst data of DEV300_m5.
Includes optional and external dependencies.

The SVG version is available as [[:Image:Module dependency graph.svg]].

File:Module dependency graph without external.odg

2008-04-29T20:18:07Z

Saperski: link, don't embed

Openoffice.org module dependency graph based on build.lst data of DEV300_m5.
No optional or external dependencies.

The SVG version is available as [[:Image:Module dependency graph without external.svg]].

File:Module dependency graph without external.odg

2008-04-29T20:17:38Z

Saperski: SVG

Openoffice.org module dependency graph based on build.lst data of DEV300_m5.
No optional or external dependencies.

The SVG version is available as [[Image:Module dependency graph without external.svg]].

File:Module dependency graph without external.odg

2008-04-29T01:25:50Z

Saperski: uploaded a new version of "Image:Module dependency graph without external.odg": Fix page size.

Openoffice.org module dependency graph based on build.lst data of DEV300_m5.
No optional or external dependencies.

User talk:Ccornell

2008-04-29T01:14:43Z

Saperski: New section: SVG support on a Wiki

File:Module dependency graph without external.odg

2008-04-29T01:05:53Z

Saperski: Openoffice.org module dependency graph based on build.lst data of DEV300_m5. No optional or external dependencies.

Openoffice.org module dependency graph based on build.lst data of DEV300_m5.
No optional or external dependencies.

File:Module dependency graph.odg

2008-04-29T01:05:39Z

Saperski: Openoffice.org module dependency graph based on build.lst data of DEV300_m5. Includes optional and external dependencies.

Openoffice.org module dependency graph based on build.lst data of DEV300_m5.
Includes optional and external dependencies.

User:Kr/exit race.c

2008-04-16T00:00:10Z

Saperski: <code> --> <source>

A race between threads and the "exit" call ...

Solaris:
<source lang="bash">
> cc exit_race.c -o exit_race.bin
> ./exit_race.bin
main - tid: 1
foo - tid: 2
bar - tid: 2
main - ad: 1

Linux:
> gcc -g exit_race.c -lpthread
> ./exit_race.bin
main - tid: b7ddbac0
foo - tid: b7ddab90
bar - tid: b7ddab90
main - ad: 1
</source>
<source lang="c">
#include <pthread.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

#ifdef __PRETTY_FUNCTION__
# define PFUN __PRETTY_FUNCTION__
#else
# define PFUN __func__
#endif

static void * foo(void * gr) {
fprintf(stderr, "%s - tid: %x\n", PFUN, pthread_self());
sleep(5);
exit(0);
}

static volatile int ad = 0;

#ifdef __GNUC__
static void bar(void) __attribute__((destructor));
#endif

static void bar(void) {
fprintf(stderr, "%s - tid: %x\n", PFUN, pthread_self());
ad = 1;
sleep(5); // this just stands for some slow de-initialization
}

#ifdef __SUNPRO_C
# pragma fini(bar)
#endif

static pthread_t bt;

static void main_cleanup(void * gr) {
fprintf(stderr, "%s - tid: %x\n", PFUN, pthread_self());
}

int main() {
fprintf(stderr, "%s - tid: %x\n", PFUN, pthread_self());
pthread_create(&bt, NULL, foo, NULL);
while (!ad) ; // Busy wait for ad to change!
fprintf(stderr, "%s - ad: %i\n", PFUN, ad);
pthread_exit(NULL);
}
</source>

User:Saperski

2008-04-11T12:30:37Z

Saperski: My issues

*[http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&issue_status=CLOSED&email1=&emailtype1=exact&emailassigned_to1=1&email2=saperski&emailtype2=exact&emailreporter2=1&emailcc2=1&emaillongdesc2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27%27&Submit+query=Submit+query My issues]

XML Signature support without Mozilla

2008-04-10T02:26:53Z

Saperski: another patch found

This page contains random notes to provide XML DSig support without Mozilla.

We need to use:
* System XmlSec instead of <code>external/libxmlsec</code>. This is now a [http://bonsai.go-oo.org/cvslog.cgi?file=external/libxmlsec/xmlsec1-1.2.6.patch patched] version of [http://www.aleksey.com/xmlsec/download/xmlsec1-1.2.6.tar.gz XmlSec 1.2.6]
* System NSS and NSPR instead of the bundled Mozilla libraries. We need to be careful about shared libraries conflict.

Mozilla (<code>MOZ:moz</code>) is also needed in the <code>dba/connectivity</code> module for addressbook integration.

Do we have with problem sharing databases with Mozilla ([https://bugzilla.mozilla.org/show_bug.cgi?id=217538 Mozilla bug 217538: softoken databases cannot be shared between multiple processes])?

Steps to do:
*Update XmlSec to
** provide <code>xmlSecNssAppliedKeysMngrCreate, xmlSecNssAppliedKeysMngrSymKeyLoad, xmlSecNssAppliedKeysMngrPubKeyLoad xmlSecNssAppliedKeysMngrPriKeyLoad</code>
** Check X.509 certificate verification semantics in (possible API breakage here)
** Verify rest of the patch
** Make sure internal XmlSec tests pass
* Verify that XmlSec is built with NSS support.
* Provide <code>SYSTEM_NSPR, SYSTEM_NSS, SYSTEM_XMLSEC</code> environment variables.
* Modify <code>xml/xmlsecurity</code> module to use system NSS, NSPR and XmlSec library. Preliminary patch:

<source lang="diff">
--- xmlsecurity/util/makefile.mk.orig 2008-04-10 01:46:36.053917594 +0200
+++ xmlsecurity/util/makefile.mk 2008-04-10 01:46:44.443729469 +0200
@@ -47,11 +47,6 @@
.INCLUDE : settings.mk
.INCLUDE : $(PRJ)$/util$/target.pmk

-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity..."
-.ENDIF
-
# --- Files --------------------------------------------------------

BMP_IN=$(PRJ)$/res
--- xmlsecurity/source/xmlsec/nss/makefile.mk.orig 2008-04-10 01:46:58.976404741 +0200
+++ xmlsecurity/source/xmlsec/nss/makefile.mk 2008-04-10 02:20:30.562702818 +0200
@@ -55,11 +55,6 @@

.IF "$(CRYPTO_ENGINE)" == "nss"

-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity/nss"
-.ENDIF
-
.IF "$(SYSTEM_MOZILLA)" != "YES"
MOZ_INC = $(SOLARVERSION)$/$(INPATH)$/inc$(UPDMINOREXT)$/mozilla
NSS_INC = $(MOZ_INC)$/nss
@@ -70,6 +65,20 @@
NSPR_INC = $(MOZ_INC)$/nspr
.ENDIF

+.IF "$(SYSTEM_NSS)" == "YES"
+XMLSEC_INC = /usr/local/include/xmlsec1
+.ELSE
+XMLSEC_INC = $(PRJ)$/source$/xmlsec
+.ENDIF
+
+.IF "$(SYSTEM_NSS)" == "YES"
+NSS_INC = /usr/local/include/nss/nss
+.ENDIF
+
+.IF "$(SYSTEM_NSPR)" == "YES"
+NSPR_INC = /usr/local/include/nspr
+.ENDIF
+
.IF "$(GUI)"=="UNX"
.IF "$(COMNAME)"=="sunpro5"
CFLAGS += -features=tmplife
@@ -121,12 +130,11 @@
SOLARINC += \
-I$(MOZ_INC) \
-I$(NSPR_INC) \
--I$(PRJ)$/source$/xmlsec
+-I$(NSS_INC) \
+-I$(XMLSEC_INC)

.IF "$(SYSTEM_MOZILLA)" == "YES"
-SOLARINC += -DSYSTEM_MOZILLA $(NSS_INC)
-.ELSE
-SOLARINC += -I$(NSS_INC)
+SOLARINC += -DSYSTEM_MOZILLA
.ENDIF

SLOFILES = \
--- xmlsecurity/source/xmlsec/makefile.mk.orig 2008-04-10 01:45:40.800153175 +0200
+++ xmlsecurity/source/xmlsec/makefile.mk 2008-04-10 01:46:02.219673838 +0200
@@ -53,10 +53,6 @@
CDEFS += -DXMLSEC_CRYPTO_MSCRYPTO -DXMLSEC_NO_XSLT
.ELSE
CDEFS += -DXMLSEC_CRYPTO_NSS -DXMLSEC_NO_XSLT
-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity.."
-.ENDIF
.ENDIF

# --- Files --------------------------------------------------------
--- xmlsecurity/prj/build.lst.orig 2008-04-10 01:40:35.017991731 +0200
+++ xmlsecurity/prj/build.lst 2008-04-10 01:40:57.763482421 +0200
@@ -1,4 +1,4 @@
-xs xmlsecurity : xmloff unotools offapi unoil svx MOZ:moz SO:moz_prebuilt LIBXMLSEC:libxmlsec NULL
+xs xmlsecurity : xmloff unotools offapi unoil svx LIBXMLSEC:libxmlsec NULL
xs xmlsecurity usr1 - all xs_mkout NULL
xs xmlsecurity\inc nmake - all xs_inc NULL
xs xmlsecurity\source\framework nmake - all xs_fw xs_inc NULL
</source>

Related:
* {{CWS|systemmozilla|SRC680}}
* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=mozilla&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27%27&Submit+query=Submit+query all isues with mozilla in subject]
* {{Bug|6391|Mozilla 1.0 does not support concurrent multiple versions using same profile (FIXED)}}
* {{Bug|8864|Accessing LDAP or Outlook/Express should not activate Mozilla prefs}}
* {{Bug|65775|update mozilla bootstrap stuff for a recent mozilla API}}
* {{Bug|81295|Adopt Mac OS X crypto API instead of using Mozilla's}}
* [http://go-oo.org/developers/ooo-build/patches/src680/system-xmlsec.diff Patch to use system XmlSec from 2005]

References:
* [http://www.aleksey.com/xmlsec/news.html XmlSec library]
* [http://thread.gmane.org/gmane.text.xml.xmlsec/1572 XmlSec 1.2.8 Release Notes - partial NSS support]

XML Signature support without Mozilla

2008-04-10T02:22:15Z

Saperski: Sharing profile - SQLLite?

This page contains random notes to provide XML DSig support without Mozilla.

We need to use:
* System XmlSec instead of <code>external/libxmlsec</code>. This is now a [http://bonsai.go-oo.org/cvslog.cgi?file=external/libxmlsec/xmlsec1-1.2.6.patch patched] version of [http://www.aleksey.com/xmlsec/download/xmlsec1-1.2.6.tar.gz XmlSec 1.2.6]
* System NSS and NSPR instead of the bundled Mozilla libraries. We need to be careful about shared libraries conflict.

Mozilla (<code>MOZ:moz</code>) is also needed in the <code>dba/connectivity</code> module for addressbook integration.

Do we have with problem sharing databases with Mozilla ([https://bugzilla.mozilla.org/show_bug.cgi?id=217538 Mozilla bug 217538: softoken databases cannot be shared between multiple processes])?

Steps to do:
*Update XmlSec to
** provide <code>xmlSecNssAppliedKeysMngrCreate, xmlSecNssAppliedKeysMngrSymKeyLoad, xmlSecNssAppliedKeysMngrPubKeyLoad xmlSecNssAppliedKeysMngrPriKeyLoad</code>
** Check X.509 certificate verification semantics in (possible API breakage here)
** Verify rest of the patch
** Make sure internal XmlSec tests pass
* Verify that XmlSec is built with NSS support.
* Provide <code>SYSTEM_NSPR, SYSTEM_NSS, SYSTEM_XMLSEC</code> environment variables.
* Modify <code>xml/xmlsecurity</code> module to use system NSS, NSPR and XmlSec library. Preliminary patch:

<source lang="diff">
--- xmlsecurity/util/makefile.mk.orig 2008-04-10 01:46:36.053917594 +0200
+++ xmlsecurity/util/makefile.mk 2008-04-10 01:46:44.443729469 +0200
@@ -47,11 +47,6 @@
.INCLUDE : settings.mk
.INCLUDE : $(PRJ)$/util$/target.pmk

-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity..."
-.ENDIF
-
# --- Files --------------------------------------------------------

BMP_IN=$(PRJ)$/res
--- xmlsecurity/source/xmlsec/nss/makefile.mk.orig 2008-04-10 01:46:58.976404741 +0200
+++ xmlsecurity/source/xmlsec/nss/makefile.mk 2008-04-10 02:20:30.562702818 +0200
@@ -55,11 +55,6 @@

.IF "$(CRYPTO_ENGINE)" == "nss"

-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity/nss"
-.ENDIF
-
.IF "$(SYSTEM_MOZILLA)" != "YES"
MOZ_INC = $(SOLARVERSION)$/$(INPATH)$/inc$(UPDMINOREXT)$/mozilla
NSS_INC = $(MOZ_INC)$/nss
@@ -70,6 +65,20 @@
NSPR_INC = $(MOZ_INC)$/nspr
.ENDIF

+.IF "$(SYSTEM_NSS)" == "YES"
+XMLSEC_INC = /usr/local/include/xmlsec1
+.ELSE
+XMLSEC_INC = $(PRJ)$/source$/xmlsec
+.ENDIF
+
+.IF "$(SYSTEM_NSS)" == "YES"
+NSS_INC = /usr/local/include/nss/nss
+.ENDIF
+
+.IF "$(SYSTEM_NSPR)" == "YES"
+NSPR_INC = /usr/local/include/nspr
+.ENDIF
+
.IF "$(GUI)"=="UNX"
.IF "$(COMNAME)"=="sunpro5"
CFLAGS += -features=tmplife
@@ -121,12 +130,11 @@
SOLARINC += \
-I$(MOZ_INC) \
-I$(NSPR_INC) \
--I$(PRJ)$/source$/xmlsec
+-I$(NSS_INC) \
+-I$(XMLSEC_INC)

.IF "$(SYSTEM_MOZILLA)" == "YES"
-SOLARINC += -DSYSTEM_MOZILLA $(NSS_INC)
-.ELSE
-SOLARINC += -I$(NSS_INC)
+SOLARINC += -DSYSTEM_MOZILLA
.ENDIF

SLOFILES = \
--- xmlsecurity/source/xmlsec/makefile.mk.orig 2008-04-10 01:45:40.800153175 +0200
+++ xmlsecurity/source/xmlsec/makefile.mk 2008-04-10 01:46:02.219673838 +0200
@@ -53,10 +53,6 @@
CDEFS += -DXMLSEC_CRYPTO_MSCRYPTO -DXMLSEC_NO_XSLT
.ELSE
CDEFS += -DXMLSEC_CRYPTO_NSS -DXMLSEC_NO_XSLT
-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity.."
-.ENDIF
.ENDIF

# --- Files --------------------------------------------------------
--- xmlsecurity/prj/build.lst.orig 2008-04-10 01:40:35.017991731 +0200
+++ xmlsecurity/prj/build.lst 2008-04-10 01:40:57.763482421 +0200
@@ -1,4 +1,4 @@
-xs xmlsecurity : xmloff unotools offapi unoil svx MOZ:moz SO:moz_prebuilt LIBXMLSEC:libxmlsec NULL
+xs xmlsecurity : xmloff unotools offapi unoil svx LIBXMLSEC:libxmlsec NULL
xs xmlsecurity usr1 - all xs_mkout NULL
xs xmlsecurity\inc nmake - all xs_inc NULL
xs xmlsecurity\source\framework nmake - all xs_fw xs_inc NULL
</source>

Related:
* {{CWS|systemmozilla|SRC680}}
* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=mozilla&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27%27&Submit+query=Submit+query all isues with mozilla in subject]
* {{Bug|6391|Mozilla 1.0 does not support concurrent multiple versions using same profile (FIXED)}}
* {{Bug|8864|Accessing LDAP or Outlook/Express should not activate Mozilla prefs}}
* {{Bug|65775|update mozilla bootstrap stuff for a recent mozilla API}}
* {{Bug|81295|Adopt Mac OS X crypto API instead of using Mozilla's}}

References:
* [http://www.aleksey.com/xmlsec/news.html XmlSec library]
* [http://thread.gmane.org/gmane.text.xml.xmlsec/1572 XmlSec 1.2.8 Release Notes - partial NSS support]

XML Signature support without Mozilla

2008-04-10T02:02:00Z

Saperski: New small project to improve XML Signature integration

This page contains random notes to provide XML DSig support without Mozilla.

We need to use:
* System XmlSec instead of <code>external/libxmlsec</code>. This is now a [http://bonsai.go-oo.org/cvslog.cgi?file=external/libxmlsec/xmlsec1-1.2.6.patch patched] version of [http://www.aleksey.com/xmlsec/download/xmlsec1-1.2.6.tar.gz XmlSec 1.2.6]
* System NSS and NSPR instead of the bundled Mozilla libraries. We need to be careful about shared libraries conflict.

Mozilla (<code>MOZ:moz</code>) is also needed in the <code>dba/connectivity</code> module for addressbook integration.

Steps to do:
*Update XmlSec to
** provide <code>xmlSecNssAppliedKeysMngrCreate, xmlSecNssAppliedKeysMngrSymKeyLoad, xmlSecNssAppliedKeysMngrPubKeyLoad xmlSecNssAppliedKeysMngrPriKeyLoad</code>
** Check X.509 certificate verification semantics in (possible API breakage here)
** Verify rest of the patch
** Make sure internal XmlSec tests pass
* Verify that XmlSec is built with NSS support.
* Provide <code>SYSTEM_NSPR, SYSTEM_NSS, SYSTEM_XMLSEC</code> environment variables.
* Modify <code>xml/xmlsecurity</code> module to use system NSS, NSPR and XmlSec library. Preliminary patch:

<source lang="diff">
--- xmlsecurity/util/makefile.mk.orig 2008-04-10 01:46:36.053917594 +0200
+++ xmlsecurity/util/makefile.mk 2008-04-10 01:46:44.443729469 +0200
@@ -47,11 +47,6 @@
.INCLUDE : settings.mk
.INCLUDE : $(PRJ)$/util$/target.pmk

-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity..."
-.ENDIF
-
# --- Files --------------------------------------------------------

BMP_IN=$(PRJ)$/res
--- xmlsecurity/source/xmlsec/nss/makefile.mk.orig 2008-04-10 01:46:58.976404741 +0200
+++ xmlsecurity/source/xmlsec/nss/makefile.mk 2008-04-10 02:20:30.562702818 +0200
@@ -55,11 +55,6 @@

.IF "$(CRYPTO_ENGINE)" == "nss"

-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity/nss"
-.ENDIF
-
.IF "$(SYSTEM_MOZILLA)" != "YES"
MOZ_INC = $(SOLARVERSION)$/$(INPATH)$/inc$(UPDMINOREXT)$/mozilla
NSS_INC = $(MOZ_INC)$/nss
@@ -70,6 +65,20 @@
NSPR_INC = $(MOZ_INC)$/nspr
.ENDIF

+.IF "$(SYSTEM_NSS)" == "YES"
+XMLSEC_INC = /usr/local/include/xmlsec1
+.ELSE
+XMLSEC_INC = $(PRJ)$/source$/xmlsec
+.ENDIF
+
+.IF "$(SYSTEM_NSS)" == "YES"
+NSS_INC = /usr/local/include/nss/nss
+.ENDIF
+
+.IF "$(SYSTEM_NSPR)" == "YES"
+NSPR_INC = /usr/local/include/nspr
+.ENDIF
+
.IF "$(GUI)"=="UNX"
.IF "$(COMNAME)"=="sunpro5"
CFLAGS += -features=tmplife
@@ -121,12 +130,11 @@
SOLARINC += \
-I$(MOZ_INC) \
-I$(NSPR_INC) \
--I$(PRJ)$/source$/xmlsec
+-I$(NSS_INC) \
+-I$(XMLSEC_INC)

.IF "$(SYSTEM_MOZILLA)" == "YES"
-SOLARINC += -DSYSTEM_MOZILLA $(NSS_INC)
-.ELSE
-SOLARINC += -I$(NSS_INC)
+SOLARINC += -DSYSTEM_MOZILLA
.ENDIF

SLOFILES = \
--- xmlsecurity/source/xmlsec/makefile.mk.orig 2008-04-10 01:45:40.800153175 +0200
+++ xmlsecurity/source/xmlsec/makefile.mk 2008-04-10 01:46:02.219673838 +0200
@@ -53,10 +53,6 @@
CDEFS += -DXMLSEC_CRYPTO_MSCRYPTO -DXMLSEC_NO_XSLT
.ELSE
CDEFS += -DXMLSEC_CRYPTO_NSS -DXMLSEC_NO_XSLT
-.IF "$(WITH_MOZILLA)" == "NO"
-@all:
- @echo "No mozilla -> no nss -> no libxmlsec -> no xmlsecurity.."
-.ENDIF
.ENDIF

# --- Files --------------------------------------------------------
--- xmlsecurity/prj/build.lst.orig 2008-04-10 01:40:35.017991731 +0200
+++ xmlsecurity/prj/build.lst 2008-04-10 01:40:57.763482421 +0200
@@ -1,4 +1,4 @@
-xs xmlsecurity : xmloff unotools offapi unoil svx MOZ:moz SO:moz_prebuilt LIBXMLSEC:libxmlsec NULL
+xs xmlsecurity : xmloff unotools offapi unoil svx LIBXMLSEC:libxmlsec NULL
xs xmlsecurity usr1 - all xs_mkout NULL
xs xmlsecurity\inc nmake - all xs_inc NULL
xs xmlsecurity\source\framework nmake - all xs_fw xs_inc NULL
</source>

Related:
* {{CWS|systemmozilla|SRC680}}
* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=mozilla&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27%27&Submit+query=Submit+query all isues with mozilla in subject]
* {{Bug|6391|Mozilla 1.0 does not support concurrent multiple versions using same profile (FIXED)}}
* {{Bug|8864|Accessing LDAP or Outlook/Express should not activate Mozilla prefs}}
* {{Bug|65775|update mozilla bootstrap stuff for a recent mozilla API}}
* {{Bug|81295|Adopt Mac OS X crypto API instead of using Mozilla's}}

References:
* [http://www.aleksey.com/xmlsec/news.html XmlSec library]
* [http://thread.gmane.org/gmane.text.xml.xmlsec/1572 XmlSec 1.2.8 Release Notes - partial NSS support]

BuildSpeedup

2008-04-05T00:35:53Z

Saperski: /* How to report build profile logs */ {{Bug}}ify

Make the OO.o build system the coolest on the planet! OpenOffice.org is one of the largest and most interesting open source projects that exists. The target of the BuildSpeedup project is to make the build system the coolest one around. A reliable and fast build system has several direct and indirect impacts, maybe most importantly it is the first thing a new contributor comes across when they pick up the project. Main main target audience is an contributor running a high-mid level desktop. Secondary target is people running build farms (notably Sun). Specification for Jam build prototype [[SpecJamBuild]].

* Simple test harness to figure out the speed of different build tools: [http://wiki.services.openoffice.org/mwiki/images/1/11/Buildtest.tgz Buildtest.tgz]
* Paper on prototype for setting up and building OO.o on large compilation cluster: [http://wiki.services.openoffice.org/wiki/Image:Build_j50.tgz Build_j50.tgz]

== How to report build profile logs ==

Thank you for sending in a build profile log. The more logs we have, the easier it is to focus our effort correctly. Here are the steps to producing a build log:

# Apply the latest patch from {{Bug|60948}} to your source tree
# in the dmake directory type "make clean; make". In the root directory type "./bootstrap"
# When building redirect stderr and stdout to the logfile. In tcsh "build --all |& tee myconfigdesc_build.log" will do the trick. You can alternatively use cat instead of tee to speed up the build slightly. You need to build in a single go and in a single process (no parallel building)
# Check that the log contains markers like "s target 1234 foo.obj". If not, then report
# Compress the log with zip/gz
# When you send in your log URL to mailto:kaib@openoffice.org please provide a short description of the build type:
#* Important configure options (like --with-lang=?)
#* OS/compiler/generic hardware description
#* No-change, partial or full build (we are especially looking for full builds)
#* External accelerators like [[wikipedia:ccache|ccache]]

Thank you again for contributing! --[[User:KaiB|KaiB]] 16:25, 25 January 2006 (CET)

== Profile results ==

Here are some initial profile results. These were done on a HP development desktop with 4GB of RAM. Due to various reasons there is a margin of error in all results, but the largest culprits are pretty clear.

=== Full rebuild from scratch ===

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Time spent
! Target type (file extension)
|-
| 33.2%
| C/C++ compilation (obj)
|-
| 27%
| dmake/build.pl (time not attributed to any target)
|-
| 22.0%
| Dependency generation (dpcc)
|-
| 3.7%
| SDK installer (sdkoo_en-US)
|-
| 1.3%
| Unknown, build related (last_target)
|-
| 1.2%
| Linking (dll)
|-
| 1.1%
| OpenOffice.org installer (openoffice_en-US)
|}

Running time: 62296 s targets: 45927 s 73%

As a benchmark, a Mozilla Firefox build corrected for differences in source code size takes about 25% of the OO.o build time.

=== Nothing changed rebuild ===

Basically profiling the build in a non-changed source tree.

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Time spent
! Target type (file extension)
|-
| 54.8%
| SDK installer (sdkoo_en-US)
|-
| 19%
| dmake/build.pl (time not attributed to any target)
|-
| 16.2%
| OpenOffice installer (openoffice_en-US)
|}

Running time: 4209 s targets: 3431 s 81%

== Notes ==

This is a workarea for ideas and notes regarding the speeding up of the build process. --[[User:KaiB|KaiB]] 12:50, 16 January 2006 (CET)

Notes:
* Newest dmake version: cws_src680_dmake43p01)
* solenv/inc define global targets
* potential modules: KaiB: transex3, tools, svx, binfilter - small to huge :)
* helpcontent2 --with-lang=ALL (there are open issues on this already)
* batched compiles
* Interix instead of cygwin
* dependency generation

Existing possibly useful Build Speed related tweaks:
* export nodep=true
* export NO_HIDS=true
* build.pl -P parallel flag
* dmake -P parallel flag and/or MAXPROCESS (cws_src680_dmake43p01 has fixes for some problems there)
* dmake -s flag for less verbose output
* for gcj users targetedaot workspace to ahead of time compile (only) HelpLinker and FCFGMerge java build tools

=== transex3 ===

Started by tackling this small module. Initial full compile time was 137 sec.

== build_profile_analyzer.py ==

(NB. Move this to an attachment once the Wiki accepts .py files)

# Copyright 2006 Google Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# OO.o build profile analyzer. To get the required patches look at:
# http://wiki.services.openoffice.org/wiki/BuildSpeedup
# Author: Kai Backman, kaib@google.com

import os
import re
import sys

def SortProfileTimes(lhs, rhs):
if lhs[1] < rhs[1] : return 1
elif rhs[1] < lhs[1] : return -1
else : return 0

def ProcessLogFile(file_name, target_durations):
# print "Processing file: " + file_name
file = open(file_name)
start_time = 0
end_time = 0

target_start = 0
target_name = ""
line = file.readline()
while line != "" :
tokens = line[:-1].split(" ")
line = file.readline()

if len(tokens) < 2 : continue
if tokens[1] == "build" :
if tokens[0] == "s" :
start_time = int(tokens[2]) * 1000
elif tokens[0] == "e" :
end_time = int(tokens[2]) * 1000
elif tokens[1] == "target" :
if tokens[0] == "s":
target_start = int(tokens[2])
target_name = tokens[3]
elif tokens[0] == "e" and target_name == tokens[3]:
target_duration = int(tokens[2]) - target_start
target_tokens = tokens[3].split(".")
target_class = target_tokens[len(target_tokens) - 1]
if target_durations.has_key(target_class) :
target_durations[target_class] += target_duration
else :
target_durations[target_class] = target_duration
file.close()
return end_time - start_time
return

if __name__ == "__main__":
target_durations = {}
total_time = 0
for file_name in sys.argv[1:] :
total_time += ProcessLogFile(file_name, target_durations)

profile = target_durations.items()
profile.sort(SortProfileTimes)
total_target_time = 0
for target_iter in profile :
target_promille = target_iter[1] * 1000 / total_time
if target_promille > 0 :
print "%6.ds %3.d.%1.d%% %s" % (target_iter[1] / 1000, target_promille/10,
target_promille % 10, target_iter[0])
total_target_time += target_iter[1]
print "Running time: %d s targets: %d s %d%%" % (total_time / 1000, total_target_time / 1000,
total_target_time * 100 / total_time)

[[Category:Development]]

Log Mac Meeting 5 September 2007

2008-04-04T10:54:52Z

Saperski: {{Bug}}, {{CWS}}

Return to Previous meetings page : [[Previous_Mac_Meeting_logs]]

Return to [[Mac_meetings_September_2007|September Meetings]]

[15:02] <PhilippL> meeting ?

[15:02] <jsi_sun> ericb2: issue 77592 ?

[15:02] <IZBot> porting FEATURE STARTED P3 Use of the Mac OS X spell checker {{Bug|77592}}

[15:02] <ericb2> jsi_sun: once mikesic confirmed, I'll set te issue as fixed

[15:03] <ericb2> PhilippL: yes ( /me completely forgot :/ )

[15:03] * shaunmcdonald has totally forgot too

[15:03] <ericb2> Agenda for 6th September 2007 meeting

[15:03] <ericb2> 1. Welcome new devs joining Mac OS X port

[15:03] <jsi_sun> shaunmcdonald: thursday @Barcelona you have enough beer ordered ;-) ?

[15:04] <shaunmcdonald> jsi_sun: I can't afford to buy any beer just now :-(

[15:04] * fipa (n=fipa@88.103.199.209) has joined #ooo_macport

[15:04] * ChanServ gives channel operator status to fipa

[15:07] * ericb2 added a point in the agenda "Adopting Crypto API to OOo Aqua"

[15:07] * ismael_ (n=ismael@247.75.102-84.rev.gaoland.net) has joined #ooo_macport

[15:07] * ChanServ gives channel operator status to ismael_

[15:08] <ericb2> new devs around ?

[15:10] <PhilippL> that's a no i guess

[15:10] <shaunmcdonald> PhilippL: _1

[15:10] <shaunmcdonald> +1

[15:10] <ericb2> For the record, the first part of our IRC meetings is always dedicated for new comers. Be welcome if you want to join us !

[15:10] <ericb2> Ok, next point

[15:10] <ericb2> 2. Latest Cocoa news ( aquavcl03 news )

[15:12] <PhilippL> no big news from me

[15:12] <PhilippL> or hdu

[15:12] <PhilippL> svdem works again.

[15:13] <ericb2> no news from me

[15:13] <PhilippL> next point ?

[15:13] <ericb2> {{CWS|aquavclcarbonfixes}} and other things have eaten a lot of time for me

[15:13] <ericb2> 3. aquavclcarbonfixes integration

[15:14] <ericb2> the cws is now ready for QA

[15:14] <PhilippL> hear hear !

[15:15] <jsi_sun> I will start testing on Thu with {{CWS|macosxspellchecker}} first and then aquavclcarbonfixes

[15:15] <ericb2> jsi_sun: thank you

[15:15] <mav_eric_away> not direct Cocoa related but a native testtool is due to test.

[15:15] * mav_eric_away is now known as mav_eric

[15:15] <mav_eric> when I'm back and german QA for 2.3.0 is done I will focus on this

[15:16] <jsi_sun> mav_eric: You are welcome; we should share experiences in the QA meeting bi-weekly on Monday 11h MESZ

[15:16] <ericb2> mav_eric: issue 81199 should have fixed the Testtool issue with libdtrans

[15:16] <IZBot> utilities DEFECT RESOLVED FIXED P3 testtool: stand alone version AQUA complains about missing libdtransX11680mxp.dylib {{Bug|81199}}

[15:16] <ericb2> mav_eric: and imho, more, because of side effects

[15:16] <ericb2> mav_eric: probably undetected bugs when using basic stuff

[15:16] <mav_eric> jsi_sun: yes. But unfortunately most of the time i forget about qa meeting :-)

[15:17] <jsi_sun> mav_eric: see title of #qa.openoffice.org channel

[15:17] <jsi_sun> mav_eric: http://wiki.services.openoffice.org/wiki/QAAutomationIRCMeetings

[15:17] <jsi_sun> mav_eric: and put it on the agenda

[15:17] <jsi_sun> mav_eric: would be great

[15:18] * ericb2 does not use Google Calendar .. too much Google in my life

[15:18] <mav_eric> jsi_sun: yes. If I come to a first result before 17th of september

[15:18] <ericb2> back to aquavclcarbonfixes cws : the issue about black frame has been removed: the backport does not work as expected, and is
already fixed in aquavcl03

[15:19] <ericb2> another issue about native FilePicker has been added. Thanks to as for the fix and the explanation. Was issue 81231

[15:19] <IZBot> framework DEFECT VERIFIED FIXED P3 System file-picker can't be used {{Bug|81231}}

[15:19] <ericb2> comboboxes, listboxes and some other little but boring things have been fixed too

[15:20] <jsi_sun> ericb2: Has somebody tested loading documents via iDisk?

[15:20] <ericb2> jsi_sun: afaik, no

[15:20] <ericb2> the last remaining issue is about DRag and drop

[15:21] <ericb2> hdu_hh: some infos from Tino ?

[15:21] <mav_eric> jsi_sun: nope

[15:21] <jsi_sun> ericb2: We should try all links (nfs, afp, WebDAV, ...) in the native filepicker... FAIR there was a problem with WebDAV (aka iDisk)

[15:21] <hdu_hh> ericb2: tino wanted to join the chat when I talked to him this morning

[15:21] <ericb2> hdu_hh: ok

[15:22] <ericb2> jsi_sun: is there an existing issue about that ?

[15:22] <jsi_sun> ericb2: No, as I saw it the filepicker was in a CWS which was not ready.... since that time I haven't used it - I use the internal one
for automation

[15:22] <jsi_sun> ericb2: I will test it in the CWS and if it fails I will write an issue

[15:23] * jsi_sun has a Sun in the network to test nfs :-)

[15:23] <ericb2> jsi_sun: ok, thanks. and if everything goes correctly, we can expect to make it work for the beta

[15:23] <jsi_sun> ericb2: yes, I have the "dead line" Barcelona week... so ready for next week of both CWSes

[15:24] <ericb2> once Drag and drop will work, native printing is the last missing feature

[15:24] <ericb2> jsi_sun: beta is after Barcelona

[15:24] <jsi_sun> ericb2: ...and another...

[15:24] <mav_eric> ericb2: and that's not unimportant at all

[15:25] <PhilippL> "native printing" meaning the native print dialog is not the last missing feature by far ;-)

[15:25] <ericb2> PhilippL: the last for beta

[15:25] <ericb2> PhilippL: end user meaning ;-)

[15:25] <mav_eric> PhilippL: native print dialog would be a good beginning

[15:26] <PhilippL> no, a beta should be feature complete.

[15:26] <PhilippL> and without e.g. multiscreen support we are not there yet.

[15:26] <ericb2> PhilippL: I'm not sure it was scheduled for beta

[15:26] <PhilippL> the native print dialog OTOH is an extra feature, that is not part of OOo's feature set yet.

[15:26] <ericb2> PhilippL: yo can believe me this is a brake for adoption / migration

[15:27] <mav_eric> PhilippL: so you mean beta after multiscreen and native print dialogues?

[15:27] <jsi_sun> I want to suggest another issue to get avoid [xml] security from Mozilla. Mac OS X has AFAIK it's own crypto API like Win32 has.
Most of you using it (maybe) in Mail.app. It would be great after having the native spellchecker, native address book also the native crypto API from
Mac OS X like only the Win32 version of OOo is using it in that system.

[15:27] <ericb2> jsi_sun: next point ?

[15:27] <hdu_hh> tino is busy with other stuff and can't join the chat. It looks like the chances for D&D for OOocon are 30..40%

[15:27] <PhilippL> A beta I would call the version we plan to release with 3.0 beta.

[15:27] <jsi_sun> PhilippL: +1

[15:27] <ericb2> PhilippL: I'd suggest the following plan :

[15:27] <PhilippL> There is nothing wrong with providing build that document our progress, but they are not "beta"

[15:28] <ericb2> alpha -> current version + drag and drop

[15:28] <mav_eric> PhilippL is right. A beta normally is feature complete

[15:28] <jsi_sun> ericb2: Ehhhh.... 'development snapshot'

[15:28] * jsi_sun hates "Alpha"

[15:28] <ericb2> jsi_sun: ok, not a problem

[15:29] <PhilippL> at least an alpha has the notion of being incomplete.

[15:29] <jsi_sun> ericb2: 'Barcelona 2007 - development snapshot' :-)

[15:29] <PhilippL> but let's not open that can of worms again :-)

[15:29] <mav_eric> jsi_sun: first talk to AMD if we're allowed to use Barcelona

[15:29] <ericb2> beta -> alpha+ native printing dialog + spell checker + address book + multi screen + (spotlight ) ?

[15:30] <jsi_sun> PhilippL: Yes, what about my suggestion to write an issue for 2.4 about Crypto API?

[15:30] <ericb2> mav_eric: put quotes in the announce "Barcelona"

[15:30] <jsi_sun> mav_eric: we use "Barcelona '07" :-)

[15:30] <PhilippL> jsi_sun: please do. If someone implements it, the more ower to him.

[15:30] <PhilippL> ower = power

[15:30] <jsi_sun> PhilippL: ok

[15:30] <ericb2> jsi_sun: I'd like to finish with point 3 and then, I promise we will talk about crypto API

[15:31] <PhilippL> +1

[15:31] <ericb2> PhilippL: are you ok with alpha, beta proposal ?

[15:32] <PhilippL> I propose to not call anything beta. Let's state that we want to be in sync with the other platforms as of 3.0 beta.

[15:32] <PhilippL> in sync with respect to releases I mean.

[15:33] <shaunmcdonald> jsi_sun: I have seen a problem with webdav when I last checked with the ooo aqua

[15:33] <ericb2> PhilippL: we used alpha and beta because of missing features. Sure we will stop once a more complete QA sill start with
milestones

[15:33] <jsi_sun> shaunmcdonald: Ok. I'll check it in CWS.

[15:33] <ericb2> PhilippL: use such names helps for visibility of our work

[15:33] <PhilippL> We didn't use beta yet and I would advise not to for a while.

[15:34] <PhilippL> such names give the user expectations we cannot fulfill. Like e.g. feature completeness.

[15:34] <ericb2> PhilippL: it's not question of time when we use the names

[15:34] <ericb2> PhilippL: it's really question of (missing) features

[15:35] <PhilippL> no, that's right. And I still propose not to call anything a beta that is not feature complete.

[15:35] <jsi_sun> ericb2: I agree on PhilippL ; no wording with beta; I wouldn't use "Alpha"; It is a snapshot of our work. Nothing more.

[15:35] <shaunmcdonald> jsi_sun: thanks (sorry if I'm late with the discussion, I had phone call)

[15:35] <PhilippL> And nothing less. It's not that bad as it is.

[15:35] <ericb2> @all : ok: no more alpha, beta ?

[15:35] <jsi_sun> PhilippL: +1

[15:36] <mav_eric> ericb2: +1

[15:36] <PhilippL> ericb2: +1

[15:36] <jsi_sun> jsi_sun: 'Developer Snapshot for OOoCon '07'

[15:36] <jsi_sun> ericb2: 'Developer Snapshot for OOoCon '07'

[15:36] <ericb2> PhilippL: what can we answer, then: we expect to provide a version by the 3.0 output ?

[15:36] <PhilippL> also we can say I think that we plan to have beta when the other platforms reach 3.0 beta.

[15:36] <ismael_> PhilippL: when is 3.0 planned?

[15:37] <mav_eric> PhilippL: sounds good

[15:37] <ericb2> PhilippL: the importan point is to all have the same language

[15:37] <jsi_sun> ismael_: AFAIR 03/08

[15:37] <ericb2> PhilippL: then, no more problems I think

[15:37] <shaunmcdonald> Bacelona is the current codename for the build due in the next 2 weeks ;-)

[15:37] <ismael_> jsi_sun: thanks

[15:37] <jsi_sun> ismael_: AFAIR 01/2008 - in that region

[15:37] <jsi_sun> ismael_: see roadmap ;-)

[15:37] <shaunmcdonald> http://porting.openoffice.org/mac/news/2007/20070818top5beforealpha.html

[15:38] <PhilippL> ismael_: http://wiki.services.openoffice.org/wiki/Product_Release#Ongoing_OpenOffice.org_3.0 , that is around march next
year

[15:39] <ismael_> PhilippL: thanks

[15:39] <jsi_sun> ismael_: http://wiki.services.openoffice.org/wiki/OOoRelease30 6th march 2008 FEATURE FREEZE (=Beta)

[15:40] <jsi_sun> Last cws integration for fixes: July 18th, 2008

[15:40] <jsi_sun> Product release: September 2nd, 2008 or OOoCon 2008 mid September ?

[15:40] <jsi_sun> 1 year

[15:41] <jsi_sun> ericb2: anything else?

[15:41] <PhilippL> 6th march, 15:32 :-)

[15:41] <PhilippL> Though I wouldn't treat that as chiseled in stone :-)

[15:41] <ericb2> Next point ?

[15:42] <jsi_sun> PhilippL: ROTFL

[15:42] <ericb2> 4. Adopting Crypto API to OOo Aqua

[15:43] <jsi_sun> copy from above ;-)

[15:43] <PhilippL> Whoever wants to do that should coordinate with MT I think.

[15:44] <jsi_sun> PhilippL: I will ad MT to cc:

[15:44] <PhilippL> BTW: do we have a volunteer for that task ?

[15:49] <ericb2> PhilippL: we can ask on mac@porting for volunteers ?

[15:49] <PhilippL> yes, we should.

[15:50] <PhilippL> next poin t ?

[15:50] <ericb2> jsi_sun: what would be great, is find people describing us *where* and *what* in the code has to be modified, with suggestions
about the design

[15:50] <ericb2> jsi_sun: would save a lot of time

[15:51] <ericb2> jsi_sun: most of the time, people don't help because nobody knows where is the relevant code

[15:51] <PhilippL> ericb2: I'd guess the relevant code would be in xmlsecurity module, but I don't know. MT would.

[15:51] <ericb2> For the record, I know Kevin Hendricks jhelped for the Mac OS X spellchecker integration

[15:52] <PhilippL> cool, I didn't hear from him in a while.

[15:52] <ericb2> he helped even a lot: some advices are gold advices

[15:53] * ericb2 dancing steve balmmer dance : document... document .. document :)

[15:53] <mav_eric> cool. would be great if he could join us again. His work back was amazing

[15:53] <ericb2> mav_eric: I wrote Kevin helped, and I wanted to thank him officially

[15:54] <ericb2> mav_eric: yes, his work was amazing, of course

[15:54] <mav_eric> ericb2: nice

[15:54] <jsi_sun> ericb2: I have written that FEATURE issue 81295 to Malte that he can add the steps to be done

[15:54] <IZBot> framework FEATURE NEW P3 Adopt Mac OS X crypto API instead of using Mozilla's {{Bug|81295}}

[15:54] <ericb2> jsi_sun: thank you very much

[15:56] <ericb2> one more time, I'd like to say if several people are aware, the work complexity is divided, and more. Document as much as
possible is essential, more than the code imho

[15:56] <jsi_sun> ericb2: aquaport is the user we collect such issues?

[15:56] <ericb2> jsi_sun: macport

[15:56] <ericb2> jsi_sun: + aqua keyword

[15:56] <ericb2> once the issue is created

[15:57] <jsi_sun> ericb2: done

[15:57] <jsi_sun> ericb2: I call such documents "project plan" :-)

[15:57] <ericb2> jsi_sun: great

[15:58] <ericb2> Other topics ? ( Misc now )

[15:58] * jsi_sun has to leave now, cul8er

[15:58] * jsi_sun is away: chrrr.......

[15:58] <ericb2> Back to OOoCon2007

[15:59] <ericb2> I have added infos about the "unofficial" Mac porters meeting

[15:59] <ericb2> http://wiki.services.openoffice.org/wiki/OOoCon2007_Specials#Mac_porters

[15:59] <ericb2> *please* complete / help if you attend

[16:00] <ericb2> thanks

[16:00] <ericb2> Apple Expo Paris now : I think everything is ready, PR, logos, etc .. volunteers, seems ok

[16:01] <ericb2> was not easy, though

[16:01] <ericb2> jsi_sun: one last thing

[16:02] <ericb2> jsi_sun: if ever soemthing goes wrong with cws, I'd like to know asap

[16:02] <ericb2> jsi_sun: every day counts

[16:03] <ericb2> Less important, I have to answer an interview for some german press, and I'll probably ask mav_eric / shaunmcdonald to help me

[16:03] <mav_eric> ericb2: feel free to do so.

[16:03] <PhilippL> ericb2: what press ?

[16:04] <shaunmcdonald> ericb2: I'll try, though louis is a lot faster at doing good translations than me

[16:04] <ericb2> PhilippL: some questions about Mac port, who we are, how we work ..etc. Now you understand better why I asked you what
answer ;-)

[16:04] <PhilippL> ericb2: no, I meant whichmagazine ?

[16:04] <ericb2> PhilippL: sorry, I forgot the link

[16:05] <ericb2> other questions, topics in Misc ?

[16:06] <shaunmcdonald> is everyone remembering that the presentation deadline for ooocon2007 is due a week on Friday?

[16:06] <ericb2> Last for me, I'm still working on my presentations for OOocon. (I know I'm late )

[16:07] <shaunmcdonald> ericb2: the deadline was extended

[16:07] <ericb2> shaunmcdonald: indeed : 14th of September

[16:07] <ericb2> shaunmcdonald: uff

[16:07] <ericb2> mav_eric: no problem, I'll do. Thanks for the proposal

[16:07] <shaunmcdonald> ericb2: I'm one of the folk who helped to extend the deadline ;-)

[16:07] <shaunmcdonald> ericb2: I'm one of the folk who helped to extend the deadline ;-)

[16:08] <ericb2> shaunmcdonald: good idea

[16:08] <hdu_hh> shaunmcdonald: thank you very much!

[16:08] <shaunmcdonald> remember the early presentation is aimed at users, and the later presentation is aimed at developers

[16:09] <shaunmcdonald> hdu_hh: ericb2: I might as well do something useful in my time

[16:09] <ericb2> last point for me: I'm invited ( means expenses funded ) to present the MAc O SX port in a french Mac Association ( Grenoble )

[16:09] <ericb2> no date yet, I have to chosse

[16:09] <ericb2> choose

[16:10] <ericb2> Other questions ?

[16:10] <ericb2> I propose next meeting:12th September, same hour, ok ?

[16:10] <PhilippL> +1

[16:11] * jamesmckenzie (n=jamesmck@ip72-211-130-42.tc.ph.cox.net) has left #ooo_macport

[16:11] * jamesmckenzie (n=jamesmck@ip72-211-130-42.tc.ph.cox.net) has joined #ooo_macport

[16:11] * ChanServ gives channel operator status to jamesmckenzie

[16:11] <ericb2> Ok, End of Meeting

[16:11] <shaunmcdonald> ericb2: fine for me

[16:11] <ericb2> the log is available here: http://wiki.services.openoffice.org/wiki/Log_Mac_Meeting_5_September_2007

Infrastructure Problems

2008-04-04T03:56:59Z

Saperski: {{Bug}}ify

== OOo's SourceCast Instance ==

The OOo instance of SourceCast is based on an extremely old version (2.6), the equivalent up-to-date product is 'CollabNet Enterprise Edition'. It is believed that many problems of the current infrastructure are fixed in the latest versions of this (ver 4.0). The use of 'SourceCast' hereinafter referrs to the (patched & older) OOo version of this infrastructure.

SourceCast provided services are typically extremely unresponsive - it typically taking longer to log-into SourceCast than search the entire-web at google.com with some complex search. High latencies are also sporadic - there are unpredictable periods of low & high latency.

=== Scaling issues ===

Under heavy load - such as close to a release - it is common for SourceCast to become almost totally unresponsive & unusable, sometimes for days.

=== Constant re-login ===

For unknown reasons SourceCast login infrastructure [http://qa.openoffice.org/issues/show_bug.cgi?id=34822 requires] that you re-log-in when closing and restarting your browser. It's hard to quantify quite how frequently, but normally for every new bug filed it is necessary to go to the IssueZilla page, log-in, hit back, hit refresh - adding (if you're lucky) 15seconds or so to any bug filing - prolly more. This latency is not present with other bugzilla derived products. Of course, developers Issue access patterns are typically not those of the casual tester, or heavy SourceCast user - they spend an hour or more fixing a bug, then return to mark the bug fixed (sometimes from one of their other desktop machines) - at which point; re-login is forced on them. A persistant, long-lived client-side authentication cookie would remove this problem entirely.

Some people report not being able to reproduce this frequent re-login issue; it is possible the bug relates closely to the end users' network topology, such as NAT gateways etc. Or - as a serious discussion without exaggeration seems to reveal - it's just that a session cookie is used and not a persistent one.

=== CVS ===

CVS is <b>extremely slow </b> ({{Bug|24771}}). This problem is compounded by the OO.o source code being extremely large it is true.
However an order of magnitude slow-down is due to a simple source-cast design bug of having the CVS .rcs files on a different disk to that of the CVS daemon itself - adding untold latency to each NFS file operation.

Access control - the CVS repository was by default constructed in such a way as to deny even those granted access commit writes to large chunks of it. This was coupled to the formal role request/granting process. Similarly the CVS structure itself (split into separate top-level modules per-project) is confusing (not matching the source directory layout), also making it not possible to have a 'familiar' structure, configure / autogen.sh / README / BUILDING etc. in the top-level directory. [ at least without breaking other CVS operations ]. This artefact also makes the real CVS structure (as seen in LXR etc.) hard to navigate & confusingly different.

CVS also has rather a [http://qa.openoffice.org/issues/show_bug.cgi?id=23306 habit] of loosing cvs tags cf. the [[CvsFAQ]]

== Searching ==

There is no ability to search openoffice.org without logging in, there's no good reason for that. More seriously googling doesn't show any results from within the mailing lists! Making them nigh on useless as a resource.

{{Bug|58310}} has been raised to address this issue. The Googlebot web crawler is well behaved, and respects the overly restrictive 'robots.txt' files scattered around the OpenOffice.org website, such as this one: http://tools.openoffice.org/source/browse/tools/www/robots.txt.
<br>
The consequences of a [http://qa.openoffice.org/robots.txt reduced robots.txt] file for [[Infrastructure_Problems#Scaling_issues|scaling issues]] are checked for the qa project starting 2005-11-21.

Hint: as a workaround, for fast and easy mailing list searches and a threaded archive go to mail-archive.com, e.g. http://www.mail-archive.com/dev@openoffice.org/, combined with Google this leads to something like ''site:mail-archive.com/dev@openoffice.org YourSearchTerm'', which works in many cases. Of course there are also others like Gmane and such.

== Projects & roles ==

There is an extremely formal project / role structure built on SourceCast's features in this area, with various roles being requested, and granted via E-mail round-trips. Thankfully this doesn't impact CVS access these days - with broadly unconstrained CVS accounts being the norm.

== IssueZilla ==

This is rather old and nasty compared with the excellent modern Bugzilla releases, that shows in lots of places - file typing, uploads, comment management, well - tens of usability & cleanup features missing. {{Bug|34665}} contains a good sample of such problems.

== Mailing lists ==

It is critical in any new Free software project to attract developers. One way to drive away newbies is to have an unstated rule that anyone who wants to get a reply from a mailing list post needs to add "please CC me I'm not subscribed - and retain this message so the rest of the thread reaches me" in a prominent place in their E-mail. Thus (I imagine) people regularly ask a question on a list, and <i>receive</i> no reply, even if one is written.

Futhermore address munging is a hugely bad idea for busy mailing lists - it is not possible to read all (busy) mailing lists on topics that people are interested in in linear time; hence keeping a thread CC'd to one is important, it allows a quick response - while keeping the mailing list informed. This is not possible with collab-net's Reply-To: mangling - hence discouraging busy people from using or CC'ing the mailing lists.

Also Reply-To: mangling is just a [http://www.unicom.com/pw/reply-to-harmful.html bad idea], cf. Linux Kernel, GNOME et. al's non-invasive, non-munging policies that encourage contributors & build collaboration.

It may be that one reason behind this mangling is to discourage people from replying off-list to people, - that unfortunately stifles community by not building strong inter-personal relationships, (although clearly off-list replies tend to be short, punchy, amusing, and not the norm). Another reason may be that there exist people out there who don't know how to use their mailer's reply-to-all feature.

It is believed that underneath SourceCast uses [http://cr.yp.to/ezmlm.html ezmlm] to handle mail.

== Missing services ==

=== LXR / Bonsai / Tinderbox ===

With 8 million lines of code no-one outside Sun is familiar with, is is essential to have some hard-code code search, change tracking, indexing functionality. Unfortunately SourceCast does not provide this, that makes it way more difficult to collaborate on developing the code.

A central well-maintained Tinderbox server, should be a pre-requisite for any large project with as many complex build issues as OO.o. One is provided at http://go-oo.org/tinderbox/ however.

=== RSS aggregator / 'planet' ===

It's not clear why it is not possible eg. to re-direct .openoffice.org domain names to existing solutions here as elsewhere.

== Additional Links ==
[[SVNMigration|Migration to SVN]]

[[Infrastructure_Requirements]]

[[Infrastructure_Overview]]

[[Category:Website]]

HSQLDB Integration

2008-04-04T03:52:09Z

Saperski: /* Desired Features */ {{Bug}}ify

This is a (more technically orientated) page about the integration of the [[HSQLDB]] engine[http://hsqldb.sourceforge.net/] into [[OpenOffice.org]].

== Things To Do ==
* [[HSQLDB_Localization|localize]] error messages (currently all hard-coded English)
* get rid of the "default_schema=true" parameter?

== OpenOffice.org-specific settings ==
Connection settings which are currently necessary to connect to HSQLDB embedded in an OpenOffice.org database file
* '''storage_key''': unique key which globally identifies the connection/storage
* '''fileaccess_class_name''': Name of the class implementing the file access
* '''default_schema=true''': lets HSQLDB behave as if it doesn't support schemas

== Desired Features ==
* single-file<br/>This would allow to get rid of the temporary files which are currently needed when working on the embedded HSQLDB, and thus remove some performance penalties
[[Category:Development]]
* separation of the "auto increment" from the "primary key" concept. Currently, if you declare a column to be an auto increment column, it inevitable becomes the primary key
* editable views<br/>Currently, if you create a view as simple as <code>SELECT * FROM table</code>, this is not updateable, even if <code>table</code> itself is.<br/>(side note: Hmm, have to check which part OOo plays here - perhaps it's OOo's fault in real?)
* more tolerance when changing column definitions<br/>For non-professional users, it's quite common that a database schema is not defined once and then fixed, but instead evolves over time, as requirements evolve. HSQLDB currently is pretty restrictive in some areas, preventing some of such on-demand adjustments to the database.<br/>For instance, simply (?) changing the length of a column is prohibited as soon as the column is part of a relationship.
* updatable result sets<br/>This would allow updatable views (wouldn't it?)
* column aliases as variables, see {{Bug|66837}}

[[Category:HSQLDB]]

Issue Tracker

2008-04-04T03:50:46Z

Saperski: advert

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

== External links ==

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

== Lifecycle ==

* [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Lifecycle] explains what the Resolved and Status fields mean.
* [http://qa.openoffice.org/issuelinks.html Issue Quick Links] enables you to track a issue and which [[CWS|childworkspace (CWS)]] it belongs to.
* ''FIXED'' means that an issue is resolved in a CWS, but not yet integrated into a master workspace / release build.
* ''VERIFIED'' means that QA has verified the resolution in the CWS, which still isn't integrated into the master at that point.
* ''CLOSED'' means the resolution is integrated in a master build. The release it will be available is indicated by the issue's ''Target milestone'' field. Again, the master build where the resolution is integrated may be obtained through the CWS query available at [http://qa.openoffice.org/issuelinks.html Issue Quick Links].

{{LinkBanner}}

Education Webconcept

2008-04-04T03:48:30Z

Saperski: {{Bug}}ify

'''Return to [[Education Project]]'''
<br><br>
== Education websiteconcept ==
=== Introduction ===

We like to redesign the project page located on [http://education.openoffice.org http://education.openoffice.org]. For a good redesign, we need a good concept. On this site we will create a overview over the work. The concept count four sub categories

* Overall informations
* Style informations (CSS)
* Page Structure (Menu submenu)
* content informations

'''All of this concept is proposal, everyone can help.''' Thats the reason that I write all in the wiki. For discussions about the Concept, please use the mailing list. Please be patiently at the biginning. The webdeveloping team of the education project is new. We need first find a way to a good collaboration. But we are happy to help in this project

Nicolas and Raphael

== Overall informations ==

=== Technical informations ===

''' Server Hosting '''

*Webserver: Collabnet Server without any server side script language (Suport Collabnet SSI?)
*Service Server: SUN Server with PHP/MySQL (not sure I talk about with Stefan (st) from SUN)
*Testserver1: Only a subdirectory on the colabnet server named ''/test/''
*Other testservers: Private testservers from Nicolas and me. I have one with PHP and MySQL Nicolas too.

''' Scripting Languages '''
*For the website: HTML, CSS, JavaScript(DOM)
*For the Service: HTML, CSS, JavaScript(DOM)(if we use it), PHP, MySQL

'''Languages'''
Main language: English
Other languages: French, German

''' Responsability '''

*Quality Sassurance: Raphael
*Outfit: Nicolas
*Grafic part: wooz (?)
*English content: all
*French content: Nicolas, other are welcome.
*German content: Raphael, other are welcome.

'''Note:''' Every site has one ore more responible persons. This persons are entry in the content concept
If we create a service, Nicolas and me (Raphael) are the responsible persons.

== Style informations (CSS) ==
The International Styleguide you can find [[http://www.openoffice.org/styles/ here]]

On this place we put all impornt Style Sheet informations.

== Content Concept ==

This list is not completed. If you have other ideas, pleas add it.

{| border="1" cellpadding="2"
|-
! File Name !! Description !! Responsible
|-
| index.html
| All the important informations about the project. Links to the localized parts, mission statement and main links in english
| WebTeam
|-
| news.html || Important news from the localized education projects, News from OpenOffice.org or FOSS who are important for the education Project
| {{Bug|84860}}
|-
| memberlist.html
| A list about the member of the education project with a profile of the listed persons
| rbircher
|-
| sponsors.html
| On this site we put the sponsors
|
|-
| partners.html
| List of partner. Scools, University etc. who collaborate with us
|
|-
| library.html
| Books, tools, dokumentation, etc.
| WebTeam
|-
| workboard.html
| A site who we put the free work at OOo. Interested Students can find easyer a work on OOo.
| WebTeam
|}

FYI: With WebTeam I mean the Education Webteam.

== Issues for the Redesign ==

{{Bug|84160|General issue for the Site Design}}

== Content (draft ) ==

Proposed by ericb (''' *first level* ONLY''' )

Two parts one on Top , one on bottom

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

1) First (TOP) part of the page :

LEFT PART

3 Big buttons,

Top : for Teachers and Students
Middle : Tools
Bottom : for Developers

CENTER PART

In the center of the page : a nice background representing Education ( some ceremony or something about diplomaes )

On top of the background, the possibility to click for display the same page, (e.g. little flags) localized in fr / de / ... (add other )

RIGHT PART

superposed tabs for :

Top: Last News
Middle: Donate
3rd: Join the project
Bottom: The Team

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

2) Second (Bottom) part of the page :

FULL WIDTH

Top :

Mission of Education project : plain text (the current one )

Middle :

Links for :

Sponsors
Success stories
Contributors blogs
FAQ

Bottom :

Legal mentions, plan of the site .. etc

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

My references are :

1) Apple : http://www.apple.com/ , support http://www.apple.com/support/ but other tabs are interesting

2) Mozilla Europe : http://www.mozilla-europe.org/fr/ and english : http://www.mozilla-europe.org/en/

3) Francophone project : http://fr.openoffice.org Note: the Education entry is an alien, and should be on Education site, not on fr.openoffice.org project.

4) MacGeneration: http://www.macgeneration.com

== design proposals ==

* my first proposal for website (Nicolas)
[[Image:Education-website-design1.jpg|left|thumb|200px|design1]]

[[Category:Education]]

IRC ActionItems

2008-04-04T03:44:50Z

Saperski: {{Bug}}ify

== IRC - Action Items ==
The purpose of this page is to track the Action Items that come out of the L10n IRC meetings as well as their progress.

=== Top L10n Issues ===
{| border="1" cellpadding="2" cellspacing="0" style="background-color: #fafafa; border: 1px #999999 solid; border-collapse: collapse"
|- style="background-color: #cccccc"
! Issue # !! Description !! Owner !! Due Date !! Status !! Notes
|-
| align="center" | {{Bug|83824}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | stalled || align="center" | Petr to contact jordimas
|-
| align="center" | {{Bug|73297}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | solved || align="center" | n/a
|-
| align="center" | {{Bug|82536}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | in progress || align="center" | n/a
|-
| align="center" | {{Bug|63832}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | in progress || align="center" | n/a
|-
| align="center" | {{Bug|82413}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | in progress || align="center" | n/a
|-
| align="center" | {{Bug|82087}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | resolved || align="center" | n/a
|-
| align="center" | {{Bug|64337}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | in progress || align="center" | n/a
|-
| align="center" | {{Bug|84301}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | in progress || align="center" | n/a
|-
| align="center" | {{Bug|82570}} || align="center" | n/a || align="center" | n/a || align="center" | n/a || align="center" | in progress || align="center" | n/a
|-
|}

[[Category:Localization]]

User:Saperski/monobook.js

2008-04-03T12:01:32Z

Saperski: test

alert("Works!")

CWS

2008-04-03T11:55:46Z

Saperski: /* Create a new module */

CWS here is meant as the acronym for ChildWorkSpace. For a lengthier cws explanation see the [http://tools.openoffice.org/servlets/ReadMsg?list=dev&msgNo=5044 introduction] and [http://tools.openoffice.org/#CWS Overview, Tools, Policies]. This text is some really, really bare bones for the quickest, most simple cws usage.

The basic overview here is that a CWS is a CVS branch, tied to a service with a database backend called [[EIS]]. The cws* tooling talks to both the CVS server and (via SOAP) to the [[EIS]] service. It makes maintaining branches more efficient, standardises their use & integrates with QA nicely.

All code that goes into OO.o has to go through a CWS. A CWS is a fairly heavy-weight beast - thus it's well worth aggregating several commits / bug-fixes into one.

NB. Since this 'howto' was written an even quicker way of committing patches to a cws has been created for people who use ooo-build: [http://cvs.gnome.org/viewcvs/ooo-build/bin/cws-commit-patch?view=log bin/cws-commit-patch].

{{LinkBanner}}

== Basic setup / Assumptions ==

It is assumed that you have fixed some bug / created some feature, and you have a live build tree. It is also assumed that you have sourced the ''LinuxIntelEnv.Set.sh'', ''winenv.set'' or ''winenv.set.sh'' script as appropriate, and as a result your shell is set up correctly with various environment variables pointing to the build tree.

It is also assumed that you have an up-stream OOo CVS account with the appropriate commit privileges, and that you have your tunnel setup and running, and the source modules you are working on has the right CVS/Root entries for that account/tunnel. (Not all source modules in the build tree need to have their CVS/Root entries pointing to the tunnel, those that you aren't going to manipulate through the cws tools can be from a tarball, or from anonymous CVS.)

=== cws config file (.cwsrc) ===

You also need to have a CWS configuration file named .cwsrc in your home directory (~/.cwsrc) for any of the cws command-line tools to work. The following is an example of a typical .cwsrc file.

[CWS_CONFIG]
CWS_DB_SERVER_1=https://eis.services.openoffice.org/soap/servlet/rpcrouter
CVS_ID=foouser
CVS_PASSWORD=SDhiod0=s
CVS_SERVER_ROOT=:pserver:foouser@localhost:/cvs

The value for the ''CVS_PASSWORD'' attribute is taken from your ~/.cvspass file once you cvs login through the tunnel.

== Creating the cws ==

You have to think of an imaginative name for your cws; if it's just some general bug fixing thing, people tend to use account-name<index> otherwise some more descriptive name

cwscreate '''-f''' ''DEV300'' ''m16'' ''link01''

NB. the '''-f''' stops cwscreate doing a slow, monstor fresh check-out (you don't want that).

NB. cwscreate in this mode: SOAP only, no CVS access.

You need to have perl SOAP::Lite module installed for cwscreate to work. See [[CPAN install]] page for how to install Perl modules.

== Filling out the details in EIS ==

[http://eis.services.openoffice.org/EIS2/Logon Login] with your OpenOffice.org email address to [[EIS]]. Navigate the DEV300 'new' tree - find your CWS (or better simply look it up under ''Child workspaces'' - ''My CWSs'' or to a full search with the name of your CWS ''Child workspaces'' - ''Search'').

Then click on the underlined link at the top. Fill out the details, as there are:

* '''Owner''', select your account from the list if it's not already prefilled.
* '''QA representative''', check with the project you're working on or ask on the dev@qa mailing list who the proper QA-rep for your CWS would be and select from the list. If no QA-rep is assigned, the CWS shows up under the '''SeekQA''' menu and someone might jump on it. However, it may also stay there for weeks if nobody does, so better communicate with your project. See also how to [[find a QA representative]].
* '''Description''', give a reasonable description of the CWS (not just 'bugfixes').
* '''Release''', the release target, e.g. ''OOo2.3''.
* '''Estimated due date "ready for QA"''', an estimate when you plan to have it ''ready for QA'', in format 2002-11-23. This is to give QA an idea when the CWS will be ready.
* '''Estimated due date''', when the CWS should be ready for integration. Note that the time span between ready-for-QA date and the final due date needs to be communicated with the QA-rep, usually it's sufficient to add 2 more weeks to give time for QA and enter that as the final due date, in format 2002-11-23. This is to give release engineering an idea when a CWS will show up for integration.
* '''Level of impact''', ''One Application'' if working on a specific application's code, ''Two or more applications'' if working on a library used by several applications, ''Whole Office'' if touching code that is used throughout the entire office suite or affects general behavior.

== Setting up the environment ==

Now we created a cws - we need to tell the tooling we're working with this cws; we do:

export CWS_WORK_STAMP=''link01''

On Windows, if using tcsh the equivalent command is:

setenv CWS_WORK_STAMP ''link01''

== Adding tasks ==

The CWS (in order to ever get merged) has to have a number of issues associated with it, describing the bugs fixed in this CWS. The developer should mark these as ''FIXED'' as he commits/tests & QA should mark these bugs ''VERIFIED''. See issue handling in [[CWS#When_you.27re_happy | When you're happy]] further down.

It's also important to get the Milestone correct in the bug. To associate the task with the CWS do:

cwsaddtask ''i24253''

NB. cwsaddtask: SOAP only, no CVS access.

== Adding modules ==

We now need to add some top-level modules to the CWS - the ones that we have changed. This tool essentially just tags cvs twice with a static: CWS_DEV300_LINK01_ANCHOR tag and a cws_dev300_link01 branch tag to commit to. It then updates the module to that branch.

cwsadd -a '''-f''' ''solenv''

This command must be run in the build tree in the top directory, where the modules in question are subdirectories that have been checked out through the tunnel. (Or at least, have been re-rooted to point to your tunnel in case they originally are from ooo-build tarballs.)

NB. here '''-f''' allows you to keep your changes, while doing the tagging on the underlying versions they are based on - incorporating them into the new cws automatically.

NB. cwsadd: SOAP and CVS access.

== Create a new module ==

(Taken from [http://tools.openoffice.org/dev_docs/child_workspace_newmodule.html].)

In case you have to introduce a new module not yet known on the master workspace you have to

* first think hard if a new module is really needed. OOo now has more than 200 modules and things are getting a bit out of hand. Of course, if the new stuff doesn't really fit anywhere than a new module might be the lesser of two evils.
* create that module in cvs.
** note: if you are adding the module under '''external''' project, then creating is a bit more complicated:
::If you checkout from the CVS the ''external module'' (<code>cvs co external</code>) you will get actually the <code>util/external</code>, the directory <code>external</code> from util project's CVS. If you create a new directory, it will be committed into the util project that you do not really want.
::In order to check out the "right" ''external'', you must checkout one of the directories of external project whose name is not identical to a directory in <code>util/external</code>. For instance:
::: <code>cvs co external/libxml2</code>
::You will have to position yourselves besides the <code>libxml2</code> subdirectory (in this case) in the <code>external</code> directory, create a new directory and commit it using <code>cvs add</code>. After that, you can checkout your module and work on it as usual, still remembering that you are working on HEAD.
* get a cvs alias for that module so that it can be checked out by it's name. See the procedure in http://external.openoffice.org/ and additionally example {{Bug|76452}} (assign it to mh).
* check in for this module to cvs HEAD in your CWS. In contrast to all added modules do not work on a cws-branch but toplevel.
* assure inter module dependencies (i.e. [[Hacking#prj/build.lst]] files) are correct. Make sure all modules needing something delivered by the new one are dependent on it. If it is not needed by any module at build time, make it a prerequisite of 'postprocess'.
* when the cws is in QA, announce the new module to Hamburg release engineering. You can do this either by writing something in the CWS description field (to RE: CWS contains new module bla) or by sending an email. This is necessary because new modules do not get tracked by CWS tooling and RE has to manually check them out before doing the integration build on the master workspace.

Additionally it is good practice to provide a short description of your new module in [[Source code directories]] table.

== Committing code ==

Committing requires nothing particular new; the database doesn't track commits. Just commit them to the branched modules you cwsadded.

CVS should add some helpful fields for you & some helpful blurb about what to write here - often it doesn't. The stock format is:

Issue number: #i24253#
Submitted by: mmeeks
Reviewed by: mmeeks
This patch fixes a silly bug in linkoo

== When you're happy ==

Finally - when you've committed everything & built & tested it, you need to hand over the CWS to QA.

The issue handling of issues added to the CWS at this stage is

* Verify all issues assigned to the CWS are really fixed in your CWS build.
* If so, reassign the issue to the QA representative of the CWS.
* Announce new features and enhancements (not mere bug fixes) using the [[feature announcement]] form within EIS.

Having done all that, login back to the CWS page in [[EIS]] and re-edit the details - marking the state to ''Ready for QA''.

Check your changes. If you did some [[Compatible_Builds#What_changes_are_binary_incompatible.3F|binary incompatible change]] mark the corresponding module ''incompatible''.

== What next ? ==

You get to wait until the CWS is [[Approve_a_CWS | approved by your QA representative]] and nominated for integration, then it will be merged into HEAD and released.

The approval procedure may take some time. In the meantime the master workspace may change significantly. If changes got into the master touching the same code lines you have changed integrating your CWS will lead to merge conflicts. [[Resolve Merge Conflicts for CWS Integration]] gives some advice how to prevent problems during integration.

== Updating to a newer milestone ==

The long-term CWSes need a resync to a newer milestone from time to time.

* step1 : prepare the place

mkdir tmp
cd tmp
export CWS_WORK_STAMP=''the_name_of_the_cws''

* step2 : the resync itself

'''Case 1 : for cws created against DEV300_m0 or later'''

cwsresync '''-m m5 all'''
''... resolve possible conflicts ...''
cwsresync '''-c all'''
cwsresync '''-f -l m5'''

'''Case 2 : ATTENTION: If your cws still is based on SRC680, use the following'''
'''export WORK_STAMP=SRC680''' # means the cws was created using SRC680 Master work space, does not exist in DEV300 database
# and the build environment did probably define DEV300 as $WORK_STAMP instead
cwsresync '''-m DEV300:m5 all'''
... resolve possible conflicts ...
cwsresync '''-c all'''
cwsresync [options] '''-f -l DEV300:m5'''

You must start in an empty directory with a correctly set CWS_WORK_STAMP environment variable. First of all, '''-m''' merges files from the CWS (according to CWS_WORK_STAMP) with the specified milestone and protocols all conflicts. '''-c''' then commits the merges to the CVS. NB.: Do it always with <code>cwsresync -c</code>, never by hand! Finally, '''-l''' updates the workspace and the milestone info of the CWS in the database

NB.: Don't forget to create a new & empty directory for this. Really.

NB. '''-f''': Speeds the things up by avoiding unnecessary updates during the third step.

NB. If you know what you are doing, you can resync just the files you have touched - specify the filename instead of '''all''' in '''-m''' and '''-c'''.

-----------
'''See also:''' [[Merge Parts Of A CWS Into Another CWS]]

[[Category:Development]]
[[Category:CWS]]

CWS

2008-04-03T11:51:03Z

Saperski: /* Create a new module */ wiki markup fix

CWS here is meant as the acronym for ChildWorkSpace. For a lengthier cws explanation see the [http://tools.openoffice.org/servlets/ReadMsg?list=dev&msgNo=5044 introduction] and [http://tools.openoffice.org/#CWS Overview, Tools, Policies]. This text is some really, really bare bones for the quickest, most simple cws usage.

The basic overview here is that a CWS is a CVS branch, tied to a service with a database backend called [[EIS]]. The cws* tooling talks to both the CVS server and (via SOAP) to the [[EIS]] service. It makes maintaining branches more efficient, standardises their use & integrates with QA nicely.

All code that goes into OO.o has to go through a CWS. A CWS is a fairly heavy-weight beast - thus it's well worth aggregating several commits / bug-fixes into one.

NB. Since this 'howto' was written an even quicker way of committing patches to a cws has been created for people who use ooo-build: [http://cvs.gnome.org/viewcvs/ooo-build/bin/cws-commit-patch?view=log bin/cws-commit-patch].

{{LinkBanner}}

== Basic setup / Assumptions ==

It is assumed that you have fixed some bug / created some feature, and you have a live build tree. It is also assumed that you have sourced the ''LinuxIntelEnv.Set.sh'', ''winenv.set'' or ''winenv.set.sh'' script as appropriate, and as a result your shell is set up correctly with various environment variables pointing to the build tree.

It is also assumed that you have an up-stream OOo CVS account with the appropriate commit privileges, and that you have your tunnel setup and running, and the source modules you are working on has the right CVS/Root entries for that account/tunnel. (Not all source modules in the build tree need to have their CVS/Root entries pointing to the tunnel, those that you aren't going to manipulate through the cws tools can be from a tarball, or from anonymous CVS.)

=== cws config file (.cwsrc) ===

You also need to have a CWS configuration file named .cwsrc in your home directory (~/.cwsrc) for any of the cws command-line tools to work. The following is an example of a typical .cwsrc file.

[CWS_CONFIG]
CWS_DB_SERVER_1=https://eis.services.openoffice.org/soap/servlet/rpcrouter
CVS_ID=foouser
CVS_PASSWORD=SDhiod0=s
CVS_SERVER_ROOT=:pserver:foouser@localhost:/cvs

The value for the ''CVS_PASSWORD'' attribute is taken from your ~/.cvspass file once you cvs login through the tunnel.

== Creating the cws ==

You have to think of an imaginative name for your cws; if it's just some general bug fixing thing, people tend to use account-name<index> otherwise some more descriptive name

cwscreate '''-f''' ''DEV300'' ''m16'' ''link01''

NB. the '''-f''' stops cwscreate doing a slow, monstor fresh check-out (you don't want that).

NB. cwscreate in this mode: SOAP only, no CVS access.

You need to have perl SOAP::Lite module installed for cwscreate to work. See [[CPAN install]] page for how to install Perl modules.

== Filling out the details in EIS ==

[http://eis.services.openoffice.org/EIS2/Logon Login] with your OpenOffice.org email address to [[EIS]]. Navigate the DEV300 'new' tree - find your CWS (or better simply look it up under ''Child workspaces'' - ''My CWSs'' or to a full search with the name of your CWS ''Child workspaces'' - ''Search'').

Then click on the underlined link at the top. Fill out the details, as there are:

* '''Owner''', select your account from the list if it's not already prefilled.
* '''QA representative''', check with the project you're working on or ask on the dev@qa mailing list who the proper QA-rep for your CWS would be and select from the list. If no QA-rep is assigned, the CWS shows up under the '''SeekQA''' menu and someone might jump on it. However, it may also stay there for weeks if nobody does, so better communicate with your project. See also how to [[find a QA representative]].
* '''Description''', give a reasonable description of the CWS (not just 'bugfixes').
* '''Release''', the release target, e.g. ''OOo2.3''.
* '''Estimated due date "ready for QA"''', an estimate when you plan to have it ''ready for QA'', in format 2002-11-23. This is to give QA an idea when the CWS will be ready.
* '''Estimated due date''', when the CWS should be ready for integration. Note that the time span between ready-for-QA date and the final due date needs to be communicated with the QA-rep, usually it's sufficient to add 2 more weeks to give time for QA and enter that as the final due date, in format 2002-11-23. This is to give release engineering an idea when a CWS will show up for integration.
* '''Level of impact''', ''One Application'' if working on a specific application's code, ''Two or more applications'' if working on a library used by several applications, ''Whole Office'' if touching code that is used throughout the entire office suite or affects general behavior.

== Setting up the environment ==

Now we created a cws - we need to tell the tooling we're working with this cws; we do:

export CWS_WORK_STAMP=''link01''

On Windows, if using tcsh the equivalent command is:

setenv CWS_WORK_STAMP ''link01''

== Adding tasks ==

The CWS (in order to ever get merged) has to have a number of issues associated with it, describing the bugs fixed in this CWS. The developer should mark these as ''FIXED'' as he commits/tests & QA should mark these bugs ''VERIFIED''. See issue handling in [[CWS#When_you.27re_happy | When you're happy]] further down.

It's also important to get the Milestone correct in the bug. To associate the task with the CWS do:

cwsaddtask ''i24253''

NB. cwsaddtask: SOAP only, no CVS access.

== Adding modules ==

We now need to add some top-level modules to the CWS - the ones that we have changed. This tool essentially just tags cvs twice with a static: CWS_DEV300_LINK01_ANCHOR tag and a cws_dev300_link01 branch tag to commit to. It then updates the module to that branch.

cwsadd -a '''-f''' ''solenv''

This command must be run in the build tree in the top directory, where the modules in question are subdirectories that have been checked out through the tunnel. (Or at least, have been re-rooted to point to your tunnel in case they originally are from ooo-build tarballs.)

NB. here '''-f''' allows you to keep your changes, while doing the tagging on the underlying versions they are based on - incorporating them into the new cws automatically.

NB. cwsadd: SOAP and CVS access.

== Create a new module ==

(Taken from [http://tools.openoffice.org/dev_docs/child_workspace_newmodule.html].)

In case you have to introduce a new module not yet known on the master workspace you have to

* first think hard if a new module is really needed. OOo now has more than 200 modules and things are getting a bit out of hand. Of course, if the new stuff doesn't really fit anywhere than a new module might be the lesser of two evils.
* create that module in cvs.
** note: if you are adding the module under '''external''' project, then creating is a bit more complicated:
::If you checkout from the CVS the ''external'' module (<code>cvs co external</code>), you will get actually the <code>util/external</code>, the directory "external" from util project's CVS. If you create a new directory, it will be committed into the util project that you do not really want.
::In order to check out the "right" ''external'', you must checkout one of the directories of external project whose name is not identical to a directory in <code>util/external</code>. For instance, <code>cvs co external/libxml2</code>. You will have to position yourselves besides the libxml2 subdirectory (in this case) in external directory, create a new directory and commit it using <code>cvs add</code>. After that, you can checkout your module and work on it as usual, still remembering that you are working on HEAD.
* get a cvs alias for that module so that it can be checked out by it's name. See the procedure in http://external.openoffice.org/ and additionally example {{Bug|76452}} (assign it to mh).
* check in for this module to cvs HEAD in your CWS. In contrast to all added modules do not work on a cws-branch but toplevel.
* assure inter module dependencies (i.e. [[Hacking#prj/build.lst]] files) are correct. Make sure all modules needing something delivered by the new one are dependent on it. If it is not needed by any module at build time, make it a prerequisite of 'postprocess'.
* when the cws is in QA, announce the new module to Hamburg release engineering. You can do this either by writing something in the CWS description field (to RE: CWS contains new module bla) or by sending an email. This is necessary because new modules do not get tracked by CWS tooling and RE has to manually check them out before doing the integration build on the master workspace.

Additionally it is good practice to provide a short description of your new module in [[Source code directories]] table.

== Committing code ==

Committing requires nothing particular new; the database doesn't track commits. Just commit them to the branched modules you cwsadded.

CVS should add some helpful fields for you & some helpful blurb about what to write here - often it doesn't. The stock format is:

Issue number: #i24253#
Submitted by: mmeeks
Reviewed by: mmeeks
This patch fixes a silly bug in linkoo

== When you're happy ==

Finally - when you've committed everything & built & tested it, you need to hand over the CWS to QA.

The issue handling of issues added to the CWS at this stage is

* Verify all issues assigned to the CWS are really fixed in your CWS build.
* If so, reassign the issue to the QA representative of the CWS.
* Announce new features and enhancements (not mere bug fixes) using the [[feature announcement]] form within EIS.

Having done all that, login back to the CWS page in [[EIS]] and re-edit the details - marking the state to ''Ready for QA''.

Check your changes. If you did some [[Compatible_Builds#What_changes_are_binary_incompatible.3F|binary incompatible change]] mark the corresponding module ''incompatible''.

== What next ? ==

You get to wait until the CWS is [[Approve_a_CWS | approved by your QA representative]] and nominated for integration, then it will be merged into HEAD and released.

The approval procedure may take some time. In the meantime the master workspace may change significantly. If changes got into the master touching the same code lines you have changed integrating your CWS will lead to merge conflicts. [[Resolve Merge Conflicts for CWS Integration]] gives some advice how to prevent problems during integration.

== Updating to a newer milestone ==

The long-term CWSes need a resync to a newer milestone from time to time.

* step1 : prepare the place

mkdir tmp
cd tmp
export CWS_WORK_STAMP=''the_name_of_the_cws''

* step2 : the resync itself

'''Case 1 : for cws created against DEV300_m0 or later'''

cwsresync '''-m m5 all'''
''... resolve possible conflicts ...''
cwsresync '''-c all'''
cwsresync '''-f -l m5'''

'''Case 2 : ATTENTION: If your cws still is based on SRC680, use the following'''
'''export WORK_STAMP=SRC680''' # means the cws was created using SRC680 Master work space, does not exist in DEV300 database
# and the build environment did probably define DEV300 as $WORK_STAMP instead
cwsresync '''-m DEV300:m5 all'''
... resolve possible conflicts ...
cwsresync '''-c all'''
cwsresync [options] '''-f -l DEV300:m5'''

You must start in an empty directory with a correctly set CWS_WORK_STAMP environment variable. First of all, '''-m''' merges files from the CWS (according to CWS_WORK_STAMP) with the specified milestone and protocols all conflicts. '''-c''' then commits the merges to the CVS. NB.: Do it always with <code>cwsresync -c</code>, never by hand! Finally, '''-l''' updates the workspace and the milestone info of the CWS in the database

NB.: Don't forget to create a new & empty directory for this. Really.

NB. '''-f''': Speeds the things up by avoiding unnecessary updates during the third step.

NB. If you know what you are doing, you can resync just the files you have touched - specify the filename instead of '''all''' in '''-m''' and '''-c'''.

-----------
'''See also:''' [[Merge Parts Of A CWS Into Another CWS]]

[[Category:Development]]
[[Category:CWS]]

Main Page

2008-04-03T11:45:49Z

Saperski: /* Going Further */ CWS link

<div style="float:right; padding-left:5px;">
{| style="text-align:left; border:1px solid #aaaaaa; background-color:#f9f9f9;width: 200px;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>
{{Welcome}}

{{Language|Languages}}
|}
</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]]
* [[#Finding general OpenOffice.org user help|User Resources]]
* [[Website]]
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; ">
<b>Get Started from Scratch</b><br />
you most likely need to:
# [[Getting It|Get it]]
# [[Building|Build it]]
# [[Installing|Install it]]
# [[Running|Run it]]
Click for instructions on <br />
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 ==

* [[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 ==
* [[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]]
* [[SCM_Requirements| SCM Requirements]]
* [[SVNMigration| Use SVN instead of CVS]]
* [[SVG_Import_Filter|SVG import]]
* [[Product Release|Product release data]]
* [[Java_and_OpenOffice.org|Java related functionality]]
* [[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;"
|
|-
|
<p style="margin: 0em 0 0 0%; line-height: 1.1">
</p>
| style="font-size: 95%;"|You loaded this Main Page on {{CURRENTDAYNAME}}, {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}} ''T'' {{CURRENTTIME}} '''[[wikipedia:UTC|UTC]]'''.
|-
|style="font-size: 95%;"|
|}
</center>
[[es:Traducci%C3%B3n_al_espa%C3%B1ol]]
[[fr:Page_principale]]

[[it:It.openoffice.org]]
[[ka:%E1%83%9B%E1%83%97%E1%83%90%E1%83%95%E1%83%90%E1%83%A0%E1%83%98_%E1%83%92%E1%83%95%E1%83%94%E1%83%A0%E1%83%93%E1%83%98]]
[[nl:Main_Page/NL]]
[[ru:%D0%93%D0%BB%D0%B0%D0%B2%D0%BD%D0%B0%D1%8F_%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B8%D1%86%D0%B0]]
[[zh:Zh]]

Help:Templates

2008-04-03T10:55:24Z

Saperski: /* Existing Templates */ add {{Bug}}, {{CWS}}, {{M}}, link to templates

Templates serve a number of purposes ranging from the saving of repetitive effort to enabling easy standardization. For information on how to create a new template see [http://meta.wikimedia.org/wiki/Help:Template]. To use a pre-existing Template, just insert the template in the desired location in the following fashion:
<pre>
{{Dummy}}
</pre>

The result will be:

{{Dummy}}

== Existing Templates ==

{| border=1
!Name of Template
!When to use
|----
|{{S|1.1.5}}
|
|----
|{{S|1.5}}
|
|----
|{{S|2.0}}
|
|----
|{{S|Art}}
|Used in connection with the Art Project.
|---
|{{S|Bug}}
|Automatically link to issues
|---
|{{S|CWS}}
|Automatically link to [[CWS|child workspaces]]
|----
|{{S|De.OOo}}
|Used by the German project.
|----
|{{S|Delete}}
|Occasionally files need to be removed. Since most of us can't do that, just use the '''Delete''' template and it will be taken care.
|----
|{{S|Dummy}}
|Used with Marketing Pages. See [[Template talk:Dummy]] for more information.
|----
|{{S|Extensions}}
|Used by the Entensions Project.
|----
|{{S|Français}}
|Used by the Francophone Project.
|----
|{{S|Language}}
|Directs a person to a language appropriate Main Page.
|----
|{{S|ListofProjects}}
|Listing of projects currently on the Wiki
|----
|{{S|M}}
|Automatically link to milestones
|----
|{{S|Marketing}}
|A link listing of Marketing Project Pages
|----
|{{S|NLC}}
|Listing of Native Language Projects
|----
|{{S|NLCListofProjects}}
|A more basic listing of Native Language Projects
|----
|{{Sn|PL:NLC}}
|Polish version of Template:NLC
|----
|{{Sn|PL:NLCListofProjects}}
|Polish version of Template:NLCListofProjects
|----
|{{Sn|PL:legenda}}
|
|----
|{{Sn|PL:st}}
|
|----
|{{Sn|PL:str}}
|
|----
|{{Sn|PL:stw}}
|
|----
|{{S|S}}
|Link to template
|----
|SV
|Namespace for the SV project, subproject of NLC.
|----
|{{Sn|SV:Menu}}
|Main menu for Sv.openoffice.org page and subpages.
|----
|{{S|SVGHEADER}}
|Inserts a right aligned header graphic.
|----
|{{S|SVGTOC}}
|
|----
|{{S|Stub}}
|Use as an invitation to help complete an obviously unfinished page.
|----
|{{S|WikiInstructions}}
|Provides generic instructions that can be somewhat customized for each OpenOffice project on the wiki.
|}

Template:Sn

2008-04-03T10:51:28Z

Saperski: New template for non-Template templates

<includeonly><code><nowiki>{{</nowiki>[[{{{1}}}]]<nowiki>}}</nowiki></code></includeonly><noinclude>
Used to present the template itself (use with full namespace)

{{Sn|Template:S}}

{{Sn|Template:Bug}}

[[Category:Formatting templates|{{PAGENAME}}]]</noinclude>

User:Saperski/myskin.js

2008-04-03T10:41:10Z

Saperski: Editform search replace

// Search box for Mediawiki
// Instrukcja obsługi [[Wikipedia:Narzędzia/Wyszukiwanie i zamiana]]
// Autor: [[:en:User:Zocky]]
// Licencja: GNU General Public License, http://opensource.org/licenses/gpl-license.php
// Wersja tłumaczona skryptu: http://en.wikipedia.org/w/index.php?title=User:Zocky/SearchBox.js&oldid=60000195
// Tłumaczenie i drobne poprawki: Maciej Jaros [[:pl:User:Nux]]

var sr$t; // sr$t=document.editform.wpTextbox1;
var sr$f; // sr$f=document.srForm;
var sr$s; // sr$s=document.srForm.srSearch;
var sr$r; // sr$r=document.srForm.srReplace;
var sr$w; // sr$w=sr$t.style.width;
var sr$i; // sr$i=document.getElementById('SearchIcon');

var sr$lang = {
// '_num_ ocurrences of _str_ replaced' : '$1 ocurrences of $2 replaced.'
'_num_ ocurrences of _str_ replaced' : 'Zmieniono $1 wystapien $2.'
};

/*
Translate also:
var srBoxCode = ...
*/

function srBack()
{
if (sr$s.value=='')
{
sr$t.focus();
return;
}

var searchString = sr$s.value;
if (!sr$f.srRegexp.checked)
searchString = searchString.replace(/([\[\]\{\}\|\.\*\?\$\^\\])/g,'\\$1')
;

searchString="("+searchString+")(?![\\s\\S]*"+searchString+")";
if (sr$f.srCase.checked)
var re=new RegExp(searchString)
else
var re=new RegExp(searchString,"i")
;

var res = re.exec (sr$t.value.substring(0,sr$t.selectionStart));
if (!res)
var res = re.exec (sr$t.value)
;

if (res)
{
sr$t.selectionStart=res.index;
sr$t.selectionEnd=res.index+res[1].length;
}
else
sr$t.selectionStart=sr$t.selectionEnd
;

srSync();
}

function srNext()
{
if (sr$s.value=='')
{
sr$t.focus();
return
}

var searchString = sr$s.value;
if (!sr$f.srRegexp.checked)
searchString=searchString.replace(/([\[\]\{\}\|\.\*\?\$\^\\])/g,'\\$1')
;

if (sr$f.srCase.checked)
var re=new RegExp(searchString,"g")
else
var re=new RegExp(searchString,"gi")
;

re.lastIndex=sr$t.selectionEnd;
var res = re.exec (sr$t.value)
if (!res)
{
re.lastIndex=0;
var res = re.exec (sr$t.value)
}

if (res)
{
sr$t.selectionEnd=res.index+res[0].length;
sr$t.selectionStart=res.index;
}
else
sr$t.selectionStart=sr$t.selectionEnd
;

srSync();
}

function srReplace()
{

var sels=sr$t.selectionStart;
var sele=sr$t.selectionEnd;
var selr=sr$t.value.length-sele;

if (sr$s.value=='' || sels==sele)
{
sr$t.focus();
return;
}

var searchString = sr$s.value;
var replaceString = sr$r.value;
if (!sr$f.srRegexp.checked)
{
searchString=searchString.replace(/([\[\]\{\}\|\.\*\?\$\^\\])/g,'\\$1');
replaceString=replaceString.replace(/([\$\\])/g,'\\$1');
}

if (sr$f.srCase.checked)
var re=new RegExp(searchString,"g")
else
var re=new RegExp(searchString,"gi")
;

re.lastIndex=sels;
var res = re.exec (sr$t.value);
var $$=0;
if (res && res.index==sels && res[0].length==sele-sels)
{
if (sr$f.srRegexp.checked)
{
replaceString=replaceString.replace(/\\\\/g,'&backslash;').replace(/\\\$/g,'&dollar;');
var replaceBits=(" "+replaceString).split(/(?=\$\d)/);
replaceString=replaceBits[0].substring(1);
for (var i=1; i<replaceBits.length; i++)
{
$$=replaceBits[i][1]-'0';
if ($$<res.length)
replaceString += res[$$] + replaceBits[i].substring(2)
else
replaceString += replaceBits[i]
;
}
replaceString=replaceString.replace(/\\n/g,"\n").replace(/&backslash;/g,"\\").replace(/&dollar;/g,"\$")
}
sr$t.value= sr$t.value.substring(0,sels) + replaceString + sr$t.value.substring(sele);
}

sr$t.selectionStart=sels;
sr$t.selectionEnd=sr$t.value.length-selr;
srSync();
}

function srReplaceall()
{
if (!sr$s.value) {
sr$t.focus();
return
}

var sels=sr$t.selectionStart;
var sele=sr$t.selectionEnd;
var selr=sr$t.value.length-sele;

var reps;
var searchString = sr$s.value;
var replaceString = sr$r.value;

if (sr$f.srRegexp.checked)
{
replaceString = replaceString.replace(/\\\\/,'&backslash;').replace(/\\n/,'\n').replace(/&backslash;/,"\\");
}
else
{
searchString = searchString.replace(/([\[\]\{\}\|\.\*\?\$\^\\])/g,'\\$1');
replaceString = replaceString.replace(/([\$\\])/g,'\\$1');
}

if (sele>sels)
reps=sr$t.value.substring(sels,sele)
else
reps=sr$t.value
;

if (sr$f.srCase.checked)
var re=new RegExp(searchString,"g")
else
var re=new RegExp(searchString,"gi")
;

var replaceCounter=0;

var replaceFunc=function()
{
replaceCounter++;
return replaceString;
};

reps=reps.replace(re,replaceFunc);

if (sele>sels)
sr$t.value = sr$t.value.substring(0,sels) + reps + sr$t.value.substring(sele);
else
sr$t.value = reps
;

sr$t.selectionStart=sels;
sr$t.selectionEnd=sele>sels ? sr$t.value.length-selr : sels;
// ## window.status = replaceCounter+" ocurrences of " + searchString + " replaced.";
window.status = sr$lang['_num_ ocurrences of _str_ replaced'].replace(/\$1/, replaceCounter).replace(/\$2/, searchString);

srSync();
}

function srToggleCase()
{
var sels=sr$t.selectionStart;
var sele=sr$t.selectionEnd;
var selr=sr$t.value.length-sele;
var selt=sr$t.value.substring(sels,sele);

if (sele>sels)
{
if (selt==selt.toUpperCase())
selt=selt.toLowerCase()
else if (selt==selt.toLowerCase() && sele-sels>1)
selt=selt.substring(0,1).toUpperCase()+selt.substring(1).toLowerCase()
else
selt=selt.toUpperCase()
;

sr$t.value = sr$t.value.substring(0,sels) + selt + sr$t.value.substring(sele);
sr$t.selectionStart=sels;
sr$t.selectionEnd=sele>sels ? sr$t.value.length-selr : sels;
}
srSync();
}
function srSync()
{
var i;
var allLines=0;
var lineNo=0;
var w=sr$t.cols-5;

var dummy=sr$t.value.split("\n");
for (i=0;i<dummy.length;i++){allLines+=Math.ceil(dummy[i].length/w)}

var dummy=sr$t.value.substring(0,sr$t.selectionStart).split("\n");
for (i=0;i<dummy.length;i++){lineNo+=Math.ceil(dummy[i].length/w)}

// alert (w+" "+lineNo+"/"+allLines);

sr$t.scrollTop=sr$t.scrollHeight*(lineNo-10)/allLines;
sr$t.focus();
}

function srInit()
{
if(document.getElementById('wpTextbox1'))
{
var srBoxCode =
'<form name="srForm"><table id="srBox" cellpadding="0" cellspacing="2">'
+'<tr>'
+'<td valign="bottom">'
+'<span class="label">znajdź:</span><br />'
+'<input size="17" type="text" name="srSearch" accesskey="F" tabindex="8" onkeypress="event.which == 13 && srNext()"; value="" />'
+'</td>'
+'<td valign="bottom">'
+'<span class="label">zamień na:</span><br />'
+'<input size="17" type="text" name="srReplace" accesskey="G" tabindex="9" onkeypress="event.which == 13 && srNext()"; value="" />'
+'</td>'
+'<td valign="top">'
+'<label><input type="checkbox" name="srCase" onclick="sr$t.focus()" tabindex="10" />uwzględnij wielkość liter</label>'
+'<label><input type="checkbox" name="srRegexp" onclick="sr$t.focus()" tabindex="11" />użyj RegEx</label>'
+'<br />'
+'<a href="javascript:srBack()" onmouseover="sr$t.focus()" title="szukaj wstecz [alt-2]" accesskey="2"><</a> '
+'<a href="javascript:srNext()" onmouseover="sr$t.focus()" title="szukaj dalej [alt-3]" accesskey="3">szukaj  ></a>&emsp;'
+'<a href="javascript:srReplace();srBack()" onmouseover="sr$t.focus()" title="zamień znalezione i szukaj poprzedniego [alt-4]" accesskey="4"><</a> '
+'<a href="javascript:srReplace()" onmouseover="sr$t.focus()" title="zamień znalezione">zamień</a> '
+'<a href="javascript:srReplace();srNext()" onmouseover="sr$t.focus()" title="zamień znalezione i szukaj następnego [alt-5]" accesskey="5">></a>&emsp;'
+'<a href="javascript:srReplaceall()" onmouseover="sr$t.focus()" title="zamień wszystkie wystąpienia, które zostaną znalezione [alt-7]" accesskey="7">zamień wszystkie</a>&emsp;'
+'</td>'
+'</tr>'
+'</table></form>'
;
var el=document.getElementById('searchInput');
if (el) el.accessKey='none';

sr$t=document.editform.wpTextbox1;
sr$w=sr$t.style.width;

//
// inserting buttons
var btns=document.createElement('span');
btns.innerHTML=
'<a id="SearchIcon" href="javascript:srShowHide()">'
+'<img style="cursor: pointer;" title="Wyszukiwanie i zamiana" alt="Wyszukiwanie i zamiana" src="http://upload.wikimedia.org/wikipedia/en/1/12/Button_find.png" border="0" height="22" width="23">'
+'</a>'
+'<a href="javascript:srToggleCase()">'
+'<img style="cursor: pointer;" title="Zmiana wielkości liter" alt="Zmiana wielkości liter" src="http://upload.wikimedia.org/wikipedia/en/1/12/Button_case.png" border="0" height="22" width="23">'
+'</a>'
;

var el=document.getElementById('toolbar');
if (el)
{
el.appendChild(btns)
}
else
{
el=document.getElementById('editform');
el.parentNode.insertBefore(btns,el);
}

sr$i=document.getElementById('SearchIcon');
sr$i.accessKey="F";

//
// inserting box
var srbox=document.createElement('div');
srbox.innerHTML=srBoxCode;
srbox.firstChild.style.display='none';

el=document.getElementById('editform');
el.parentNode.insertBefore(srbox,el);

sr$f=document.srForm;
sr$s=document.srForm.srSearch;
sr$r=document.srForm.srReplace;
}
}

function srShowHide()
{
if (sr$f.style.display=='none')
{
sr$f.style.display='block';
sr$i.accessKey="none";
sr$t.style.width='auto';
sr$s.focus();
}
else
{
sr$f.style.display='none';
sr$t.style.width=sr$w;
sr$i.accessKey="F";
}
}
addOnloadHook(srInit);

User Experience/ToDo/Product

2008-04-03T10:38:28Z

Saperski: {{Bug}}ify, "here" is a basic usability bug

<noinclude>
{{User Experience}}
[[User_Experience/ToDo|UX ToDo List]]: [[User_Experience/ToDo/Project|UX@OOo Project Tasks]] - '''OOo Product Tasks'''
__TOC__
</noinclude>
<includeonly>
== OOo Product Tasks ==
</includeonly>

=== General ===
----

==== Look&Feel needs to be reworked ====
Look&Feel in general needs to be reworked to a more pleasing appearance. (see discussion [http://ux.openoffice.org/servlets/SearchList?list=discuss&searchText=my+user+experience&defaultField=subject&Search=Search 'My user experience with OOo...']) J.S. Martin made some pretty nice [http://josmar52789.googlepages.com/thebasicdesign sketches]. Also, Trollen Lord made [http://docs.google.com/Doc?id=dgfdgp6x_3c7brj2 a sketch] of the formatting and status bar. No floating box, just context sensitivity and theme -> styles -> minor manual edit options context sensitively. It should provide all the same options for users, but often with less effort and with more intuitive ui. Also the status bar has been cleared of redundant, irrelevant and confusing items (the zoom percentage is still missing from magnifier glass), giving more valuable space vertically.

==== Styles and Formatting not usable intuitively ====
The 'Styles and Formatting' floating window is not usable intuitively. The differentiation of styles and hard formatting is not obvious for a user; a solution could be the implementation of style themes (customizable). (see discussion [http://ux.openoffice.org/servlets/SearchList?list=discuss&searchText=my+user+experience&defaultField=subject&Search=Search 'My user experience with OOo...'])

==== Provide In-Place Manipulation For Special Objects ====
At the moment there are many ways to interact with special objects like Hyperlinks, Smart Tags, AutoCorrection. The Wiki page [[Proposal_DirectManipulationSnippets]] tries to address those issues for both objects in the document and the document itself.

==== Customizable font list ====
Make the fonts list customizable, so that the user only sees his favorite used fonts. (see discussion [http://ux.openoffice.org/servlets/SearchList?list=discuss&searchText=my+user+experience&defaultField=subject&Search=Search 'My user experience with OOo...'])

==== Rulers on demand ====
Offer the functionality of hiding the rulers and calling them temporarily if required. (see discussion [http://ux.openoffice.org/servlets/SearchList?list=discuss&searchText=my+user+experience&defaultField=subject&Search=Search 'My user experience with OOo...']) Also, Trollen Lord made proposals ([http://docs.google.com/Doc?id=dgfdgp6x_5399x8k 1], [http://docs.google.com/Doc?id=dgfdgp6x_9dbn5bc 2]) about possible rulers and how some parts of context sensitivity might work.

==== Modern Color Palette ====
Change the standard color palette to a modern look. That is planned. (see discussion [http://ux.openoffice.org/servlets/SearchList?list=discuss&searchText=my+user+experience&defaultField=subject&Search=Search 'My user experience with OOo...'])

==== More intuitive color management ====
Color management: Setting, changing or exchanging colors /color palettes is not at all intuitive. (see discussion [http://ux.openoffice.org/servlets/SearchList?list=discuss&searchText=my+user+experience&defaultField=subject&Search=Search 'My user experience with OOo...'])

==== Selection color scheme ====
A new color scheme for selections in OOo. Let's get rid of simple inverted XOR white on black.
*What's needed is a competitive analysis. What's typical for other applications on Windows and Linux?
*What are the system's default selection colors for different themes?
*How do we use the selection color provided?
*Where do we apply it? eg. Text in Writer, Tables in Writer, Cells in Calc...
*What is the difference for windows with/without focus? What about tool windows?
*What about consistency with controls like text boxes and list boxes?
*What about High Contrast for A11y?
;Issues
: {{Bug|7512|Selection colour}}
: {{Bug|78181|Calc: Highlight Current Row + Advanced Table Formatting}}
;Discussion
: http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=1886649

==== Fresh looking icons ====
Icons: There is an ongoing [http://ui.openoffice.org/VisualDesign/OOo_galaxy.html project on new icons]. (see discussion [http://ux.openoffice.org/servlets/SearchList?list=discuss&searchText=my+user+experience&defaultField=subject&Search=Search 'My user experience with OOo...'])

==== Toolbar improvements ====
Make toolbars saveable so edited toolbars can be used on another computer. Also, add a mode in which toolbar icons can be dragged and dropped from and to menus and toolbars.

=== Writer ===
----
* Individual Header and Footer page editing should be improved/made easier (e.g. dissconnecting header of one page with the one on the next page - like in MS Word). As I deal a lot with writing papers and need this function everyday, it seems quite important.

* Also integrating Reference Management software, like JabRef, would be highly appreciated. (or just making the transfer process from the BibTex file less time consuming and complicated).

* Accessing the Thesaurus is far more difficult for users than in competitive office suites. Access to the thesaurus via a right click context menu far more handy than it is implemented in OpenOffice.org. Please see {{Bug|51258}}

* I know several persons who tried to rotate an image in Writer, but it is impossible. It is very unintuitive to describe: "Please import the image into draw, rotate it, copy it, paste it into writer" Please refer to the very old bug {{Bug|3545}}.

* The way revision is handled currently only with one window. {{Bug|6191}} {{Bug|9661}}

* The ability to import PDF documents (like KWord does) would be extremely useful, as there are a lot of text documents in PDF format which users have to cut and paste from.

=== Math ===
----
* OpenOffice.org Math is in terms of User experience quite terrible. Most people do not even find the floating toolbars in order to click together their formulas. Moreover, there is no help at all regarding the formula syntax. I believe that the idea of the assisted command line is great, but not nicely at all put into practice. An idea is given by the {{Bug|34183}}.

=== Calc ===
----
* Calc has a very nice feature to import (or link) tables in webpages to the spreadsheet; however it is not nice done regarding the user experience. The dialog does not display a preview of the tables on the webpage, but gives a list of ALL tables on the webpage (e.g. table0, table1, table2, ..... table xy). Always you have to try out which table is the one you actually want. Please see {{Bug|70062}}.
==== UX to Do List ====
There a [[Calc/To-Dos/Usability|UX to do list for Calc]].

==== Improvements that should be made on keyboard shortcuts ====

* Add shortcuts to Edit/Fill-in/Down and Edit/Fill-in/Right (Ex: Ctrl+D, Ctrl+R)
* In FR localized version of OOo, some shortcuts are not working : Insertion/Cellules (Ctrl++)
* In FR localized version of OOo, some menus share the same shortcut Insertion/[[L]]ignes, Insertion/Co[[l]]onnes, Insertion/Feui[[l]]le...
* When doing a shortcut combination (ex: Alt+IC to insert a new cell in FR version), you have to press Enter to select the menu, this is time consuming, it should not be necesary.

=== Impress / Draw ===
----
* ...

Compatibility with Microsoft Office Powerpoint presentations could be improved, because there are some minor bugs that cause presentation layout to distort.

Thanks.

-

Also can you integrate Flash .flv files with Impress? .Flv files are easy to use as video demonstration purposes in Impress.

* Specify an user interface for setting the pixel resolution when exporting graphics. First draft specification is on [[Export_Resolution]] and [[Export_Resolution_Draft2]]. There is already code to set pixel resolution, which you can reach via API through a macro.

=== Other ===
----
* Separate lightweight reader with MS doc/xls format converter (for allowing viewing and converting odt/ods documents by others without OpenOffice), and lightweight firefox plug-ins for odt and ods files are a real necessity to proliferate use of the ODF format. This would allow users to simply attach an ODF file to an email with a link to the reader, or put an ODF file on a web page and expect the recipient to download and use the viewer to read it. The biggest stumbling block to wider ODF adoption is the size of the OpenOffice download. It effectively prevents government departments and other putting ODF files on their web pages, and pretty well all OpenOffice users end up sending documents and email attachments to others in MS doc or xls formats rather than ODF format. This is just a plain daft situation which needs to be redressed.

=== Even More Lists With OOo Product Related Tasks ===
----
==== IssueTracker ====
* See issues that result from our last usability test: [http://ux.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=TASK&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=ux-ctest&short_desc_type=substring&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=ux-all&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query IssueTracker query]; before starting to work on any of these tasks, please contact the owner of the respective issue.

* [http://ux.openoffice.org/issues/buglist.cgi?resort=1&issue_id=5038,8811,11121,30523,38714,41801,51564,64944,68639,48454,59251,72921,3997,1163,1596,1598,2131,2497,2864,3243,3356,3403,3545,3687,3790,3959,4040,4499,4638,4914,5156,5289,5487,5608,5963,5991,5998,6087,6193,6342,7277,7311,7553,8275,8302,8949,10166,10384,10865,10931,11215,11278,11393,12138,12684,12686,13257,13441,13645,14007,14832,15220,15378,15456,15511,15773,15878,16895,17169,17387,17964,18179,18486,18651,18731,18748,18860,18959,19291,19601,20370,20496,20857,20878,21280,22147,22406,22905,23078,23465,23839,24070,24460,24500,24969,25341,25483,25680,25732,25855,26446,27377,27417,27745,27836,28526,28913,29431,29646,29807,30216,30502,31624,31774,31927,32117,32309,32446,33336,33668,33851,35545,35579,37201,37511,38998,39527,39656,40827,41419,41675,42464,42606,42646,42768,43981,44088,45593,46027,46165,46333,46594,47740,47895,47952,48059,48179,48409,48700,49475,49978,49991,50134,51151,51662,51787,51904,53184,53545,54019,54288,54293,55002,56629,58313,59504,59651,59745,61007,61075,61685,61724,62948,64670,65295,66403,66919,67838,68841,69032,69129,69830,69845,72559,72957,74441,74442,74858,74859,166,366,972,3395,4579,4695,4904,5085,5261,7065,7998,8095,8808,8855,9899,11174,12666,13791,14069,14163,15666,16032,16036,16280,16295,17171,20327,20808,23526,24203,24614,25072,28595,30631,32785,36490,37991,38494,41800,43029,45689,49133,54567,60950,62564,74992,1069,22519,8938,26449,28714,69429,70753,73457,1035,1601,4219,5930,7088,8824,9370,9661,10547,12052,13939,15546,40778,46241,70445,2593,4401,5560,6401,7512,24256,36672,45491,9437,10326,5948,6191,18829,29924,30215,40800,4260,18004,44102&order=issues.votes%20desc%2C%20issues.priority%2C%20issues.issue_status%2C%20issues.priority%2C%20issues.issue_id Issues with more than 10 votes] (static list 20:18, 10 April 2007 (CEST))
==== and more... ====
* [[/Competitor_Software|Competitor Software Analysis]]
* [[/Useless_GUI_Elements|Completely Useless GUI Elements]]

<noinclude>
[[Category:User Experience|To-Do]]
[[Category:To-Do|User Experience]]
</noinclude>

Specification Template

2008-04-03T10:32:22Z

Saperski: another whitespace

=State Specification Title Here=

{{Specification_Header|<YOUR NAME HERE>||Preliminary}}

== Abstract ==
<START '''TYPING''' HERE>
__TOC__

== References ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="300" bgcolor="#dddddd" | '''Reference Document''' || bgcolor="#dddddd" | '''Check''' || bgcolor="#dddddd" | '''Location (URL)'''
|-
| |'''[http://wiki.services.openoffice.org/wiki/Specification#Before_Writing_a_Software_Specification_--_What_Else_Do_I_have_to_Do.3F Prerequisites]'''
| [passed/failed]
| n/a
|-
| '''Product Requirement, RFE, Issue ID''' (required)
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| '''[[Test case specification]]''' (required)
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| IDL Specification
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| [http://wiki.services.openoffice.org/wiki/The_Three_Golden_Rules_for_Writing_OpenOffice.org_Specifications '''Software Specification Rules''']
| n/a
| n/a
|-
| Other, e.g. references to related specs, Product Concept Document
|
| <PLEASE ENTER LOCATION HERE>
|-
|}

== Contacts ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="300" bgcolor="#dddddd" | '''Role''' || bgcolor="#dddddd" | '''Name''' || bgcolor="#dddddd" | '''E-Mail Address'''
|-
| '''Developer'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''Quality Assurance'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''Documentation'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''User Experience'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
|}

== Acronyms and Abbreviations ==
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| bgcolor="#dddddd" | '''Acronym / Abbreviation''' || bgcolor="#dddddd" | '''Definition'''
|-
| <WYSIWYG>
| <What You See Is What You Get>
|-
|}

== Detailed Specification ==
<START '''TYPING''' HERE>
[[Specification_Template_Help#Detailed_Specification|Help]] | [[UI-Elements|User Interface Element Templates]] | [[Specification_Example|Example Spec]]

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

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

[[Specification_Template_Help#Configuration|Help]] | [[Configuration-Table|Configuration Table Template]]

== File Format ==
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.> [[Specification_Template_Help#File_Format|Help]]

[[Specification_Template_Help#File Format|Help]] | [[File Format Table|File Format Table Template]]

== Open Issues ==
<State a bulleted list of issues Issue here>

[[Category:Specification]]

Specification Template

2008-04-03T10:31:32Z

Saperski: Fix broken whitespaces

Export Resolution Draft2

2008-04-03T10:29:55Z

Saperski: {{Bug}}ify

=Setting Pixel Resolution when Exporting Graphics=

{{Specification_Header|Regina Henschel||Preliminary}}

== Abstract ==
This specification describes an User Interface to determine the amount of pixels which are used, when exporting a graphic from Draw or Impress to a raster format like BMP oder PNG.
The corresponding enhancement request has 45 votes and several duplicates.
__TOC__

== References ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="300" bgcolor="#dddddd" | '''Reference Document''' || bgcolor="#dddddd" | '''Check''' || bgcolor="#dddddd" | '''Location (URL)'''
|-
| |'''[http://wiki.services.openoffice.org/wiki/Specification#Before_Writing_a_Software_Specification_--_What_Else_Do_I_have_to_Do.3F Prerequisites]'''
| [passed/failed]
| n/a
|-
| '''Product Requirement, RFE, Issue ID''' (required)
| [available]
| {{Bug|4499}}
|-
| '''[[Test case specification]]''' (required)
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| IDL Specification
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| [http://wiki.services.openoffice.org/wiki/The_Three_Golden_Rules_for_Writing_OpenOffice.org_Specifications '''Software Specification Rules''']
| n/a
| n/a
|-
| Other, e.g. references to related specs, Product Concept Document
|
| <PLEASE ENTER LOCATION HERE>
|-
|}

== Contacts ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="300" bgcolor="#dddddd" | '''Role''' || bgcolor="#dddddd" | '''Name''' || bgcolor="#dddddd" | '''E-Mail Address'''
|-
| '''Developer'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''Quality Assurance'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''Documentation'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''User Experience'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
|}

== Acronyms and Abbreviations ==
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| bgcolor="#dddddd" | '''Acronym / Abbreviation''' || bgcolor="#dddddd" | '''Definition'''
|-
| <WYSIWYG>
| <What You See Is What You Get>
|-
|}

== Detailed Specification ==
=== Current Situation in OOo2.4 ===
OpenOffice.org can export the vector format drawings to a raster format. The amount of pixels are calculated from the screen resolution of the operating system, the view scale setting in Tools > Options and the width and height of the object.
For example: An object with 1.0 x 0.5 inches, with a Windows XP screen resolution of "120DPI" and an OOo view scaling of 125% gives on export to BMP a size of 151 x 76 Pixels. This is approximately the calculation 1.0 inches ⋅ 120DPI ⋅ 125% = 150 dots.
During export there is a list to determine "DPI", but that does not change the amount of pixels but only sets an meta information.
There exists already some code to set pixel resolution. But this can only be used with a macro.
The current export dialog uses a lot of dialogs, depending on the kind of target format.
* EMF, MET, PICT, SVM, WMF
[[Image:exportOOo2draw2emf.png]]
[[Image:exportOOo2draw2met.png]]
[[Image:exportOOo2draw2pict.png]]
[[Image:exportOOo2draw2svm.png]]
[[Image:exportOOo2draw2wmf.png]]
* PBM, PPM
[[Image:exportOOo2draw2pbm.png]]
[[Image:exportOOo2draw2ppm.png]]
* BMP
[[Image:exportOOo2draw2bmp.png]]
* EPS
[[Image:exportOOo2draw2eps.png]]
* GIF
[[Image:exportOOo2draw2gif.png]]
* JPEG
[[Image:exportOOo2draw2jpeg.png]]
* PDF
[[Image:exportOOo2draw2pdf.png]]
* PNG
[[Image:exportOOo2draw2png.png]]
* Without any dialog are RAS, SVG, SWF, TIFF
* Export to HTML uses a wizard.

=== Competitor's Solutions ===
==== Corel Draw 12 ====
Corel Draw 12 uses one dialog for all kind of target raster formats. Elements which do not apply to the specified format are greyed out. Settings which are only necessary for a specific format are set in a following dialog. In addition to the pixel resolution the user can set the color depth. Examples:
* Standard Bitmap Dialog
[[Image:ExportCorel2rasterstandard.png|common dialog for export to a raster graphic format]]
* Special Options Dialogs
[[Image:ExportCorel2pngoptions.png]]
[[Image:ExportCorel2jpegoptions.png]]

=== New Behavior in OpenOffice.org ===
OpenOffice.org uses a unified dialog, which appears after the user has chosen the export file format. The lower section of the dialog depends on the export format. All settings are persistent during one OOo session.

There is no restriction to the settings but the available space in RAM and on disk.

The new dialog applies to all export formats but HTML, XHTML, PDF, SWF and PWP.

[[Image:ExportNewRasterGraphicOptions.png]]

''The values don't fit together but only show the design of the dialog.''

The upper part is common to all formats. If a setting or value makes no sense for the chosen format, then it is disabled or hidden.

The drop-down list for the unit of measurement offers the items

'''Pixels'''
Millimeter
Centimeter
Meter
Inch
Foot
Pica
Point

The length values refer to the "drawing" size, not to the "real" size. Example: The user sets "Meter" as unit of measurement for Draw in Tools > Options > General and sets the "drawing scale" to "1:10" there. If a dimension line shows 0,65m or a square has size 0,65 x 0,65 in the status bar, then the drawing size is 6,5 cm. And this size of 6,5cm will be used in the export dialog as "original size".

"Pixels" is the decisive value. The other values are calculated from the pixels width and height according to the actual setting in "Resolution". The pixel width and height is rounded up to an integer after each changing.

The user can enter decimals for all length values. Decimals are kept with the entered or calculated precision, but only shown with maximal 3 decimal places.

The drop-down list for the pixel resolution unit has the items

pixel/cm
pixel/inch

The resolution value field contains positive integers. If the resolution value is changed, the amount of pixels is recalculated with 'new resolution value' / 'old resolution value' * 'old pixel value'. The length values of width and height are recalculated afterwards.

The value of pixel/inch is written to the meta data of the graphic, if the format allows such setting.

If keep ratio is checked, when height or width is changed, the other one is calculated automatically. 'keep ratio' does not refer to the original size but to the previous values in the dialog.

The button original size sets the height and width to that of the selection or page which is to be exported.

The color depth is a drop-down list with items

1 Bit Threshold
1 Bit Dithered
4 Bit Grayscales
4 Bit Color Palette
8 Bit Grayscales
8 Bit Color Palette
24 Bit True Color

Changing the color depth effects "size in memory" and "round file size" but not the pixel dimensions.

The text in the part memory changes accordingly to the chosen object size, resolution and color depth. Both values are not guaranteed to be exact.

The lower part contains settings, which are specific to the format.
''The current settings should be possible, but I suggest some additions.''

==== BMP ====
[[Image:ExportToBMPSpecialSettings.png]]

RLE compression reflects back to memory size texts.

All color depths are available but '24 Bit Grayscales'.
''Why is 24 Bit Grayscales not implemented for BMP export?''

==== EMF ====
No special settings needed.

''Hide color depth and pixel dimension? What to do if the selection or page which is to be exported contains bitmaps?''

==== EPS ====
[[Image:ExportToEPSSpecialSettings.png]]

Compression and preview settings reflect back to memory size texts.

''What further settings are used for the preview image? Are the user allowed to change them?''

==== GIF ====
[[Image:ExportToGIFSpecialSettings.png]]

Color depth list shows the currently used setting, other values are disabled.

''It should be possible to set the color depth.''

==== JPEG ====
[[Image:ExportToJPGSpecialSettings.png]]

The compression reflects back to the memory size texts.

The color depth list shows the values '24 Bit Color' and '8 Bit Grayscales', which substitute the current radio buttons. Other values are hidden. ''The Grayscales export has a bug currently. It uses gray colors in a RGB color space. Although gray, the picture is still of kind 24bpp. see {{Bug|87410}}''

==== MET ====
No special settings needed.

The color depth list shows the currently used setting, other values are disabled.

==== PBM ====
[[Image:ExportToPBGPMSpecialSettings.png]]

The file format reflects back to the memory size texts.

The color depth list shows '1 Bit Treshold', other values are disabled.
''That is the color depth used in PBM format.''

==== PGM ====
[[Image:ExportToPBGPMSpecialSettings.png]]

''PBM need to be exchanged wtih PGM.''

The file format reflects back to the memory size texts.

The color depth list shows '8 Bit Grayscaled', other values are disabled.
''That is the color depth used in PGM format.''

==== PICT ====
No special settings needed.

Color depth list shows the currently used setting, other values are disabled.
''PICT allows many settings, but currently the user cannot select any of them.''

==== PNG ====
[[Image:ExportToPNGSpecialSettings.png]]

The compression reflects back to the memory size texts.

The color depth shows the currently used setting.
''The user should be allowed to set the color depth. It is already possible for embedded png-pictures. So why not implement it for export? The code is already there.''

==== PPM ====
[[Image:ExportToPBGPMSpecialSettings.png]]

''Replace PBM with PPM.''

The file type reflects back to the memory size texts.

The color depth shows the currently used setting.

==== RAS ====
Currently no export dialog exists.

''The format itself allows many settings. Perhaps it should be handled like BMP.''

==== SVG ====
Currently no export dialog exists.

''What to do if the selection or page which is to be exported contains bitmaps?''

==== SVM ====
No special settings needed.

''Hide color depth and pixel dimension?''

==== TIFF ====
Currently no export dialog exists.

''The format itself allows many settings. Here are some additional implementations desirable.''

==== WMF ====
No special settings needed.

''Hide color depth and pixel dimension? What to do if the selection or page which is to be exported contains bitmaps?''

==== XPM ====
Currently no export dialog exists.

''I don't know this format. Are there now settings needed?''

[[Specification_Template_Help#Detailed_Specification|Help]] | [[UI-Elements|User Interface Element Templates]] | [[Specification_Example|Example Spec]]

== Migration ==
Old documents need no change.

== Configuration ==
''Not decided yet.''
[[Specification_Template_Help#Configuration|Help]] | [[Configuration-Table|Configuration Table Template]]

== File Format ==
Export does not effect any of OOo's file formats.
[[Specification_Template_Help#File_Format|Help]]

[[Specification_Template_Help#File Format|Help]] | [[File Format Table|File Format Table Template]]

== Open Issues ==
* Can the settings be saved in the user settings? Should there be settings in Tools > Options which are use to prefill the dialog?
* The memory size might be very large. What to do if the available RAM is not enough? What to do if the memory size exceeds the setting in Tools > Options?
* What to do if the disk space are not enough?

[[Category:Specification]]

Template:Bug

2008-04-03T10:27:51Z

Saperski: description

[http://qa.openoffice.org/issues/show_bug.cgi?id={{{1|}}} issue {{{1|}}} {{{2|}}}]<noinclude>
[[Category:Templates for links|{{PAGENAME}}]]</noinclude>

EIS

2008-04-03T10:25:34Z

Saperski: /* Tips & Tricks */ linking from wiki

[[Category:Quality Assurance]][[Category: Development]][[Category: Specification]]
== 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/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 thuse 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 CVS master build" and "[http://eis.services.openoffice.org/EIS2/wsm.FixedTasksExplorer Show] treeview of all integrated CVS 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 [mailto:bei@openoffice.org Bernd Eilers]. Bernd can often be found on the #dev.OpenOffice.org [http://en.wikipedia.org/wiki/IRC IRC]
channel on irc.freenode.net with the nickname rfc821. 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]]

Template:Issue

2008-04-03T10:24:44Z

Saperski: redirect

#REDIRECT[[Template:Bug]]

File Chooser Type Handling Specification

2008-04-03T10:23:43Z

Saperski: {{Bug}}

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"

|- align="left"
| colspan="2" bgcolor="#cccccc" | '''Specification Status'''
|-
| width="150" | '''Author''' || Allen Pulsifer
|-
| width="150" | '''Last Change''' || 2007-02-13
|-
| width="150" | '''Status''' || Preliminary [[Specification_Template_Help#Status|Help]]
|-
|}

== Abstract ==
The specification relates to the handling of file "types" in the File | Open dialog. It specifies how the user's choice of file type affects the files displayed in the file chooser and the filters that may be used to open or import the file. It also specifies how files with unrecognized formats are handled.
__TOC__

== References ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="300" bgcolor="#dddddd" | '''Reference Document''' || bgcolor="#dddddd" | '''Check''' || bgcolor="#dddddd" | '''Location (URL)'''
|-
| |'''[http://wiki.services.openoffice.org/wiki/Category:Specification#Before_Writing_a_Software_Specification_--_What_Else_Do_I_have_to_Do.3F Specification Process Entry Check]'''
| [passed/failed]
| n/a
|-
| '''Product Requirement, RFE, Issue ID''' (required)
| available
|{{Bug|67163}} {{Bug|74277}} {{Bug|74295}}
|-
| Product Concept Document
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| '''[[Test case specification]]''' (required)
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| IDL Specification
| [available/not available]
| <PLEASE ENTER LOCATION HERE>
|-
| [http://wiki.services.openoffice.org/wiki/The_Three_Golden_Rules_for_Writing_OpenOffice.org_Specifications '''Software Specification Rules''']
| n/a
| n/a
|-
| Other, e.g. references to related specs
|
| <PLEASE ENTER LOCATION HERE>
|-
|}

== Contacts ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="300" bgcolor="#dddddd" | '''Role''' || bgcolor="#dddddd" | '''Name''' || bgcolor="#dddddd" | '''E-Mail Address'''
|-
| '''Developer'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''Quality Assurance'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''Documentation'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
| '''User Experience'''
| <First Name, Last Name>
| <User@openoffice.org>
|-
|}

== Acronyms and Abbreviations ==
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| bgcolor="#dddddd" | '''Acronym / Abbreviation''' || bgcolor="#dddddd" | '''Definition'''
|-
| <WYSIWYG>
| <What You See Is What You Get>
|-
|}

== Detailed Specification ==

'''''Comment: Except as noted, the following paragraphs describe the behavior that is already implemented in OOo v2.1. The sections describing new behavior begin at Paragraph 4.'''''

1. When the user does a File | Open, the File Chooser dialog (also known as the File Picker dialog) shall be displayed. The File Chooser dialog shall allow the user to browse the files available on the local and network storage locations using either a OOo dialog or a native (operating system) dialog.

''Comment: Support for this specification in a native dialog may depend on the host operating system.''

2. The File Chooser dialog shall display a drop down selection for File Type.

The first or top option in the File Type drop down list shall be "All Files (*.*)"

Immediately under "All Files (*.*)" shall be the following list of document type groups:

* Text documents
* Spreadsheets
* Presentations
* Drawings
* Web pages
* Master documents
* Formulas
* Database documents

Following the document type groups shall be a list of specific formats. For example, there shall be selections available for:

* OpenDocument Text (*.odt)
* OpenDocument Text Template (*.ott)
* OpenOffice.org 1.0 Text document (*.swx)
* ''etc.''

The specific formats shall be grouped by application type, separated a horizontal line, with Text document types first, then Spreadsheets types, Presentation types, Drawing types, Web page types, Master document types, Formula types and Database document types.

''Comment: OOo v2.1 lists Database document types above Formula document types.''

3. When "All Files (*.*)" is selected, all files shall be displayed in the File Chooser dialog, with the exception of hidden files not displayed by the operating system's native dialog.

When one of the document type groups is selected, the list of displayed files shall be filtered by extension, and only files with extensions corresponding to known document types shall be displayed. So for example, when "Text documents" is selected, only files with .odt, .ott, .swx, etc., shall be displayed.

When one of the specific document formats is selected, only the files with extensions corresponding to that document type shall be displayed.

'''''Comment: The following paragraphs specify new behavior that is not implemented in OOo v2.1:'''''

4. The default type selected in the File Type drop down shall correspond to the application that has the foreground window when File | Open is selected. For example, if the foreground window is a Writer document, the default File Type shall be the "Text documents" group. If there is no document open in the foreground window, or if the document type cannot be determined, the default selection for File Type shall be "All Files (*.*)".

Ref: {{Bug|67163}}

''Comment: If the default File Type is a type group such as Text documents, the user can easily open a document of any other type, such as a spreadsheet, by simply selecting that file type or "All Files (*.*)" in the File Type drop down list.''

===Opening a File===

5. After the user selects a file to open, the filter behavior shall depend on the type selected in the File Type drop down, as specified in the sections below:

====When "All Files" is selected====

If All Files (*.*) is selected for the File Type, OOo shall attempt to detect the file format.

A. If the file format detection fails, OOo shall attempt to determine if the operating system has an association for the file extension. For example, if the file extension is .pdf, the operating system may tell OOo that the file is associated with the Adobe Reader application.

Ref: {{Bug|74295}}

: A(i). If the operating system provides a file association, OOo shall display the following dialog:

::: Title: Error opening document
::: Icon: Warning icon (!)
::: Text: File <path>\n. OOo cannot open this file. Would you like to open the document using <detected application name>?
::: Buttons: OK; Cancel

: A(ii). If the operating system does not provide a file association, OOo shall display the following dialog:

::: Title: Error opening document
::: Icon: Warning icon (!)
::: Text: File <path>\n. The format is not recognized. Would you like to chose a specific format?
::: Buttons: OK; Cancel

:: If OK is selected, OOo shall present the user with the Type Chooser Dialog (see below). The Type Chooser Dialog shall by default display all available types.

B. If the format is detected as "ASCII" or "plain text" and the file has no extension or a presumptive text file extension (as listed below), OOo shall attempt to open the document as a Text document using the ASCII filter. Otherwise, if the file has an unknown extension, or if the ASCII import filter requires configuration (for example, the character encoding or paragraphs markers), OOo shall first display the following dialog before proceeding:

::: Title: Open as Text?
::: Icon: Question mark icon (?)
::: Text: File <path>\n. Would you like to open the file as a Text document?
::: Buttons: OK; Cancel

The Text import filter shall not fail due to the content of the file, instead, all characters in the file shall be converted to a text representation and displayed in a new document.

: Presumptive text file extensions: .txt, .log

C. If the format is detected as some type other than "ASCII", OOo shall attempt to open the document in the detected format. If the file import filter fails, OOo shall display the following dialog:

::: Title: Error opening document
::: Icon: Warning icon (!)
::: Text: File <path>\n. This file cannot be opened as a <type> document. Would you like to try opening it in another format?
::: Buttons: OK; Cancel

====When a document type group is selected====

If a document type group such as "Text document" is selected for the File Type, OOo shall attempt to detect the format using only the import filters that correspond to the selected type group.

Ref: {{Bug|74277}}

A. If the file format detection fails, OOo shall display the following dialog:

::: Title: Error opening document
::: Icon: Warning icon (!)
::: Text: File <path>\n. This file cannot be opened as a <type group> document. Would you like to try opening it in another format?
::: Buttons: OK; Cancel

: If OK is selected, OOo shall present the user with the Type Chooser Dialog (see below). The Type Chooser Dialog shall by default display all available types.

B. If the file format detection succeeds, OOo shall attempt to open the file using the filter for the detected type. If the filter fails, OOo shall display the following dialog:

::: Title: Error opening document
::: Icon: Warning icon (!)
::: Text: File <path>\n. This file cannot be opened as a <detected format> document. Would you like to try opening it in another format?
::: Buttons: OK; Cancel

: If OK is selected, OOo shall present the user with the Type Chooser Dialog (see below). The Type Chooser Dialog shall by default display all available types.

====When a specific document format is selected====

If a specific format is selected for the File Type, OOo shall attempt to open the document using the import filter for that format. If the import filter fails, OOo shall attempt to detect the file format.

A. If an alternate format is detected, OOo shall display the following dialog:

::: Title: Error opening document
::: Icon: Warning icon (!)
::: Text: Text: File <path>\n. This file cannot be opened as a <failed type> document. Would you like to try opening it as a <detected type> document?
::: Buttons: OK; Choose type...; Cancel

: If OK is selected, OOo shall attempt to open the document as if the user had selected the detected type.

: If Choose type... is detected, OOo shall present the user with the type chooser dialog (see below). The initial list of types in the type chooser dialog shall include only the types that open in the same application as the type the user initially chose. For example, if the user initially chose the type OpenDocument Text (*.odt), then only Text document types shall be initially displayed.

B. If no alternate format is detected, OOo shall display the following dialog:

::: Title: Error opening document
::: Icon: Warning icon (!)
::: Text: File <path>\n. This file cannot be opened as a <type> document. Would you like to try opening it in another format?
::: Buttons: OK; Cancel

: If OK is selected, OOo shall shall present the user with the type chooser dialog, as specified in Paragraph A.

===The Type Chooser Dialog===

At the top of the Type Chooser dialog shall be a drop down list. This list shall contain the following options:

* All types
* Text documents
* Spreadsheets
* Presentations
* Drawings
* Web pages
* Master documents
* Formulas
* Database documents

Below the drop down list shall be a scrollable list of types. The types displayed shall be filtered to only include the types selected in the drop down list. For example, if "Text documents" is selected in the drop down list, then only the types that open as Text documents shall be displayed.

The default selection in the drop down list shall depend on the context in which the Type Chooser dialog is presented to the user, as specified in the paragraphs above.

[[Specification_Template_Help#Detailed_Specification|Help]] | [[UI-Elements|User Interface Element Templates]] | [[Specification_Example|Example Spec]]

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

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

[[Specification_Template_Help#Configuration|Help]] | [[Configuration-Table|Configuration Table Template]]

== File Format ==
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.> [[Specification_Template_Help#File_Format|Help]]

[[Specification_Template_Help#File Format|Help]] | [[File Format Table|File Format Table Template]]

== Open Issues ==
* What happens when attempting to open more than one file at once, i.e., when more than one file has been selected in the File Chooser dialog?
* TODO: expand list of presumptive text file extensions
* For the test spec:
** test with common unsupported document types, such as .pdf
** try opening a text document with each type group selected

[[Category:Specification]]

CWS

2008-04-03T10:20:28Z

Saperski: template ad

CWS here is meant as the acronym for ChildWorkSpace. For a lengthier cws explanation see the [http://tools.openoffice.org/servlets/ReadMsg?list=dev&msgNo=5044 introduction] and [http://tools.openoffice.org/#CWS Overview, Tools, Policies]. This text is some really, really bare bones for the quickest, most simple cws usage.

The basic overview here is that a CWS is a CVS branch, tied to a service with a database backend called [[EIS]]. The cws* tooling talks to both the CVS server and (via SOAP) to the [[EIS]] service. It makes maintaining branches more efficient, standardises their use & integrates with QA nicely.

All code that goes into OO.o has to go through a CWS. A CWS is a fairly heavy-weight beast - thus it's well worth aggregating several commits / bug-fixes into one.

NB. Since this 'howto' was written an even quicker way of committing patches to a cws has been created for people who use ooo-build: [http://cvs.gnome.org/viewcvs/ooo-build/bin/cws-commit-patch?view=log bin/cws-commit-patch].

{{LinkBanner}}

== Basic setup / Assumptions ==

It is assumed that you have fixed some bug / created some feature, and you have a live build tree. It is also assumed that you have sourced the ''LinuxIntelEnv.Set.sh'', ''winenv.set'' or ''winenv.set.sh'' script as appropriate, and as a result your shell is set up correctly with various environment variables pointing to the build tree.

It is also assumed that you have an up-stream OOo CVS account with the appropriate commit privileges, and that you have your tunnel setup and running, and the source modules you are working on has the right CVS/Root entries for that account/tunnel. (Not all source modules in the build tree need to have their CVS/Root entries pointing to the tunnel, those that you aren't going to manipulate through the cws tools can be from a tarball, or from anonymous CVS.)

=== cws config file (.cwsrc) ===

You also need to have a CWS configuration file named .cwsrc in your home directory (~/.cwsrc) for any of the cws command-line tools to work. The following is an example of a typical .cwsrc file.

[CWS_CONFIG]
CWS_DB_SERVER_1=https://eis.services.openoffice.org/soap/servlet/rpcrouter
CVS_ID=foouser
CVS_PASSWORD=SDhiod0=s
CVS_SERVER_ROOT=:pserver:foouser@localhost:/cvs

The value for the ''CVS_PASSWORD'' attribute is taken from your ~/.cvspass file once you cvs login through the tunnel.

== Creating the cws ==

You have to think of an imaginative name for your cws; if it's just some general bug fixing thing, people tend to use account-name<index> otherwise some more descriptive name

cwscreate '''-f''' ''DEV300'' ''m16'' ''link01''

NB. the '''-f''' stops cwscreate doing a slow, monstor fresh check-out (you don't want that).

NB. cwscreate in this mode: SOAP only, no CVS access.

You need to have perl SOAP::Lite module installed for cwscreate to work. See [[CPAN install]] page for how to install Perl modules.

== Filling out the details in EIS ==

[http://eis.services.openoffice.org/EIS2/Logon Login] with your OpenOffice.org email address to [[EIS]]. Navigate the DEV300 'new' tree - find your CWS (or better simply look it up under ''Child workspaces'' - ''My CWSs'' or to a full search with the name of your CWS ''Child workspaces'' - ''Search'').

Then click on the underlined link at the top. Fill out the details, as there are:

* '''Owner''', select your account from the list if it's not already prefilled.
* '''QA representative''', check with the project you're working on or ask on the dev@qa mailing list who the proper QA-rep for your CWS would be and select from the list. If no QA-rep is assigned, the CWS shows up under the '''SeekQA''' menu and someone might jump on it. However, it may also stay there for weeks if nobody does, so better communicate with your project. See also how to [[find a QA representative]].
* '''Description''', give a reasonable description of the CWS (not just 'bugfixes').
* '''Release''', the release target, e.g. ''OOo2.3''.
* '''Estimated due date "ready for QA"''', an estimate when you plan to have it ''ready for QA'', in format 2002-11-23. This is to give QA an idea when the CWS will be ready.
* '''Estimated due date''', when the CWS should be ready for integration. Note that the time span between ready-for-QA date and the final due date needs to be communicated with the QA-rep, usually it's sufficient to add 2 more weeks to give time for QA and enter that as the final due date, in format 2002-11-23. This is to give release engineering an idea when a CWS will show up for integration.
* '''Level of impact''', ''One Application'' if working on a specific application's code, ''Two or more applications'' if working on a library used by several applications, ''Whole Office'' if touching code that is used throughout the entire office suite or affects general behavior.

== Setting up the environment ==

Now we created a cws - we need to tell the tooling we're working with this cws; we do:

export CWS_WORK_STAMP=''link01''

On Windows, if using tcsh the equivalent command is:

setenv CWS_WORK_STAMP ''link01''

== Adding tasks ==

The CWS (in order to ever get merged) has to have a number of issues associated with it, describing the bugs fixed in this CWS. The developer should mark these as ''FIXED'' as he commits/tests & QA should mark these bugs ''VERIFIED''. See issue handling in [[CWS#When_you.27re_happy | When you're happy]] further down.

It's also important to get the Milestone correct in the bug. To associate the task with the CWS do:

cwsaddtask ''i24253''

NB. cwsaddtask: SOAP only, no CVS access.

== Adding modules ==

We now need to add some top-level modules to the CWS - the ones that we have changed. This tool essentially just tags cvs twice with a static: CWS_DEV300_LINK01_ANCHOR tag and a cws_dev300_link01 branch tag to commit to. It then updates the module to that branch.

cwsadd -a '''-f''' ''solenv''

This command must be run in the build tree in the top directory, where the modules in question are subdirectories that have been checked out through the tunnel. (Or at least, have been re-rooted to point to your tunnel in case they originally are from ooo-build tarballs.)

NB. here '''-f''' allows you to keep your changes, while doing the tagging on the underlying versions they are based on - incorporating them into the new cws automatically.

NB. cwsadd: SOAP and CVS access.

== Create a new module ==

(Taken from [http://tools.openoffice.org/dev_docs/child_workspace_newmodule.html].)

In case you have to introduce a new module not yet known on the master workspace you have to

* first think hard if a new module is really needed. OOo now has more than 200 modules and things are getting a bit out of hand. Of course, if the new stuff doesn't really fit anywhere than a new module might be the lesser of two evils.
* create that module in cvs.
** note: if you are adding the module under '''external''' project, then creating is a bit more complicated:
If you checkout from the CVS the "external" module (cvs co external), you will get actually the
"util/external", the directory "external" from util project's CVS. If you create a new directory,
it will be committed into the util project that you do not really want.

In order to check out the "right" "external", you must checkout one of the directories of external
project whose name is not identical to a directory in "util/external". For instance,
"cvs co external/libxml2". You will have to position yourselves besides the libxml2 subdirectory
(in this case) in external directory, create a new directory and commit it using cvsadd. After that,
you can checkout your module and work on it as usual, still remembering that you are working on HEAD.
* get a cvs alias for that module so that it can be checked out by it's name. See the procedure in http://external.openoffice.org/ and additionally [http://www.openoffice.org/issues/show_bug.cgi?id=76452 example issue] (assign it to mh).
* check in for this module to cvs HEAD in your CWS. In contrast to all added modules do not work on a cws-branch but toplevel.
* assure inter module dependencies (i.e. [[Hacking#prj/build.lst]] files) are correct. Make sure all modules needing something delivered by the new one are dependent on it. If it is not needed by any module at build time, make it a prerequisite of 'postprocess'.
* when the cws is in QA, announce the new module to Hamburg release engineering. You can do this either by writing something in the CWS description field (to RE: CWS contains new module bla) or by sending an email. This is necessary because new modules do not get tracked by CWS tooling and RE has to manually check them out before doing the integration build on the master workspace.

Additionally it is good practise to provide a short description of your new module in [[Source code directories]] table.

== Committing code ==

Committing requires nothing particular new; the database doesn't track commits. Just commit them to the branched modules you cwsadded.

CVS should add some helpful fields for you & some helpful blurb about what to write here - often it doesn't. The stock format is:

Issue number: #i24253#
Submitted by: mmeeks
Reviewed by: mmeeks
This patch fixes a silly bug in linkoo

== When you're happy ==

Finally - when you've committed everything & built & tested it, you need to hand over the CWS to QA.

The issue handling of issues added to the CWS at this stage is

* Verify all issues assigned to the CWS are really fixed in your CWS build.
* If so, reassign the issue to the QA representative of the CWS.
* Announce new features and enhancements (not mere bug fixes) using the [[feature announcement]] form within EIS.

Having done all that, login back to the CWS page in [[EIS]] and re-edit the details - marking the state to ''Ready for QA''.

Check your changes. If you did some [[Compatible_Builds#What_changes_are_binary_incompatible.3F|binary incompatible change]] mark the corresponding module ''incompatible''.

== What next ? ==

You get to wait until the CWS is [[Approve_a_CWS | approved by your QA representative]] and nominated for integration, then it will be merged into HEAD and released.

The approval procedure may take some time. In the meantime the master workspace may change significantly. If changes got into the master touching the same code lines you have changed integrating your CWS will lead to merge conflicts. [[Resolve Merge Conflicts for CWS Integration]] gives some advice how to prevent problems during integration.

== Updating to a newer milestone ==

The long-term CWSes need a resync to a newer milestone from time to time.

* step1 : prepare the place

mkdir tmp
cd tmp
export CWS_WORK_STAMP=''the_name_of_the_cws''

* step2 : the resync itself

'''Case 1 : for cws created against DEV300_m0 or later'''

cwsresync '''-m m5 all'''
''... resolve possible conflicts ...''
cwsresync '''-c all'''
cwsresync '''-f -l m5'''

'''Case 2 : ATTENTION: If your cws still is based on SRC680, use the following'''
'''export WORK_STAMP=SRC680''' # means the cws was created using SRC680 Master work space, does not exist in DEV300 database
# and the build environment did probably define DEV300 as $WORK_STAMP instead
cwsresync '''-m DEV300:m5 all'''
... resolve possible conflicts ...
cwsresync '''-c all'''
cwsresync [options] '''-f -l DEV300:m5'''

You must start in an empty directory with a correctly set CWS_WORK_STAMP environment variable. First of all, '''-m''' merges files from the CWS (according to CWS_WORK_STAMP) with the specified milestone and protocols all conflicts. '''-c''' then commits the merges to the CVS. NB.: Do it always with <code>cwsresync -c</code>, never by hand! Finally, '''-l''' updates the workspace and the milestone info of the CWS in the database

NB.: Don't forget to create a new & empty directory for this. Really.

NB. '''-f''': Speeds the things up by avoiding unnecessary updates during the third step.

NB. If you know what you are doing, you can resync just the files you have touched - specify the filename instead of '''all''' in '''-m''' and '''-c'''.

-----------
'''See also:''' [[Merge Parts Of A CWS Into Another CWS]]

[[Category:Development]]
[[Category:CWS]]

Issue

2008-04-03T10:18:34Z

Saperski: replace with a template

[[Category:Quality Assurance]]

The term "Issue" refers to any kind of change required/desired to OpenOffice.org, covering misbehavior ("Bugs"), enhancements and entirely new features.

[http://qa.openoffice.org/issues/query.cgi Search for issues]

[http://qa.openoffice.org/issue_handling/pre_submission.html File an issue/enhancement]

[http://qa.openoffice.org/ Go to the QA Homepage]

{{LinkBanner}}

CVS

2008-04-03T10:17:56Z

Saperski: {{Bug}}, {{CWS}} templates

This page describes some difficulties with the modified CVS version, which is used for OpenOffice.org

== FAQ ==

=== How do I setup a CVS client? ===
http://specs.openoffice.org/servlets/ProjectSource

=== How do I setup a tunnel? ===
http://www.openoffice.org/scdocs/ddSSHGuide

=== Why do I need a tunnel? ===
A tunnel is used to commit files to the CVS system. Otherwise you have just read acccess.

=== I can't checkout with a certain tag ===

OpenOffice.org CVS is loosing from time to time it's CVSROOT/valtags file so one needs to recreate this tags, this can be done by creating just another dummy branch:

cvs -d:pserver:mh@my-tunnel:/cvs co test
cd test/playground
cvs tag -b cws_src680_asyncdialogs2 Makefile

{{Bug|23306}}

=== how to track the patch code of a issue which has been fixed and integrated ? ===
(e.g) The issue {{Bug|69010}}, belongs to the {{CWS|impress110}}, has been integrated into {{m|192}}.

There are two possibilties to track this:

# Use EIS (eis.services.openoffice.org). Login into EIS, search for the <code>impress110</code> cws and look there for the modules and files section. There you find the registered task and the files affected by this task. Following the link of the revision shows you the diff.
# use bonsai (go-ooo.org/bonsai) to track all the changes of the cws (e.g. http://bonsai.go-oo.org/cvsquery.cgi?treeid=default&module=all&branch=cws_src680_impress110&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=all&mindate=&maxdate=&cvsroot=%2Fhome%2Fooweb%2Fcvsup)
using the first alternative work fine once a cws has been integrated, the second alternative works fine before integration of the cws.

{{LinkBanner}}

Template:LinkBanner

2008-04-03T10:17:30Z

Saperski: New template

'''Tip:''' On this wiki you can use {{S|CWS}}, {{S|m}}, {{S|Bug}} templates to easily link to [[CWS|child workspaces]], [[milestone]]s and [[issue]]s.<noinclude>

[[Category:Formatting templates|{{PAGENAME}}]]
</noinclude>

Category:Formatting templates

2008-04-03T10:15:21Z

Saperski: New category

Templates used to format some text.

[[Category:Templates]]

Template:S

2008-04-03T10:14:25Z

Saperski: typo

<includeonly><code><nowiki>{{</nowiki>[[Template:{{{1}}}|{{{1}}}]]<nowiki>}}</nowiki></code></includeonly><noinclude>
Used to present the template itself:

{{S|S}}

{{S|Bug}}

[[Category:Formatting templates|{{PAGENAME}}]]</noinclude>

Template:S

2008-04-03T10:14:03Z

Saperski: Documentation

<includeonly><code><nowiki>{{</nowiki>[[Template:{{{1}}}|{{{1}}}]]<nowiki>}}</nowiki></code></includeonly><noinclude>
Used to present thetemplate itself:

{{S|S}}

{{S|Bug}}

[[Category:Formatting templates|{{PAGENAME}}]]</noinclude>