[
https://issues.apache.org/jira/browse/COMDEV-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Schmidt updated COMDEV-77:
----------------------------------
Description:
Apache OpenOffice is the leading open source desktop office suite. Our most
recent release has had over 40 million downloads.
OpenOffice has a powerful API and extension framework that allows to extend the
office with new features or provide connectors into external applications and
simplify the interoperability between the application and office. Many service
provider interfaces (SPI) are available and allow specific integration into
existing areas. For example you can provide extensions that behaves as normal
build in function in the spreadsheet application. Or you can provide an grammar
checking extensions etc.
A key element here to simplify the development of such extensions is to have a
good tooling. There is already a plugin available for NetBeans [1] that
provides some basic project types and wizards to simplify the setup of a new
project and the ongoing maintenance and development (including deployment and
debugging in the office) of such extension projects.
The idea is to have a similar plugin for Eclipse in place to reach even more
extension developers and give them a powerful tooling to speed up their work
and to help growing the eco-system around OpenOffice. The focus is here on Java
extensions but on demand the support for C++ or Python extension is also
possible.
Project scope and ideas:
1. thinking about a good project structure for an Eclipse extension project
2. evaluating how to package an extension package (oxt), deploy it from Eclipse
into the office and how to remote debug the extension in the office
3. Implement some basic wizards to support specific SPIs (e.g. Calc Add-in,
Add-on, ...) and help to setup a basic project
The OpenOffice SDK provided a code skeleton generator that can be used to
generate necessary code skeletons.
Skills needed:
-- Java programming ("Core Java"), good working knowledge, but don't need to be
a guru or anything
-- open minded to learn something new, the office API and some basic concepts
regarding the underlying component technology
-- open to have fun with one of the biggest open source projects
[1] http://wiki.openoffice.org/wiki/OpenOffice_NetBeans_Integration
was:
Apache OpenOffice is the leading open source desktop office suite. Our most
recent release has had over 40 million downloads.
OpenOffice has a powerful API and extension framework that allows to extend the
office with new features or provide connectors into external applications and
simplify the interoperability between the application and office. Many service
provider interfaces (SPI) are available and allow specific integration into
existing areas. For example you can provide extensions that behaves as normal
build in function in the spreadsheet application. Or you can provide an grammar
checking extensions etc.
A key element here to simplify the development of such extensions is to have a
good tooling. There is already a plugin available for NetBeans [1] that
provides some basic project types and wizards to simplify the setup of a new
project and the ongoing maintenance and development (including deployment and
debugging in the office) of such extension projects.
The idea is to have a similar plugin for Eclipse in place to reach even more
extension developers and give them a powerful tooling to speed up their work
and to help growing the eco-system around OpenOffice. The focus is here on Java
extensions but on demand the support for C++ or Python extension is also
possible.
Project scope and ideas:
1. thinking about a good project structure for an Eclipse extension project
2. evaluating how to package an extension package (oxt), deploy it from Eclipse
into the office and how to remote debug the extension in the office
3. Implement some basic wizards to support specific SPIs (e.g. Calc Add-in,
Add-on, ...) and help to setup a basic project
The OpenOffice SDK provided a code skeleton generator that can be used to
generate necessary code skeletons.
Skills needed:
-- Java programming ("Core Java"), good working knowledge, but don't need to be
a guru or anything
-- open minded to learn something new, the office API and some basic concepts
regarding the underlying component technology
-- open to have fun with one of the biggest open source projects
> [GSoC] Apache OpenOffice Extension Plugin for Eclipse
> -----------------------------------------------------
>
> Key: COMDEV-77
> URL: https://issues.apache.org/jira/browse/COMDEV-77
> Project: Community Development
> Issue Type: New Feature
> Reporter: Juergen Schmidt
> Labels: gsoc, gsoc2013, mentor
>
> Apache OpenOffice is the leading open source desktop office suite. Our most
> recent release has had over 40 million downloads.
> OpenOffice has a powerful API and extension framework that allows to extend
> the office with new features or provide connectors into external applications
> and simplify the interoperability between the application and office. Many
> service provider interfaces (SPI) are available and allow specific
> integration into existing areas. For example you can provide extensions that
> behaves as normal build in function in the spreadsheet application. Or you
> can provide an grammar checking extensions etc.
> A key element here to simplify the development of such extensions is to have
> a good tooling. There is already a plugin available for NetBeans [1] that
> provides some basic project types and wizards to simplify the setup of a new
> project and the ongoing maintenance and development (including deployment and
> debugging in the office) of such extension projects.
> The idea is to have a similar plugin for Eclipse in place to reach even more
> extension developers and give them a powerful tooling to speed up their work
> and to help growing the eco-system around OpenOffice. The focus is here on
> Java extensions but on demand the support for C++ or Python extension is also
> possible.
> Project scope and ideas:
> 1. thinking about a good project structure for an Eclipse extension project
> 2. evaluating how to package an extension package (oxt), deploy it from
> Eclipse into the office and how to remote debug the extension in the office
> 3. Implement some basic wizards to support specific SPIs (e.g. Calc Add-in,
> Add-on, ...) and help to setup a basic project
> The OpenOffice SDK provided a code skeleton generator that can be used to
> generate necessary code skeletons.
> Skills needed:
> -- Java programming ("Core Java"), good working knowledge, but don't need to
> be a guru or anything
> -- open minded to learn something new, the office API and some basic concepts
> regarding the underlying component technology
> -- open to have fun with one of the biggest open source projects
> [1] http://wiki.openoffice.org/wiki/OpenOffice_NetBeans_Integration
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
