| |
| |
| <!--#include virtual="/doctype.html" --> |
| <html> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
| |
| <title>null</title> |
| <link href="/css/ooo.css" rel="stylesheet" type="text/css"> |
| |
| |
| |
| <script src="https://www.apachecon.com/event-images/snippet.js"></script> |
| </head> |
| <body> |
| <!--#include virtual="/brand.html" --> |
| <div id="topbara"> |
| <!--#include virtual="/topnav.html" --> |
| <div id="breadcrumbsa"><a href="/">home</a> » <a href="/marketing/">marketing</a> » <a href="/marketing/ooocon2004/">ooocon2004</a></div> |
| </div> |
| <div id="clear"></div> |
| |
| |
| <div id="content"> |
| |
| <html><head> |
| <title>Abstracts of Conference Papers - Thursday</title> |
| |
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
| <link rel="stylesheet" href="conference.css" media="screen" type="text/css" /> |
| <!-- > |
| $Id: thurs_dev.html,v 1.11 2004/09/09 17:39:48 louis Exp $ |
| < --> |
| </head> |
| |
| <table id="top" name="top" summary="" border="0" cellspacing="5" cellpadding="5"> |
| <tr><td><table width="100%" summary="" ><tr> |
| <td><img src="../conference/group_red.gif" width="52" height="17" alt="image" /></td> |
| <td><h2>Abstracts of Conference Papers - Thursday</h2></td></tr> |
| </table></td></tr> |
| |
| <tr> |
| <td> |
| <table id="D1" name="D1" summary="" border="1" cellpadding="8" cellspacing="0" bordercolor="#000080"> |
| <tr> |
| <td class="dev"> |
| <strong><a name="D1"></a>OpenOffice.org as a Platform for Developers</strong> |
| </td> |
| </tr> |
| |
| <tr> |
| <td>Mathias Bauer<em> Manager Software Engineering, Sun Microsystems, Inc.</em></td> |
| </tr> |
| |
| <tr> |
| <td><p>This session gives an overview about the opportunities OpenOffice.org offers for developers |
| (third party developers). It will explain different concepts (Add-ons, Add-ins, ...) and technologies |
| how OpenOffice.org can be extended or how it can be used in own solutions. The session will |
| demonstrate several existing solutions which emphasize the opportunities for developers and how |
| developers can benefit from own extensions for OpenOffice.org.</p> |
| |
| <p>Outline:</p> |
| <ul> |
| <li>Introduction |
| <li>Opportunities for Developers |
| <li>UNO Components in general |
| <li> Add-on Components |
| <li>Add-in Components |
| <li>Examples |
| <li>Conclusion |
| </ul> |
| </td> |
| </tr> |
| |
| <tr> |
| <td><em> |
| <!-- |
| Biography: |
| --> |
| </em> |
| </td> |
| </tr> |
| |
| </table> |
| |
| <p><a href="thursday.html" title="Agenda for Thursday">Back</a></p> |
| |
| <table id="D2" name="D2" summary="" border="1" cellpadding="8" cellspacing="0" bordercolor="#000080"> |
| |
| <tr> |
| <td class="dev"> |
| <strong><a name="D2"></a>Miscellaneous Topics In Macro Programming</strong> |
| </td> |
| </tr> |
| |
| <tr> |
| <td>Andrew Douglas Pitonyak <em>Lead Software Engineer, Qwest Communications International Inc.</em></td> |
| </tr> |
| |
| <tr> |
| <td><p>Demonstrate idiosyncrasies, common pitfalls, and capabilities that are not well understood |
| in OpenOffice.org Basic programming. Although the topics are of an advanced nature, they are |
| completely accessible to an absolute beginner, providing new insights into the behavior of |
| macros in OpenOffice.</p> |
| |
| <ul> |
| <li>Introduction |
| <li>Library management |
| <li>Arrays |
| <li>Copy by reference or copy by value |
| <li>Using the Select statement |
| <li>Implementing advanced data structures |
| <li>Using the correct text object |
| <li>Traversing text content in a Write document |
| </ul> |
| |
| </td> |
| </tr> |
| |
| <tr> |
| <td><em>Biography: Andrew Pitonyak is a Lead Software Engineer for Qwest Communications |
| International Inc. He has been using OpenOffice.org since it was StarOffice 5 and he is the author |
| of "Andrew's Macro Document" and "OpenOffice.org Macros Explained". He has a Master of |
| Science degree in computer science and another in mathematics. In his spare time, Andrew |
| participates in the contemporary worship team at church, is a trained Stephen Minister and |
| a professional puppeteer, works on his house, and spends time with his wife. He is an NRA |
| certified firearms instructor, and he holds a General class amateur radio license. Andrew's |
| diverse background allows him to jump with ease between different problem domains.</em> |
| </td> |
| </tr> |
| |
| </table> |
| |
| <p><a href="thursday.html" title="Agenda for Thursday">Back</a></p> |
| |
| <table id="D3" name="D3" summary="" border="1" cellpadding="8" cellspacing="0" bordercolor="#000080"> |
| |
| <tr> |
| <td class="dev"> |
| <strong><a name="D3"></a>The new development process - How Child workspaces will |
| improve the developer experience and the quality (aka How to contribute)</strong> |
| </td> |
| </tr> |
| |
| <tr> |
| <td>Martin Hollmichel <em>Sun Microsystems, Inc.</em></td> |
| </tr> |
| |
| <tr> |
| <td><p>The new OpenOffice.org development process differs in several aspects from usual |
| OpenSource habits of other projects. The session will explain reasons for this differences |
| and also discuss chances and difficulties of having an own development style. In detail we |
| will have a look onto different roles of contributors, especially at the impact of the new |
| development process to core-developer, QA folks and addon-developers.</p> |
| |
| <p>Different kind of contributions can be made to the project, we will cover: </p> |
| |
| <ul> |
| <li>legal aspects |
| <li>access to resources of the Projects (website, IssueTracker, etc) |
| <li>CVS access and branches |
| <li>channels of communication |
| </ul> |
| </td> |
| </tr> |
| |
| <!-- <tr> |
| <td><em>Biography: </em> |
| </td> |
| </tr>--> |
| |
| </table> |
| |
| <p><a href="thursday.html" title="Agenda for Thursday">Back</a></p> |
| |
| <table id="D4" name="D4" summary="" border="1" cellpadding="8" cellspacing="0" bordercolor="#000080"> |
| |
| <tr> |
| <td class="dev"> |
| <strong><a name="D4"></a>Making the source more manageable for new developers</strong> |
| </td> |
| </tr> |
| |
| <tr> |
| <td>Chris Halls <em>The Debian project and Credativ GmbH</em></td> |
| </tr> |
| |
| <tr> |
| <td><p>In the year since the last conference, the project has only attracted a small number |
| of new developers. One of the barriers that prospective new developers face is to try and |
| build OOo for the first time.</p> |
| |
| <p>Although precompiled solver tarballs can help those who do not want to compile the complete |
| suite, the time it takes to download a solver puts many people off. These problems will get |
| worse as the OOo project continues to grow.</p> |
| |
| <p>In this session we will look at ways in which we can reduce the amount of time that developers |
| and translators need to spend on their build environment instead of being productive, such as |
| precompiled tools, providing library development packages and separating translations and |
| other resources from the source code directories.</p> |
| </td> |
| </tr> |
| |
| <tr> |
| <td><em>Biography: Chris Halls is a Debian Developer working as a Linux consultant |
| for Credativ, Germany. He is part of the team that packages OpenOffice.org for the |
| Debian distribution, and also works on the build tools for the main codebase. He is |
| 30, married and is British.</em> |
| </td> |
| </tr> |
| |
| </table> |
| |
| <p><a href="thursday.html" title="Agenda for Thursday">Back</a></p> |
| |
| <table id="D5" name="D5" summary="" border="1" cellpadding="8" cellspacing="0" bordercolor="#000080"> |
| |
| <tr> |
| <td class="dev"> |
| <strong><a name="D5"></a>OpenOffice.org KDE Integration Project</strong> |
| </td> |
| </tr> |
| |
| <tr> |
| <td>Jan Holesovsky <em>SUSE/Novell</em></td> |
| </tr> |
| |
| <tr> |
| <td><p>OpenOffice.org KDE Integration Project aims to provide tight (but optional) integration of the |
| OpenOffice.org to the KDE environment beginning with KDE look and feel and ending with KDE data |
| sources.</p> |
| |
| <p>The project can be divided into its visible and its core part. The visible part includes the KDE-like look |
| and feel, dialogs, etc., the core part focuses on the infrastructure needed for the visible part, and on |
| the KDE data sources. Some of the work (mainly the visible part) is already available as patches to |
| the current OpenOffice.org 1.1.x, other (most of the core part) focuses on the upcoming OOo 2.0. |
| The most important subprojects are:</p> |
| |
| <p>Visible:</p> |
| |
| <ul> |
| <li>"KDE Native Widget Framework" provides the OOo with the look of the |
| theme that the user chose for his KDE desktop. The framework uses the QStyle |
| API to draw its widgets the same way a real KDE/Qt application would. |
| <li>"KDE Icons for OOo" replaces the OOo icons with the default KDE icons (CrystalSVG). |
| <li>"cuckooo" allows OOo to be embedded in the Konqueror window as a read-only KPart |
| so that people could browse to documents recognized by OOo which would open directly |
| in the browser. |
| <li>"KDE File Dialog" replaces the default OOo file dialog with the KDE one. This is |
| work in progress. |
| </ul> |
| |
| <p>Core:</p> |
| |
| <ul> |
| <li>"KDE vclplug" has the goal to get OOo controlled by Qt events and drawn by Qt painting |
| methods instead of pure X calls when running in KDE. It is developed for OOo 2.0 and is still |
| quite experimental. |
| <li>"KIO for OOo" is planned to use the KDE's virtual file system library KIO. The work did |
| not start yet. |
| </ul> |
| |
| <p>This talk will describe the background of the subprojects, and compare the plain OOo with |
| the KDEized one. It will also discuss the current status and the future plans.</p> |
| </td> |
| </tr> |
| |
| <tr> |
| <td><p><em>Biography: Jan Holesovsky works in the SUSE Labs as an OpenOffice.org |
| developer focusing on the KDE integration.</em></p> |
| |
| <p><em>His first Linux experience dates back to 1995. During 1998 and 1999 he was part of a team |
| programming KTTV, an editor of lecture notes for Linux (word processor and vector drawing program) |
| as a school project. In 1999-2002 he worked for SUSE as a YaST2 developer, but he left to finish |
| the school. In 2003 he graduated from the Charles University in Prague with master degree and |
| started with the OpenOffice.org development.</em></p> |
| |
| <p><em>In 2004 he joined SUSE again, this time as the OpenOffice.org developer.</em></p> |
| </td> |
| </tr> |
| |
| </table> |
| |
| <p><a href="thursday.html" title="Agenda for Thursday">Back</a></p> |
| |
| <table id="D6" name="D6" summary="" border="1" cellpadding="8" cellspacing="0" bordercolor="#000080"> |
| |
| <tr> |
| <td class="dev"> |
| <strong><a name="D6"></a>Linux Development Tools</strong> |
| </td> |
| </tr> |
| |
| <tr> |
| <td>Caolán McNamara <em>Desktop Engineer, Red Hat Inc.</em></td> |
| </tr> |
| |
| <tr> |
| <td>A whirlwind tour to the development tools of gdb/oprofile/valgrind/kcachegrind/callcollector |
| /stlport debugmode from the perspective of OpenOffice |
| </td> |
| </tr> |
| |
| <tr> |
| <td><p><em>Biography: </em></p> |
| |
| <ul> |
| <li><em>libwmf, libwv, various MS File Format interoperability interests</em> |
| <li><em>Sun StarOffice Hamburg Jan 2000, MSWord/RTF/etc im/ex</em> |
| <li><em>Red Hat March 2004, Desktop Engineer</em> |
| <li><em>Co-lead sw module</em> |
| </ul> |
| </td> |
| </tr> |
| |
| </table> |
| <p><a href="thursday.html" title="Agenda for Thursday">Back</a></p> |
| |
| <table id="D6" name="D12" summary="" border="1" cellpadding="8" cellspacing="0" bordercolor="#000080"> |
| |
| <tr> |
| <td class="dev"> |
| <strong><a name="D12"></a>QA at OpenOffice.org</strong> |
| </td> |
| </tr> |
| |
| <tr> |
| <td>Joost Andrae / Jörg Sievers <em>Sun Microsystem, Inc.</em> |
| </td> |
| </tr> |
| |
| <tr> |
| <td> |
| <p> |
| In the first part we will hear about the contributions |
| from members of the QA project. |
| <ul> |
| <li>confirming issues |
| <li>available types of OpenOffice.org automation |
| <li>doing localization QA |
| <li>working together with OpenOffice.org port contributors |
| </ul> |
| Additional topics will cover |
| <ul> |
| <li>Statistics about the QA team |
| <li>Statistics about OpenOffice.org (IssueTracker statistics) |
| <li>About IssueTracker keywords |
| <li>writing and using testplans |
| <li>Releases |
| <li>Developer Builds |
| <li>QA events (bug day events, discussion about timezones, using IRC) |
| </ul> |
| </p> |
| <p> |
| The second part gives an introduction in Automated GUI Testing. |
| "How can the new port be tested" is often the first question |
| after a successful build. |
| The 'qa/qatesttool'- project is using the TestTool binary with |
| its own environment to test the "front side" - the GUI - of OOo |
| on many platforms.<br> |
| This part of the session describes how and where to start |
| with automated [GUI] testing of OOo. Using the |
| 'TestTool Environment' is simple but writing own |
| testcases is also easy with littlet BASIC skills and some |
| knowledge about the 'TestTool Environment'. |
| </p> |
| </td> |
| </tr> |
| |
| <tr> |
| <!-- |
| <td><p><em>Biography: </em></p> |
| <ul> |
| <li><em>libwmf, libwv, various MS File Format interoperability interests</em> |
| <li><em>Sun StarOffice Hamburg Jan 2000, MSWord/RTF/etc im/ex</em> |
| <li><em>Red Hat March 2004, Desktop Engineer</em> |
| <li><em>Co-lead sw module</em> |
| </ul> |
| </td> |
| --> |
| </tr> |
| |
| </table> |
| </td> |
| </tr> |
| </table> |
| |
| <hr /> |
| |
| <p><a href="thursday.html">Back to Thursday</a><br /> |
| <a href="#top">Back to Top</a><br /> |
| <!-- <a href="agenda2.html">Back to Overview</a></p>--> |
| |
| <p>Please Note: Program content subject to change.</p> |
| |
| |
| </div> |
| <!--#include virtual="/footer.html" --> |
| </body> |
| </html> |