Hi Shrirang, I'm CC:ing you because I don't know wether you are subscribed to this list.
Shrirang Bhate wrote: > Hi, I am highly interested in contributing to tab document > windows. What requirements (in technical skills) would > one need in order to adequately contribute to this > project? I am looking for a reasonable goal, but not an > easy one. Any additional information of the project > and/or on proposal writing would be great. 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. :-) Please note that you must apply at Google and that the deadline in June 14th. Please find more information on http://code.google.com/summfaq.html Some words about us and about the project. 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 other students also showed interest in this project. ATM we won't exclude anybody, and finally it's up to Google to decide which students they select, so let's see how we can proceed. Best regards, Mathias --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
