| <html> |
| <head> |
| <title>Week 2</title> |
| |
| <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> |
| </head> |
| <body> |
| <h1>OpenOffice.org<br> |
| Development digest<br> |
| 12th January 2004 |
| </h1> |
| <h3 align="center">by <a href="mailto:cphennessy@openoffice.org">C.P. |
| Hennessy</a></h3> |
| Welcome to what I hope will become the weekly digest of OpenOffice.org |
| development. |
| <ul> |
| <li> <a href="#intro">Introduction</a> |
| <ul> |
| <li><a href="#intro_help">So how can I help?</a></li> |
| <li><a href="#intro_branches">So what are all these branches?</a></li> |
| <li><a href="#intro_cvs">Current organization and contents of the |
| CVS log</a></li> |
| </ul> |
| </li> |
| <li><a href="#other">Other developement news</a></li> |
| <li><a href="#intro_summary">This weeks summary</a></li> |
| <li><a href="#cvs_stats">CVS statistics</a></li> |
| <li><a href="#branch_index">Branches with changes this week</a></li> |
| <li><a href="#project_index">Projects which were changed</a></li> |
| <li><a href="#details">Detailed changes on each branch</a></li> |
| </ul> |
| <a name="intro"></a> |
| <h2>Introduction</h2> |
| Following what's happening in OpenOffice.org code development is not so |
| easy, not because there is no information, but rather because that |
| there is so much information and it is so spread out. Hopefully this |
| digest will help to summarize all of that information into something |
| reasonably readable and useful. |
| <p>Most of this digest will be concerned with what code has changed in |
| CVS, and presenting that info in a readable format, but I also hope to |
| include news and information from other OpenOffice.org projects |
| including <a href="http://qa.openoffice.org">QA</a>, <a |
| href="http://native-lang.openoffice.org">native language projects</a>, |
| <a href="http://api.openoffice.org">API</a>, and any other interesting |
| projects.</p> |
| <p>Obviously I could really use help with all of this so if you have |
| something you would like to contribute, or you see ommisions or |
| mistakes please <a |
| href="mailto:cphennessy@openoffice.org?subject=OOo%20Digest%20Suggestion">email |
| me</a> your contribution to the digest.</p> |
| <p>Some of the areas which are not related to development I do not plan |
| on covering, these include <a href="http://marketing.openoffice.org">marketing</a>, |
| <a href="http://documentation.openoffice.org">documentation</a>, and |
| the <a href="http://website.openoffice.org">website</a>. However, I |
| will obviously include any news sent to me about these projects.</p> |
| <p><a name="intro_help"></a></p> |
| <h3>So how can I help?</h3> |
| There are several teams who could do with your help : |
| <ul> |
| <li>for the non-programmers there is the <a |
| href="http://qa.openoffice.org">QA team</a> where you can help to get |
| enough details to reproduce bugs and triage them, help the <a |
| href="http://documentation.openoffice.org">documentation project</a> |
| by contributing templates and clipart, and the <a |
| href="http://native-lang.openoffice.org">localization projects</a> ( |
| e.g. <a |
| href="http://lingucomponent.openoffice.org/servlets/ReadMsg?msgId=965426&listName=dev">help |
| to improve compound word spellchecking</a> );</li> |
| <li>for the script programmer there is the <a |
| href="http://api.openoffice.org">API project</a> where you can develop |
| on top of OpenOffice.org and program in StarBasic ( very similar to VBA |
| ), java, python, C++, and perl. A good project to learn the object |
| model on and improve your OpenOffice.org scripting skills might be the <a |
| href="http://bibliographic.openoffice.org/">bibliographic project</a> |
| where a <a |
| href="http://bibliographic.openoffice.org/servlets/ReadMsg?msgId=965024/&listName=dev">programmer |
| new to python and OpenOffice.org APIs</a> was able to help after only a |
| few days!;</li> |
| <li>for the XML programmers, there are also interesting projects |
| which you could help write using various technologies to transform |
| OpenOffice.orgs based XML based to other formats. Two transforms which |
| come with OpenOffice.org 1.1 are DocBook, and XHTML. There is |
| infrastructure to use XSLT directly from OpenOffice.org, but there are |
| also several projects which are generating OpenOffice.org formatted |
| files outside of the OpenOffice.org suite. To help get you started, <a |
| href="http://books.evc-cit.info/">OpenOffice.org XML Essentials?Using |
| OpenOffice.org?s XML Data Format</a> is a book in progress written by |
| J. David Eisenberg for <a href="http://www.oreilly.com/">O?Reilly |
| & Associates</a> using the <a |
| href="http://creativecommons.org/licenses/by-nd-nc/1.0">Creative |
| Commons License</a>.</li> |
| <li>for the developer there are many areas to get involved in |
| including a call for helping to <a |
| href="http://lingucomponent.openoffice.org/servlets/ReadMsg?msgId=965426/&listName=dev">improve |
| the code for the spellchecker ( especially for German)</a>(which is |
| also use in Mozilla.org), help to <a |
| href="http://sc.openoffice.org/servlets/ReadMsg?msgId=965017/&listName=dev">increase |
| the number of rows Calc can handle</a>, or <a |
| href="mailto:dev@gsl.openoffice.org">help with the native widget |
| framework</a> for Aqua or KDE ports which compliment the official Win32 |
| and GTK work. |
| <p>It is not always necessary to recompile all of OpenOffice.org to |
| work on only one of its components, but if you do then a very good |
| place to start would be the <a |
| href="http://ooo.ximian.com/hackers-guide.html">Unofficial OpenOffice |
| Hacker's guide</a> which explains how to build and work on |
| OpenOffice.org source code. If you have development related questions |
| then please send an email to <a href="mailto:dev@openoffice.apache.org">the |
| development project</a>.</p> |
| </li> |
| </ul> |
| Over the next number of weeks and months I hope to add more information |
| here to help you understand how and where you can contribute, how |
| OpenOffice.org the community works, and how the various components |
| within OpenOffice.org the product work. |
| <p><a name="intro_branches"></a></p> |
| <h3>So what are all these branches?</h3> |
| There is alot of OpenOffice.org development happening as can be seen |
| from the details below. |
| <p>As with many very large projects with many developers, development |
| is going on independently in parallel. To help manage the code in a |
| reasonable way a feature of <a href="http://www.cvshome.org">CVS</a> |
| called branches is used quite extensively. Basically each major feature |
| is developed on a branch by one developer (or a small team of |
| developers).<br> |
| This type of branch is called a "child workspaces"(CWS). Usually when a |
| feature has been completed and some fundamental testing has been |
| performed, the branch is then marked as ready for merging to a master |
| branch.<br> |
| Sometime later the developers branch with the feature is then merged to |
| the "master workspace"(MWS) branch where further testing happens to |
| make sure that features from different branches do not conflict and |
| cause errors.</p> |
| <p>At some point a master branch is labelled and a public release of |
| code is made.</p> |
| <p>An overview of which features will be implement on which branches |
| can be found <a |
| href="http://development.openoffice.org/releases/OOo_2_0_timetable.html">here</a>. |
| There is a <a href="http://tools.openoffice.org/builds/index.html">more |
| complete (and accurate) description of important branches currently used</a>.</p> |
| <p><a name="intro_cvs"></a></p> |
| <h2>Current organization and contents of the CVS log</h2> |
| The CVS summary linked below is organized into what has changed on a |
| particular branch by a each developer. There is currently a color |
| coding on the left side to make it easier to see what type of change |
| has occured. For each change you should see : |
| <ul> |
| <li>a link to the relevant bug in <a |
| href="http://www.openoffice.org/issues/query.cgi">Issuezilla</a> |
| (except for bugs over 100000 as these are currently Sun internal);</li> |
| <li>a comment the developer made while checking in those changes; and</li> |
| <li>a link to the difference of each change in webcvs.</li> |
| </ul> |
| There is also two indexes, the first lists all of the development |
| branches and logically groups these branches.<br> |
| The second index lists all of the OpenOffice.org components which were |
| worked on and lists those branches which have changes on those |
| components. |
| <p><a name="other"></a></p> |
| <h2>In Other Development News</h2> |
| Alexander Bürger <a |
| href="http://openoffice.org/link-to-dev-list-announcement">announced</a> |
| a program to convert files from xfig format to OOo Draw. This program |
| is now in a usable state (for Linux) and available for <a |
| href="http://fig2sxd.sourceforge.net">download</a>. <br> |
| <a href="http://ooo">Building OOo for MaxOSX 10.3 ( Panther) is now |
| reasonably easy</a>, but volunteers are desparately needed to build and |
| package on 10.2 and 10.1.<br> |
| Takamichi Akiyama wrote to me about developments contributed by the |
| members of the <a href="http://ja.openoffice.org">Japanese |
| project</a>:<br> |
| <ul> |
| <li>Graphic Applications (aka graphics)<a |
| href="http://www.openoffice.org/issues/show_bug.cgi?id=9391"><br> |
| Enabling the DXF import filter to handle Japanese texts</a><br> |
| Status: Done (Integrated in OOo 1.1.1)<br> |
| Todos: To cover more encoding types for other languages<br> |
| <br> |
| OOo 1.0 can import a DXF file, but cannot properly handle Japanese |
| texts in it. This effort has solved this problem caused by ethnic text |
| encoding and given OOo more flexibility.<br> |
| DXF file format is one of the AutoCAD drawing file formats, especially |
| designed for data exchange between different application software.It is |
| composed of certain sections and includes drawing objects such as a |
| line, polyline, oval, text, and so forth. A type of encoding is stated |
| in the HEADER section and texts are encoded in the encoding type.<br> |
| Mr. Miyazaki, a member of ja.openoffice.org, initially reported this |
| issue in November, 2002 and Tora collected related information, then, |
| Kevin B. Hendricks wrote source codes for this new function. |
| HiranoKazunari verified it. Stefan Baltzer, wg, sj and msc have |
| supported us.</li> |
| <li>Graphic System Layer (aka gsl)<br> |
| <a href="http://www.openoffice.org/issues/show_bug.cgi?id=22367">Finding |
| out font names of garbage characters in Asian version</a><br> |
| Status: Done (Integrated in cws_src680)<br> |
| OOo Asian versions sometime display unexpected garbage characters due |
| to insufficient font names in the default font name lists that keep |
| several different font names for each specific use such as UI, fixed, |
| etc. Linux distributions vary and their primary Asian font name might |
| differ, and thus, OOo's default font name list could be improved in |
| order to cover such Linux variants.<br> |
| This debug version of vcl module helps users find out a font name that |
| is improperly chosen and used for displaying Asian characters, |
| resulting in garbage characters. Instructions and sample outputs are |
| available in a <a |
| href="http://www.openoffice.org/servlets/ReadMsg?list=dev&msgId=951064">post</a> |
| by Hirano Kazunari.<br> |
| For quick solution to the garbage characters, find out the improper |
| font name and replace it with correct one using Tools > Options |
| menu. For practical solution, tune up the default font name list in |
| share/registry/data/org/openoffice/VCL.xcu on the basis of the debug |
| outputs.<br> |
| This effort comes from Herbert Duerr's debug codes and Tora's |
| additional codes. Hirano Kazunari has tested it on his Linux machines |
| and widely informed this function to the OOo community.<br> |
| </li> |
| </ul> |
| The integration work from Jan to integrate OOo better into the KDE |
| desktop also received alot of attention.<br> |
| <br> |
| <p><a name="intro_summary"></a></p> |
| <h2>This weeks summary</h2> |
| A developers snapshot release (read do not even consider this alpha |
| quality) called <a href="http://download.openoffice.org/680/index.html">680_m17</a> |
| is now available and contains many bug fixes (including valgrind |
| indicated problems, cleanup of compiler flags for gcc, and more VCL |
| cleanups). This builds on the earlier developer snapshot releases <a |
| href="http://development.openoffice.org/releases/680_m15_snapshot.html">m15</a> |
| (with the new VCL plug which will allow native toolkits to be used |
| instead of the OpenOffice.org one, improvements to the scripting |
| framework, lots of compatability and rtl fixes, improvement in graphics |
| handling and the draw tool, and changes in the installation process), <a |
| href="http://development.openoffice.org/releases/680_m13_snapshot.html">m13</a> |
| (mostly bug fixes), and <a |
| href="http://development.openoffice.org/releases/680_m11_snapshot.html">m11</a>(with |
| many features). Note the temporary <a |
| href="%20http://graphics.openoffice.org/unbranded-source/browse/%7Echeckout%7E/graphics/svx/res/Attic/openintro_sun.bmp?rev=1.1.2.1&content-type=image/bmp">splash |
| screen</a>! ( <a href="mailto:dev@openoffice.apache.org">Maybe you can |
| contribute</a>? )<br> |
| <b>Note: these are all developers releases so be careful and do not |
| complain if it crashes, burns and/or eats your computer! </b>However |
| if you do test these please report all errors in IssueTracker (to |
| report a bug or request a feature http://openoffice.org -> |
| "Register", then when you receive a confirmation email, "Login" and |
| "File an issue" ).<br> |
| <br> |
| As progress to the next major release there should be development |
| snapshots every 2 weeks with more features for you to examine. |
| <p>Many bugs have been worked on and resolved ( as of Monday Jan 05 |
| 2004 ):</p> |
| <table class="iz_stats" border="1" cellspacing="0"> |
| <tbody> |
| <tr> |
| <th><br> |
| </th> |
| <th>No this week</th> |
| <th>Change from last week</th> |
| </tr> |
| <tr> |
| <td>Issues which have the status UNCONFIRMED</td> |
| <td>472<br> |
| </td> |
| <td>-66<br> |
| </td> |
| </tr> |
| <tr> |
| <td>Issues which have the status NEW</td> |
| <td>988<br> |
| </td> |
| <td>+191<br> |
| </td> |
| </tr> |
| <tr> |
| <td>Issues which have the status STARTED</td> |
| <td>961<br> |
| </td> |
| <td>+34<br> |
| </td> |
| </tr> |
| <tr> |
| <td>Issues which have the status FIXED</td> |
| <td>7427<br> |
| </td> |
| <td>+164<br> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <br> |
| Please note that even though the unconfirmed issues remain a bit high, |
| the <a href="http://qa.openoffice.org">QA</a> team is really doing |
| some great work in keeping the bugs triaged ready for developers to |
| disect. |
| <p>Some of the interesting developments over the last number of weeks |
| include:</p> |
| <ul> |
| <li><a href="http://development.openoffice.org/digest/cvs2004_02.html">week |
| 2 (2004)</a>: Back with a bang! Over 40MB of changes to be digested. As |
| you might expect changes happened all over the place including :<br> |
| </li> |
| <ul> |
| <li>fixes for building with Visual Studio .Net 2003</li> |
| <li>improving vertical alignment import from MSWord</li> |
| <li>DDE enabled on non-Windows plattforms</li> |
| <li>fixes for Japanese wordbreak iterators</li> |
| <li>improvement of undo capability of attributes and properties of |
| pages and fields</li> |
| <li>more compilation and linking fixes for MacOSX and NetBSD</li> |
| <li>Slovenian extras added</li> |
| <li>more row limit work ( i.e. to increase rows from 32000k )</li> |
| <li>lots of native widget work, GTK, Windows, and KDE</li> |
| <li>new animation work for draw and impress?</li> |
| <li>added support for hidden text</li> |
| <li>ongoing work to make the database componet more visible and |
| compatible with competitors</li> |
| <li>updates to the flash code including master-page animations</li> |
| <li>the spec for a new concept for database application was also |
| released</li> |
| <li>work continues of the reimplementation of the charting |
| application<br> |
| </li> |
| </ul> |
| <li><a href="http://development.openoffice.org/digest/cvs2004_01.html">week |
| 1 (2004)</a> : since most developers were taking a well earned rest, |
| cvs was quite. But a few did find time to contribute:</li> |
| <ul> |
| <li>committed Spanish DicOOo tutorial files <br> |
| </li> |
| <li>a microsoft access sdbc driver for linux users<br> |
| </li> |
| </ul> |
| <li><a href="http://development.openoffice.org/digest/cvs2003_53.html">week |
| 53 (2003)</a> : again a quite week:</li> |
| <ul> |
| <li>some checks for X86_64 and other 64 bit cleanups; and<br> |
| </li> |
| <li>dictionary work.<br> |
| </li> |
| </ul> |
| <li><a href="http://development.openoffice.org/digest/cvs2003_52.html">week |
| 52 (2003)</a>: <br> |
| </li> |
| <ul> |
| <li>lots of cleanups of warnings</li> |
| <li>more bug fixes for 1.1.1 and fixes for MacOSX 10.2</li> |
| <li>added Dutch extras</li> |
| <li>native widget changes<br> |
| </li> |
| </ul> |
| <li><a href="http://development.openoffice.org/digest/cvs2003_51.html">week |
| 51</a>:</li> |
| <ul> |
| <li>fixes for configuring Visual Studio .NET 2003</li> |
| <li>work on importing and exporting databases in XML format?</li> |
| <li>autoshape ?</li> |
| <li>more MacOSX and PPC compilation cleanups <br> |
| </li> |
| <li>more work on allowing table cells to span a page boundary</li> |
| <li>work on XSL for importing Excel XML files</li> |
| <li>lots of work on java installation wizards?</li> |
| <li>GTK and VCL plugin work</li> |
| <li>beanshwll scripting work including code completion and syntax |
| highlighting</li> |
| <li>improved canvas for Impress</li> |
| <li>lots of VCL cleanups</li> |
| <li>new URI processing API</li> |
| <li>add session manager service and interfaces <br> |
| </li> |
| <li>dialog factory for making dialogs loadable on demand</li> |
| <li>chart2 work, and more</li> |
| <li>updates to the Developers Guide ( which can be found here )</li> |
| <li>ADO Browse Dialog And LDAP authentication enhancements |
| specifications<br> |
| </li> |
| </ul> |
| <li><a href="http://development.openoffice.org/digest/cvs2003_50.html">week |
| 50</a>:</li> |
| <ul> |
| <li>work on importing MSWord and Excel XML files</li> |
| <li>start vcl changes for GTK plugin</li> |
| <li>many layout manager additions</li> |
| <li>VCL related cleanups</li> |
| <li>several backports for MSWord compatability <br> |
| </li> |
| <li>dialog diet work - i.e. load code for dialogs only when needed</li> |
| <li>improve network installation</li> |
| <li>native widget work for GTK widgets</li> |
| <li>added a document for using valgrind <br> |
| </li> |
| <li>chart2 work for statistics, linear regression, mean-value, log |
| scaling, error-bar calculation</li> |
| <li>database specs for FormWizard, QueryWizard, and FilterCriteria<br> |
| </li> |
| </ul> |
| <li>week 49</li> |
| <ul> |
| <li>more backports for 1.1.2</li> |
| <li><span style="font-weight: bold;">MORE TO COME</span><br> |
| </li> |
| </ul> |
| <li>week 48<br> |
| </li> |
| <ul> |
| <li>the <a href="#cws_srx645_ooo111fix1_ihi">merge of bug fixes in |
| branches for 1.1.1</a> is ongoing</li> |
| </ul> |
| <ul> |
| <li>working on converting OpenOffice.org's widget set so that it |
| can use the <a href="#cws_srx645_nativewidget1">platforms native |
| widgets</a> is going very well.</li> |
| </ul> |
| <ul> |
| <li>more work on <a href="#cws_srx645_layoutmanager">the new |
| layout manager for custom toolbars and menus</a></li> |
| </ul> |
| <ul> |
| <li><a href="#cws_src680_xmlsec01">xml security</a>, <a |
| href="#cws_src680_so8forms1">xpath</a>, and <a href="#HEAD_lo">dom</a> |
| APIs and features were worked on</li> |
| </ul> |
| <ul> |
| <li>nice <a href="#cws_srx645_alphaart">alpha artwork and fixes</a> |
| added by <a href="http://ximina.com">Ximian</a></li> |
| </ul> |
| <ul> |
| <li>continued improvements on compatibility : <a |
| href="#cws_srx645_droghedafilterteam15">drogheda</a>, <a |
| href="#cws_src680_mullingarfilterteam18">mullingar</a>, <a |
| href="#cws_src680_portlaoisefilterteam16">portlaoise</a></li> |
| </ul> |
| <ul> |
| <li><a href="#cws_srx645_ooo111fix1_pjanik">Catalan, Hungarian, |
| Finnish and Slovenian changes</a> were added</li> |
| </ul> |
| <ul> |
| <li>the work to <a href="#cws_srx645_cellbreak">split a table row |
| over a page boundary</a> continues</li> |
| </ul> |
| <ul> |
| <li><a href="#cws_src680_networker2">more reworking of the |
| installation mechanism</a></li> |
| </ul> |
| <ul> |
| <li>the <a |
| href="http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html">developers |
| guide</a> was also <a href="#HEAD_jsc">updated</a></li> |
| </ul> |
| <ul> |
| <li>and finally alot of integration of branches : <a |
| href="#mws_fix645_hr">1</a>, <a href="#mws_fix645_obo">2</a> and <a |
| href="#HEAD_rt">3</a>.</li> |
| </ul> |
| </ul> |
| </body> |
| </html> |
