Difference between revisions of "OpenOffice.org Internship/ProjectProposals"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Integration/porting)
Line 2: Line 2:
 
http://wiki.services.openoffice.org/wiki/Community_Innovation_Program/proposals and  
 
http://wiki.services.openoffice.org/wiki/Community_Innovation_Program/proposals and  
 
http://wiki.services.openoffice.org/wiki/Summer_of_Code_2008/proposals#Proposals
 
http://wiki.services.openoffice.org/wiki/Summer_of_Code_2008/proposals#Proposals
 +
 +
<font color=red size=4> '''This is a draft, and the proposed subjects below can be removed if not conform to the Internship needs</font>
 +
  
 
== Integration/porting ==
 
== Integration/porting ==

Revision as of 12:31, 13 May 2010

start with some C&P from http://wiki.services.openoffice.org/wiki/Community_Innovation_Program/proposals and http://wiki.services.openoffice.org/wiki/Summer_of_Code_2008/proposals#Proposals

This is a draft, and the proposed subjects below can be removed if not conform to the Internship needs


Integration/porting

Maxima Integration

Integrate the Maxima symbolic computer algebra system into OOo, to solve calc problems in Writer.

The idea : create a Maxima session inside an OOo Writer document, in an embeded frame, or equivalent.

IMPORTANT :

Weekly IRC meetings. Wiki use mandatory. Specifications and documentation MUST be written in parallel, in same time the code is written. Every diff of code will be documented on the wiki. the code must be written in C++ (prefered). A proof of concept using Python would be appreciated. Iterations

  • Step 1

Discover and learn UNO API be able to create a Writer document (and play with it) be able to launch an external application using UNO In parallel : learn how a Writer document is structured and how to use it programmaticaly (structure, foundations)

  • Step 2

Learn Maxima session requirements implement a way to launch a Maxima session from OOo implement a way to exchange datas with the open Maxima session propose a follow up for the devs who will continue the implementation Estimated Timeline

3 weeks of work = step 1 5 weeks of work = step 2 Required skills/knowledge lisp, c++, UNO API knowledge Difficulty medium Contact ericb at openoffice.org

Personal tools