Difference between revisions of "Community Innovation Program/proposals"
(→Writer) |
B michaelsen (talk | contribs) |
||
(11 intermediate revisions by 8 users not shown) | |||
Line 23: | Line 23: | ||
</DT><DD> | </DT><DD> | ||
dev@sw.openoffice.org | dev@sw.openoffice.org | ||
− | + | <DD STYLE="margin-bottom: 0.5cm"> | |
Oliver.Specht at sun dot com | Oliver.Specht at sun dot com | ||
− | + | </DL> | |
<P> | <P> | ||
<BR><BR> | <BR><BR> | ||
</P> | </P> | ||
+ | === Improve Equation Editor Math === | ||
+ | |||
+ | ==== Intro ==== | ||
+ | |||
+ | Objectives: '''Implement missing features in the equations editor Starmath, to make it the best equation editor ever ''' | ||
+ | |||
+ | '''Context''' : this application is well targeted for students and does concern an important (the single most one ?) usability problem with Math. It was already attempted to solve at least 3 times but always needed to be dropped because of lack of resources.''' | ||
+ | |||
+ | The equations editor has some issues (including very old one) and they need to be fixed, because all those issues are a '''strong brake''' for OpenOffice.org acceptance in Education. The main objective here is to implement a new feature for baseline computation. | ||
+ | |||
+ | Concerns: OpenOffice.org 3.x all versions | ||
+ | |||
+ | |||
+ | Main issues are: | ||
+ | |||
+ | - misalignment. Todo: compute the baseline for equations anchored as character (main case) | ||
+ | |||
+ | - missing symbols ( |-> , <-| , angle A^B .. etc) | ||
+ | |||
+ | - + some other little issues to be fixed in starmath | ||
+ | |||
+ | ==== Skills==== | ||
+ | |||
+ | Skills with languages C/C++ (tokenization, debugging ) maths symbols and good math knowledge (for equations writing ) is a plus. | ||
+ | |||
+ | Good communication skills are expected too (because several modules are concerned ) | ||
+ | |||
+ | ====Tasks ==== | ||
+ | |||
+ | Familiarize with the starmath editor code. ( see [http://eric.bachard.free.fr/Education/Documentation/starmath/Doc_Math/html/ '''source code documentation online'''] ) | ||
+ | |||
+ | Familiarize with links in writer (writer is concerned in some issues) | ||
+ | |||
+ | '''Expected''': | ||
+ | |||
+ | For issue 972 ( see links [[Education_Project/Effort#Implement_Math_Baseline_Alignement_.28click_me.29| '''Education Project effort for starmath''']] and [[Education_Project/Effort/Math_baseline_alignment| '''Math_baseline_alignment''']] ) | ||
+ | |||
+ | |||
+ | - '''code to Implement a new parameter for baseline computation without edit equations''' | ||
+ | |||
+ | - '''write specs''' | ||
+ | |||
+ | - '''design a proof of concept''' | ||
+ | |||
+ | - '''implement it''' | ||
+ | |||
+ | The task could be completed with other little tasks, depending on the agenda ( e.g.implement missing |-> and <-| symbols .. etc ) | ||
+ | |||
+ | ; Contact | ||
+ | : dev@education.openoffice.org | ||
+ | : ericb at openoffice dot org | ||
+ | |||
+ | ;Proposed by: Eric Bachard, Thomas Lange (to be confirmed) | ||
+ | |||
+ | ;Mentor: Eric Bachard (to be confirmed) | ||
+ | |||
+ | <br> | ||
==Calc/Chart== | ==Calc/Chart== | ||
Line 59: | Line 116: | ||
: dev@sc.openoffice.org | : dev@sc.openoffice.org | ||
: Niklas.Nebel at sun.com | : Niklas.Nebel at sun.com | ||
+ | |||
+ | === Improve numerical stability of spreadsheet functions === | ||
+ | |||
+ | Some statistical and financial analysis spreadsheet functions need improvement in numerical stability, for example for very large and/or small values, see [http://qa.openoffice.org/issues/show_bug.cgi?id=18704 issue 18704] and dependencies. | ||
+ | |||
+ | * Reguired skills/knowledge: C++, knowledge of numerical analysis and algorithms, mathematical background | ||
+ | |||
+ | ; Contact | ||
+ | : dev@sc.openoffice.org | ||
+ | : Eike.Rathke at sun dot com | ||
+ | |||
+ | === Add new spreadsheet functions and parameters according to ODFF === | ||
+ | |||
+ | The [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office OpenDocument Format Formula specification] (ODFF aka OpenFormula) defines several new spreadsheet functions and new optional parameters to already existing functions that have to be implemented. | ||
+ | |||
+ | * Reguired skills/knowledge: C++; for some statistical functions knowledge of numerical algorithms and mathematical background | ||
+ | |||
+ | ; Contact | ||
+ | : dev@sc.openoffice.org | ||
+ | : Eike.Rathke at sun dot com | ||
==Impress/Draw== | ==Impress/Draw== | ||
+ | ===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. | ||
+ | |||
+ | * Reguired skills/knowledge: good C++ or Java expertise, graphics programming | ||
+ | * Recommendend skills/knowledge: Visio file format, ODF and/or OOo API | ||
+ | |||
+ | ; Contact | ||
+ | : dev@graphics.openoffice.org | ||
+ | : Sven.Jacobi at sun dot com | ||
+ | |||
==Base== | ==Base== | ||
+ | ===Dialogs with Form Functionality=== | ||
+ | |||
+ | When creating a form, the user always needs to bother with a Writer document. Very often, this is much too oversized. It would be sufficient to have a simple dialog which contains all the data access controls. | ||
+ | |||
+ | The project is to (in different steps) | ||
+ | - extend the dialog runtime engine to (optionally) include data-aware form controls | ||
+ | - create a form designer for dialog-based forms (similar to the existing Basic Dialog IDE) | ||
+ | - implement persistence of dialog-based forms | ||
+ | - embed dialog-based forms into database documents (.odb) | ||
+ | |||
+ | Depending on more fine-grained planning, it might become apparent that not all of this can be done in the scope of a Google Summer of Code project, and reasonable milestones need to be defined. | ||
+ | |||
+ | * required skills C++, UNO | ||
+ | * useful skills: familiarity with OOo's database access and form API, as well as OOo's [http://api.openoffice.org/docs/common/ref/com/sun/star/awt/module-ix.html toolkit API] | ||
+ | * Mentor: Frank.Schoenheit at sun.com | ||
+ | * Contact: [mailto:dev@dba.openoffice.org dev@dba.openoffice.org] | ||
+ | * estimated effort: 3 months | ||
+ | |||
+ | * more information on [[Base_To-Do/Dialogs_with_Form_Functionality|the project page]] | ||
==Misc== | ==Misc== | ||
Line 104: | Line 211: | ||
: [mailto:dev@api.openoffice.org dev@api.openoffice.org] | : [mailto:dev@api.openoffice.org dev@api.openoffice.org] | ||
: steffen.grund at sun.com | : steffen.grund at sun.com | ||
+ | |||
+ | ===WebDAV Versioning (with the DeltaV protocol extension)=== | ||
+ | |||
+ | To support office collaboration scenarios (e.g. remote collaboration document authoring) OOo needs a tool to provide remote versioning. With the already implemented WebDAV feature we've got the basis for such a tool and the DeltaV protocol extension of WebDAV could add the versioning functionality. | ||
+ | |||
+ | The goal is to provide at least the basic feature "core-versioning" of the protocol. | ||
+ | |||
+ | * Required skills/knowledge: C++ | ||
+ | |||
+ | ;Contact | ||
+ | : [mailto:dev@ucb.openoffice.org dev@ucb.openoffice.org] | ||
+ | : tobias.krause at sun.com | ||
+ | |||
+ | ===Extended Basic/Dialog Library OXT Export=== | ||
+ | |||
+ | The OOo Basic Macro Organizer already allows to export a Basic/Dialog Library as extension, but without support for the description.xml file described in: | ||
+ | |||
+ | http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/description.xml | ||
+ | |||
+ | The goal of this project is to add support for this by creating a corresponding dialog allowing the user to edit all supported elements and by saving the description.xml file into the oxt file afterwards. | ||
+ | |||
+ | * Required skills/knowledge: C++, Extensions | ||
+ | |||
+ | ; Contact | ||
+ | : [mailto:dev@api.openoffice.org dev@api.openoffice.org] | ||
+ | : andreas.bregas at sun.com | ||
+ | |||
+ | ===Dialog Editor: Single dialog import=== | ||
+ | |||
+ | The Dialog Editor allows to export a single dialog as xdl file and - in case of localized dialogs - additional properties files containing the resource strings. This is very useful for adding dialogs / option pages to extensions. But there is no corresponding import functionality which makes it difficult to reimport and change dialogs exported before. | ||
+ | |||
+ | The goal of this project is to add this functionality. It has to be evaluated first how this can be done in a reasonable way as the dialogs are not handled like documents supporting Load/Save/Save as... but stored implicitely in the Library Container system. So there are several options how importing a dialog could work, e.g. replacing the current dialog after warning the user, adding it as new dialog after solving potential name conflicts. Also potential conflicts concerning the languages supported by the imported dialog respectively the target library have to be handled. | ||
+ | |||
+ | * Required skills/knowledge: C++ | ||
+ | |||
+ | ; Contact | ||
+ | : [mailto:dev@api.openoffice.org dev@api.openoffice.org] | ||
+ | : andreas.bregas at sun.com | ||
+ | |||
+ | ===UNO Web Service Proxy - Add Support for Anonymous Complex Types=== | ||
+ | |||
+ | Web services are more and more emerging. Some examples are Google and Amazon which are providing a SOAP Web service interface for their traditional services, like searching the Web or querying the online bookstore. These interfaces can be reached using UNO and StarBasic using the UNO Web service proxy. | ||
+ | |||
+ | http://udk.openoffice.org/java/examples/wsproxy/component_description.html | ||
+ | |||
+ | The current implementation of the UNO Web Service Proxy lacks support for a very important WSDL feature, that is widely used by existing Web Services - anonymous complex types. | ||
+ | |||
+ | The goal for this project is to add support for anonymous complex types to the existing UNO Web Service Proxy implementation. | ||
+ | |||
+ | * Required skills/knowledge: Java, UNO, JAX-RPC, WSDL, SOAP, Netbeans | ||
+ | |||
+ | ;Contact | ||
+ | : [mailto:dev@udk.openoffice.org dev@udk.openoffice.org] | ||
+ | : kai.sommerfeld at sun.com | ||
+ | |||
+ | |||
+ | == '''Applications for Mac OS X only''' == | ||
+ | |||
+ | === [[Education_Project/Effort/Write_a_new_canvas | Implement new canvas using Core Graphics (click me)]]=== | ||
+ | |||
+ | |||
+ | * '''Goal''' : Implement a new canvas on Mac OS X | ||
+ | |||
+ | * '''Problem''' : nothing yet | ||
+ | |||
+ | * '''Time plan''' : respecting Community Innovation Program timeline | ||
+ | |||
+ | Contacts: | ||
+ | |||
+ | * for [[Education Project |Education project]]: ericb , (please add your name ) | ||
+ | |||
+ | * for the task : Thorsten Behrens thb/ Eric Bachard ericb : all @openoffice.org | ||
+ | |||
+ | Difficulty: ***** | ||
+ | |||
+ | Needs: | ||
+ | |||
+ | * experimental tests in canvas, with dummy methods, for proof of concept | ||
+ | |||
+ | * good Core Graphics understanding | ||
+ | |||
+ | * good C++ skills | ||
+ | |||
+ | * good Cairo understanding ( we use the existing implementation) | ||
=New Tasks= | =New Tasks= | ||
Line 124: | Line 315: | ||
: dev@project.openoffice.org | : dev@project.openoffice.org | ||
: The.Mentor at organization com | : The.Mentor at organization com | ||
+ | [[Category:Community Council]] |
Latest revision as of 16:59, 14 December 2009
Proposals
Writer
Enhanced usability of working with page attributes and properties
Currently changing page attributes or adding page properties like headers and footers is hard to understand. Users that don't know about hard page breaks, page styles and follow styles will have a hard time to format pages to their likings. A nice UI that hides the technical details and uses terms of the user space would help a lot.
Tasks
learn about Writer's page styles and their (UNO) API
design and code the new user interface based on this API
Required skills/knowledge: C++; UI design
- Contact
- dev@sw.openoffice.org
- Oliver.Specht at sun dot com
Improve Equation Editor Math
Intro
Objectives: Implement missing features in the equations editor Starmath, to make it the best equation editor ever
Context : this application is well targeted for students and does concern an important (the single most one ?) usability problem with Math. It was already attempted to solve at least 3 times but always needed to be dropped because of lack of resources.
The equations editor has some issues (including very old one) and they need to be fixed, because all those issues are a strong brake for OpenOffice.org acceptance in Education. The main objective here is to implement a new feature for baseline computation.
Concerns: OpenOffice.org 3.x all versions
Main issues are:
- misalignment. Todo: compute the baseline for equations anchored as character (main case)
- missing symbols ( |-> , <-| , angle A^B .. etc)
- + some other little issues to be fixed in starmath
Skills
Skills with languages C/C++ (tokenization, debugging ) maths symbols and good math knowledge (for equations writing ) is a plus.
Good communication skills are expected too (because several modules are concerned )
Tasks
Familiarize with the starmath editor code. ( see source code documentation online )
Familiarize with links in writer (writer is concerned in some issues)
Expected:
For issue 972 ( see links Education Project effort for starmath and Math_baseline_alignment )
- code to Implement a new parameter for baseline computation without edit equations
- write specs
- design a proof of concept
- implement it
The task could be completed with other little tasks, depending on the agenda ( e.g.implement missing |-> and <-| symbols .. etc )
- Contact
- dev@education.openoffice.org
- ericb at openoffice dot org
- Proposed by
- Eric Bachard, Thomas Lange (to be confirmed)
- Mentor
- Eric Bachard (to be confirmed)
Calc/Chart
Component to check spreadsheet documents for potential errors
Write an extension that checks a spreadsheet document for potential errors in formulas, presents a list of the findings to the user, and allows to correct them.
Things to look for could include
- Cells that contain numbers stored as text and are used in formulas,
- Number cells that are not used in any formulas,
- Empty cells that are used in single-cell formula references.
The list is not meant to be exhaustive.
- Required skills/knowledge: Java or C++, spreadsheet usage
- Contact
- dev@sc.openoffice.org
- Niklas.Nebel at sun.com
Watch Window
A Watch Window is a separate, small window that remains "on top" and enables users to monitor a selected set of cells, see issue 28386.
This could be implemented as an add-on component with a modeless dialog containing the list of watched cells as well as the UI to add or remove cells.
- Required skills/knowledge: Java or C++
- Contact
- dev@sc.openoffice.org
- Niklas.Nebel at sun.com
Improve numerical stability of spreadsheet functions
Some statistical and financial analysis spreadsheet functions need improvement in numerical stability, for example for very large and/or small values, see issue 18704 and dependencies.
- Reguired skills/knowledge: C++, knowledge of numerical analysis and algorithms, mathematical background
- Contact
- dev@sc.openoffice.org
- Eike.Rathke at sun dot com
Add new spreadsheet functions and parameters according to ODFF
The OpenDocument Format Formula specification (ODFF aka OpenFormula) defines several new spreadsheet functions and new optional parameters to already existing functions that have to be implemented.
- Reguired skills/knowledge: C++; for some statistical functions knowledge of numerical algorithms and mathematical background
- Contact
- dev@sc.openoffice.org
- Eike.Rathke at sun dot com
Impress/Draw
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.
- Reguired skills/knowledge: good C++ or Java expertise, graphics programming
- Recommendend skills/knowledge: Visio file format, ODF and/or OOo API
- Contact
- dev@graphics.openoffice.org
- Sven.Jacobi at sun dot com
Base
Dialogs with Form Functionality
When creating a form, the user always needs to bother with a Writer document. Very often, this is much too oversized. It would be sufficient to have a simple dialog which contains all the data access controls.
The project is to (in different steps) - extend the dialog runtime engine to (optionally) include data-aware form controls - create a form designer for dialog-based forms (similar to the existing Basic Dialog IDE) - implement persistence of dialog-based forms - embed dialog-based forms into database documents (.odb)
Depending on more fine-grained planning, it might become apparent that not all of this can be done in the scope of a Google Summer of Code project, and reasonable milestones need to be defined.
- required skills C++, UNO
- useful skills: familiarity with OOo's database access and form API, as well as OOo's toolkit API
- Mentor: Frank.Schoenheit at sun.com
- Contact: dev@dba.openoffice.org
- estimated effort: 3 months
- more information on the project page
Misc
OXT Extension wizard for templates and XSLT based filter
OXT extensions provide a nice way to bundle a group of templates and share them with other users. Templates are normally created with the office and the idea is to provide a wizard that helps on a higher abstraction level to collect templates and all necessary oxt specific information and build an oxt extension package. The second part is to extend the XSLT filter dialog to export new created XSLT based filters as an oxt extension as well. Currently it is only possible to create a jar file. The new feature should collect some more oxt related info and should create a well formed oxt extension package. The goal is to simplify these tasks and make it as easy as possible to create oxt extension packages that can be easy deployed and can be uploaded in the extensions repository to share them with many other users.
- Required skills/knowledge: Java or C++
- Contact
- juergen.schmidt at sun.com
ODT/PDF export from OpenOffice.org Wiki
OpenOffice.org documentation is being moved to the OpenOffice.org Wiki. This makes it easier for people to contribute to the content of the documentation, but producing a PDF of ODT of the entire Wiki document or book is not yet possible. The OpenOffice.org Wiki needs a MediaWiki extension developed that will provide a way to convert an aggregation of wiki pages (a "book") to ODT and/or PDF.
- Required skills/knowledge: PHP and XML, familiarity with ODF a plus
- Contact
- dev@documentation.openoffice.org
- ccornell at openoffice.org, juergen.schmidt at sun.com
Netbeans OOo API Plugin: UNO IDL language support
Currently, the IDL language support consists only of syntax highlighting. With NetBeans 6 there is a project to support a generic language syntax. This can be used to create a full support including e.g. auto-completion and tool-tips in IDL files.
OpenOffice.org API plugin for NetBeans
Generic Language Framework in NetBeans (Project Schliemann)
The work for this project consists of creating the description of the static elements of IDL files. But to provide a meaningful auto completion, the currently available keywords have to be taken dynamically from OpenOffice.org. With this, not only the build-in UNO types of OOo, but also added types from registered extensions can be offered for auto-completion.
Since there may be performance issues regarding the usage of the Generic Language Framework, this project includes some evaluation work.
- Required skills/knowledge: Java, OpenOffice.org API, ideally NetBeans API
- Contact
- dev@api.openoffice.org
- steffen.grund at sun.com
WebDAV Versioning (with the DeltaV protocol extension)
To support office collaboration scenarios (e.g. remote collaboration document authoring) OOo needs a tool to provide remote versioning. With the already implemented WebDAV feature we've got the basis for such a tool and the DeltaV protocol extension of WebDAV could add the versioning functionality.
The goal is to provide at least the basic feature "core-versioning" of the protocol.
- Required skills/knowledge: C++
- Contact
- dev@ucb.openoffice.org
- tobias.krause at sun.com
Extended Basic/Dialog Library OXT Export
The OOo Basic Macro Organizer already allows to export a Basic/Dialog Library as extension, but without support for the description.xml file described in:
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/description.xml
The goal of this project is to add support for this by creating a corresponding dialog allowing the user to edit all supported elements and by saving the description.xml file into the oxt file afterwards.
- Required skills/knowledge: C++, Extensions
- Contact
- dev@api.openoffice.org
- andreas.bregas at sun.com
Dialog Editor: Single dialog import
The Dialog Editor allows to export a single dialog as xdl file and - in case of localized dialogs - additional properties files containing the resource strings. This is very useful for adding dialogs / option pages to extensions. But there is no corresponding import functionality which makes it difficult to reimport and change dialogs exported before.
The goal of this project is to add this functionality. It has to be evaluated first how this can be done in a reasonable way as the dialogs are not handled like documents supporting Load/Save/Save as... but stored implicitely in the Library Container system. So there are several options how importing a dialog could work, e.g. replacing the current dialog after warning the user, adding it as new dialog after solving potential name conflicts. Also potential conflicts concerning the languages supported by the imported dialog respectively the target library have to be handled.
- Required skills/knowledge: C++
- Contact
- dev@api.openoffice.org
- andreas.bregas at sun.com
UNO Web Service Proxy - Add Support for Anonymous Complex Types
Web services are more and more emerging. Some examples are Google and Amazon which are providing a SOAP Web service interface for their traditional services, like searching the Web or querying the online bookstore. These interfaces can be reached using UNO and StarBasic using the UNO Web service proxy.
http://udk.openoffice.org/java/examples/wsproxy/component_description.html
The current implementation of the UNO Web Service Proxy lacks support for a very important WSDL feature, that is widely used by existing Web Services - anonymous complex types.
The goal for this project is to add support for anonymous complex types to the existing UNO Web Service Proxy implementation.
- Required skills/knowledge: Java, UNO, JAX-RPC, WSDL, SOAP, Netbeans
- Contact
- dev@udk.openoffice.org
- kai.sommerfeld at sun.com
Applications for Mac OS X only
Implement new canvas using Core Graphics (click me)
- Goal : Implement a new canvas on Mac OS X
- Problem : nothing yet
- Time plan : respecting Community Innovation Program timeline
Contacts:
- for Education project: ericb , (please add your name )
- for the task : Thorsten Behrens thb/ Eric Bachard ericb : all @openoffice.org
Difficulty: *****
Needs:
- experimental tests in canvas, with dummy methods, for proof of concept
- good Core Graphics understanding
- good C++ skills
- good Cairo understanding ( we use the existing implementation)
New Tasks
If you have a task that is challenging enough, and there is an OpenOffice.org Project Member willing to mentor the task, feel free to coordinate with the appropriate project lead. If the appropriate project has been found and it supports the task, add it below and make sure the mentor applies with the web app.
Each entry should contain the task description, required skills, project mailing list for discussion and personal contact. Links to the To-Dos are appreciated provided that the task is well described there ;-)
===Example entry=== This is just an example - the real entry must not start with a space at the beginning of the line. A full description of the task should be here; one that will help to see that this task is important, and interesting to hack on. Alternatively it could be an exact link to the description that is already in To-Dos. * Required skills/knowledge: Language, technology1, technology2, ... ; Contact : dev@project.openoffice.org : The.Mentor at organization com