Hi Richard,

I'm CC:ing you because I don't know wether you are subscribed to this list.

Richard Jones wrote:
> Hey Mathias,
> 
> was browsing the list of potential topics for the Google Summer of Code
> projects and I came upon one that interests me.  I can't tell you how many
> times I have been typing documents or working with spreadsheets and wished
> that I could remove the clutter from my task bar while being able to keep
> all of my work at my fingertips.  Therefore, I am interested in working on
> extending the framework to allow for tabbed document windows.  I was hoping
> to get a little more information about what exactly is desired this projects
> as well what kind of application material you are looking for (resume, code
> samples, etc.).  Just a little bit of background information about myself.
> I am a Duke University student with a Bachelors of Science in Computer
> Science and Economics with two summers of work experience doing Java
> development at a BPM firm called Pegasystems.  I also have experience with
> C++, C, and to a lesser extent C#.  If you could provide me with more
> information, it would be greatly appreciated.

First let me thank you for your interest.
As you might know already, the final selection of the "Google Summer of
Code" program is up to Google, at the moment we can just confirm wether
we want to take the mentoring role in your project.

And of course we will.  :-)

As a prerequisite to any code contributions to our project you have to
sign a joint copyright assignment with Sun. You can read more about
contributions here:

http://contributing.openoffice.org/programming.html

The "tabbing" component is planned to work on the new OpenOffice.org 2.0
codebase. The latest milestone can be downloaded from

http://download.openoffice.org/680/index.html

Later I will post a raw concept document for the "tabbing component". It
will outline how we thought this feature could be implemented. Of course
there is still enough room to incorporate any ideas and suggestions from
your side. For this reason you should read about our Application
Framework API in our Developers Guide.

You can read it online at

http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html

or offline as part of our SDK (see below).

The Framework API is described in chapter 6.1, but you also need to
understand some basic concepts of our API and our Middleware technology,
called UNO. My recommendation is to read the following chapters of the
DevGuide:

1       Reader's Guide
2       First Steps
3.1     Professional UNO: Introduction
3.2     Professional UNO: API Concepts
3.3.3   Using UNO Interfaces
3.3.6   Event Model
3.3.8   Lifetime of UNO Objects
3.4.2   C++ Language Binding
6.1     StarOffice Application Environment (Framework)

(Remark: while reading the DevGuide you might stumble over references to
Java or Inter Process Communication, but you can skip this because our
component will be in-process and it will be developed using C++.)

Everything else (like e.g. component creation and registration) can be
learned "on demand" while the project is done.

You can also take our SDK and play with the C++ examples to find out how
the development of C++ components can be done. An SDK for the OOo2.0
milestone builds can be found at

http://download.openoffice.org/680/sdk.html

Please note that our estimated schedule was done under the assumption
that you are an experienced C++ developer who already has done his own
C++ projects and who knows all the main stream stuff like templates or
exceptions quite well, is able to think in object terms and understands
the idea of separating interface and implementation. As you might have
read on code.google.com you must finish the planned work in the
estimated time to get the payment from Google, so please be consider
this carefully.

You might have seen that another student showed interest in this
project. ATM we won't exclude anybody, so let's see how we can proceed.

Best regards,
Mathias


-- 
Mathias Bauer - OpenOffice.org Application Framework Project Lead
Please reply to the list only, [EMAIL PROTECTED] is a spam sink.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to