Apache OpenOffice Wiki - User contributions [en]

Summer of Code 2006

2006-05-05T19:52:31Z

Rauterkus: tiny edits

=='''OpenOffice.org Summer of Code Projects'''==

OpenOffice.org is proud to participate in the [http://code.google.com/soc/ Summer of Code] initiative sponsored by Google. Some suitable suggestions are listed below. Ideas for other tasks can be sent to related developer [http://projects.openoffice.org/accepted.html OpenOffice.org project] or contact the project lead.

We would be glad to support a few projects. Mentoring capacities are limited. So we depend on your dedication during the preparation of the detailed specification and description of the outcome.

The application period is May 1 - May 8, 2006. But keep in mind that it may need some prearrangement before you are ready to [http://code.google.com/soc/student_step1.html sign up] and apply.

For further general questions about the initiative Google prepared FAQs for [http://code.google.com/soc/studentfaq.html students] and [http://code.google.com/soc/mentorfaq.html mentors].

[[Image:Bnr_soc_125x58.gif|right|SoC 2006 Logo]]

__TOC__

==API / Programmability==

===Programmability: Dynamic IDL-Referenz-Browser===

The OpenOffice.org API is specified in IDL (Interface Definition Language). IDL allows a language independent description of the API and language bindings/bridges allows the use of the same API from various languages where exactly such a language binding/bridge exists.
But often it is difficult for users of the API to map the language independent IDL reference documentation to their preferred and used programming language, e.g. Java or StarBasic. But exactly this would speed up their daily work, a Java programmer would like to have a Javadoc like reference of the API. The idea of a “Dynamic IDL Reference Browser” is to develop a new concept for documenting IDL types in XML and a concept to provide a dynamically created representation for different languages.
That means in detail that the reference browser would dynamically create a piece of XML code from the IDL definition and the provided XML documentation string for the IDL type. An appropriate XSL transformation would convert the XML representation into the required language representation. For example a Java developer gets the correct Java mapping for an IDL interface type.
The dynamically approach has the advantage that we can (in a second step) analyze the navigation path to a type and can show context specific documentation. That can be very useful for generic types which have different meanings in different contexts. For example a return type of a generic type XEnumeration from function F of interface X. The generated documentation for XEnumeration would show exactly the info which is necessary to understand and use XEnumeration in the context of function F from interface X. It shows for example that the enumeration in this context always contains objects of type Y and even more information for more complex context dependent information.

* required skills/knowledge: Java, XML, XSLT

; Contact
: dev@api.openoffice.org
: Juergen.Schmidt at sun.com

===Basic IDE: BASIC/UNO Object Browser===

Target of this project is to create an UI component that allows to browse through the structure of UNO objects.
Unlike the Basic IDE watch window that recently has been improved to display object properties and their values in an reasonable way the object browser should show the objects' API structure (properties, methods, interfaces, services).
It has to be specified if this should refer to the Basic API view (Basic types, no explicit distinction of different interfaces) or the UNO view (UNO types, interface oriented) or if the browser should support two modes allowing to switch between Basic and UNO view. A Basic view is more challenging because it requires Basic related knowledge and probably new functionality in the Basic project.
Actually the component is more like a type browser as the objects' static class/interface structure should be displayed, but unfortunately most information are only available for a "living" object using the XtypeProvider interface and the Reflection and Introspection API. Nevertheless it would also make sense to support types directly, e.g. to show the new style UNO service / multi inheritance interfaces.

* required skills/knowledge: Java, C++, StarBASIC, UNO

; Contact
: dev@api.openoffice.org
: Andreas.Bregas at sun.com

==[http://bibliographic.openoffice.org/ Bibliographic]==

===Basic Citation Enhancements===
'''Priority:''' Critical '''Difficulty:''' medium-high

The bibliographic facility on Openoffice needs considerable enhancement to make it competitive with other bibliographic applications. This is a vital task in the enhancement project.

The task is to implement the most basic changes and additions to the Writer core code (the [http://api.openoffice.org/API API] basic code, and [http://udk.openoffice.org UNO] mappings) necessary to implement basic support for:

* code to read and write the new, and much improved, citation format (A developer - CPH has already made good progress with this). See [[New_Citation_XML_info_design_and_implementation | Citation XML info design and implementation ]] and [[Citeproc_Writer_Interaction | implementation discussion]].
* exposing the new code though UNO
* Write a simple program in OOo Basic or Python to demonstrate the new UNO functions by Inserting and displaying the enhanced citations in Writer using the new format.

See our [[Bibliographic_Project's_Developer_Page | Developer's Page]] and Florien's [http://blogs.sun.com/roller/page/flo?entry=the_community_and_me_the blog entry] on this topic.

* required skills/knowledge: good C++ programming skills.
* required skills/knowledge: experience with Object Oriented Technologies such as COM/COM+/DCOM and Corba.
* required skills/knowledge: some knowledge of, or ability to quickly utilise, the Openoffice API and UNO
* required skills/knowledge: able to write a small OOo basic program.
'''Contact'''

[[SOC_Draft_tasks#Applying.2C_suggestions | Application advice]] dev@bibliographic.openoffice.org

David Wilson (dnw at openoffice.org),
Florian Reuter (Florian.Reuter at sun.com)

===Convert the Citeproc Bibliographic Formatting Engine to Python or C++===
'''Priority:''' Important '''Difficulty:''' medium

The new Bibliographic formatting engine, [http://bibliographic.openoffice.org/citeproc/index.html Citeproc], currently exists as a set of XSLT 2.0 stylesheets. In addition, a Ruby [[Bibliographic_Project's_Developer_Page#Formating_Engine | prototype]] has been started. The formatting engine needs to be re-written in C++ or Python (although ultimately to be C++) and then integrated into OOo, though the [http://udk.openoffice.org UNO] bridge and the OOo add-on package manager.

The developer will need to test the coding by calling the formatting engine from within Writer (using OOo Basic), and passing a list of citation reference IDs to the Citeproc and returning the formatted citation text and inserting it into Writer.

If possible, it would be great if the developer could also utilise the [[Bibliographic_Project's_Developer_Page#New_Citation_Coding | new internal citation structures]] being developed for Writer for the demonstration.

See our [[Bibliographic_Project's_Developer_Page | Developer's Page]] and this [[Current_Implementation_of_the_OpenOffice.org_Bibliographic_Component | article]]

* required skills/knowledge: good C++ or Python programming skills.
'''Contact'''

[[SOC_Draft_tasks#Applying.2C_suggestions | Application advice]] dev@bibliographic.openoffice.org

David Wilson (dnw at openoffice.org)

===Develop a Bibliographic Database design and implement a Ruby On Rails prototype===
'''Priority:''' Important '''Difficulty:''' medium

Assist is the development of of a [[Bibliographic_Database | Bibliographic Database]] and build a [http://www.rubyonrails.org/ Ruby On Rails] database management system with Browse, Add, Delete and Edit functions.

OOo Bibliographic project Leader, Bruce D'Arcus, has started working on database designs and now needs a skilled database designer to take on this task. The person would preferably have some Ruby on Rails exposure.

See our [[Bibliographic_Project's_Developer_Page | developer's wiki page]]

* required skills/knowledge: strong Database design.
* required skills/knowledge: Ruby On Rails exposure.
'''Contact'''

[[SOC_Draft_tasks#Applying.2C_suggestions | Application advice]] dev@bibliographic.openoffice.org

David Wilson (dnw at openoffice.org)

==Calc==

===Calc: Show formula syntax in tip help===

When a cell formula is being edited, in addition to the function selection above the cell, show some input hints (like the syntax of the function that is edited) in a tip help window below the cell.

* required skills/knowledge: good C++ expertise
* recommended skills/knowledge: -

; Contact
: dev@sc.openoffice.org
: Niklas.Nebel at sun.com

===Calc: Add resizeable margin on page preview===

In the page preview, add the possibility to interactively change page margins by dragging an indicator, instead of using the page style dialog (see http://www.openoffice.org/issues/show_bug.cgi?id=51656).

* required skills/knowledge: good C++ expertise
* recommended skills/knowledge: -

; Contact
: dev@sc.openoffice.org
: Niklas.Nebel at sun.com

===Calc: Extend non-linear optimiser in spreadsheet (solver)===

Improve the solver component for Calc
Kohei Yoshida has written a basic 'Solver' component for Calc
which handles simple linear and non-linear optimisations of
spreadsheet content. It would be useful to extend the set of
optimisers to be faster and more stable. Finding appropropriately
licensed libraries would be ideal, although some candidates may be
interested in creating new analytics. This will be an ongoing
project, so the preference will be towards maintainable, documented
code rather than hard core performance.

Developers should be able to build OOo and have a
background in numeric
optimisation.

Skills: C++, Numeric Analysis

; Contact
: dev@sc.openoffice.org
: Jody Goldberg <jodygoldberg@openoffice.org>
: Kohei Yoshida <kohei@openoffice.org>

==Database Access==

===Linking external text tables into OOo databases===

Native OOo Base databases (.odb) use the HSQLDB (http://hsqldb.org/)
database engine. HSQLDB features a mechanism to link external text
tables into the database, as if they were a native HSQL table
(http://hsqldb.org/doc/guide/ch06.html).

The task of this project is to bring this feature to OpenOffice.org. For
this, the respective database driver of OOo Base has to be extended with
an API to administrate such text table links. Additionally, an user
interface needs to be designed and implemented for using this API.

* required skills/knowledge: C++, relational database concepts
* recommended skills/knowledge: OOo's component technology (UNO)
* useful skills/knowledge: HSQLDB text table concepts

; Contact
: dev@dba.openoffice.org
: Frank.Schoenheit at Sun.COM

===Native SQLite driver===

SQLite (http://www.sqlite.org/) is a SQL database used as lean backend
in a number of applications. The task is to write a native SDBC database
driver (resp. finalize the existing skeleton:
http://dba.openoffice.org/drivers/sqlite/index.html) for OpenOffice.org,
accessing SQLite files efficiently.

* required skills/knowledge: C++, relational database concepts
* recommended skills/knowledge: SQLite API
* useful skills/knowledge: OOo's component technology (UNO)

; Contact
: dev@dba.openoffice.org
: Ocke.Janssen at Sun.COM

===Embed Derby into OpenOffice.org databases===

OpenOffice.org Base features an abstract mechanism to embed database
backend files into OOo databases (.odb). Currently, this is implemented
for HSQLDB (http:///hsqldb.org), which is used as OOo's default database
engine.

To allow this feature for other engines, one must:
* virtualize the engine's file access, so that it re-routes all its file operations through an abstract API.
* implement this API on the OOo Base side

The project is to do those implementations for Apache Derby database (http://db.apache.org/derby/).

* required skills/knowledge: C++
* recommended skills/knowledge: relational database concepts
* useful skills/knowledge: OOo's component technology (UNO)

; Contact
: dev@dba.openoffice.org
: Ocke.Janssen at Sun.COM

===Database driver UI modularization===

OpenOffice.org Base follows a component-oriented approach for enabling
database access. For this, database drivers are installed in
OpenOffice.org which provide access to a certain (class of) database(s).

While at the driver level, the implementation is pretty good
modularized, the UI implementation can be improved. Currently, there are
a lot of places in the code with hard-coded information, such as
"database X requires UI option Y".

The goal of this project is to design and implement a reasonable
architecture for bringing a driver to the UI. The existing
implementation needs to be migrated to this new architecture. As a proof
of concept, an existing currently-external driver (e.g.
http://dba.openoffice.org/drivers/postgresql/index.html) should be
modified so that it can be deployed into an OOo installation and makes
use of the features of the new architecture.

* required skills/knowledge: C++
* recommended skills/knowledge: OOo's component technology (UNO)
* useful skills/knowledge: OOo's configuration concepts

; Contact
: dev@dba.openoffice.org
: Frank.Schoenheit at Sun.COM

===HSQLDB: single-file backend===

HSQLDB (http:///hsqldb.org) is the database engine used by OpenOffice.org.

HSQL currently creates a number of adjacent files to store its data,
where all files together comprise the whole database. To allow the user
of OpenOffice.org Base to have a "all-in-one-file" database experience,
those HSQL files are currently embedded in some OOo-specific
container-file (the .odb file).

To overcome various disadvantages of this approach, it is desirable that
HSQL stores its data in a single, large file. Preliminary code and
concepts exist for this, but no final implementation.

This project needs to be worked on in close collaboration with the
HSQLDB project, whose owner, Fred Toussi, will act as co-mentor.

* required skills/knowledge: good Java expertise, relational databases
* recommended skills/knowledge: HSQLDB architecture

<hr/>

''The following project description was provided by Fred Toussi, HSQLDB project owner:''

Currently, HSQLDB stores the database information in four separate files. These files are written to using different API’s. Streams are used for some while random access is used for others.

The project’s aim is to allow a single file to be used for all permanent data (temporary session data, or file locking may still use a separate file). So existing files that need to be integrated into one are the .properties, .log, .data and .backup files. The new single file will be accessed only as a random access file.

The project consists of developing an interface between exsisting code. At the low level, there is already an implementation of a random access file, org.hsqldb.persist.ScaledRAFile. The new interfaces will allow existing file services to use the single random access file.

All the files in the org.hsqldb.persist package should be studied, with the understanding that the funtionality of many of these files, including lock and property saving functionality, will become redundant with the introduction of single file persistence.

The student is expected to study and become proficient in the Java IO packages and the API calls to these packages currently made from HSQLDB, and write the code and test packages.

The mentor will provide regular guidance and help on the design of required interfaces and supervise their implementation.

As this is considered an essential development for HSQLDB, all the work done by the student will be used, and if necessary, modified or improved by other project developers. The student will get due credit and will be provided with work references by the HSQLDB Project Maintainer upon successful completion of the project.

<hr/>

; Contact
: dev@dba.openoffice.org
: Frank.Schoenheit at Sun.COM

===HSQLDB: editable views===

[http:///hsqldb.org HSQLDB], used as OpenOffice.org's database engine, features the usage of views (basically, stored SQL queries).

An advantage of views over queries is that the former can be re-used in other queries, i.e. you can do a <code>SELECT * FROM foo</code> where <code>foo</code> is the name of an existing view, i.e. a <code>SELECT</code> statement itself.

A disadvantage of views is that the constituting statement cannot be edited once the view has been created.

Goal of this project is to provide a "Edit view" functionality in OpenOffice.org Base, for the moment for the HSQLDB backend only.
For this, an API needs to be defined which allows editing views. This API has to be implemented in Base' dedicated HSQLDB driver. Additionally, the user interface should respect the existence of this API by offering an "Edit View" item in the context menu of views. Once chosen, Base' query designer is to be started, to modify the SQL statement constituting the view. Saving the work in the designer should change the view's underlying statement.

* required skills/knowledge: C++
* recommended skills/knowledge: OpenOffice.org's component model (UNO)

; Contact
: dev@dba.openoffice.org
: Frank.Schoenheit at Sun.COM

==Distribution==

===Download / Mirror Management Tool: Bouncer===

We made the first steps to use bouncer for OpenOffice.org download and mirror management. This tool developed at the [http://wiki.osuosl.org/display/LNX/Google+Summer+of+Code+2006+Ideas Oregon State University Open Source Lab] would significantly ease the handling of download pages.
There are some crucial features open for [http://wiki.osuosl.org/display/Bouncer/Bouncer+3 Bouncer v3] you could help to finalize.

; Contact
: mirrors@distribution.openoffice.org
: [http://morgamic.com/ Mike Morgan] and [http://osuosl.org/Members/lars/ Lars Lohn]

==Framework==

===Performance: Fast native implemented OOo Dispatch Loader===

Implementing a faster small Office Loader, independent from OOo libraries that uses native APIs to show the splashscreen. This will speed up UI response time after first Office start by 90 percent.
Implementing propagation of command line parameters with a native pipe implementation. This will speed up loading of documents after double clicking them in the OS desktop environment.
Remove any dependency to OOo libraries from the loader code, so that it is implemented with native APIs only. This allows the loader to be as small as possible and to run without any bootstrapping. This will reduce I/O overhead and unnecessary code execution at startup.
Adjust the pipe implementation in desktop module to fit the native pipe implementations
Prototypes of a Loader for Windows and Linux are available, implementing the required features at least on one platform.

; Contact
: dev@framework.openoffice.org
: Hennes.Rohling at sun.com

==Graphics==

===Filter: creating a Visio filter for OOo Draw===

OOo currently lacks support for a Visio import
filter, so that it would be good to have someone
starting to write such a filter from scratch
utilizing the OOo API for direct creation of the
document or the ODF format as input format to
be loaded by the OOo application. Although
a full blown filter seems to be unrealistic
to be written within the short timeframe, large
parts of Visio documents should be able to be
filtered correctly.

* required skills/knowledge: good C++ expertise, graphics programming
* recommended skills/knowledge: Visio file format / ODF or OOo API

; Contact
: dev@graphics.openoffice.org
: Sven.Jacobi at Sun.COM

===GSL: Port Cairo Canvas to Win32===

Cairo canvas is an OpenOffice.org canvas backend, which provides
beautiful anti-aliased rendering functionality using the 'cairo'
library. Today the cairo canvas backend works only on u*ix systems.
The objective is to allow OpenOffice.org to use cairo on win32. Cairo already
targets win32, and using it would give a faster, more beautiful
slide-show experience.

Building OOo on Win32 is moderately painful, requiring a VC++.Net 2003
compiler, although it's possible that (with some extra work) the (free)
VC++ Express Edition could be used.

* Skills: C, C++, cygwin, Win32 compiling

; Contact
: dev@gsl.openoffice.org
: Radek Doulik (radekdoulik at openoffice.org)

==Stats==

===Source Code Repository Activity===

Provide statistics for CVS repository activity. The first step would be a quick analyse what type of statistics other projects are providing. Together with our requirement to better understand how the code base and groups of committers are evolving this should give input to start work on the preparation of some nice stats and graphs about repository activity. Results should be generated with open-source tools, automatically and on a regular basis for the http://stats.openoffice.org website. Additionally an interface to [http://cia.navi.cx cia] would be helpful.

; Contact
: dev@stats.openoffice.org
: Stefan Taxhet (stefan.taxhet at sun.com)

== Tools ==

===Integrating Autodoc generated IDL documentation into the Visual .NET IDE===

; Background

Autodoc (http://tools.openoffice.org), the OpenOffice.org (http://www.OpenOffice.org) documentation parser, creates a series of HTML documentation pages out of the SDK IDL files (see http://api.openoffice.org/docs/common/ref/com/sun/star/module-ix.html).
The generated documentation can be integrated for example into Netbeans. “Integrated” means that from that IDE (integrated development environment) the documentation is accessible via internal indexes and/or context sensitive help. It would be useful to be able to integrate it also into other much used development environments, for example the Visual .NET IDE.
Integration into the Visual .NET IDE can be done by providing some additional files that match the MS Help 2.0 format (see http://www.helpware.net/mshelp2/h20.htm for some information).

; Task

# Enable Autodoc to provide the additionally needed files to integrate the created documentation into the Visual .NET IDE.
# Document the mechanism to compile those files and make the Autodoc generated documentation visible within the IDE.

; Skills

* Needed: Good C++.
* Helpful: Knowledge about the OpenOffice.org SDK, experience with an IDE.

; Contact
: dev@tools.openoffice.org
: Nikolai.Pretzell at sun.com

==Writer==

===Writer: Improved Lotus WordPro Import Filter===

Currently there is a very basic import filter for WordPro that only
imports pure text. It would be desirable to import more content and
structure from WordPro documents.

; Contact
: dev@sw.openoffice.org
: Oliver.Specht at sun.com

===Writer: Component for guessing the language of a text===

Currently the OOo spell checker tries to guess the language of a text
with an unknown word by searching for it in a fixed number of
dictionaries or thesauri because checking all available languages would
be too much. This limited search is inconvenient if the used language is
not amongst the preselected ones. There are already known heuristic
approaches to guess the possible language of a text, some of them are
available as descriptions, some even as source code. Integrating such a
component into OOo would improve working in multi language documents.

(Possibly useful references: [http://chardet.feedparser.org/ #1], [http://www.mozilla.org/projects/intl/UniversalCharsetDetection.html #2])

; Contact
: dev@sw.openoffice.org
: Thomas.Lange at sun.com

===Writer: Import Filter for Word Perfect Graphics files===

The writerperfect import filter for WordPerfect(tm) documents, based on libwpd (http://libwpd.sourceforge.net), was integrated into the OOo2.0.
The libwpd is a standalone library also used by other projects like KOffice or AbiWord. Another standalone library that reads WordPerfect graphics files would improve the interoperability with the WordPerfect
Office Suite. An import filter for this file format based on this new standalone library can become embedded into OOo in the same way as libwpd. Please find more information at
http://fridrich.blogspot.com/2006/04/wordperfect-graphics-conversion-wants.html." The base for this work will be the, already existing, even though unreleased, code of libwpg library (http://sourceforge.net/projects/libwpg)

;Skills
* Being highly comfortable developping using C++ and Standard Template Library. Have in mind that the code has to be strictly portable.
* Not need of knowing the OpenOffice.org API

;Some hints about possible tasks
#Convert all vector graphics records of WPG2 format. It is already done for WPG1 and it works quite correctly (some problems with colours due to an undocumented record, but fixable since we have a kind of documentation now).
#The parameters of the API callbacks should be as close as possible following the SVG properties for a given object (ellipse, circle, path, ...). So that one can use the <code>wpg2svg</code> to visualize instantly the conversion result. And like that, it will be easier to use the libwpg library with another libraries that render SVG, i.e. librsvg. And, last but not least, the converter code could be than used with anything that generates SVG.
#Still maintain <code>wpg2raw</code> in order to be able to create a regression test suite.
#Create a <code>wpg2odg</code> converter which outputs SAX messages in odg format (handler independent) + write two handlers (very trivial), one for dumping the content.xml into stdout and other for writing a zipped odg file. Because of the OOo document handler, everything should be preferably contained in one single flat <code>content.xml</code> including styles and metadata if converted. One can use <code>styles.xml</code> in the handler that writes the zipped file if we need to set some default styles for third party applications as we do it in the wannabe KWord import filter and in the CVS version of <code>wpd2sxw</code>.
#Abstract the stream implementation inside libwpg and make the odg filter core not depend on any specific stream abstaction layer. Only the handlers. Write a sample input stream implementation class using C++ STL input stream classes (get rid of dependency on libgsf).

If this is done in short time, the following things could be done, but optional:
#Rewrite the libwpg API so that it is breakage proof like libwpd is currently, possibly using libwpd's public API (<code>WPXProperty</code>, <code>WPXPropertyList</code>, <code>WPXPropertyListVector</code> and <code>WPXString</code>). Or extend the libwpd's API if the original one is not corresponding to our needs (i.e. the SVG property <code>points="X1,Y1 X2,Y2 ... Xn,Yn"</code> could be a problem).
#Convert text strings.
#Find a way to extract the bitmap part of WPG2, decode it (run-length encoding) convert it to some simple raster format (*.bmp ???) and add it [maybe base64 encoded] into the resulting xml.

;Practical guidelines
#For a nice integration with OO.o, no STL types should appear in the API. Many distributions use OO.o built against system libraries and OO.o uses internally stlport. STL and stlport types do not have the same signatures, so bad bad if one links a library compiled using STL from inside OO.o build environment.
#Put the libwpg API in a separate namespace in order to avoid possible conflicts with whatever other library OO.o could use.
#Avoid completely "<code>using namespace std</code>" statement, since it is possible that it will have problems with one or other of the compilers on one of OO.o platforms.

; Contact
: dev@wp.openoffice.org
: Fridrich Strba (fridrich_strba at openoffice dot org)

===Writer: iWork 'Pages' importer===

The Apple iWork 'Pages' product stores its files in a .zip file,
using an XML format. It would be simple enough to parse this and
import at least some of the information: at a minimum raw text, simple
styles, tables and images.

There is some documentation for the Apple format at:
http://developer.apple.com/documentation/AppleApplications/Conceptual/iWork2-0_XML/index.html
and we can ask for more information where necessary. It would be
necessary for the applicant to have a copy of Pages to generate &
compare test files.

Skills: C++, XML

;Contact
: dev@sw.openoffice.org
: Michael Meeks (mmeeks at openoffice.org)
: Svante Schubert (Svante.Schubert at Sun.com)

==Porting==

===Porting: Integrate the native Mac OS X FilePicker into OpenOffice.org (Aqua/X11)===

Concerns : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions)

Integrate the native Mac OS X FilePicker into OpenOffice.org
The OOo FilePicker is already designed as a UNO component. What is needed is a new implementation of the FilePicker component based on the native Mac OS X FilePicker as it has been done on MS Windows for instance. On current Mac OS X port of OpenOffice.org, the current FilePicker is not native, less ergonomic.

Possible tasks :

Familiarize with the native Mac OS X FilePicker API and the OOo UNO interfaces for the FilePicker
Describe current implementation : design, concerned modules, isolate classes and parameters to manage
propose a new design using Apple API
write and test a proof of concept

* Skills : knowledge of languages C / C++ , using Carbon/Cocoa API
* Proposed by : Tino Rachui

; Contact
: dev@porting.openoffice.org
: Tino Rachui ( Tino dot Rachui at Sun dot COM )

===Porting: Integrate OpenOffice.org help into Mac OS X help center (Aqua/X11)===

The OpenOffice.org help system is quite independent of the
underlying operating system and thus doesn't integrate well into
the help system on Mac OS X.

Possible tasks:

Learn how help system works in OpenOffice.org and how you can call it

Create sample help book for Apple Help

Prepare conversion framework for current XML/HTML based help pages to help book

Integrate provided solution into Openoffice.org CVS

* Skills: C/C++, XML/XSLT, Carbon API
* Proposed by: Pavel Janík

; Contact
: dev@porting.openoffice.org
: Pavel Janík ( Pavel at Janik dot cz )
: Frank Peters (Frank dot Thomas dot Peters at Sun dot COM)

===Porting : Mac OS X Address book integration (Aqua / X11) ===

Synopsis:
OOo currently is integrated with the Mozilla address book but not with the native Mac OS X address book. This is annoying for Mac OS X user. For better system integration it would be desirable to integrate with the Mac OS X address book.

Concerns: OpenOffice.org 2.x for Mac OS X (both Aqua and X11 versions)

Skills: Knowledge of languages C/C++, Mac OS X APIs and Application frameworks like Carbon or Cocoa for instance, knowledge of the Mac OS X address book APIs

Tasks:
Familiarize with the Mac OS X address book API's
Familiarize with the current OOo Mozilla address book integration
Make a prototype for OOo Mac OS X address book integration

; Contact
: dev@porting.openoffice.org
: Oliver Braun ( obrmac at openoffice dot org )
: Frank Schoenheit ( Frank dot Schoenheit at Sun.COM )

===Porting: Implement native font support, using native Apple API (Aqua / X11)===

Does concern : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions)

Subject proposed by : none yet

Tasks :

(1) analyze current implementation : design, concerned modules, isolate classes and parameters

(2) propose a design for the new one, using Apple API

(3) write and test a proof of concept

If enough time: (4) implement the solution, with possible backport to X11 version.

* Skills : knowledge of languages C / C++ , using Carbon/Cocoa API, knowledge of font systems and font technology

; Contact
: dev@porting.openoffice.org
: Eric Bachard (ericb at openoffice dot org)

===Porting : Mac OS X Spell checker integration (Aqua / X11)===

Synopsis:
OOo currently uses aspell or hunspell as spell checking components. Mac OS X comes with a build-in spell checker, which should be used by OOo for consitancy reasons, i.e. to save the user from having to maintain two dictionaries (OOo/OS X) in parallel.

Concerns: OpenOffice.org 2.x for Mac OS X (both Aqua and X11 versions)

Skills: Knowledge of languages C/C++/Objective C or Java, Mac OS X APIs and Application frameworks like Carbon or Cocoa for instance, knowledge of the Mac OS X spell checking APIs

Tasks:
Familiarize with the Mac OS X spell checking API's
Familiarize with the way OOo utilizes spell checkers
Make a prototype for OOo Mac OS X spell checker integration

; Contact
: dev@porting.openoffice.org
: Oliver Braun ( obrmac at openoffice dot org )
: Thomas Lange ( Thomas dot Lange at Sun.COM )

== QA ==

=== Release QA Tracking Tool ===

Tracking a release with dozens of languages and several platforms can be tedious. This is especially the case if the only used tool is a manually maintained table with colors indicating the status.

A web based tool should help us to keep track of the location and status of the builds as well as the responsible contact. The [http://qa.openoffice.org/localized/index.html workflow] in place should be supported. The tool should provide an [http://qa.openoffice.org/localized/status.html overview], the means to maintain a release including easy status manipulations.

; Contact
: dev@qa.openoffice.org
: Andre Schnabel (Andre.Schnabel at gmx.net)

=== Testtool Result Tracking Tool ===

Many of the QA team members are running automated tests for several releases, snapshots ... Every release should have successfully passed a number of tests. At the moment it is almost impossible to tell, what scripts have been run and what the results have been.

An online database could be of help here. The idea is to send the resultfiles (or an extract of the results) to this database, so they can be collected and analyzed.

A browser based frontend could help us to keep track of the testtool results.

; Contact
: dev@qa.openoffice.org
: André Schnabel (Andre.Schnabel at gmx.net)
: Helge Delfs (Helge.Delfs at Sun.COM)

==VBA interop: Chart API==

OpenOffice.org has Excel VBA interoperability support under development,
with some exciting preliminary results (see eg. [http://www.gnome.org/~michael/hypocycloid.jpeg here])
The work is essentially creating and extending simple mapping layers
between new VBA compatible object model APIs and the existing OOo UNO
APIs (using UNO).

A significant missing piece here is the Shape API (of which Charting
is an extension). Samples of existing wrappers for other objects can be
found here: http://go-oo.org/ooo-build/scratch/sc-vba/ and
http://go-oo.org/ooo-build/scratch/offapi-vba/

* Skills: C++, Basic/VBA, [UNO]

; Contact
: dev at graphics.openoffice.org
: Noel Power <npower at openoffice.org>

----

==OOo Project==

===SoC Sample Suggestion Title===

Description

; Contact
: list@project
: Contact Person (email at domain)

FAQ

2006-01-31T21:45:52Z

Rauterkus: /* Where can I suggest ideas for what OpenOffice.org should do and what I don't/do like about it? */

So no-one ever asked me these, I just made them up to astro-turf
a bit (safer, wipe-clean, more durable questions).


== Why do branches like 'mws_srx645' have odd numbers in them ? ==


By consulting various oracles, entrails etc. it transpires that
in theory this number once incremented weekly, there being weekly
freezes and hence solvers, development environments.
The 'mws' stands for 'Master Workspace'. The latest 2.0 development
is done with the SRC680 stem; with auto-incrementing milestones; hence
tags like <code>SRC680_m66</code> would be common.


== Why does XYZ require Java ? up-stream/Sun are so evil !? ==

Nah up-stream just use the best tool to hand, and have a different set world-view to you, where Java is an engineering solution to their cross platform problems. By using Java StarDivision can avoid having to re-invent and then maintain an essentially competing cross-platform layer. There is no malice here whatsoever; just pragmatic engineering from a different perspective.

See [[Java and OpenOffice.org]]

== Why is [t]csh so broken ? ==


This is rather inscrutable; some particularly curious brokenness
would be the way piping commands on stdin is crucially different
to inputting them from the tty thus:
<code>echo 'echo #define DLL_NAME "libsch641li.so" >./foo.hxx' | /bin/tcsh -s</code>
fails to do anything whereas typing the same thing into the shell
works just fine. Even more oddly:
<code>tcsh -fc 'echo #define DLL_NAME "libsch641li.so" >./foo.hxx'</code>
does do the right thing. See also [http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/ csh].


== I just tried to re-locate the build, why doesn't it work ? ==


The simple answer is: you need to run <code>relocate /path/to/new/build</code>;
another more complex answer is:


Well, assuming you have re-configured things (LinuxIntelEnv.Set will
need paths tweaking too — and re-importing to your shell) — then it's most
likely down to the ubiquitous non-relative paths, coded in lots
of generated / built files, particularly '.dpc*' (dependency)
files. Try:
<code>find -name '*.dpc*' -exec rm {} \;</code>


The stlport does some really broken things, so
you will also need to edit the 'stl_gcc.h' inside the solver/, and replace the
two path instances there (see inc/stl/config/stl_gcc.h).


== CVS says 'Fatal Error aborting. [acc] no such user', why ? ==


While of course it's possible that your user name is not registered; often
this just means your ~/.cvspass got lost and/or that you haven't logged in.
cvs login, and repeat the command.


== What does '.pro' in 'unxlngi4.pro' mean ? ==


Product — isn't it obvious ?


== What does OpenOffice really look like ? ==


Today I found a photograph of it on my system, so I stuck it in here:


http://go-oo.org/images/layers.png Abstraction Layers

This diagram is superb but, what does each acronym mean? (ie, GO search don't find it and guessing could be wrongly)

== How do I take a screenshot of OO.o ? ==

OOo does some very odd things with X resources, thus some conventional
screenshot apps fail to take accurate shots. ImageMagick's 'import'
however does a good job; use:
<code>import foo.png</code> from the console, or
<code>sleep 2; import -window root foo.png</code> instead.
NB. unless you want your world to look tiny, you need to turn large
toolbar icons first.


== Why does the code look so ugly? ==

The authors must be using a really strange editor.
It thinks tab stops are on every fourth column.
Of course, the files come out ugly in Unix editors which know
that tabs are eight characters wide.


If you happen to use
[http://www.gnu.org/software/emacs/ a Real Editor],
we have some pink glasses to sell to you. Paste the contents of
[http://go-ooo.org/emacs.el] into your <tt>.emacs</tt>,
or load it with a line like this: <tt>(load "/path/to/that/file.el")</tt>.
Don't forget to adapt <tt>my-openoffice-path-regexp</tt> to your needs.


Henceforth emacs will use 4-column tabs for your OOo source files.
(And use C++-Mode for <tt>sdi</tt>-, <tt>hrc</tt>-,
and <tt>src</tt>-files.) Alternatively if you are sufficiently set in
your ways that you can't cope with investing these few seconds do:
<code>M-x set-variable\ntab-width 4</code> & learn to love change.


Apparently if you use vi you can do: <code>:set ts=4 sw=4</code>, and
good luck to you. For a better vim, use <code>:set ts=4 sw=4 et</code> to also expand tabs to spaces, as this is what new code should use.


== Where can I suggest ideas for what OpenOffice.org should do and what I don't/do like about it? ==
''Awaiting an answer from a kind contributor.''

== How can OOo be used to author wiki pages at a MediaWiki site?==
''Awaiting an answer from a kind contributor.''

== Can the content of a MediaWiki hosted wiki be exported into OOo? ==
''Awaiting an answer from a kind contributor.''

The dream idea is to take a complete wiki and flow it into a filter so that it can be exported into a series of OOo documents, or one larger OOo document. This would allow writters to start a wiki and then finish with a book.

== How can OOo be used to author blog pages at a Blogspot.com hosted site? ==
A filter exists for MS Word users to write blog articles -- and then upload the content to the blog easily.
''Awaiting an answer from a kind contributor.''

== See also ==

* [[CvsFAQ]] - for CVS problems
* [[OOo_Ergonomics]] - why is it so painful to use ?

FAQ

2006-01-31T21:42:17Z

Rauterkus: /* Where can I suggest ideas for what Open office should do and what I don't/do like about it? */

So no-one ever asked me these, I just made them up to astro-turf
a bit (safer, wipe-clean, more durable questions).


== Why do branches like 'mws_srx645' have odd numbers in them ? ==


By consulting various oracles, entrails etc. it transpires that
in theory this number once incremented weekly, there being weekly
freezes and hence solvers, development environments.
The 'mws' stands for 'Master Workspace'. The latest 2.0 development
is done with the SRC680 stem; with auto-incrementing milestones; hence
tags like <code>SRC680_m66</code> would be common.


== Why does XYZ require Java ? up-stream/Sun are so evil !? ==

Nah up-stream just use the best tool to hand, and have a different set world-view to you, where Java is an engineering solution to their cross platform problems. By using Java StarDivision can avoid having to re-invent and then maintain an essentially competing cross-platform layer. There is no malice here whatsoever; just pragmatic engineering from a different perspective.

See [[Java and OpenOffice.org]]

== Why is [t]csh so broken ? ==


This is rather inscrutable; some particularly curious brokenness
would be the way piping commands on stdin is crucially different
to inputting them from the tty thus:
<code>echo 'echo #define DLL_NAME "libsch641li.so" >./foo.hxx' | /bin/tcsh -s</code>
fails to do anything whereas typing the same thing into the shell
works just fine. Even more oddly:
<code>tcsh -fc 'echo #define DLL_NAME "libsch641li.so" >./foo.hxx'</code>
does do the right thing. See also [http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/ csh].


== I just tried to re-locate the build, why doesn't it work ? ==


The simple answer is: you need to run <code>relocate /path/to/new/build</code>;
another more complex answer is:


Well, assuming you have re-configured things (LinuxIntelEnv.Set will
need paths tweaking too — and re-importing to your shell) — then it's most
likely down to the ubiquitous non-relative paths, coded in lots
of generated / built files, particularly '.dpc*' (dependency)
files. Try:
<code>find -name '*.dpc*' -exec rm {} \;</code>


The stlport does some really broken things, so
you will also need to edit the 'stl_gcc.h' inside the solver/, and replace the
two path instances there (see inc/stl/config/stl_gcc.h).


== CVS says 'Fatal Error aborting. [acc] no such user', why ? ==


While of course it's possible that your user name is not registered; often
this just means your ~/.cvspass got lost and/or that you haven't logged in.
cvs login, and repeat the command.


== What does '.pro' in 'unxlngi4.pro' mean ? ==


Product — isn't it obvious ?


== What does OpenOffice really look like ? ==


Today I found a photograph of it on my system, so I stuck it in here:


http://go-oo.org/images/layers.png Abstraction Layers

This diagram is superb but, what does each acronym mean? (ie, GO search don't find it and guessing could be wrongly)

== How do I take a screenshot of OO.o ? ==

OOo does some very odd things with X resources, thus some conventional
screenshot apps fail to take accurate shots. ImageMagick's 'import'
however does a good job; use:
<code>import foo.png</code> from the console, or
<code>sleep 2; import -window root foo.png</code> instead.
NB. unless you want your world to look tiny, you need to turn large
toolbar icons first.


== Why does the code look so ugly? ==

The authors must be using a really strange editor.
It thinks tab stops are on every fourth column.
Of course, the files come out ugly in Unix editors which know
that tabs are eight characters wide.


If you happen to use
[http://www.gnu.org/software/emacs/ a Real Editor],
we have some pink glasses to sell to you. Paste the contents of
[http://go-ooo.org/emacs.el] into your <tt>.emacs</tt>,
or load it with a line like this: <tt>(load "/path/to/that/file.el")</tt>.
Don't forget to adapt <tt>my-openoffice-path-regexp</tt> to your needs.


Henceforth emacs will use 4-column tabs for your OOo source files.
(And use C++-Mode for <tt>sdi</tt>-, <tt>hrc</tt>-,
and <tt>src</tt>-files.) Alternatively if you are sufficiently set in
your ways that you can't cope with investing these few seconds do:
<code>M-x set-variable\ntab-width 4</code> & learn to love change.


Apparently if you use vi you can do: <code>:set ts=4 sw=4</code>, and
good luck to you. For a better vim, use <code>:set ts=4 sw=4 et</code> to also expand tabs to spaces, as this is what new code should use.


== Where can I suggest ideas for what OpenOffice.org should do and what I don't/do like about it? ==
''Awaiting an answer from a kind contributor.''

== See also ==

* [[CvsFAQ]] - for CVS problems
* [[OOo_Ergonomics]] - why is it so painful to use ?