Difference between revisions of "Progressive implementation"
Line 15: | Line 15: | ||
Subject proposed by : none yet | Subject proposed by : none yet | ||
Tasks : | Tasks : | ||
+ | |||
(1) analyze current implementation : design, concerned modules, isolate classes and parameters | (1) analyze current implementation : design, concerned modules, isolate classes and parameters | ||
+ | |||
(2) propose a design for the new one, using Apple API | (2) propose a design for the new one, using Apple API | ||
+ | |||
(3) write and test a proof of concept | (3) write and test a proof of concept | ||
+ | |||
If enough time : (4) implement the solution, with possible backport to X11 version. | If enough time : (4) implement the solution, with possible backport to X11 version. | ||
Line 27: | Line 31: | ||
Subject proposed by : none yet, but Oliver Braun nerd@warpsite.de was working on that subject | Subject proposed by : none yet, but Oliver Braun nerd@warpsite.de was working on that subject | ||
+ | |||
Concerns : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions) | Concerns : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions) | ||
+ | |||
Skills : knowledge of languages C / C++ , using Carbon/Cocoa API | Skills : knowledge of languages C / C++ , using Carbon/Cocoa API | ||
+ | |||
Tasks : | Tasks : | ||
+ | |||
write specs describe current implementation : design, concerned modules, isolate classes and parameters to manage propose a new design using Apple API write and test a proof of concept | write specs describe current implementation : design, concerned modules, isolate classes and parameters to manage propose a new design using Apple API write and test a proof of concept | ||
+ | |||
; Contact | ; Contact | ||
: Oliver Braun ( nerd at warpsite dot de ) | : Oliver Braun ( nerd at warpsite dot de ) | ||
Line 36: | Line 45: | ||
===Porting : Integrate the native Mac OS X FilePicker into OpenOffice.org (Aqua/X11)=== | ===Porting : Integrate the native Mac OS X FilePicker into OpenOffice.org (Aqua/X11)=== | ||
+ | |||
Concerns : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions) | Concerns : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions) | ||
+ | |||
Skills : knowledge of languages C / C++ , using Carbon/Cocoa API | Skills : knowledge of languages C / C++ , using Carbon/Cocoa API | ||
+ | |||
Proposed by : Tino Rachui Tino.Rachui@Sun.COM | Proposed by : Tino Rachui Tino.Rachui@Sun.COM | ||
+ | |||
Integrate the native Mac OS X FilePicker into OpenOffice.org The OOo FilePicker is already designed as a UNO component. What is needed is a new implementation of the FilePicker component based on the native Mac OS X FilePicker as it has been done on MS Windows for instance. On current Mac OS X port of OpenOffice.org, the current FilePicker is not native, less ergonomic. | Integrate the native Mac OS X FilePicker into OpenOffice.org The OOo FilePicker is already designed as a UNO component. What is needed is a new implementation of the FilePicker component based on the native Mac OS X FilePicker as it has been done on MS Windows for instance. On current Mac OS X port of OpenOffice.org, the current FilePicker is not native, less ergonomic. | ||
+ | |||
Possible tasks : | Possible tasks : | ||
+ | |||
Familiarize with the native Mac OS X FilePicker API and the OOo UNO interfaces for the FilePicker Describe current implementation : design, concerned modules, isolate classes and parameters to manage propose a new design using Apple API write and test a proof of concept | Familiarize with the native Mac OS X FilePicker API and the OOo UNO interfaces for the FilePicker Describe current implementation : design, concerned modules, isolate classes and parameters to manage propose a new design using Apple API write and test a proof of concept | ||
Line 49: | Line 64: | ||
Subject proposed by: Oliver Braun nerd at warpsite dot de | Subject proposed by: Oliver Braun nerd at warpsite dot de | ||
+ | |||
Synopsis: OOo currently is integrated with the Mozilla address book but not with the native Mac OS X address book. This is annoying for Mac OS X user. For better system integration it would be desirable to integrate with the Mac OS X address book. | Synopsis: OOo currently is integrated with the Mozilla address book but not with the native Mac OS X address book. This is annoying for Mac OS X user. For better system integration it would be desirable to integrate with the Mac OS X address book. | ||
+ | |||
Concerns: OpenOffice.org 2.x for Mac OS X (both Aqua and X11 versions) | Concerns: OpenOffice.org 2.x for Mac OS X (both Aqua and X11 versions) | ||
+ | |||
Skills: Knowledge of languages C/C++, Mac OS X APIs and Application frameworks like Carbon or Cocoa for instance, knowledge of the Mac OS X address book APIs | Skills: Knowledge of languages C/C++, Mac OS X APIs and Application frameworks like Carbon or Cocoa for instance, knowledge of the Mac OS X address book APIs | ||
+ | |||
Tasks: Familiarize with the Mac OS X address book API's Familiarize with the current OOo Mozilla address book integration Make a prototype for OOo Mac OS X address book integration | Tasks: Familiarize with the Mac OS X address book API's Familiarize with the current OOo Mozilla address book integration Make a prototype for OOo Mac OS X address book integration | ||
Revision as of 21:30, 24 April 2006
scheduled subjects :
Contents
- 1 Porting : Implement drawing support (Aqua only)
- 2 Porting : Implement native font support, using native Apple API (Aqua / X11)
- 3 Porting : Implement printing support (Aqua / X11)
- 4 Porting : Integrate the native Mac OS X FilePicker into OpenOffice.org (Aqua/X11)
- 5 Porting : Mac OS X Address book integration (Aqua / X11)
Porting : Implement drawing support (Aqua only)
Does concern : native Mac OS X port only Skills : good knowledge of languages C / C++ , using Carbon/Cocoa API (Quartz 2D ) No description available yet
- Contact
- Stephan Schaefer ( ssa at openoffice dot org )
- dev@porting.openoffice.org
Porting : Implement native font support, using native Apple API (Aqua / X11)
Does concern : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions) Skills : knowledge of languages C / C++ , using Carbon/Cocoa API, knowledge of font systems and font technology Subject proposed by : none yet Tasks :
(1) analyze current implementation : design, concerned modules, isolate classes and parameters
(2) propose a design for the new one, using Apple API
(3) write and test a proof of concept
If enough time : (4) implement the solution, with possible backport to X11 version.
Contact
- dev@porting.openoffice.org
- Eric Bachard (ericb at openoffice dot org)
Porting : Implement printing support (Aqua / X11)
Subject proposed by : none yet, but Oliver Braun nerd@warpsite.de was working on that subject
Concerns : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions)
Skills : knowledge of languages C / C++ , using Carbon/Cocoa API
Tasks :
write specs describe current implementation : design, concerned modules, isolate classes and parameters to manage propose a new design using Apple API write and test a proof of concept
- Contact
- Oliver Braun ( nerd at warpsite dot de )
- dev@porting.openoffice.org
Porting : Integrate the native Mac OS X FilePicker into OpenOffice.org (Aqua/X11)
Concerns : OpenOffice.org 2.0.3 or superior, for Mac OS X port (both Aqua and X11 versions)
Skills : knowledge of languages C / C++ , using Carbon/Cocoa API
Proposed by : Tino Rachui Tino.Rachui@Sun.COM
Integrate the native Mac OS X FilePicker into OpenOffice.org The OOo FilePicker is already designed as a UNO component. What is needed is a new implementation of the FilePicker component based on the native Mac OS X FilePicker as it has been done on MS Windows for instance. On current Mac OS X port of OpenOffice.org, the current FilePicker is not native, less ergonomic.
Possible tasks :
Familiarize with the native Mac OS X FilePicker API and the OOo UNO interfaces for the FilePicker Describe current implementation : design, concerned modules, isolate classes and parameters to manage propose a new design using Apple API write and test a proof of concept
- Contact Tino Rachui ( Tino dot Rachui at Sun dot COM )
- dev@porting.openoffice.org
Porting : Mac OS X Address book integration (Aqua / X11)
Subject proposed by: Oliver Braun nerd at warpsite dot de
Synopsis: OOo currently is integrated with the Mozilla address book but not with the native Mac OS X address book. This is annoying for Mac OS X user. For better system integration it would be desirable to integrate with the Mac OS X address book.
Concerns: OpenOffice.org 2.x for Mac OS X (both Aqua and X11 versions)
Skills: Knowledge of languages C/C++, Mac OS X APIs and Application frameworks like Carbon or Cocoa for instance, knowledge of the Mac OS X address book APIs
Tasks: Familiarize with the Mac OS X address book API's Familiarize with the current OOo Mozilla address book integration Make a prototype for OOo Mac OS X address book integration
- Contact
- Oliver Braun ( nerd at warpsite dot de )
- dev@porting.openoffice.org