Apache OpenOffice Wiki - User contributions [en]

Product Release

2008-12-17T13:07:58Z

KAMiKAZOW: /* Ongoing OpenOffice.org 3.x.x */

== Product Releases of OpenOffice.org ==

For detailed release information or roadmap please see http://development.openoffice.org/releases/

For a list of uploaded developer snapshots and release candidates/releases see http://wiki.services.openoffice.org/wiki/Product_Release/builds_uploaded

For guidance on announcing new releases see http://wiki.services.openoffice.org/wiki/PolicyMirrorLinking

Change & transition to more regular time-based releases is
underway here; checkout Martin's
[http://development.openoffice.org/releases/OpenOffice_org_2_x.html#plan mail]
on the releases list.

=== Ongoing OpenOffice.org 3.x.x ===
* [[OOoRelease301]] estimated release January 15th, 2009: for details, please have a look at the document
* [[OOoRelease31]] estimated release March 29th, 2009: for details, please have a look at the document

=== Released OpenOffice.org 3.x.x ===

* [[OOoRelease30|OpenOffice.org 3.0]] (October 13th, 2008)

=== Ongoing OpenOffice.org 2.x.x ===
* [[OOoRelease242|OpenOffice.org 2.4.2]] (October 28th, 2008)

=== Released OpenOffice.org 2.x.x ===
* [[OOoRelease241|OpenOffice.org 2.4.1]] (June 10th, 2008)
* [[OOoRelease24|OpenOffice.org 2.4]] (March 27th, 2008)
* [[OOoRelease231|OpenOffice.org 2.3.1]] (December 4th, 2007)
* [[OOoRelease23|OpenOffice.org 2.3]] (September 17th 2007)
* [[OOoRelease221|OpenOffice.org 2.2.1]] (June 12th 2007)
* [[OOoRelease22|OpenOffice.org 2.2]] (March 29th 2007)
* [[OOoRelease205|OpenOffice.org 2.1]] (December 12th 2006)
* [[OOoRelease204|OpenOffice.org 2.0.4]] (October 13th 2006)
* [[OOoRelease203|OpenOffice.org 2.0.3]] (June 29th 2006)
* [[OOoRelease202|OpenOffice.org 2.0.2]] (March 8th 2006)
* [[OOoRelease201|OpenOffice.org 2.0.1]] (December 21st 2005)
* [[OOoRelease200|OpenOffice.org 2.0.0]] (October 21st 2005)

=== OpenOffice.org 1.1 ===

* OpenOffice.org 1.1.5 (September 9th, 2005)
* OpenOffice.org 1.1.4 (December 22th, 2004)
* OpenOffice.org 1.1.3 (October 4th, 2004)
* OpenOffice.org 1.1.2 (June 18th, 2004)
* OpenOffice.org 1.1.1
* OpenOffice.org 1.1.0 (October 1st, 2003)

=== OpenOffice.org 1.0 ===

* OpenOffice.org 1.0.3 (April 10th, 2003)
* OpenOffice.org 1.0.2 (tag OpenOffice_1_0_2) (January, 20th, 2003)
* OpenOffice.org 1.0.1 (tag OpenOffice_1_0_1) (July 17th, 2002)

[[Category:Releases]]
[[Category:Quality Assurance]]

Mac OS X Porting - OpenGL transitions

2008-12-17T13:05:10Z

KAMiKAZOW:

== <div align="left" style="color:red; font-size:18px">'''OpenGL transitions on Mac OS X '''</div> ==

=== Description ===

<br>
'''In Impress, there are transitions between slides, with or without funny 3D effects. The problem is, those nice and Funny effects are power consuming, and without hardware acceleration – means software rendered –, extremely slow, what is not acceptable by users.'''

'''This task aims to replace the software rendered transitions with hardware accelerated transitions on Mac OS X.'''

'''We'll use OpenGL, the API Mac OS X does natively use'''

'''Below the technical description, the involved code, the plan, and so on. Feel free to add information if you estimate it usefull for the task.'''

'''Thanks in advance :-)'''

=== Goal ===

<div align="left" style="color:blue; font-size:14px">'''Make OpenGL transitions work in Impress, on Mac OS X Aqua'''</div>

=== Timeline ===

Expected timeline: '''October / November 2008'''

=== Current status ===
<br>

<div align="left" style="color:green; font-size:14px">'''26th September '''</div>

'''One issue verified on 42" screen ''' : during OpenGL transitions, the view does not use the fullscreen area, but the Windowed view area (needs to check the exact area ) -> work in progress''', + some limitations (unimplemented features), explained below.

<br>

<div align="left" style="color:green; font-size:14px">'''7th September '''</div>

Excepted the flicker (caused be the slideshow itself) the transitions work. We have two working solutions, and a choice for the implementation will probably be done soon ( waiting from ssa, who will decide what is the best )

Remaining tasks:

* build issue in officecfg: the .xcs and .xcu files have to be modified when ENABLE_OPENGL is true
* check for memory leaks
* check for stability

<div align="left" style="color:green; font-size:14px">'''31st August '''</div>

FIXED: Fixed the colorspace issue: was the pDetectedFormat

TODO:

* Cleanup in void OGLTransitionerImpl::GLInitSlides()
* Continue to search what happens with the frame (why this sort of "refresh ?" )
* Work in progress: started learning the slideshow

<div align="left" style="color:green; font-size:14px">'''30th August '''</div>

The issue with flicker seems to be caused by the slideshow itself. I'll add symbols in libsd, and I'll try to see what happens.

concerned code is in: sd/source/ui/slideshow

The color issue seems to be caused by some color/alpha channel ( RGBA .. RGAB ) or something like that issue.

Shane M. Mathews (I'm in contact with him) suggested several possibilites. I'll give them a try.

Issue 0 was not an issue. OpenGL version detected is at least 1.3, but can be more.

'''TODO''': test on Leopard, just in case the issue is Tiger only (that would be a bad news)

<div align="left" style="color:green; font-size:14px">'''29th August '''</div>

Re-reading OpenGL Programming Guide. Tested a lot of possibilities with NSOpenGLContext, unsuccessfully.

Radek Dulik adviced me to check whether the context is really Double buffered (was an issue on Linux). Maybe a missing makeCurrentcontext somewhere (where ? )

Analyzed the known issues:

0) solved: OpenGL 1.2 or 1.3 detected (2.0 should work imho)

1) bad colors (bad OpenGL initialization?)
Looks like the complementary color appears, of red effect added. Needs more work

2) offset in window mode, caused by scrollbar not included in the slide position computation
(the frame dimensions are different)

3) flicker

the problem is (using ssa words):

* the slideshow displays the slide first
* then an opengl view is painted on top of it and plays the slide transition
* once it is removed the old background appears again still containing the first frame of the animation
* and after a very short time the slideshow engine draws the final frame,
* which is visible as a flicker

4) optimization / compatibility?

<div align="left" style="color:green; font-size:14px">'''28th August '''</div>

'''Works''' (experimental and hacked builds are available at [http://oooaqua.laurentbuisson.fr Laurent Buisson site]).

There are currently no crash, but it needs improvement:

* bad colors
* flickering at the end (will need precise and non trivial work)
* no optimization

other tests in progress: replace the NSOpenGLView, with a customized NSView ( sublassed as NSOpenGLView, with more possibilities)

'''cws state changed for new'''

'''added tasks and modules to the cws'''. First commits to come soon.

=> Important: don't forget to run autoconf in config_office, to regenerate configure (configure.in has been modified)

<div align="left" style="color:green; font-size:14px">'''27th August '''</div>

'''cws ogltrans4mac has been created ''' (planned)

Stephan Schaefer helped me ( he made the NSOpenGLView work some weeks ago), and including all the changes, I was able to package a working version!

Created the patches concerning:

* scp2,
* config_office (René confirmed it is ok to bypass OpenGL / gl.h, glut.h headers and GLUT tests, and declare ENABLE_OPENGL=TRUE as default on Mac OS X),
* officecfg,
* sd,
* slideshow

Waiting for more information, about how proceed in vcl (I now know it works, but a big issue remains to be fixed :-) ).

<div align="left" style="color:green; font-size:14px">'''26th August '''</div>

Found why the libOGLTrans was not loaded: the registration as UNO_COMPONENT was not done.

Other issues : the new transitions effects are not listed, because not in the .xcu nor any .xml

I finally found where: in sd/xml! -> transitions-ogl (who is a plain .xml file) has to be

* renammed into transition-ogl.xml
* copied into the solver (accordingly to th esd/prj/d.lst file)

Consequence : some changes are needed in officecfg too:

Existing transitions are put in officecfg/registry/data/org/openoffice/Office/UI/Effects.xcu

-> new entries, matching with transitions-ogl.xml have to be entered (probably around line 1910, after "Random Transition" effect)

FIXME : localisation of new transitions names?

<div align="left" style="color:green; font-size:14px">'''25th August '''</div>

Reading documentation (vcl code, mostly about outdev and co)

Defined the implementation plan (working with DEV300_m29)

<div align="left" style="color:green; font-size:14px">'''24th August '''</div>

Did some tests, using the first aquaOpenGLView I created. Lot of crashes.

<div align="left" style="color:green; font-size:14px">'''23rd August '''</div>

Added other ideas

<div align="left" style="color:green; font-size:14px">'''22nd August '''</div>

Started the wiki page and the implementation in parallel

PLEASE DO NOT REMOVE THE CREATION DATE

Page created [[User:Ericb|Ericb]] 11:55, 22 August 2008 (CEST)

=== Concerned domains ===
<br>
<div align="left" style="color:blue; font-size:14px">'''Build :'''</div>

* conditional activation of ENABLE_OPENGL in configure
* addition of NSOpenGLView class in vcl
* conditional build of libOGLTrans.dylib in slideshow
* conditional packaging of ligOGLTrans.dylib in scp2
* conditional addition of new transitions in the officecfg schema/UI files
* conditional registration of libOGLTrans.dylib at packaging time

<div align="left" style="color:blue; font-size:14px">'''Core :'''</div>

* NSOpenGLView implementation in vcl
* OpenGL initialization and context creation in the slideshow
* load the libOGLTrans.dylib

<div align="left" style="color:blue; font-size:14px">'''User Interface :'''</div>

* add the list of the new transitions in the list
* use them

=== ''' Concerned modules''' ===

* config_office: make OpenGL default on Mac OS X Aqua => ENABLE_OPENGL=TRUE
* slideshow: where the lib is built. This lib is linked with libvcl (vcl must be built before slideshow)
* scp2: to add the new lib in the package
* sd : rename the transitions-ogl in transitions-ogl.xml and deliver it
* officecfg : add the new transitions names in the list, to make them appear in the UI + add the transitions-ogl.xml file name in the matching Effects.xcs schema

=== Examples ===

<br>

<div align="left" style="color:red; font-size:16px">'''To illustrate the current work in progress, some experimental screenshots are available [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_August_2008/OGLTransitions/screenshots => CLICK ME]'''</div>

<br>

=== Feedback ===

<br>

The page below, '''is the place for user experience comments, suggestions and feddback'''.

<div align="left" style="color:red; font-size:16px">'''PLEASE use it and contribute! [http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_OpenGL_transitions/Feedback click me]'''</div>

<br>

== '''Modifications''' ==

=== Existing (historical implementation) ===

Common:

vcl/source/opengl.cxx, implements:

* functions pointers (most important gl functions typedef'ed)
* + corresponding macro for functions initialization
* + impl functions getters
* Ctor: parameter pOutDev is a pointer on a OutputDevice*, using mpOutDev
* Dtor: deletes mpOGL
* usual methods ... and so on

vcl/source/salogl.cxx:

* Static members: oslModule (himpOGLLib == libgl.dylib), NSOpenGLContext* .. (bool) state
* Macros
* Callbacks for CreateContext, DeleteContext, MakeCurrent, GetCurrentContext
* OpenGLWndProc (what's that ?)

vcl/source/gdi/outdev.cxx
->there is a very interesting OpenGL* OutputDevice::GetOpenGL()

FIXME: To be continued

=== Concerned files / ideas ===

==== ''' Ideas''' ====

27th August

Created the patches concerning:

* scp2,
* config_office (René confirmed it is ok to bypass OpenGL / gl.h, glut.h headers and GLUT tests, and declare ENABLE_OPENGL=TRUE as default on Mac OS X),
* officecfg,
* sd,
* slideshow

Should be the only concerned modules. I used the OpenGL transitions listed in sd/xml/transitions-ogl.xml, but there are obvisouly more in slideshow/source/engine/transitions.

Waiting for more information, about how proceed in vcl (I now know it works, but a big issue remains to be fixed :-) ).

26th August:

I finally found why the libOGLTrans was not loaded: the registration as UNO_COMPONENT was not done.

Other issues : the new transitions effects are not listed, because not in the .xcu nor any .xml

I finally found where: in sd/xml! -> transitions-ogl (who is a plain .xml file) has to be

* renammed into transition-ogl.xml
* copied into the solver (accordingly to th esd/prj/d.lst file)

Consequence: some changes are needed in officecfg too:

Existing transitions are put in officecfg/registry/data/org/openoffice/Office/UI/Effects.xcu

-> new entries, matching with transitions-ogl.xml have to be entered (probably around line 1910, after "Random Transition" effect)

FIXME : localisation of new transitions names?

25th august:

After reading a lot of code (mostly vcl), it appears this is not possible (excepted doing hacks), to use OpenGL without use outdev thing (got systematic crashes using NSOpenGLView directly, and outdev complains about lost events and pending pointers)

The consequence is, the slideshow calls must be abstraction of CreateContext, MakeCurrentContext, ReleaseContext ..etc.

And the real implementation must go in vcl/aqua/source/gdi/salogl.cxx, respecting vcl/source/gdi/opengl.cxx virtual classes.

The plan (to be confirmed seems to be):

* design the abstraction we'll use, and prepare the OGLTrans_TransitionerImpl.cxx like it is for Linux, but adapted to Mac OS X
* implement NSOpenGLView* pOpenGLView in vcl, guessing it will be sufficient (else, we'll have to implement a new class, but things will become complicated)
* define the NSView containing the scene, instantiate an OpenGLNSView using the same frame, and use addSubview. Current choosen Place to do that: OGLTrans_TransitionerImpl.cxx
* implement (using existing Windows and Linux implementation) the same classes / macros ( :-/ ) methods in salogl.cxx
* add the mac osx cases in outdev and anywhere else it is needed

Retry with the coming DEV300_m30

====Possibilities:====

Everything is based on implement an OpenGLView adding a new NSOpenGLView* pOpenGLView object in sysdata.hxx, or an NSView drawn as a subview of the (NSView * type) pView.

'''TODO''': investigate about ImplOutdev and co

Try 1: '''either''' implement (NSView * type) pOpenGLView in vcl, more precisely, modify:

vcl/inc/vcl/sysdata.hxx

vcl/aqua/inc/salframe.h

vcl/aqua/inc/salframeview.h,

vcl/aqua/source/window/salframe.cxx

vcl/aqua/source/window/salobj.cxx

+ the makefile

and in slideshow:

slideshow/source/engine/OGLTrans/OGLTrans_TransitionImpl.hxx

slideshow/source/engine/OGLTrans/OGLTrans_TransitionImpl.cxx

slideshow/source/engine/OGLTrans/OGLTrans_TransitionerImpl.cxx

'''Issue is at buildtime''':

Pb: visibility of the vcl/aqua/inc headers from slideshow at buildtime

Update: predeclaration in vcl/inc/vcl/sysdata.hxx will help a lot.

Main issue is, how to explain the compiler NSView* pOpenGLView has new methods (OpenGL specific), the NSView* pView has not ?

More precisely, there are warnings because the pOpenGLView is supposed receive no answer from the OpenGL specific methods used in OGLTrans_TransitionerImpl.cxx. In theory, it should work out of the box, but the code aims to be warning free; so this solution is not acceptable.

Workaround could be implement the new methods directly in the NSView, or delegate. Just wild guess [FIXME]

Try 2 '''or'''

(maybe completely wrong, but worth a try)

Implement the OpenGL methods directly in the SalframeView. just two methods have the same names/parameters numbers, so just rename they properly to avoid clash. Important: initWithFrame for OpenGL has two parameters, while initWithFrame for normal NSView has only one.

Try 3 '''or'''

Add an NSOpenGLView * pOpenGLView in the sysdata.hxx, and modify everything in vcl accordingly.

<div align="left" style="color:blue; font-size:18px">''' [[Mac_OS_X_Porting_-_OpenGL_transitions/NSOpenGLView | ==> click here to have a look at NSOpenGLView available methods]]''' </div>

Thus, in OGLTrans_TransitionerImpl.cxx instanciate

an NSView who is a pointer on the normal NSView, and an NSOpenGLView, who is a pointer

'''or'''

create the AquaOpenGLView object directly in slideshow, modify the other slideshow files mentioned above (changes are similar)

===='''Result''' ====

Using the second solution, the subview seems to -somewhat- show something.

'''Test''': a right click in the transition demo, using the presentation wizard, give the same contextual menu we have in fullscreen (yes, this is weird, but this is encouraging for the future).

'''Known issue''': there is no communication between the subView and the NSApplication, events are lost, timeout and chaos in event queue

-> deadlock and crash.

TODO: Second test will consist in delegate the notifications send for the refresh, to the NSApp.

It is expected, once this NSOpenGL view will work, this should be no problem to use it from the slideshow.

Communication between slideshow object and the NSApplication (customized NSView, itself inheriting of NSWindow) will use the notification center as proxy (what is extremely fast in theory).
<br>
<br>

==== '''Tasks and concerned files''' ====
<br>
<div align="left" style="color:blue; font-size:14px">'''Make ENABLE_OPENGL default on Mac OS X'''</div>

'''config_office/configure.in''' + run autoconf '''Add the info in the cws comments for the RE !'''

Result: ENABLE_OPENGL=TRUE on Mac OS X Aqua // '''OK'''

<div align="left" style="color:blue; font-size:14px">'''Task: build the lib'''</div>

'''slideshow/source/engine/OGLTrans/makefile.mk''' // '''OK'''

add the case Aqua, modify CFLAGSCXX + add fremaworks OpenGL, GLUT and Cocoa for linking

<div align="left" style="color:blue; font-size:14px">'''Task: Deliver the libs / includes:'''</div>

'''slideshow/prj/d.lst''' // '''OK'''

deliver the new lib on Aqua (libOGLTrans.dylib)

Other modified files in slideshow:

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionImpl.cxx''' // '''OK'''

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionImpl.hxx''' // '''OK'''

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionerImpl.cxx''' // '''OK'''

<div align="left" style="color:blue; font-size:14px">'''Task: package and register the OGLTrans as UNO_COMPONENT '''</div>

Must be done only if ENABLE_OPENGL is TRUE, and this environment variable must be turned in preprocessor macro:

'''scp2/source/impress/makefile.mk''' // '''OK'''

Package and registration of the lib :

'''scp2/source/ooo/file_library_ooo.scp''' // '''OK'''

'''scp2/source/ooo/makefile.mk''' // '''OK'''

Package and registration of the new file transitions-ogl.xml

'''scp2/source/impress/file_impress.scp''' // '''OK'''

<div align="left" style="color:blue; font-size:14px">'''Task: rename the transitions-ogl in transitions-ogl.xml and deliver it '''</div>

'''sd/prj/build.lst''' // '''OK'''

'''sd/prj/d.lst''' // '''OK'''

'''sd/xml/makefile.mk''' // '''OK''' ## New file to be created

'''sd/xml/transitions-ogl''' // '''OK''' to be renamed in transitions-ogl.xml and delivered in the solver, in solver/300/$build_type/xml

<div align="left" style="color:blue; font-size:14px">'''Task: add the new transitions names in the list, to make them appear in the UI '''</div>

'''officecfg/registry/data/org/openoffice/Office/UI/Effects.xcu''' // '''OK'''

<div align="left" style="color:orange; font-size:14px">'''FIXME: this change is plain wrong, because created even when ENABLE_OPENGL is not TRUE :-/ '''</div>

<div align="left" style="color:blue; font-size:14px">'''Task: add the transitions-ogl.xml file name in the Impress.xcs schema '''</div>

'''officecfg/registry/schema/org/openoffice/Office/Impress.xcs''' // '''OK'''

( the final file containing the new transitions will be OOO_BASE_DIR/share/config/soffice.cfg/simpress/transitions-ogl.xml )

<div align="left" style="color:orange; font-size:14px">'''FIXME: this change is plain wrong, because created even when ENABLE_OPENGL is not TRUE :-/ '''</div>

Better solution : reuse the fix I provided in macmenusquit ( at packaging time, modify the .xml on the fly, using xsltproc)

New files who could contain the customized NSView if ever the NSOpenGLView does not work well (to be confirmed, not sure at all):

slideshow/source/engine/OGLTrans/aquaOpenGLView.h

slideshow/source/engine/OGLTrans/aquaOpenGLView.m

== '''Issues attached to the task''' ==

[http://www.openoffice.org/issues/show_bug.cgi?id=93013 issue 93013]

==''' TODO (draft)'''==

* [DONE] build the OpenGL trans lib, warning free, on Mac OS X
**[DONE] fix warnings and breakages, with empty implementation
**[DONE] fix linking
**[Done but needs work] create customized NSView (skeleton, and pre-implementation)
*[DONE] add the lib to the package
* [DONE] register the lib
* [DONE] rename the transitions-ogl in transitions-ogl.xml in sd and deliver it properly in the solver
* in officecfg, add the new transitions names in the list, to make them appear in the UI
* [DONE] in officecfg, add the transitions-ogl.xml file name in the matching Effects.xcs schema
*[DONE] Design the first implementation
** design the abstraction used in slideshow
*[DONE] implement NSOpenGLView or customize an NSView [Current plan: try using NSOpenGLView first]
** manage OpenGL context
** manage OpenGL pixels mapping
** manage colors
** manage events and notifications '''critical'''
** initialize the view properly in splitted view
** manage geometry
**[WORKS] implement the fullscreen mode
* finalize the transitions integration in Aqua bundle
*[DONE] make transitions work
* work on the flickering issue with last image
* test
*integrate

== '''LINKS''' ==

Below a now exhaustive list of links. Feel free to add interesting links.

[http://wiki.services.openoffice.org/wiki/Impress:_OpenGL_rendered_transitions '''Original Shane M. Mathews OpenGL transitions implementation (GSoC 2007, mentor: Thorsten Behrens)''']

[http://developer.apple.com/documentation/GraphicsImaging/OpenGL-date.html Apple OpenGL Documentation]

[http://www.cocoadev.com/index.pl?CocoaOpenGl Cocoa OpenGL]

[http://www.cocoadev.com/index.pl?CustomGLView Custom GLView]

[http://search.lists.apple.com/?q=NSView++NSOpenGLView&cmd=Search%21 NSView + OpenGLView in Apple database]

[http://lists.apple.com/archives/mac-opengl/2005/Dec/msg00089.html NSOpenGLView initialisation issue]

{| class="prettytable" border="1"

|-

! Name

! OOo Nickname

! Role

|-

| Eric Bachard

| ericb2

| Development, Documentation

|-

| Stephan Schaefer

| ssa

| Development

|-

| xxxx

| xxxx

| User Experience

|-

| xxxxxx

| xxxxxx

| Documentation

|}

== COMPLETE ME ==

[[Category:Aqua]]

[[Category:MacOSX]]

[[Category:Education]]

Mac OS X Porting - OpenGL transitions

2008-12-17T13:01:10Z

KAMiKAZOW: /* Description */

== <div align="left" style="color:red; font-size:18px">'''OpenGL transitions on Mac OS X '''</div> ==

=== Description ===

<br>
'''In Impress, there are transitions between slides, with or without funny 3D effects. The problem is, those nice and Funny effects are power consuming, and without hardware acceleration – means software rendered –, extremely slow, what is not acceptable by users.'''

'''This task aims to replace the software rendered transitions with hardware accelerated transitions on Mac OS X.'''

'''We'll use OpenGL, the API Mac OS X does natively use'''

'''Below the technical description, the involved code, the plan, and so on. Feel free to add information if you estimate it usefull for the task.'''

'''Thanks in advance :-)'''

=== Goal ===

<div align="left" style="color:blue; font-size:14px">'''Make OpenGL transitions work in Impress, on Mac OS X Aqua'''</div>

=== Timeline ===

Expected timeline: '''October / November 2008'''

=== Current status ===
<br>

<div align="left" style="color:green; font-size:14px">'''26th September '''</div>

'''One issue verified on 42" screen ''' : during OpenGL transitions, the view does not use the fullscreen area, but the Windowed view area (needs to check the exact area ) -> work in progress''', + some limitations (unimplemented features), explained below.

<br>

<div align="left" style="color:green; font-size:14px">'''7th September '''</div>

Excepted the flicker (caused be the slideshow itself) the transitions work. We have two working solutions, and a choice for the implementation will probably be done soon ( waiting from ssa, who will decide what is the best )

Remaining tasks :

* build issue in officecfg : the .xcs and .xcu files have to be modified wen ENABLE_OPENGL is true
* check for memory leaks
* check for stability

<div align="left" style="color:green; font-size:14px">'''31st August '''</div>

FIXED : Fixed the colorspace issue: was the pDetectedFormat

TODO :

* Cleanup in void OGLTransitionerImpl::GLInitSlides()
* Continue to search what happens with the frame (why this sort of "refresh ?" )
* Work in progress: started learning the slideshow

<div align="left" style="color:green; font-size:14px">'''30th August '''</div>

The issue with flicker seems to be caused by the slideshow itself. I'l add symbols in libsd, and I'll try to see what happens.

concerned code is in : sd/source/ui/slideshow

The color issue seems to be caused by some color/alpha channel ( RGBA .. RGAB ) or something like that issue.

Shane M. Mathews (I'm in contact with him) suggested several possibilites. I'll give them a try.

Issue 0 was not an issue. OpenGL version detected is at least 1.3, but can be more.

'''TODO''' : test on Leopard, just in case the issue is Tiger only (that would be a bad news)

<div align="left" style="color:green; font-size:14px">'''29th August '''</div>

Re-reading OpenGL Programming Guide. Tested a lot of possibilities with NSOpenGLContext, unsuccessfully.

Radek Dulik adviced me to check whether the context is really Double buffered (was an issue on Linux). Maybe a missing makeCurrentcontext somewhere (where ? )

Analyzed the known issues:

0) solved: OpenGL 1.2 or 1.3 detected (2.0 should work imho )

1) bad colors ( bad OpenGL initialization ? )
Looks like the complementary color appears, of red effect added. Needs more work

2) offset in window mode, caused by scrollbar not included in the slide position computation
(the frame dimensions are different)

3) flicker

the problem is (using ssa words) :

* the slideshow displays the slide first
* then an opengl view is painted on top of it and plays the slide transition
* once it is removed the old background appears again still containing the first frame of the animation
* and after a very short time the slideshow engine draws the final frame,
* which is visible as a flicker

4) optimization / compatibility ?

<div align="left" style="color:green; font-size:14px">'''28th August '''</div>

'''Works''' (experimental and hacked builds are available at [http://oooaqua.laurentbuisson.fr Laurent Buisson site]).

There are currently no crash, but it needs improvement:

* bad colors
* flickering at the end (will need precise and non trivial work)
* no optimization

other tests in progress: replace the NSOpenGLView, with a customized NSView ( sublassed as NSOpenGLView, with more possibilities)

'''cws state changed for new'''

'''added tasks and modules to the cws'''. First commits to come soon.

=> Important: don't forget to run autoconf in config_office, to regenerate configure (configure.in has been modified)

<div align="left" style="color:green; font-size:14px">'''27th August '''</div>

'''cws ogltrans4mac has been created ''' (planned)

Stephan Schaefer helped me ( he made the NSOpenGLView work some weeks ago), and including all the changes, I was able to package a working version !

Created the patches concerning :

* scp2,
* config_office (René confirmed it is ok to bypass OpenGL / gl.h, glut.h headers and GLUT tests , and declare ENABLE_OPENGL=TRUE as default on Mac OS X),
* officecfg,
* sd,
* slideshow

Waiting for more information, about how proceed in vcl (I now know it works, but a big issue remains to be fixed :-) ).

<div align="left" style="color:green; font-size:14px">'''26th August '''</div>

Found why the libOGLTrans was not loaded: the registration as UNO_COMPONENT was not done.

Other issues : the new transitions effects are not listed, because not in the .xcu nor any .xml

I finally found where: in sd/xml ! -> transitions-ogl (who is a plain .xml file) has to be

* renammed into transition-ogl.xml
* copied into the solver (accordingly to th esd/prj/d.lst file)

Consequence : some changes are needed in officecfg too:

Existing transitions are put in officecfg/registry/data/org/openoffice/Office/UI/Effects.xcu

-> new entries, matching with transitions-ogl.xml have to be entered (probably around line 1910, after "Random Transition" effect)

FIXME : localisation of new transitions names ?

<div align="left" style="color:green; font-size:14px">'''25th August '''</div>

Reading documentation ( vcl code, mostly about outdev and co )

Defined the implementation plan (working with DEV300_m29)

<div align="left" style="color:green; font-size:14px">'''24th August '''</div>

Did some tests, using the first aquaOpenGLView I created. Lot of crashes.

<div align="left" style="color:green; font-size:14px">'''23rd August '''</div>

Added other ideas

<div align="left" style="color:green; font-size:14px">'''22nd August '''</div>

Started the wiki page and the implementation in parallel

PLEASE DO NOT REMOVE THE CREATION DATE

Page created [[User:Ericb|Ericb]] 11:55, 22 August 2008 (CEST)

=== Concerned domains ===
<br>
<div align="left" style="color:blue; font-size:14px">'''Build :'''</div>

* conditional activation of ENABLE_OPENGL in configure
* addition of NSOpenGLView class in vcl
* conditional build of libOGLTrans.dylib in slideshow
* conditional packaging of ligOGLTrans.dylib in scp2
* conditional addition of new transitions in the officecfg schema/UI files
* conditional registration of libOGLTrans.dylib at packaging time

<div align="left" style="color:blue; font-size:14px">'''Core :'''</div>

* NSOpenGLView implementation in vcl
* OpenGL initialization and context creation in the slideshow
* load the libOGLTrans.dylib

<div align="left" style="color:blue; font-size:14px">'''User Interface :'''</div>

* add the list of the new transitions in the list
* use them

=== ''' Concerned modules''' ===

* config_office: make OpenGL default on Mac OS X Aqua => ENABLE_OPENGL=TRUE
* slideshow: where the lib is built. This lib is linked with libvcl (vcl must be built before slideshow)
* scp2: to add the new lib in the package
* sd : rename the transitions-ogl in transitions-ogl.xml and deliver it
* officecfg : add the new transitions names in the list, to make them appear in the UI + add the transitions-ogl.xml file name in the matching Effects.xcs schema

=== Examples ===

<br>

<div align="left" style="color:red; font-size:16px">'''To illustrate the current work in progress, some experimental screenshots are available [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_August_2008/OGLTransitions/screenshots => CLICK ME]'''</div>

<br>

=== Feedback ===

<br>

The page below, '''is the place for user experience comments, suggestions and feddback'''.

<div align="left" style="color:red; font-size:16px">'''PLEASE use it and contribute ! [http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_OpenGL_transitions/Feedback click me]'''</div>

<br>

== '''Modifications''' ==

=== Existing (historical implementation) ===

Common:

vcl/source/opengl.cxx, implements:

* functions pointers (most important gl functions typedef'ed)
* + corresponding macro for functions initialization
* + impl functions getters
* Ctor: parameter pOutDev is a pointer on a OutputDevice*, using mpOutDev
* Dtor: deletes mpOGL
* usual methods ... and so on

vcl/source/salogl.cxx:

* Static members: oslModule (himpOGLLib == libgl.dylib), NSOpenGLContext* .. (bool) state
* Macros
* Callbacks for CreateContext, DeleteContext, MakeCurrent, GetCurrentContext
* OpenGLWndProc (what's that ?)

vcl/source/gdi/outdev.cxx
->there is a very interesting OpenGL* OutputDevice::GetOpenGL()

FIXME: To be continued

=== Concerned files / ideas ===

==== ''' Ideas''' ====

27th August

Created the patches concerning :

* scp2,
* config_office (René confirmed it is ok to bypass OpenGL / gl.h, glut.h headers and GLUT tests , and declare ENABLE_OPENGL=TRUE as default on Mac OS X),
* officecfg,
* sd,
* slideshow

Should be the only concerned modules. I used the OpenGL transitions listed in sd/xml/transitions-ogl.xml, but there are obvisouly more in slideshow/source/engine/transitions.

Waiting for more information, about how proceed in vcl (I now know it works, but a big issue remains to be fixed :-) ).

26th August:

I finally found why the libOGLTrans was not loaded: the registration as UNO_COMPONENT was not done.

Other issues : the new transitions effects are not listed, because not in the .xcu nor any .xml

I finally found where: in sd/xml ! -> transitions-ogl (who is a plain .xml file) has to be

* renammed into transition-ogl.xml
* copied into the solver (accordingly to th esd/prj/d.lst file)

Consequence : some changes are needed in officecfg too:

Existing transitions are put in officecfg/registry/data/org/openoffice/Office/UI/Effects.xcu

-> new entries, matching with transitions-ogl.xml have to be entered (probably around line 1910, after "Random Transition" effect)

FIXME : localisation of new transitions names ?

25th august:

After reading a lot of code (mostly vcl), it appears this is not possible (excepted doing hacks), to use OpenGL without use outdev thing (got systematic crashes using NSOpenGLView directly, and outdev complains about lost events and pending pointers)

The consequence is, the slideshow calls must be abstraction of CreateContext, MakeCurrentContext, ReleaseContext ..etc.

And the real implementation must go in vcl/aqua/source/gdi/salogl.cxx, respecting vcl/source/gdi/opengl.cxx virtual classes.

The plan (to be confirmed seems to be):

* design the abstraction we'll use, and prepare the OGLTrans_TransitionerImpl.cxx like it is for Linux, but adapted to Mac OS X
* implement NSOpenGLView* pOpenGLView in vcl, guessing it will be sufficient (else, we'll have to implement a new class, but things will become complicated)
* define the NSView containing the scene, instantiate an OpenGLNSView using the same frame, and use addSubview. Current choosen Place to do that: OGLTrans_TransitionerImpl.cxx
* implement (using existing Windows and Linux implementation) the same classes / macros ( :-/ ) methods in salogl.cxx
* add the mac osx cases in outdev and anywhere else it is needed

Retry with the coming DEV300_m30

====Possibilities:====

Everything is based on implement an OpenGLView adding a new NSOpenGLView* pOpenGLView object in sysdata.hxx, or an NSView drawn as a subview of the (NSView * type) pView.

'''TODO''': investigate about ImplOutdev and co

Try 1: '''either''' implement (NSView * type) pOpenGLView in vcl, more precisely, modify:

vcl/inc/vcl/sysdata.hxx

vcl/aqua/inc/salframe.h

vcl/aqua/inc/salframeview.h,

vcl/aqua/source/window/salframe.cxx

vcl/aqua/source/window/salobj.cxx

+ the makefile

and in slideshow:

slideshow/source/engine/OGLTrans/OGLTrans_TransitionImpl.hxx

slideshow/source/engine/OGLTrans/OGLTrans_TransitionImpl.cxx

slideshow/source/engine/OGLTrans/OGLTrans_TransitionerImpl.cxx

'''Issue is at buildtime''':

Pb: visibility of the vcl/aqua/inc headers from slideshow at buildtime

Update: predeclaration in vcl/inc/vcl/sysdata.hxx will help a lot.

Main issue is, how to explain the compiler NSView* pOpenGLView has new methods (OpenGL specific), the NSView* pView has not ?

More precisely, there are warnings because the pOpenGLView is supposed receive no answer from the OpenGL specific methods used in OGLTrans_TransitionerImpl.cxx. In theory, it should work out of the box, but the code aims to be warning free; so this solution is not acceptable.

Workaround could be implement the new methods directly in the NSView, or delegate. Just wild guess [FIXME]

Try 2 '''or'''

(maybe completely wrong, but worth a try)

Implement the OpenGL methods directly in the SalframeView. just two methods have the same names/parameters numbers, so just rename they properly to avoid clash. Important: initWithFrame for OpenGL has two parameters, while initWithFrame for normal NSView has only one.

Try 3 '''or'''

Add an NSOpenGLView * pOpenGLView in the sysdata.hxx, and modify everything in vcl accordingly.

<div align="left" style="color:blue; font-size:18px">''' [[Mac_OS_X_Porting_-_OpenGL_transitions/NSOpenGLView | ==> click here to have a look at NSOpenGLView available methods]]''' </div>

Thus, in OGLTrans_TransitionerImpl.cxx instanciate

an NSView who is a pointer on the normal NSView, and an NSOpenGLView, who is a pointer

'''or'''

create the AquaOpenGLView object directly in slideshow, modify the other slideshow files mentioned above (changes are similar)

===='''Result''' ====

Using the second solution, the subview seems to -somewhat- show something.

'''Test''': a right click in the transition demo, using the presentation wizard, give the same contextual menu we have in fullscreen (yes, this is weird, but this is encouraging for the future).

'''Known issue''': there is no communication between the subView and the NSApplication, events are lost, timeout and chaos in event queue

-> deadlock and crash.

TODO: Second test will consist in delegate the notifications send for the refresh, to the NSApp.

It is expected, once this NSOpenGL view will work, this should be no problem to use it from the slideshow.

Communication between slideshow object and the NSApplication (customized NSView, itself inheriting of NSWindow) will use the notification center as proxy (what is extremely fast in theory).
<br>
<br>

==== '''Tasks and concerned files''' ====
<br>
<div align="left" style="color:blue; font-size:14px">'''Make ENABLE_OPENGL default on Mac OS X'''</div>

'''config_office/configure.in''' + run autoconf '''Add the info in the cws comments for the RE !'''

Result: ENABLE_OPENGL=TRUE on Mac OS X Aqua // '''OK'''

<div align="left" style="color:blue; font-size:14px">'''Task: build the lib'''</div>

'''slideshow/source/engine/OGLTrans/makefile.mk''' // '''OK'''

add the case Aqua, modify CFLAGSCXX + add fremaworks OpenGL, GLUT and Cocoa for linking

<div align="left" style="color:blue; font-size:14px">'''Task: Deliver the libs / includes:'''</div>

'''slideshow/prj/d.lst''' // '''OK'''

deliver the new lib on Aqua (libOGLTrans.dylib)

Other modified files in slideshow:

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionImpl.cxx''' // '''OK'''

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionImpl.hxx''' // '''OK'''

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionerImpl.cxx''' // '''OK'''

<div align="left" style="color:blue; font-size:14px">'''Task: package and register the OGLTrans as UNO_COMPONENT '''</div>

Must be done only if ENABLE_OPENGL is TRUE, and this environment variable must be turned in preprocessor macro:

'''scp2/source/impress/makefile.mk''' // '''OK'''

Package and registration of the lib :

'''scp2/source/ooo/file_library_ooo.scp''' // '''OK'''

'''scp2/source/ooo/makefile.mk''' // '''OK'''

Package and registration of the new file transitions-ogl.xml

'''scp2/source/impress/file_impress.scp''' // '''OK'''

<div align="left" style="color:blue; font-size:14px">'''Task: rename the transitions-ogl in transitions-ogl.xml and deliver it '''</div>

'''sd/prj/build.lst''' // '''OK'''

'''sd/prj/d.lst''' // '''OK'''

'''sd/xml/makefile.mk''' // '''OK''' ## New file to be created

'''sd/xml/transitions-ogl''' // '''OK''' to be renamed in transitions-ogl.xml and delivered in the solver, in solver/300/$build_type/xml

<div align="left" style="color:blue; font-size:14px">'''Task: add the new transitions names in the list, to make them appear in the UI '''</div>

'''officecfg/registry/data/org/openoffice/Office/UI/Effects.xcu''' // '''OK'''

<div align="left" style="color:orange; font-size:14px">'''FIXME: this change is plain wrong, because created even when ENABLE_OPENGL is not TRUE :-/ '''</div>

<div align="left" style="color:blue; font-size:14px">'''Task: add the transitions-ogl.xml file name in the Impress.xcs schema '''</div>

'''officecfg/registry/schema/org/openoffice/Office/Impress.xcs''' // '''OK'''

( the final file containing the new transitions will be OOO_BASE_DIR/share/config/soffice.cfg/simpress/transitions-ogl.xml )

<div align="left" style="color:orange; font-size:14px">'''FIXME: this change is plain wrong, because created even when ENABLE_OPENGL is not TRUE :-/ '''</div>

Better solution : reuse the fix I provided in macmenusquit ( at packaging time, modify the .xml on the fly, using xsltproc)

New files who could contain the customized NSView if ever the NSOpenGLView does not work well (to be confirmed, not sure at all):

slideshow/source/engine/OGLTrans/aquaOpenGLView.h

slideshow/source/engine/OGLTrans/aquaOpenGLView.m

== '''Issues attached to the task''' ==

[http://www.openoffice.org/issues/show_bug.cgi?id=93013 issue 93013]

==''' TODO (draft)'''==

* [DONE] build the OpenGL trans lib, warning free, on Mac OS X
**[DONE] fix warnings and breakages, with empty implementation
**[DONE] fix linking
**[Done but needs work] create customized NSView (skeleton, and pre-implementation)
*[DONE] add the lib to the package
* [DONE] register the lib
* [DONE] rename the transitions-ogl in transitions-ogl.xml in sd and deliver it properly in the solver
* in officecfg, add the new transitions names in the list, to make them appear in the UI
* [DONE] in officecfg, add the transitions-ogl.xml file name in the matching Effects.xcs schema
*[DONE] Design the first implementation
** design the abstraction used in slideshow
*[DONE] implement NSOpenGLView or customize an NSView [Current plan: try using NSOpenGLView first]
** manage OpenGL context
** manage OpenGL pixels mapping
** manage colors
** manage events and notifications '''critical'''
** initialize the view properly in splitted view
** manage geometry
**[WORKS] implement the fullscreen mode
* finalize the transitions integration in Aqua bundle
*[DONE] make transitions work
* work on the flickering issue with last image
* test
*integrate

== '''LINKS''' ==

Below a now exhaustive list of links. Feel free to add interesting links.

[http://wiki.services.openoffice.org/wiki/Impress:_OpenGL_rendered_transitions '''Original Shane M. Mathews OpenGL transitions implementation (GSoC 2007, mentor: Thorsten Behrens)''']

[http://developer.apple.com/documentation/GraphicsImaging/OpenGL-date.html Apple OpenGL Documentation]

[http://www.cocoadev.com/index.pl?CocoaOpenGl Cocoa OpenGL]

[http://www.cocoadev.com/index.pl?CustomGLView Custom GLView]

[http://search.lists.apple.com/?q=NSView++NSOpenGLView&cmd=Search%21 NSView + OpenGLView in Apple database]

[http://lists.apple.com/archives/mac-opengl/2005/Dec/msg00089.html NSOpenGLView initialisation issue]

{| class="prettytable" border="1"

|-

! Name

! OOo Nickname

! Role

|-

| Eric Bachard

| ericb2

| Development, Documentation

|-

| Stephan Schaefer

| ssa

| Development

|-

| xxxx

| xxxx

| User Experience

|-

| xxxxxx

| xxxxxx

| Documentation

|}

== COMPLETE ME ==

Bla bla ...

[[Category:Aqua]]

[[Category:MacOSX]]

[[Category:Education]]

Features

2008-12-17T13:00:19Z

KAMiKAZOW: /* '''Impress''' */

New features planned for OpenOffice.org

<div style="float:right; padding-left:5px;">
{| style="text-align:left; border:1px solid #aaaaaa; background-color:#f9f9f9;width: 200px;font-family: Verdana, sans-serif;"
|- padding:5px;padding-top:0.5em;font-size: 95%;
[mailto:feedback@website.openoffice.org?subject=Wiki%20Features%20feedback feedback]
|-
|}
</div>
== Intro ==

This page is a roadmap for the features planned in future OpenOffice.org releases.

For older releases, see [[/Archive|the archives]].

'''Caution:'''
The items listed here are under continuous development and the dates are therefore subject to change!

=== Project-Specific Wiki-Pages ===

==== Calc ====

See also the [[Calc/To-Dos/Usability|Calc Usability Activities]] page on this wiki.

== Current Release ==

=== Features for the [[OOoRelease24|2.4 Release]] (March 2008) ===

For a comprehensive list, see the [[New_Features_2.4|New Features in OOo 2.4]] page.

=== Writer ===
* [http://www.OOoNinja.com/2007/12/block-selection-mode-new-feature.html Block selection]
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Support for backward references in Find & Replace]
* [http://www.oooninja.com/2008/02/set-select-language-spell-check-switch.html New ways to change language for spell check]

=== Calc ===
* [http://so-web.germany.sun.com/EIS2/changesmails.EditFeature?ReadOnly=true&Id=4087 Separate zoom per sheet]
* [http://www.oooninja.com/2008/01/text-columns-calc-convert-openoffice.html Convert text to columns]
* [http://www.oooninja.com/2008/03/drag-drop-move-copy-link-cells-calc.html Move, copy, and link cells using drag and drop]

=== Impress ===
* [http://www.oooninja.com/2008/02/eye-candy-3d-opengl-transitions-impress.html Thrilling 3D slide transitions using OpenGL]

=== Chart ===
* [http://specs.openoffice.org/chart/DisplayTrendlineEquations.odt Display Trendline equations] ([http://blogs.sun.com/GullFOSS/entry/more_than_just_a_check GullFOSS article], [http://www.OOoNinja.com/2007/12/display-equations-for-regression-lines.html OOoNinja article])
* [http://specs.openoffice.org/chart/Chart_Scales_and_Intervals.odt Scale and Intervals in Chart]
** [http://www.oooninja.com/2008/02/reverse-axis-chart-bar-graph.html Reverse direction of axis]
** Logarithmic scale
** Axis at
** [http://www.oooninja.com/2008/03/data-label-options-calc-chart.html Number Format for Data Labels]
** [http://www.oooninja.com/2008/03/data-label-options-calc-chart.html Display both, the Value and the Percentage]
** [http://www.oooninja.com/2008/03/data-label-options-calc-chart.html Flexible Placement of Data Labels]
** [http://www.oooninja.com/2008/03/data-label-options-calc-chart.html Best Fit Data Label Positioning for Pie Charts]
* [http://specs.openoffice.org/chart/BarChartOptions.odt Options for Bar Charts]
** Show Bars Attached to Different Axes Side-by-side ([http://blogs.sun.com/GullFOSS/entry/new_chart_features_in_openoffice GullFOSS article], [http://www.oooninja.com/2008/01/show-bars-side-by-side-double-column.html OOoNinja article])
** Spacing (gap width)
** Overlap
* Article: [[Chart2/Features2.4|Chart2 features in 2.4]] (this wiki)
* Article: [http://blogs.sun.com/GullFOSS/entry/new_chart_features_in_openoffice New Chart features in OpenOffice.org 2.4] (GullFOSS)

=== Base ===
* [http://eis.services.openoffice.org/EIS2/changesmails.EditFeature?Id=4061 views in HSQLDB database can be edited]
* [http://eis.services.openoffice.org/EIS2/changesmails.EditFeature?Id=4062 property browser: query designer now also available for list box content]
* [http://eis.services.openoffice.org/EIS2/changesmails.EditFeature?Id=4063 property browser: query designer also available for "native" SQL commands]
* [http://eis.services.openoffice.org/EIS2/changesmails.EditFeature?Id=4081 Base now supports also MS Access 2007 files (*.accdb)]

=== General ===
* [http://so-web.germany.sun.com/EIS2/changesmails.EditFeature?ReadOnly=true&Id=4069 Relative links now available in PDF export filter, plus other features added.]
* [http://www.OOoNinja.com/2008/01/generating-pdfa-for-long-term-archiving.html PDF/A export]
* [http://www.oooninja.com/2008/02/create-relative-links-in-pdfs.html Create relative links in PDFs]
* [http://www.oooninja.com/2008/02/convert-document-references-pdf-targets.html Convert document references in PDF targets]

== Planned Features for [[OOoRelease30|3.0 Release]] (mid-October 2008) ==

=== General ===
* OpenDocument:
** ODF 1.2 Specification
** [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office-formula ODF formula specification]
** ODF Toolkit: installation set, aka [[ODF_Toolkit/Efforts/Packaging_Modularization]]
** ODF Toolkit: Java tools for odf
* Bibliographic
** [[Bibliographic/Developer_Page#1st_Stage.2C_Bibliographic_Facility_Redevelopment | Basic API & UNO support for bibliographic enhancements]]

=== Performance Improvements ===
* Drawing Engine

=== Writer ===
* new [[Notes2]] module for displaying notes in the margins
* Office 12 (.docx) import filter
* ODF documents' metadata editor
* Preview of hyperlinks inside the document

=== Calc ===
* Office 12 (.xlsx) Import Filter
* Compliance with ODF formula specification
* GETPIVOTDATA function
* [http://www.oooninja.com/2008/04/shared-calc-spreadsheets-documents.html Live sharing of Calc workbooks]

=== Impress ===
* Office 12 (.pptx) Import Filter
* Table support in Impress
* [http://www.oooninja.com/2008/04/interactive-picture-crop-in-draw-and.html Interactive cropping] [http://blogs.sun.com/GullFOSS/entry/improved_picture_cropping_for_draw of images]

=== Extensions ===
==== For end users ====
* [[MediaWiki Extension]], available at [http://extensions.services.openoffice.org/project/wikipublisher Extension Site]
* [http://www.oooninja.com/2008/06/pdf-import-hybrid-odf-pdfs-extension-30.html PDF Import], available at [http://extensions.services.openoffice.org/project/pdfimport Extension Site]
* [[Presenter Screen]], available at [http://extensions.services.openoffice.org/project/presenter-screen Extension Site]

==== For developers ====
* API enhancements
* GUI enhancements - The GUI should be redesigned to get a more modern look. A good guideline is the new IBM Lotus Symphony that uses dynamic panels. This is better than MS Office's "ribbon", at least for documents, because it saves space on the top (normally documents are vertical).
* [http://specs.openoffice.org/appwide/packagemanager/options_dialog_for_extensions.odt Option page]

=== Various ===
* Better VBA? [http://blogs.sun.com/GullFOSS/entry/sun_and_novell_work_together]

* [http://porting.openoffice.org/mac/news/index.html MacOSX Aqua Port]

* [[Windows_Vista]] Enhancements:
** new File Dialog
** visualization of Meta data in Explorer

* Web services
** Web Services wizard?

* OpenOffice.org Repackaging
** Repackaging step one [http://odftoolkit.openoffice.org/transition.html]

* Articles
** [http://www.oooninja.com/2008/03/openofficeorg-30-new-features.html New Features in OpenOffice.org 3.0] (March 18, 2008)

== Planned Features for 3.1 Release (March 2009) ==

* Arabic

* High Document Fidelity (AntiAliasing of Drawing Object and optimized graphic primitives)

* Improved packaging, package pools

* New template dialog and template repository

* [http://qa.openoffice.org/issues/show_bug.cgi?id=81536 WebDAV compatibility for users of Mac OS X]

* user data/feedback extention

=== Writer ===

* overline text

* transparent selection

* reply to existing notes

* search inside notes

* RichText Import/Export of notes for Word 97/2003/XP files

* Japanese reconversion

* Bibliographic - [[Bibliographic/Writer_enhancements_for_OOBib#Enhanced_Bookmark_Function_to_Include_Formatted_Text | New field type to support formatted text]]

* Bibliographic - meta data support for text objects in Writer in 3.1

=== Base ===

* SQL syntax highlighting

* MySQL integration

=== '''Impress''' ===

* Zoomslider for Draw and Impress

*'''[Integrated in DEV300_m35]'''[[Mac OS X Porting - Apple Remote implementation | Apple Remote support (Mac OS X only)]]

* [[Mac OS X Porting - OpenGL transitions | OpenGL transitions in Impress (Mac OS X)]]

== Planned Feature for 3.2 Release (September 2009) ==

* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query QA tracked]

== Planned Features for 3.x Release ==

* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&target_milestone=OOo+3.x&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query QA tracked]

* XForms Enhancements

[[Category:Features]]
[[Category:Alpha Centauri]]

[[Category:Releases]]
[[Category:Alpha Centauri]]

Mac OS X Porting - OpenGL transitions

2008-08-25T09:56:53Z

KAMiKAZOW:

== <div align="left" style="color:red; font-size:18px">'''OpenGL transitions on Mac OS X '''</div> ==

=== Description ===

'''In Impress, there are transitions between slides, with or without funny 3D effects. The problem is, those nice and Funny effects are power consuming, and without hardware acceleration – means software rendered –,extremely slow, what is not acceptable by users.'''

'''This tasks aims to replace the software rendered transitions with hardware accelerated transitions on Mac OS X.'''

'''We'll use OpenGL, the API Mac OS X does natively use'''

'''Below the technical description, the involved code, the plan, and so on. Feel free to add information if you estimate it usefull for the task.'''

'''Thanks in advance :-)'''

=== Goal ===

<div align="left" style="color:blue; font-size:14px">'''Make OpenGL transitions work in Impress, on Mac OS X Aqua'''</div>

=== Timeline ===
Expected timeline: '''October / November 2008'''

=== Examples ===

FIXME: add screenshots or links for demos

== '''Modifications''' ==

=== Existing (historical implementation) ===

Common:

vcl/source/opengl.cxx, implements:

* functions pointers (most important gl functions typedef'ed)
* + corresponding macro for functions initialization
* + impl functions getters
* Ctor: parameter pOutDev is a pointer on a OutputDevice*, using mpOutDev
* Dtor: deletes mpOGL
* usual methods ... and so on

vcl/source/salogl.cxx:

* Static members: oslModule (himpOGLLib == libgl.dylib), NSOpenGLContext* .. (bool) state
* Macros
* Callbacks for CreateContext, DeleteContext, MakeCurrent, GetCurrentContext
* OpenGLWndProc (what's that ?)

vcl/source/gdi/outdev.cxx
->there is a very interesting OpenGL* OutputDevice::GetOpenGL()

FIXME: To be continued

=== Concerned files / ideas ===

==== ''' Ideas''' ====

25th august:

After reading a lot of code (mostly vcl), it appears this is not possible (excepted doing hacks), to use OpenGL without use outdev thing (got systematic crashes using NSOpenGLView directly, and outdev complains about lost events and pending pointers)

The consequence is, the slideshow calls must be abstraction of CreateContext, MakeCurrentContext, ReleaseContext ..etc.

And the real implementation must go in vcl/aqua/source/gdi/salogl.cxx, respecting vcl/source/gdi/opengl.cxx virtual classes.

The plan (to be confirmed seems to be):

* design the abstraction we'll use, and prepare the OGLTrans_TransitionerImpl.cxx like it is for Linux, but adapted to Mac OS X
* implement NSOpenGLView* pOpenGLView in vcl, guessing it will be sufficient (else, we'll have to implement a new class, but things will become complicated)
* define the NSView containing the scene, instantiate an OpenGLNSView using the same frame, and use addSubview. Current choosen Place to do that: OGLTrans_TransitionerImpl.cxx
* implement (using existing Windows and Linux implementation) the same classes / macros ( :-/ ) methods in salogl.cxx
* add the mac osx cases in outdev and anywhere else it is needed

Retry with the coming DEV300_m30

====Possibilities:====

Everything is based on implement an OpenGLView adding a new NSOpenGLView* pOpenGLView object in sysdata.hxx, or an NSView drawn as a subview of the (NSView * type) pView.

'''TODO''': investigate about ImplOutdev and co

Try 1: '''either''' implement (NSView * type) pOpenGLView in vcl, more precisely, modify:

vcl/inc/vcl/sysdata.hxx

vcl/aqua/inc/salframe.h

vcl/aqua/inc/salframeview.h,

vcl/aqua/source/window/salframe.cxx

vcl/aqua/source/window/salobj.cxx

+ the makefile

and in slideshow:

slideshow/source/engine/OGLTrans/OGLTrans_TransitionImpl.hxx

slideshow/source/engine/OGLTrans/OGLTrans_TransitionImpl.cxx

slideshow/source/engine/OGLTrans/OGLTrans_TransitionerImpl.cxx

'''Issue is at buildtime''':

Pb: visibility of the vcl/aqua/inc headers from slideshow at buildtime

Update: predeclaration in vcl/inc/vcl/sysdata.hxx will help a lot.

Main issue is, how to explain the compiler NSView* pOpenGLView has new methods (OpenGL specific), the NSView* pView has not ?

More precisely, there are warnings because the pOpenGLView is supposed receive no answer from the OpenGL specific methods used in OGLTrans_TransitionerImpl.cxx. In theory, it should work out of the box, but the code aims to be warning free; so this solution is not acceptable.

Workaround could be implement the new methods directly in the NSView, or delegate. Just wild guess [FIXME]

Try 2 '''or'''

(maybe completely wrong, but worth a try)

Implement the OpenGL methods directly in the SalframeView. just two methods have the same names/parameters numbers, so just rename they properly to avoid clash. Important: initWithFrame for OpenGL has two parameters, while initWithFrame for normal NSView has only one.

Try 3 '''or'''

Add an NSOpenGLView * pOpenGLView in the sysdata.hxx, and modify everything in vcl accordingly.

<div align="left" style="color:blue; font-size:18px">''' [[Mac_OS_X_Porting_-_OpenGL_transitions/NSOpenGLView | ==> click here to have a look at NSOpenGLView available methods]]''' </div>

Thus, in OGLTrans_TransitionerImpl.cxx instanciate

an NSView who is a pointer on the normal NSView, and an NSOpenGLView, who is a pointer

'''or'''

create the AquaOpenGLView object directly in slideshow, modify the other slideshow files mentioned above (changes are similar)

===='''Result''' ====

Using the second solution, the subview seems to -somewhat- show something.

'''Test''': a right click in the transition demo, using the presentation wizard, give the same contextual menu we have in fullscreen (yes, this is weird, but this is encouraging for the future).

'''Known issue''': there is no communication between the subView and the NSApplication, events are lost, timeout and chaos in event queue

-> deadlock and crash.

TODO: Second test will consist in delegate the notifications send for the refresh, to the NSApp.

It is expected, once this NSOpenGL view will work, this should be no problem to use it from the slideshow.

Communication between slideshow object and the NSApplication (customized NSView, itself inheriting of NSWindow) will use the notification center as proxy (what is extremely fast in theory).

==== '''Concerned files''' ====

Task: build the lib

'''slideshow/source/engine/OGLTrans/makefile.mk'''

add the case Aqua, modify CFLAGSCXX + add fremaworks OpenGL, GLUT and Cocoa for linking

Task: Deliver the libs / includes:

'''slideshow/prj/d.lst'''

deliver the new lib on Aqua (libOGLTrans.dylib)

Modified files:

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionImpl.cxx'''

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionImpl.hxx'''

'''slideshow/source/engine/OGLTrans/OglTrans_TransitionerImpl.cxx'''

New files (to be confirmed):

slideshow/source/engine/OGLTrans/aquaOpenGLView.h

slideshow/source/engine/OGLTrans/aquaOpenGLView.m

=== ''' Concerned modules''' ===

* config_office: make OpenGL default on Mac OS X Aqua => ENABLE_OPENGL=TRUE
* slideshow: where the lib is built. This lib is linked with libvcl (vcl must be built before slideshow)
* vcl (add NSOpenGLView* in salframe.h ? / implement it in NSApp + NSApp should receive notifications, maybe an object should be added and managed)
* scp2: to add the new lib in the package
* other changes ?

== '''Issues attached to the task''' ==

[http://www.openoffice.org/issues/show_bug.cgi?id=93013 issue 93013]

==''' TODO (draft)'''==

* build the OpenGL trans lib, warning free, on Mac OS X
**[DONE] fix warnings and breakages, with empty implementation
**[DONE] fix linking
**[DONE] create customized NSView (skeleton, and pre-implementation)
*[DONE] add the lib to the package
* register the lib
* Design the first implementation
** design the abstraction used in slideshow
** implement the abstracted methods/classes in vcl/aqua/source/gdi/salogl
* implement NSOpenGLView or customize an NSView [Current plan: try using NSOpenGLView first]
** manage OpenGL context
** manage OpenGL pixels mapping
** manage events and notifications '''critical'''
** initialize the view properly in splitted view
** implement the fullscreen mode
* finalize the transitions integration in Aqua bundle
* make transitions work
* test
*integrate

Notes about lib registration:

When using UNO services (if I'm not wrong) a lib must be listed in services.rdb blob.

For your tests, and until the lib will be packaged, you need to do this action '''manually'''. For that, you need to place you in the bundle:
<pre>
cd <Bundle_dir>/OpenOffice.org.app/Contents/basis-link/program
chmod ug+w services.rdb # else everything below will fail
../ure-link/bin/regcomp -register -r ./services.rdb -c libOGLTrans.uno.dylib
../ure-link/bin/regcomp -register -r ./services.rdb -c slideshow.uno.dylib
../ure-link/bin/regcomp -register -r ./services.rdb -c libslideshowtestmxi.dylib
chmod ug-w services.rdb
</pre>

With the new libs you built previously

If you want to go backward, just replace register with '''revoke'' in the same place, using similar command line:
<pre>
cd <Bundle_dir>/OpenOffice.org.app/Contents/basis-link/program
chmod ug+w services.rdb # else everything below will fail
../ure-link/bin/regcomp -revoke -r ./services.rdb -c libOGLTrans.uno.dylib
../ure-link/bin/regcomp -revoke -r ./services.rdb -c slideshow.uno.dylib
../ure-link/bin/regcomp -revoke -r ./services.rdb -c libslideshowtestmxi.dylib
chmod ug-w services.rdb
</pre>

== '''LINKS''' ==

Below a now exhaustive list of links. Feel free to add interesting links.

[http://developer.apple.com/documentation/GraphicsImaging/OpenGL-date.html Apple OpenGL Documentation]

[http://www.cocoadev.com/index.pl?CocoaOpenGl Cocoa OpenGL]

[http://www.cocoadev.com/index.pl?CustomGLView Custom GLView]

[http://search.lists.apple.com/?q=NSView++NSOpenGLView&cmd=Search%21 NSView + OpenGLView in Apple database]

[http://lists.apple.com/archives/mac-opengl/2005/Dec/msg00089.html NSOpenGLView initialisation issue]

== COMPLETE ME ==

Bla bla ...

[[Category:Aqua]]

[[Category:MacOSX]]

Documentation/Building Guide/Building on MacOSX

2008-01-05T21:33:05Z

KAMiKAZOW: /* '''Prerequisites''' */

<div align="left" style="color:blue; font-size:18px">'''Cocoa migration is in progress '''</div>

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

=== Important links for Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

(Outdated): To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

=== Mac OS X version ===

=> '''Minimal version for AquaBuild is Mac OS X 10.4 (aka Tiger).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

=== Xcode ===

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''. Older are deprecated.

=== Java ===

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change the Java version -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables the build using java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. e.g. several known build issues have to be fixed e.g. hsqldb, but probably other modules are concerned.

Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build OpenOffice.org several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.

You can install it using fink. It is simply named "ccache". For MacPorts users the package is called "ccache".

If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/

In order to use ccache you need to change the following environment variables '''assuming you're using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

== '''Everything is installed ? Now build it... '''==

<br><br>
<div align="left" style="color:green; font-size:22px">'''=> Current Milestone is m239'''</div>
<br><br>

== '''Getting the code (checkout, merge and patch the puppy)''' ==

=== Create a directory for a given milestone, setup CVS access: ===
<code>[bash,N]
mkdir SRC680_m239
cd SRC680_m239
</code>
<code>[bash,N]
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs login
(password is 'anoncvs' ) + Enter
</code>
<code>[bash,N]
Note: The source should be downloaded to a path that does not contain any spaces, otherwise compiling might be troublesome.
</code>

=== checkout SRC680 (Master workspace since aquavcl01 integration) (1,5 GB): ===
<code>[N]
cvs -z3 co -r SRC680_m239 OpenOffice2 # don't forget the "2" !!
</code>
Once done, you'll obtain milestone m239.

=== <div align="left" style="color:green; font-size:18px">'''Additional dependencies for current Milestone builds'''</div>===

==== prebuilt Mozilla archives ====

To enable the use of macros (disabled by default for security reasons), you'll have to put the prebuilt archives of mozilla binaries in moz/zipped directory after renaming them properly.

URL : http://tools.openoffice.org/moz_prebuild/680/

Note: archives are Universal Binaries, and you'll have to rename them, depending on your architecture (either Intel or PowerPC)

Archives to be downloaded :

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBinc.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBlib.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBruntime.zip

If you want to build using them on PowerPC or Intel architecture (with Tiger) please rename them this way :

{| border="1"
|Archive || Name in Intel architecture || Name on PowerPC architecture
|-
| headers || MACOSXGCC'''I'''inc.zip || MACOSXGCC'''P'''inc.zip
|-
| runtime || MACOSXGCC'''I'''runtime.zip || MACOSXGCC'''P'''lib.zip
|-
| libs || MACOSXGCC'''I'''lib.zip || MACOSXGCC'''P'''lib.zip
|}

As you can see, '''P''' means PowerPC, and '''I''' means Intel (replacing '''UB''' in the original name)

.. and put them into '''<ooo build directory>/SRC680_m239/moz/zipped'''

OpenOffice.org should detect and use them if you respect the configure command line as described in Milestone build.

=== One-Time preparations and scripts ===

OpenOffice.org's build environment is configured using the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
SRC680_m225/
SRC680_m239/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd SRC680_ m239/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' (to be written) looks like :

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version: $OOVERSION
./configure \
--with-lang="en-US de fr" \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-headless \
--disable-build-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--without-nas \
--with-use-shell=bash
</code>

Note : --disable-neon has been removed since m217 resync. See issue : [[http://qa.openoffice.org/issues/show_bug.cgi?id=78206 --disable-neon breaks aqua build]]

--disable-odk : disables SDK build, and will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

--disable-build-mozilla: will disable the mozilla build (in the moz module), but mozilla pre-built archives will be used instead (they are mandatory to enable the macro security configuration dialog (see [http://www.openoffice.org/issues/show_bug.cgi?id=79885 issue 79885]).

--enable-dbgutil: add this option to enable assertions and other functionality useful for debugging

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd SRC680_m239/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

==== Mac Intel ====

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
cd instsetoo_native
export TMP=/tmp
export SYSTEM_OPENSSL=YES

+
build --all -P4 --dlv_switch -link --dontgraboutput

or

build --all -P4

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360 | issue 77360])

==== On PowerPC ====

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
cd instsetoo_native
export TMP=/tmp
export SYSTEM_OPENSSL=YES

+

build --all -P2 --dlv_switch -link --dontgraboutput

or

build --all -P2

===== Comments on above =====

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360|issue 77360])

The main purpose of the '''bootstrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set.sh' should be substituted with 'MacOSXX86Env.Set.sh'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours, and 3 to 6 hours on Mac Intel (3:30h on a 2GHz DualCore INTEL iMac). Be patient.

If you want to see how the progress on that build is you can use two '''build''' options to get a comfortable view:

build ... <see above> ... --html --html_path /Users/$USER/Sites

where $USER is your user name. Then you can load in Firefox (not Safari!) the HTML file '''unxmacxi.pro.build.html''' via the in Mac OS X included Apache web server or diretctly form the directory ''/Users/$USER/Sites/''. This file is automatically being updated and is showing the status of the build and also the time needed since the build started.

== '''Installing, preparing and running OpenOffice.org''' ==

===''' Find the Bundle''' ===

Once the build completed, the Final product ( en-US version ) is named : OOo_2.4.0_071211_MacOSXIntel_install.dmg ( for version 2.4.0 e.g.)

And is located in instsetoo_native/unxmacxi.pro/OpenOffice/archive/install/en-US directory ( replace en-US with your locale )

[[Image:Bundle_Location_2.4.0.jpg]]

<br><br>

=== '''Run the soffice.bin''' ===

In one line :

<big>'''Double click the .dmg , drag the OpenOffice.org icon in the folder you want, and double click to run it !!'''</big>

Note : soffice.bin leads XCode to not work (because of the dot in the name). The issue has been reported to xcode-users list.

We're nearly through, let's fire-off the binary:

But a lot has to be done, and if you want to trace (using gdb e.g.), just do:

cd <INSTALL_DIR>/OpenOffice.org\ 2.4.app/Contents/MacOS

and run:

gdb --args soffice.bin

(add any breakpoint you want)

r to run OpenOffice.org

=== Use vcl menubar and / or vcl menus ===

Native menus are defaults. If you want to use vcl menus, do:

<pre>
AQUA_NATIVE_MENUS=FALSE ./soffice.bin
</pre>

Note: options to not recover is -norestore , and to bypass the user informations to fill in, use -nofirststartwizard

AQUA_NATIVE_MENUS=FALSE ./soffice.bin -nofirststartwizard -norestore

You can also insert environement variables in a Dictionary Class of Info.plist located in the Contents directory of OpenOffice.org bundle.

For example, you can add the following XML in a text editor (or make it generated by Property List Editor) in your Info.plist :

<key>LSEnvironment</key>
<dict>
<key>AQUA_NATIVE_MENUS</key>
<string>TRUE</string>
<key>OOO_DISABLE_RECOVERY</key>
<string>TRUE</string>
<key>SAL_NO_NWF</key>
<string>TRUE</string>
<dict>

Notice that in order to work, the OOO_DISABLE_RECOVERY variable detection must be manually inserted in OOo code using the following patch :
http://www.go-oo.org/patches/src680/disable-recovery.diff

This patch is outdated, but you can make the modifications yourself.

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="15" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=FALSE || disable native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

== '''Debug and contribute ''' ==
<ul>
<li>You want to provide crash issue details? Please see [[Providing_a_gdb_backtrace]]</li>
<li>You want to debug using XCode? Please see [[MacOSX_Debug_OpenOffice.org_using_XCode]]</li>
<li>You want to debug using Xemacs? Please see [http://www.mikesicotte.com/2007/02/21/debugging-ooo-with-xemacs-and-gdb Michael Sicotte's blog entry]</li>
</ul>

<br>

<div align="left" style="color:green; font-size:18px">'''[[AquaBuild/Cocoa Informations]] <== Additionnal informations for advanced developers '''</div>

<br>

== '''Current Work in progress''' ==

==='''Developers are working on the following Child workspaces, all Mac OSX dedicated (not integrated )''' ===

*'''stl4leopardppc''' : allow OpenOffice.org to be built on Mac OS X 10.5 PowerPC using system stl, using --without-stlport4 configure option.

If possible, continue with other builds (Leopard / Tiger Intel and PowerPC).

Concerned modules : connectivity, cosv, fpicker, autodoc

*'''aquafilepicker02''' : replace Carbon native FilePicker with Cocoa native FilePicker

Concerned module : fpicker

*'''nativeprintdlg01''' : add support for native print dialog

Concerned modules: offapi, vcl, sfx2, svtools, sw

*'''quicklookplugin01''' : This cws provides a plugin for the QuickLook system available in MacOSX from versions 10.5 onwards

Concerned modules : extensions scp2

*'''macosxdnd''' Drag and Drop for Aqua

Concerned modules : dtrans svtools vcl

*'''[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Faquavcl05 aquavcl05]''':

concerned modules : vcl

==='''Closed for development''' ===

*'''[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Faquavcl04 aquavcl04]''':

concerned modules : desktop vcl rsc shell svx sw solenv instsetoo_native

==='''Integrated''' ===

Integrated in m239

*'''macosxquicktime01''' : use QTKit for sounds and movies

Concerned modules : avmedia scp2 vcl

Integrated in m238

*'''macosx24dmg''' : fix bad icon positionning in the mounted disk image ( already Approved by QA )

Concerned module : instsetoo_native

Integrated in m237

*'''pj86''' : Make module sw warning free on Mac OS X

Concerned modules : sw , solenv

*'''macleopardbuild''' : be Leopard compatible, when building on Tiger

Concerned modules : idlc soltools jvmfwk extensions stlport

Integrated in m233

*'''readme4macintel'''

concerned module : readlicense_oo

Integrated in m233

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, svtools, vcl

*'''spotlightplugin01''' ( add a new Sportlight plugin )

Concerned modules: extensions, scp2

Integrated in m229

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''macosxspellchecker''' : use Mac OS X spellchecker

Concerned modules: lingucomponent, solenv

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl, fpicker, libxmlsec, xmlsecurity, basic

Integrated in m228

*'''cloph09''' ( remove X11SDK dependance for Aquabuild )

Concerned modules: np_sdk

Integrated in m227

*'''aquaremovescripts''': remove useless Applescripts from Aqua version

concerned module: instsetoo_native

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

*'''Panther''' build (X11 only) : currently broken ( work in progress )

Since latest resync, no build issues have been reported.

*'''Tiger''': no problem nor for X11 nor Aqua versions (main baseline)

*'''Leopard''' Intel : builds OK now. Build is broken in cppu for PowerPC architecture, and builds fine using --without-stlport4 flag

*Native FilePicker is fixed (aquafilepicker02 + pl fixed repaint issue )

*Lot of warnings in vcl, due to other deprecated stuff

<div align="left" style="color:grey; font-size:12px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

Documentation/Building Guide/Building on MacOSX

2008-01-05T21:32:14Z

KAMiKAZOW: /* Important links for Cocoa development */

<div align="left" style="color:blue; font-size:18px">'''Cocoa migration is in progress '''</div>

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

=== Important links for Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

(Outdated): To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

=== Mac OS X version ===

=> '''Minimal version for AquaBuild is Mac OS X 10.4 ( aka Tiger ).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

=== Xcode ===

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''. Older are deprecated.

=== Java ===

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change the Java version -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables the build using java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. e.g. several known build issues have to be fixed e.g. hsqldb, but probably other modules are concerned.

Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build OpenOffice.org several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.

You can install it using fink. It is simply named "ccache". For MacPorts users the package is called "ccache".

If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/

In order to use ccache you need to change the following environment variables '''assuming you're using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

== '''Everything is installed ? Now build it... '''==

<br><br>
<div align="left" style="color:green; font-size:22px">'''=> Current Milestone is m239'''</div>
<br><br>

== '''Getting the code (checkout, merge and patch the puppy)''' ==

=== Create a directory for a given milestone, setup CVS access: ===
<code>[bash,N]
mkdir SRC680_m239
cd SRC680_m239
</code>
<code>[bash,N]
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs login
(password is 'anoncvs' ) + Enter
</code>
<code>[bash,N]
Note: The source should be downloaded to a path that does not contain any spaces, otherwise compiling might be troublesome.
</code>

=== checkout SRC680 (Master workspace since aquavcl01 integration) (1,5 GB): ===
<code>[N]
cvs -z3 co -r SRC680_m239 OpenOffice2 # don't forget the "2" !!
</code>
Once done, you'll obtain milestone m239.

=== <div align="left" style="color:green; font-size:18px">'''Additional dependencies for current Milestone builds'''</div>===

==== prebuilt Mozilla archives ====

To enable the use of macros (disabled by default for security reasons), you'll have to put the prebuilt archives of mozilla binaries in moz/zipped directory after renaming them properly.

URL : http://tools.openoffice.org/moz_prebuild/680/

Note: archives are Universal Binaries, and you'll have to rename them, depending on your architecture (either Intel or PowerPC)

Archives to be downloaded :

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBinc.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBlib.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBruntime.zip

If you want to build using them on PowerPC or Intel architecture (with Tiger) please rename them this way :

{| border="1"
|Archive || Name in Intel architecture || Name on PowerPC architecture
|-
| headers || MACOSXGCC'''I'''inc.zip || MACOSXGCC'''P'''inc.zip
|-
| runtime || MACOSXGCC'''I'''runtime.zip || MACOSXGCC'''P'''lib.zip
|-
| libs || MACOSXGCC'''I'''lib.zip || MACOSXGCC'''P'''lib.zip
|}

As you can see, '''P''' means PowerPC, and '''I''' means Intel (replacing '''UB''' in the original name)

.. and put them into '''<ooo build directory>/SRC680_m239/moz/zipped'''

OpenOffice.org should detect and use them if you respect the configure command line as described in Milestone build.

=== One-Time preparations and scripts ===

OpenOffice.org's build environment is configured using the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
SRC680_m225/
SRC680_m239/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd SRC680_ m239/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' (to be written) looks like :

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version: $OOVERSION
./configure \
--with-lang="en-US de fr" \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-headless \
--disable-build-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--without-nas \
--with-use-shell=bash
</code>

Note : --disable-neon has been removed since m217 resync. See issue : [[http://qa.openoffice.org/issues/show_bug.cgi?id=78206 --disable-neon breaks aqua build]]

--disable-odk : disables SDK build, and will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

--disable-build-mozilla: will disable the mozilla build (in the moz module), but mozilla pre-built archives will be used instead (they are mandatory to enable the macro security configuration dialog (see [http://www.openoffice.org/issues/show_bug.cgi?id=79885 issue 79885]).

--enable-dbgutil: add this option to enable assertions and other functionality useful for debugging

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd SRC680_m239/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

==== Mac Intel ====

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
cd instsetoo_native
export TMP=/tmp
export SYSTEM_OPENSSL=YES

+
build --all -P4 --dlv_switch -link --dontgraboutput

or

build --all -P4

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360 | issue 77360])

==== On PowerPC ====

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
cd instsetoo_native
export TMP=/tmp
export SYSTEM_OPENSSL=YES

+

build --all -P2 --dlv_switch -link --dontgraboutput

or

build --all -P2

===== Comments on above =====

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360|issue 77360])

The main purpose of the '''bootstrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set.sh' should be substituted with 'MacOSXX86Env.Set.sh'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours, and 3 to 6 hours on Mac Intel (3:30h on a 2GHz DualCore INTEL iMac). Be patient.

If you want to see how the progress on that build is you can use two '''build''' options to get a comfortable view:

build ... <see above> ... --html --html_path /Users/$USER/Sites

where $USER is your user name. Then you can load in Firefox (not Safari!) the HTML file '''unxmacxi.pro.build.html''' via the in Mac OS X included Apache web server or diretctly form the directory ''/Users/$USER/Sites/''. This file is automatically being updated and is showing the status of the build and also the time needed since the build started.

== '''Installing, preparing and running OpenOffice.org''' ==

===''' Find the Bundle''' ===

Once the build completed, the Final product ( en-US version ) is named : OOo_2.4.0_071211_MacOSXIntel_install.dmg ( for version 2.4.0 e.g.)

And is located in instsetoo_native/unxmacxi.pro/OpenOffice/archive/install/en-US directory ( replace en-US with your locale )

[[Image:Bundle_Location_2.4.0.jpg]]

<br><br>

=== '''Run the soffice.bin''' ===

In one line :

<big>'''Double click the .dmg , drag the OpenOffice.org icon in the folder you want, and double click to run it !!'''</big>

Note : soffice.bin leads XCode to not work (because of the dot in the name). The issue has been reported to xcode-users list.

We're nearly through, let's fire-off the binary:

But a lot has to be done, and if you want to trace (using gdb e.g.), just do:

cd <INSTALL_DIR>/OpenOffice.org\ 2.4.app/Contents/MacOS

and run:

gdb --args soffice.bin

(add any breakpoint you want)

r to run OpenOffice.org

=== Use vcl menubar and / or vcl menus ===

Native menus are defaults. If you want to use vcl menus, do:

<pre>
AQUA_NATIVE_MENUS=FALSE ./soffice.bin
</pre>

Note: options to not recover is -norestore , and to bypass the user informations to fill in, use -nofirststartwizard

AQUA_NATIVE_MENUS=FALSE ./soffice.bin -nofirststartwizard -norestore

You can also insert environement variables in a Dictionary Class of Info.plist located in the Contents directory of OpenOffice.org bundle.

For example, you can add the following XML in a text editor (or make it generated by Property List Editor) in your Info.plist :

<key>LSEnvironment</key>
<dict>
<key>AQUA_NATIVE_MENUS</key>
<string>TRUE</string>
<key>OOO_DISABLE_RECOVERY</key>
<string>TRUE</string>
<key>SAL_NO_NWF</key>
<string>TRUE</string>
<dict>

Notice that in order to work, the OOO_DISABLE_RECOVERY variable detection must be manually inserted in OOo code using the following patch :
http://www.go-oo.org/patches/src680/disable-recovery.diff

This patch is outdated, but you can make the modifications yourself.

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="15" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=FALSE || disable native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

== '''Debug and contribute ''' ==
<ul>
<li>You want to provide crash issue details? Please see [[Providing_a_gdb_backtrace]]</li>
<li>You want to debug using XCode? Please see [[MacOSX_Debug_OpenOffice.org_using_XCode]]</li>
<li>You want to debug using Xemacs? Please see [http://www.mikesicotte.com/2007/02/21/debugging-ooo-with-xemacs-and-gdb Michael Sicotte's blog entry]</li>
</ul>

<br>

<div align="left" style="color:green; font-size:18px">'''[[AquaBuild/Cocoa Informations]] <== Additionnal informations for advanced developers '''</div>

<br>

== '''Current Work in progress''' ==

==='''Developers are working on the following Child workspaces, all Mac OSX dedicated (not integrated )''' ===

*'''stl4leopardppc''' : allow OpenOffice.org to be built on Mac OS X 10.5 PowerPC using system stl, using --without-stlport4 configure option.

If possible, continue with other builds (Leopard / Tiger Intel and PowerPC).

Concerned modules : connectivity, cosv, fpicker, autodoc

*'''aquafilepicker02''' : replace Carbon native FilePicker with Cocoa native FilePicker

Concerned module : fpicker

*'''nativeprintdlg01''' : add support for native print dialog

Concerned modules: offapi, vcl, sfx2, svtools, sw

*'''quicklookplugin01''' : This cws provides a plugin for the QuickLook system available in MacOSX from versions 10.5 onwards

Concerned modules : extensions scp2

*'''macosxdnd''' Drag and Drop for Aqua

Concerned modules : dtrans svtools vcl

*'''[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Faquavcl05 aquavcl05]''':

concerned modules : vcl

==='''Closed for development''' ===

*'''[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Faquavcl04 aquavcl04]''':

concerned modules : desktop vcl rsc shell svx sw solenv instsetoo_native

==='''Integrated''' ===

Integrated in m239

*'''macosxquicktime01''' : use QTKit for sounds and movies

Concerned modules : avmedia scp2 vcl

Integrated in m238

*'''macosx24dmg''' : fix bad icon positionning in the mounted disk image ( already Approved by QA )

Concerned module : instsetoo_native

Integrated in m237

*'''pj86''' : Make module sw warning free on Mac OS X

Concerned modules : sw , solenv

*'''macleopardbuild''' : be Leopard compatible, when building on Tiger

Concerned modules : idlc soltools jvmfwk extensions stlport

Integrated in m233

*'''readme4macintel'''

concerned module : readlicense_oo

Integrated in m233

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, svtools, vcl

*'''spotlightplugin01''' ( add a new Sportlight plugin )

Concerned modules: extensions, scp2

Integrated in m229

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''macosxspellchecker''' : use Mac OS X spellchecker

Concerned modules: lingucomponent, solenv

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl, fpicker, libxmlsec, xmlsecurity, basic

Integrated in m228

*'''cloph09''' ( remove X11SDK dependance for Aquabuild )

Concerned modules: np_sdk

Integrated in m227

*'''aquaremovescripts''': remove useless Applescripts from Aqua version

concerned module: instsetoo_native

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

*'''Panther''' build (X11 only) : currently broken ( work in progress )

Since latest resync, no build issues have been reported.

*'''Tiger''': no problem nor for X11 nor Aqua versions (main baseline)

*'''Leopard''' Intel : builds OK now. Build is broken in cppu for PowerPC architecture, and builds fine using --without-stlport4 flag

*Native FilePicker is fixed (aquafilepicker02 + pl fixed repaint issue )

*Lot of warnings in vcl, due to other deprecated stuff

<div align="left" style="color:grey; font-size:12px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

FAQ OpenOffice.org and NeoOffice

2008-01-05T21:23:32Z

KAMiKAZOW: /* Native OpenOfficeOrg port status */

{{Documentation/Candidate}}

=== What is OpenOffice.org X11 for Mac OS X / Darwin PPC?===
OpenOffice.org X11 is a version of OpenOffice.org (OOo for short) that uses the UNIX system, that the Mac OS X is based on. So, the OpenOffice.org X11 behaves like a UNIX program within Mac OS X. The program can be used quite productively on Mac OS X system, if you are an experienced Mac OS X user or familiar with UNIX systems (e.g. Linux). If you know what UNIX means, you should be able to work with OpenOffice.org X11 with relatively little effort.

'''For developers:''' OpenOffice.org X11 uses LGPL license and is developed within openoffice.org CVS. You will also have to sign a [http://contributing.openoffice.org/programming.html JCA] (read the bottom of the page) to contribute to the effort.

More information about OpenOffice.org X11 in [http://porting.openoffice.org/mac/ OpenOffice.org Mac porting pages]

=== What is NeoOffice? ===

[http://www.neooffice.org NeoOffice] is a fork of [http://www.openoffice.org/ OpenOffice.org] for Mac OS X.

'''Fork''' Means NeoOffice is another project, and is not OpenOffice.org. This way, NeoOffice project does not contribute to OpenOffice.org, and does not help to fix any OpenOffice.org bug.

Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way).

NeoOffice uses GPL license and is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).

Said differently, it means uses a license not compatible with OpenOffice.org, so, to avoid legal issues, NeoOffice code cannot be used in OpenOffice.org, and OpenOffice.org developers must entirely rewrite the code for the same features.

More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice]

===Native OpenOffice.org port status ===
IMPORTANT:

<div class="messagebox cleanup metadata" style="border:1px solid blue;background-color:#B3FFF5;padding:7px;">
<big>

'''[http://porting.openoffice.org/mac/download/aqua.html Download Aqua version (development)]'''

</big>
</div>

Mac OS X port Home: '''[[http://porting.openoffice.org/mac/ Mac OS X port Home]]'''

'''3rd February 2007 OpenOffice.org Mac Porting team announces'''
'''[http://porting.openoffice.org/mac/news/2007/20070203toptenbeforealpha.html The TOP 10 of issues before Alpha version of native OpenOffice.org for Mac OS X]'''

'''All other Aqua links:'''

'''[[http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua Version of OpenOffice.org]]'''

'''Some news and other links:'''

'''[[http://porting.openoffice.org/mac/news/news2007.html News from 2007]]'''

'''[[http://porting.openoffice.org/mac/news/news2006.html News from 2006]]'''

'''[[http://porting.openoffice.org/mac/news/news2005.html News from 2005]]'''

'''Blogs:'''

'''[[http://porting.openoffice.org/mac/links.html Developers blogs]]'''

=== What is OpenOffice.org Aqua/Native port (without X11)?===

'''Starting in October 2005''', there has been an effort to revive the direct native port of OpenOffice.org for Mac OS X. In Jan 2006 this effort was at its first stages.

Current status is: Top 10 of issues before public alpha version. Alpha means not complete, but already functional. The missing features will be progressively implemented, depending on resources.

See previous part for more news about this effort.

----

=== Q1: Where can I find OpenOffice.org or NeoOffice? ===
'''A:''' You can download both from respective sites.

[http://download.openoffice.org/ Download OpenOffice.org from here] (openoffice.org). Note that you have to have Apple X11 installed (see Q6).

[http://trinity.neooffice.org/modules.php?name=Downloads Download NeoOffice from here] (neooffice.org)

=== Q2: Why does there seem to be several parallel efforts? ===
'''A:''' This is a very normal situation in open source. And because of historical and personal choices.

This [http://porting.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14452 mail from Kevin Hendricks] provides some historical details.

If you want to really understand the situation, here's some additional reading for you: [http://neowiki.sixthcrusade.com/index.php/History_of_NeoOffice_and_OpenOffice.org:_Introduction History of NeoOffice and OpenOffice.org], [http://porting.openoffice.org/servlets/ReadMsg?list=mac&msgNo=125 Quote from Patrick] may explain some of the licensing situation, and finally, you may also want to read [http://www.planamesa.com/neojava/en/faq.php another FAQ]

=== Q3: Where do I get support for OpenOffice.org X11? ===
'''A:''' The [http://support.openoffice.org/ support.openoffice.org] is the main place for all support related to openoffice.org.

The [http://porting.openoffice.org/mac/support.html OpenOffice.org for Mac OSX support page] is specifically for Mac OS X users.

=== Q4: But everybody could use OpenOffice.org X11...? ===
'''A:''' Yes, to use OpenOffice.org, Apple X11 or XDarwin must be installed (see Q1).

=== Q5: But it would be more efficient, if there would be only one effort...===

'''A:''' Probably. A proposal to work together has been made, and NeoOffice developers refused.

OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is '''community project'''.

The NeoOffice project is a Patrick Luby and Ed Peterlin project only.

The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''.
So every change must be rewritten for OpenOffice.org project, using another implementation.

A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon.

=== Q6: What is this X11 thing and how do I install it?===
'''A:''' To be able to use OpenOffice.org X11 for Mac OS X / Darwin PPC, you have to have Apple X11 installed. It allows graphical UNIX programs to be run in Mac OS X.

The X11.app is located in Application -> Utilities folder.

If you do not have X11 installed, '''Tiger''' users can install it from the Mac OS X 10.4 install DVD by running the '''Optional Installs''' package. You may need to scroll down in the Mac OS X Install DVD file listing to see the package. Once the optional installer is running, select '''X11''' from the Applications list. For more information on how to install X11 see:
[http://docs.info.apple.com/article.html?artnum=301229 Apple Support Article 301229]. The
interesting part begins below the title ''More custom reinstallation
options with Mac OS X 10.4''.

'''Panther''' users will need to download X11 from [http://www.apple.com/downloads/macosx/apple/x11formacosx.html Apple's webpages].

'''Intel or 10.4.x''' cannot install the X11User.dmg that Apple supplies on its web site. It will tell you newer software is already installed. Instead insert your installation disc 1 and look up
<pre>
/Volumes/Mac OS X Install Disc 1/System/Installation/Packages/X11User.dmg
</pre>
on the disc. Source: http://occy.net/node/166.

=== Q7: OK. I downloaded OpenOffice.org X11. How do I use it? ===

'''The complete installation, either for PowerPC or Intel machines''' and even more are described (currently) in .pdf format for the following locales:

* '''English-US''': http://porting.openoffice.org/mac/Howto_OOo_2.0_MacOSX_english.pdf
* '''German''': http://de.openoffice.org/files/documents/66/3209/MacOSX_Install_de_HowTo_OOo2_1.4.pdf
* '''French''': http://fr.openoffice.org/docs/MacOSX_Install_fr_HowTo_OOo2_V1.4.pdf

Any other contribution and other translations are welcome!!

Further informations are available at: '''http://porting.openoffice.org/mac/'''

Please contact us on mac@porting mailing list if you are willing to translate thes HowTo's in your locale.

=== Q8: Where can I compare the features of the different office applications? ===
To be completed with objective values.

When Aqua will be out. Doesn't make sense before

FAQ OpenOffice.org and NeoOffice

2008-01-05T21:21:36Z

KAMiKAZOW: /* Q7: OK. I downloaded OpenOffice.org X11. How do I use it? */

{{Documentation/Candidate}}

=== What is OpenOffice.org X11 for Mac OS X / Darwin PPC?===
OpenOffice.org X11 is a version of OpenOffice.org (OOo for short) that uses the UNIX system, that the Mac OS X is based on. So, the OpenOffice.org X11 behaves like a UNIX program within Mac OS X. The program can be used quite productively on Mac OS X system, if you are an experienced Mac OS X user or familiar with UNIX systems (e.g. Linux). If you know what UNIX means, you should be able to work with OpenOffice.org X11 with relatively little effort.

'''For developers:''' OpenOffice.org X11 uses LGPL license and is developed within openoffice.org CVS. You will also have to sign a [http://contributing.openoffice.org/programming.html JCA] (read the bottom of the page) to contribute to the effort.

More information about OpenOffice.org X11 in [http://porting.openoffice.org/mac/ OpenOffice.org Mac porting pages]

=== What is NeoOffice? ===

[http://www.neooffice.org NeoOffice] is a fork of [http://www.openoffice.org/ OpenOffice.org] for Mac OS X.

'''Fork''' Means NeoOffice is another project, and is not OpenOffice.org. This way, NeoOffice project does not contribute to OpenOffice.org, and does not help to fix any OpenOffice.org bug.

Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way).

NeoOffice uses GPL license and is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).

Said differently, it means uses a license not compatible with OpenOffice.org, so, to avoid legal issues, NeoOffice code cannot be used in OpenOffice.org, and OpenOffice.org developers must entirely rewrite the code for the same features.

More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice]

===Native OpenOfficeOrg port status ===

IMPORTANT :

<div class="messagebox cleanup metadata" style="border:1px solid blue;background-color:#B3FFF5;padding:7px;">
<big>

'''[http://porting.openoffice.org/mac/download/aqua.html Download Aqua version (development ) ]'''

</big>
</div>

Mac OS X port Home : '''[[http://porting.openoffice.org/mac/ Mac OS X port Home]]'''

'''3rd February 2007 OpenOffice.org Mac Porting team announces'''
'''[http://porting.openoffice.org/mac/news/2007/20070203toptenbeforealpha.html The TOP 10 of issues before Alpha version of native OpenOffice.org for Mac OS X]'''

'''All other Aqua links : '''

'''[[http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua Version of OpenOffice.org]]'''

'''Some news and other links :'''

'''[[http://porting.openoffice.org/mac/news/news2007.html News from 2007]]'''

'''[[http://porting.openoffice.org/mac/news/news2006.html News from 2006]]'''

'''[[http://porting.openoffice.org/mac/news/news2005.html News from 2005]]'''

'''Blogs :'''

'''[[http://porting.openoffice.org/mac/links.html Developers blogs]]'''

=== What is OpenOffice.org Aqua/Native port (without X11)?===

'''Starting in October 2005''', there has been an effort to revive the direct native port of OpenOffice.org for Mac OS X. In Jan 2006 this effort was at its first stages.

Current status is: Top 10 of issues before public alpha version. Alpha means not complete, but already functional. The missing features will be progressively implemented, depending on resources.

See previous part for more news about this effort.

----

=== Q1: Where can I find OpenOffice.org or NeoOffice? ===
'''A:''' You can download both from respective sites.

[http://download.openoffice.org/ Download OpenOffice.org from here] (openoffice.org). Note that you have to have Apple X11 installed (see Q6).

[http://trinity.neooffice.org/modules.php?name=Downloads Download NeoOffice from here] (neooffice.org)

=== Q2: Why does there seem to be several parallel efforts? ===
'''A:''' This is a very normal situation in open source. And because of historical and personal choices.

This [http://porting.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14452 mail from Kevin Hendricks] provides some historical details.

If you want to really understand the situation, here's some additional reading for you: [http://neowiki.sixthcrusade.com/index.php/History_of_NeoOffice_and_OpenOffice.org:_Introduction History of NeoOffice and OpenOffice.org], [http://porting.openoffice.org/servlets/ReadMsg?list=mac&msgNo=125 Quote from Patrick] may explain some of the licensing situation, and finally, you may also want to read [http://www.planamesa.com/neojava/en/faq.php another FAQ]

=== Q3: Where do I get support for OpenOffice.org X11? ===
'''A:''' The [http://support.openoffice.org/ support.openoffice.org] is the main place for all support related to openoffice.org.

The [http://porting.openoffice.org/mac/support.html OpenOffice.org for Mac OSX support page] is specifically for Mac OS X users.

=== Q4: But everybody could use OpenOffice.org X11...? ===
'''A:''' Yes, to use OpenOffice.org, Apple X11 or XDarwin must be installed (see Q1).

=== Q5: But it would be more efficient, if there would be only one effort...===

'''A:''' Probably. A proposal to work together has been made, and NeoOffice developers refused.

OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is '''community project'''.

The NeoOffice project is a Patrick Luby and Ed Peterlin project only.

The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''.
So every change must be rewritten for OpenOffice.org project, using another implementation.

A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon.

=== Q6: What is this X11 thing and how do I install it?===
'''A:''' To be able to use OpenOffice.org X11 for Mac OS X / Darwin PPC, you have to have Apple X11 installed. It allows graphical UNIX programs to be run in Mac OS X.

The X11.app is located in Application -> Utilities folder.

If you do not have X11 installed, '''Tiger''' users can install it from the Mac OS X 10.4 install DVD by running the '''Optional Installs''' package. You may need to scroll down in the Mac OS X Install DVD file listing to see the package. Once the optional installer is running, select '''X11''' from the Applications list. For more information on how to install X11 see:
[http://docs.info.apple.com/article.html?artnum=301229 Apple Support Article 301229]. The
interesting part begins below the title ''More custom reinstallation
options with Mac OS X 10.4''.

'''Panther''' users will need to download X11 from [http://www.apple.com/downloads/macosx/apple/x11formacosx.html Apple's webpages].

'''Intel or 10.4.x''' cannot install the X11User.dmg that Apple supplies on its web site. It will tell you newer software is already installed. Instead insert your installation disc 1 and look up
<pre>
/Volumes/Mac OS X Install Disc 1/System/Installation/Packages/X11User.dmg
</pre>
on the disc. Source: http://occy.net/node/166.

=== Q7: OK. I downloaded OpenOffice.org X11. How do I use it? ===

'''The complete installation, either for PowerPC or Intel machines''' and even more are described (currently) in .pdf format for the following locales:

* '''English-US''': http://porting.openoffice.org/mac/Howto_OOo_2.0_MacOSX_english.pdf
* '''German''': http://de.openoffice.org/files/documents/66/3209/MacOSX_Install_de_HowTo_OOo2_1.4.pdf
* '''French''': http://fr.openoffice.org/docs/MacOSX_Install_fr_HowTo_OOo2_V1.4.pdf

Any other contribution and other translations are welcome!!

Further informations are available at: '''http://porting.openoffice.org/mac/'''

Please contact us on mac@porting mailing list if you are willing to translate thes HowTo's in your locale.

=== Q8: Where can I compare the features of the different office applications? ===
To be completed with objective values.

When Aqua will be out. Doesn't make sense before

FAQ OpenOffice.org and NeoOffice

2008-01-05T21:20:34Z

KAMiKAZOW: /* Q3: Where do I get support for OpenOffice.org X11 ? */

{{Documentation/Candidate}}

=== What is OpenOffice.org X11 for Mac OS X / Darwin PPC?===
OpenOffice.org X11 is a version of OpenOffice.org (OOo for short) that uses the UNIX system, that the Mac OS X is based on. So, the OpenOffice.org X11 behaves like a UNIX program within Mac OS X. The program can be used quite productively on Mac OS X system, if you are an experienced Mac OS X user or familiar with UNIX systems (e.g. Linux). If you know what UNIX means, you should be able to work with OpenOffice.org X11 with relatively little effort.

'''For developers:''' OpenOffice.org X11 uses LGPL license and is developed within openoffice.org CVS. You will also have to sign a [http://contributing.openoffice.org/programming.html JCA] (read the bottom of the page) to contribute to the effort.

More information about OpenOffice.org X11 in [http://porting.openoffice.org/mac/ OpenOffice.org Mac porting pages]

=== What is NeoOffice? ===

[http://www.neooffice.org NeoOffice] is a fork of [http://www.openoffice.org/ OpenOffice.org] for Mac OS X.

'''Fork''' Means NeoOffice is another project, and is not OpenOffice.org. This way, NeoOffice project does not contribute to OpenOffice.org, and does not help to fix any OpenOffice.org bug.

Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way).

NeoOffice uses GPL license and is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).

Said differently, it means uses a license not compatible with OpenOffice.org, so, to avoid legal issues, NeoOffice code cannot be used in OpenOffice.org, and OpenOffice.org developers must entirely rewrite the code for the same features.

More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice]

===Native OpenOfficeOrg port status ===

IMPORTANT :

<div class="messagebox cleanup metadata" style="border:1px solid blue;background-color:#B3FFF5;padding:7px;">
<big>

'''[http://porting.openoffice.org/mac/download/aqua.html Download Aqua version (development ) ]'''

</big>
</div>

Mac OS X port Home : '''[[http://porting.openoffice.org/mac/ Mac OS X port Home]]'''

'''3rd February 2007 OpenOffice.org Mac Porting team announces'''
'''[http://porting.openoffice.org/mac/news/2007/20070203toptenbeforealpha.html The TOP 10 of issues before Alpha version of native OpenOffice.org for Mac OS X]'''

'''All other Aqua links : '''

'''[[http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua Version of OpenOffice.org]]'''

'''Some news and other links :'''

'''[[http://porting.openoffice.org/mac/news/news2007.html News from 2007]]'''

'''[[http://porting.openoffice.org/mac/news/news2006.html News from 2006]]'''

'''[[http://porting.openoffice.org/mac/news/news2005.html News from 2005]]'''

'''Blogs :'''

'''[[http://porting.openoffice.org/mac/links.html Developers blogs]]'''

=== What is OpenOffice.org Aqua/Native port (without X11)?===

'''Starting in October 2005''', there has been an effort to revive the direct native port of OpenOffice.org for Mac OS X. In Jan 2006 this effort was at its first stages.

Current status is: Top 10 of issues before public alpha version. Alpha means not complete, but already functional. The missing features will be progressively implemented, depending on resources.

See previous part for more news about this effort.

----

=== Q1: Where can I find OpenOffice.org or NeoOffice? ===
'''A:''' You can download both from respective sites.

[http://download.openoffice.org/ Download OpenOffice.org from here] (openoffice.org). Note that you have to have Apple X11 installed (see Q6).

[http://trinity.neooffice.org/modules.php?name=Downloads Download NeoOffice from here] (neooffice.org)

=== Q2: Why does there seem to be several parallel efforts? ===
'''A:''' This is a very normal situation in open source. And because of historical and personal choices.

This [http://porting.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14452 mail from Kevin Hendricks] provides some historical details.

If you want to really understand the situation, here's some additional reading for you: [http://neowiki.sixthcrusade.com/index.php/History_of_NeoOffice_and_OpenOffice.org:_Introduction History of NeoOffice and OpenOffice.org], [http://porting.openoffice.org/servlets/ReadMsg?list=mac&msgNo=125 Quote from Patrick] may explain some of the licensing situation, and finally, you may also want to read [http://www.planamesa.com/neojava/en/faq.php another FAQ]

=== Q3: Where do I get support for OpenOffice.org X11? ===
'''A:''' The [http://support.openoffice.org/ support.openoffice.org] is the main place for all support related to openoffice.org.

The [http://porting.openoffice.org/mac/support.html OpenOffice.org for Mac OSX support page] is specifically for Mac OS X users.

=== Q4: But everybody could use OpenOffice.org X11...? ===
'''A:''' Yes, to use OpenOffice.org, Apple X11 or XDarwin must be installed (see Q1).

=== Q5: But it would be more efficient, if there would be only one effort...===

'''A:''' Probably. A proposal to work together has been made, and NeoOffice developers refused.

OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is '''community project'''.

The NeoOffice project is a Patrick Luby and Ed Peterlin project only.

The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''.
So every change must be rewritten for OpenOffice.org project, using another implementation.

A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon.

=== Q6: What is this X11 thing and how do I install it?===
'''A:''' To be able to use OpenOffice.org X11 for Mac OS X / Darwin PPC, you have to have Apple X11 installed. It allows graphical UNIX programs to be run in Mac OS X.

The X11.app is located in Application -> Utilities folder.

If you do not have X11 installed, '''Tiger''' users can install it from the Mac OS X 10.4 install DVD by running the '''Optional Installs''' package. You may need to scroll down in the Mac OS X Install DVD file listing to see the package. Once the optional installer is running, select '''X11''' from the Applications list. For more information on how to install X11 see:
[http://docs.info.apple.com/article.html?artnum=301229 Apple Support Article 301229]. The
interesting part begins below the title ''More custom reinstallation
options with Mac OS X 10.4''.

'''Panther''' users will need to download X11 from [http://www.apple.com/downloads/macosx/apple/x11formacosx.html Apple's webpages].

'''Intel or 10.4.x''' cannot install the X11User.dmg that Apple supplies on its web site. It will tell you newer software is already installed. Instead insert your installation disc 1 and look up
<pre>
/Volumes/Mac OS X Install Disc 1/System/Installation/Packages/X11User.dmg
</pre>
on the disc. Source: http://occy.net/node/166.

=== Q7: OK. I downloaded OpenOffice.org X11. How do I use it? ===

'''The complete installation, either for PowerPC or Intel machines''' and even more are described (currently) in .pdf format for the following locales :

* '''English-US''' : http://porting.openoffice.org/mac/Howto_OOo_2.0_MacOSX_english.pdf

* '''German''' : http://de.openoffice.org/files/documents/66/3209/MacOSX_Install_de_HowTo_OOo2_1.4.pdf

* '''French''' : http://fr.openoffice.org/docs/MacOSX_Install_fr_HowTo_OOo2_V1.4.pdf

Any other contribution and other translations are welcome !!

Further informations are available at : '''http://porting.openoffice.org/mac/'''

Please contact us on mac@porting mailing list if you are willing to translate thes HowTo's in your locale.

=== Q8: Where can I compare the features of the different office applications? ===
To be completed with objective values.

When Aqua will be out. Doesn't make sense before

FAQ OpenOffice.org and NeoOffice

2008-01-05T21:20:16Z

KAMiKAZOW: /* Q1: Where can I find OpenOffice.org or NeoOffice ? */

{{Documentation/Candidate}}

=== What is OpenOffice.org X11 for Mac OS X / Darwin PPC?===
OpenOffice.org X11 is a version of OpenOffice.org (OOo for short) that uses the UNIX system, that the Mac OS X is based on. So, the OpenOffice.org X11 behaves like a UNIX program within Mac OS X. The program can be used quite productively on Mac OS X system, if you are an experienced Mac OS X user or familiar with UNIX systems (e.g. Linux). If you know what UNIX means, you should be able to work with OpenOffice.org X11 with relatively little effort.

'''For developers:''' OpenOffice.org X11 uses LGPL license and is developed within openoffice.org CVS. You will also have to sign a [http://contributing.openoffice.org/programming.html JCA] (read the bottom of the page) to contribute to the effort.

More information about OpenOffice.org X11 in [http://porting.openoffice.org/mac/ OpenOffice.org Mac porting pages]

=== What is NeoOffice? ===

[http://www.neooffice.org NeoOffice] is a fork of [http://www.openoffice.org/ OpenOffice.org] for Mac OS X.

'''Fork''' Means NeoOffice is another project, and is not OpenOffice.org. This way, NeoOffice project does not contribute to OpenOffice.org, and does not help to fix any OpenOffice.org bug.

Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way).

NeoOffice uses GPL license and is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).

Said differently, it means uses a license not compatible with OpenOffice.org, so, to avoid legal issues, NeoOffice code cannot be used in OpenOffice.org, and OpenOffice.org developers must entirely rewrite the code for the same features.

More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice]

===Native OpenOfficeOrg port status ===

IMPORTANT :

<div class="messagebox cleanup metadata" style="border:1px solid blue;background-color:#B3FFF5;padding:7px;">
<big>

'''[http://porting.openoffice.org/mac/download/aqua.html Download Aqua version (development ) ]'''

</big>
</div>

Mac OS X port Home : '''[[http://porting.openoffice.org/mac/ Mac OS X port Home]]'''

'''3rd February 2007 OpenOffice.org Mac Porting team announces'''
'''[http://porting.openoffice.org/mac/news/2007/20070203toptenbeforealpha.html The TOP 10 of issues before Alpha version of native OpenOffice.org for Mac OS X]'''

'''All other Aqua links : '''

'''[[http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua Version of OpenOffice.org]]'''

'''Some news and other links :'''

'''[[http://porting.openoffice.org/mac/news/news2007.html News from 2007]]'''

'''[[http://porting.openoffice.org/mac/news/news2006.html News from 2006]]'''

'''[[http://porting.openoffice.org/mac/news/news2005.html News from 2005]]'''

'''Blogs :'''

'''[[http://porting.openoffice.org/mac/links.html Developers blogs]]'''

=== What is OpenOffice.org Aqua/Native port (without X11)?===

'''Starting in October 2005''', there has been an effort to revive the direct native port of OpenOffice.org for Mac OS X. In Jan 2006 this effort was at its first stages.

Current status is: Top 10 of issues before public alpha version. Alpha means not complete, but already functional. The missing features will be progressively implemented, depending on resources.

See previous part for more news about this effort.

----

=== Q1: Where can I find OpenOffice.org or NeoOffice? ===
'''A:''' You can download both from respective sites.

[http://download.openoffice.org/ Download OpenOffice.org from here] (openoffice.org). Note that you have to have Apple X11 installed (see Q6).

[http://trinity.neooffice.org/modules.php?name=Downloads Download NeoOffice from here] (neooffice.org)

=== Q2: Why does there seem to be several parallel efforts? ===
'''A:''' This is a very normal situation in open source. And because of historical and personal choices.

This [http://porting.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14452 mail from Kevin Hendricks] provides some historical details.

If you want to really understand the situation, here's some additional reading for you: [http://neowiki.sixthcrusade.com/index.php/History_of_NeoOffice_and_OpenOffice.org:_Introduction History of NeoOffice and OpenOffice.org], [http://porting.openoffice.org/servlets/ReadMsg?list=mac&msgNo=125 Quote from Patrick] may explain some of the licensing situation, and finally, you may also want to read [http://www.planamesa.com/neojava/en/faq.php another FAQ]

=== Q3: Where do I get support for OpenOffice.org X11 ? ===
'''A:''' The [http://support.openoffice.org/ support.openoffice.org] is the main place for all support related to openoffice.org.

The [http://porting.openoffice.org/mac/support.html OpenOffice.org for Mac OSX support page] is specifically for Mac OS X users.

=== Q4: But everybody could use OpenOffice.org X11...? ===
'''A:''' Yes, to use OpenOffice.org, Apple X11 or XDarwin must be installed (see Q1).

=== Q5: But it would be more efficient, if there would be only one effort...===

'''A:''' Probably. A proposal to work together has been made, and NeoOffice developers refused.

OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is '''community project'''.

The NeoOffice project is a Patrick Luby and Ed Peterlin project only.

The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''.
So every change must be rewritten for OpenOffice.org project, using another implementation.

A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon.

=== Q6: What is this X11 thing and how do I install it?===
'''A:''' To be able to use OpenOffice.org X11 for Mac OS X / Darwin PPC, you have to have Apple X11 installed. It allows graphical UNIX programs to be run in Mac OS X.

The X11.app is located in Application -> Utilities folder.

If you do not have X11 installed, '''Tiger''' users can install it from the Mac OS X 10.4 install DVD by running the '''Optional Installs''' package. You may need to scroll down in the Mac OS X Install DVD file listing to see the package. Once the optional installer is running, select '''X11''' from the Applications list. For more information on how to install X11 see:
[http://docs.info.apple.com/article.html?artnum=301229 Apple Support Article 301229]. The
interesting part begins below the title ''More custom reinstallation
options with Mac OS X 10.4''.

'''Panther''' users will need to download X11 from [http://www.apple.com/downloads/macosx/apple/x11formacosx.html Apple's webpages].

'''Intel or 10.4.x''' cannot install the X11User.dmg that Apple supplies on its web site. It will tell you newer software is already installed. Instead insert your installation disc 1 and look up
<pre>
/Volumes/Mac OS X Install Disc 1/System/Installation/Packages/X11User.dmg
</pre>
on the disc. Source: http://occy.net/node/166.

=== Q7: OK. I downloaded OpenOffice.org X11. How do I use it? ===

'''The complete installation, either for PowerPC or Intel machines''' and even more are described (currently) in .pdf format for the following locales :

* '''English-US''' : http://porting.openoffice.org/mac/Howto_OOo_2.0_MacOSX_english.pdf

* '''German''' : http://de.openoffice.org/files/documents/66/3209/MacOSX_Install_de_HowTo_OOo2_1.4.pdf

* '''French''' : http://fr.openoffice.org/docs/MacOSX_Install_fr_HowTo_OOo2_V1.4.pdf

Any other contribution and other translations are welcome !!

Further informations are available at : '''http://porting.openoffice.org/mac/'''

Please contact us on mac@porting mailing list if you are willing to translate thes HowTo's in your locale.

=== Q8: Where can I compare the features of the different office applications? ===
To be completed with objective values.

When Aqua will be out. Doesn't make sense before

FAQ OpenOffice.org and NeoOffice

2008-01-05T21:19:59Z

KAMiKAZOW: /* What is OpenOffice.org Aqua port /Native ( without X11 ) port ? */

{{Documentation/Candidate}}

=== What is OpenOffice.org X11 for Mac OS X / Darwin PPC?===
OpenOffice.org X11 is a version of OpenOffice.org (OOo for short) that uses the UNIX system, that the Mac OS X is based on. So, the OpenOffice.org X11 behaves like a UNIX program within Mac OS X. The program can be used quite productively on Mac OS X system, if you are an experienced Mac OS X user or familiar with UNIX systems (e.g. Linux). If you know what UNIX means, you should be able to work with OpenOffice.org X11 with relatively little effort.

'''For developers:''' OpenOffice.org X11 uses LGPL license and is developed within openoffice.org CVS. You will also have to sign a [http://contributing.openoffice.org/programming.html JCA] (read the bottom of the page) to contribute to the effort.

More information about OpenOffice.org X11 in [http://porting.openoffice.org/mac/ OpenOffice.org Mac porting pages]

=== What is NeoOffice? ===

[http://www.neooffice.org NeoOffice] is a fork of [http://www.openoffice.org/ OpenOffice.org] for Mac OS X.

'''Fork''' Means NeoOffice is another project, and is not OpenOffice.org. This way, NeoOffice project does not contribute to OpenOffice.org, and does not help to fix any OpenOffice.org bug.

Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way).

NeoOffice uses GPL license and is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).

Said differently, it means uses a license not compatible with OpenOffice.org, so, to avoid legal issues, NeoOffice code cannot be used in OpenOffice.org, and OpenOffice.org developers must entirely rewrite the code for the same features.

More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice]

===Native OpenOfficeOrg port status ===

IMPORTANT :

<div class="messagebox cleanup metadata" style="border:1px solid blue;background-color:#B3FFF5;padding:7px;">
<big>

'''[http://porting.openoffice.org/mac/download/aqua.html Download Aqua version (development ) ]'''

</big>
</div>

Mac OS X port Home : '''[[http://porting.openoffice.org/mac/ Mac OS X port Home]]'''

'''3rd February 2007 OpenOffice.org Mac Porting team announces'''
'''[http://porting.openoffice.org/mac/news/2007/20070203toptenbeforealpha.html The TOP 10 of issues before Alpha version of native OpenOffice.org for Mac OS X]'''

'''All other Aqua links : '''

'''[[http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua Version of OpenOffice.org]]'''

'''Some news and other links :'''

'''[[http://porting.openoffice.org/mac/news/news2007.html News from 2007]]'''

'''[[http://porting.openoffice.org/mac/news/news2006.html News from 2006]]'''

'''[[http://porting.openoffice.org/mac/news/news2005.html News from 2005]]'''

'''Blogs :'''

'''[[http://porting.openoffice.org/mac/links.html Developers blogs]]'''

=== What is OpenOffice.org Aqua/Native port (without X11)?===

'''Starting in October 2005''', there has been an effort to revive the direct native port of OpenOffice.org for Mac OS X. In Jan 2006 this effort was at its first stages.

Current status is: Top 10 of issues before public alpha version. Alpha means not complete, but already functional. The missing features will be progressively implemented, depending on resources.

See previous part for more news about this effort.

----

=== Q1: Where can I find OpenOffice.org or NeoOffice ? ===
'''A:''' You can download both from respective sites.

[http://download.openoffice.org/ Download OpenOffice.org from here] (openoffice.org). Note that you have to have Apple X11 installed (see Q6).

[http://trinity.neooffice.org/modules.php?name=Downloads Download NeoOffice from here] (neooffice.org)

=== Q2: Why does there seem to be several parallel efforts? ===
'''A:''' This is a very normal situation in open source. And because of historical and personal choices.

This [http://porting.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14452 mail from Kevin Hendricks] provides some historical details.

If you want to really understand the situation, here's some additional reading for you: [http://neowiki.sixthcrusade.com/index.php/History_of_NeoOffice_and_OpenOffice.org:_Introduction History of NeoOffice and OpenOffice.org], [http://porting.openoffice.org/servlets/ReadMsg?list=mac&msgNo=125 Quote from Patrick] may explain some of the licensing situation, and finally, you may also want to read [http://www.planamesa.com/neojava/en/faq.php another FAQ]

=== Q3: Where do I get support for OpenOffice.org X11 ? ===
'''A:''' The [http://support.openoffice.org/ support.openoffice.org] is the main place for all support related to openoffice.org.

The [http://porting.openoffice.org/mac/support.html OpenOffice.org for Mac OSX support page] is specifically for Mac OS X users.

=== Q4: But everybody could use OpenOffice.org X11...? ===
'''A:''' Yes, to use OpenOffice.org, Apple X11 or XDarwin must be installed (see Q1).

=== Q5: But it would be more efficient, if there would be only one effort...===

'''A:''' Probably. A proposal to work together has been made, and NeoOffice developers refused.

OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is '''community project'''.

The NeoOffice project is a Patrick Luby and Ed Peterlin project only.

The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''.
So every change must be rewritten for OpenOffice.org project, using another implementation.

A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org since OpenOffice.org project wants to use only Cocoa/Carbon.

=== Q6: What is this X11 thing and how do I install it?===
'''A:''' To be able to use OpenOffice.org X11 for Mac OS X / Darwin PPC, you have to have Apple X11 installed. It allows graphical UNIX programs to be run in Mac OS X.

The X11.app is located in Application -> Utilities folder.

If you do not have X11 installed, '''Tiger''' users can install it from the Mac OS X 10.4 install DVD by running the '''Optional Installs''' package. You may need to scroll down in the Mac OS X Install DVD file listing to see the package. Once the optional installer is running, select '''X11''' from the Applications list. For more information on how to install X11 see:
[http://docs.info.apple.com/article.html?artnum=301229 Apple Support Article 301229]. The
interesting part begins below the title ''More custom reinstallation
options with Mac OS X 10.4''.

'''Panther''' users will need to download X11 from [http://www.apple.com/downloads/macosx/apple/x11formacosx.html Apple's webpages].

'''Intel or 10.4.x''' cannot install the X11User.dmg that Apple supplies on its web site. It will tell you newer software is already installed. Instead insert your installation disc 1 and look up
<pre>
/Volumes/Mac OS X Install Disc 1/System/Installation/Packages/X11User.dmg
</pre>
on the disc. Source: http://occy.net/node/166.

=== Q7: OK. I downloaded OpenOffice.org X11. How do I use it? ===

'''The complete installation, either for PowerPC or Intel machines''' and even more are described (currently) in .pdf format for the following locales :

* '''English-US''' : http://porting.openoffice.org/mac/Howto_OOo_2.0_MacOSX_english.pdf

* '''German''' : http://de.openoffice.org/files/documents/66/3209/MacOSX_Install_de_HowTo_OOo2_1.4.pdf

* '''French''' : http://fr.openoffice.org/docs/MacOSX_Install_fr_HowTo_OOo2_V1.4.pdf

Any other contribution and other translations are welcome !!

Further informations are available at : '''http://porting.openoffice.org/mac/'''

Please contact us on mac@porting mailing list if you are willing to translate thes HowTo's in your locale.

=== Q8: Where can I compare the features of the different office applications? ===
To be completed with objective values.

When Aqua will be out. Doesn't make sense before

Chart2/Features3.0

2008-01-05T15:16:36Z

KAMiKAZOW:

== Select 'Range' for error bars ==
* Issue: [http://distribution.openoffice.org/issues/show_bug.cgi?id=366 366]

== Ease editing regression lines (trendlines) ==
* Issue: [http://distribution.openoffice.org/issues/show_bug.cgi?id=44768 44768]

== Title for secondary y axis ==
* Issue: [http://distribution.openoffice.org/issues/show_bug.cgi?id=1163 1163]

== Clockwise pie chart ==
* Issue: [http://distribution.openoffice.org/issues/show_bug.cgi?id=37823 37823]

== Starting angle for pie charts - rotation of pie charts ==
* Issue: [http://distribution.openoffice.org/issues/show_bug.cgi?id=16776 16776]

== Handling of empty cells (interpolate,zero,don't paint) ==
* Issue: [http://distribution.openoffice.org/issues/show_bug.cgi?id=65549 65549]

== Offer multiple sets of default colors for charts ==
* Issue: [http://distribution.openoffice.org/issues/show_bug.cgi?id=74992 74992]

== Others Links ==
* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Chart&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&issue_status=CLOSED&target_milestone=OOo+3.0&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query List features issues for Chart 3.0]

VBA

2008-01-05T15:15:05Z

KAMiKAZOW:

[[VBA zh|中]]

[http://vba.openoffice.org VBA interoperability] project is a joint Novell & Sun incubator project whose aim is to deliver a way to run Excel and Word macros natively in imported documents.
* Noel Power (lead)
* Andreas Breagas (co-lead)

'''Visual Basic for Applications''' ('''VBA''') is an implementation of Microsoft's [[wikipedia:Visual Basic|Visual Basic]] which is built into all Microsoft Office applications.

== Latest news ==
* cws [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fnpower6 npower6] has been integrated into m211
* Update Wiki Page with latest info
* [http://blogs.sun.com/GullFOSS/entry/sun_and_novell_work_together Novell and Sun to work together] on the VBA incubator project
* I am delighted that Andreas Bregas now joins me to co-lead the vba incubator project

== Terminology ==

* [[helperapi]] - The compatibility API generously donated by Sun that was part of their migration toolkit
* [[oovbaapi]] - the ooo-build vba interoperability solution originally implemented by Novell + object implementations from the helperapi. Note: [[Ooo-build]] contains the latest VBA model and patches which allows you to run macros from your Microsoft Office documents. This model is under heavy development by Novell and others and the changes are continuously ported to openoffice. It is expected that many macros won't run for now.

== Dashboard ==

* cws [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fnpower8 npower8] (nearly complete) (contains)
* some helperapi object porting
* changes to include new multi-inheritance style idl and new style service definitions
* removal of idl for compatibilty constants[1]
* cws [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fnpower7 npower7] integrated
* cws [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fnpower6 npower6] integrated

[1] these will be generated using the mechanism from the helperapi (basically the idl is generated from metadata files, the idl files are not preserved (or needed) but the types database generated from the idl files

Task queue and status (in order of priority)

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Feature || Description|| Issue # || Planned cws || State || Milestone integrated ||
|-
| autogenerate constants in oovbaapi || port helperapi constant solution to oovbaapi module || 75551 || npower8 || done || n/a ||
|-
| ooo-build api sync || synchronise ooo-build api changes with upstream || 77189 || npower8 || in progress || n/a ||
|-
| array of array indexing || in vba array of array indexing is very common, e.g. <tt>myArray(1)(2)</tt>|| n/a || n/a || n/a || n/a ||
|-
| toolbox control event support || these controls support a loose binding where the presence of a macro event handler of the form <tt>controlname_xxx e.g. controlname_click</tt> results in the appropriate macro getting called when the associated action takes place || n/a || n/a || n/a || n/a |||
|-
|}

Completed Features

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Feature || Description|| Issue # || Planned cws || State || Milestone integrated ||
|-
| vba constants || adjust basic runtime to be 'conditionally' aware of the vba constants defined in oovbaapi module || 68897 || npower7 || complete || n/a ||
|-
| support dim of vba object || adjust basic runtime to be 'conditionally' allow a vba compatibilty api object to be used like <tt>Dim r1 as Range</tt> || 68897 || npower7 || complete || n/a ||
|-
| compatible erase array || in vba compatibility mode erase does not behave as expected || 70380 || npower7 || complete || n/a ||
|-
| null variant behaviour || in vba compatibility mode operations on null variant objects behave differently || 71827 || npower7 || complete || n/a ||
|-
| 'Like' || new 'Like' operator for basic || 73830 || npower7 || complete || n/a ||
|-
| Module scope variable || in vba module scope variables lifetime is tied to the document containing the macro || 76819 || npower7 || complete || n/a ||
|-
| support simple range short cut references || in vba the evaluate function is used for resolving many things, one of theses is short cut range references e.g. '[a1:b2]' || 68898 || npower7 || complete || n/a ||
|-
| fix accent handling || in vba mode accents in modules or macros are not handled || 76818 || npower7 || complete || n/a ||
|-
| fix object comparison || in vba mode there is a problem comparing objects with default paramaters (when the default is not specified) || 76820 || npower7 || complete || n/a ||
|-
| class module import || when class modules are imported the correct 'option' should be set || 76822 || npower7 || complete || n/a ||
|-
| migrate ooo-build code || suck in the mountain of idl and implementation code from ooo-build || 74096 || npower6 || complete || m211 ||
|-
| import vba code || conditionally import (uncommented) vba code and set appropriate module options || 64570 || npower6 || complete || m211 ||
|}

Broader scope tasks that need more investigation (and splitting into smaller tasks) (to be added)

create list of items that may need promoting from vba compatibility to <tt>Standard</tt> ooo-basic behaviour e.g. like issue [[http://www.openoffice.org/issues/show_bug.cgi?id=70380 70380]]

== How to enable the VBA model ==

The VBA model is enabled by default in the current ooo-build. It's enough to [[Getting It|get]], [[Building with ooobuild|build]], [[Installing|install]], and [[Running|be able to run]] it.

If you are using upstream OpenOffice.org and wish to play with this feature then check out and build the cws [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fnpower6 npower6] which contains the initial code drop for the oovbaapi

== How to disable the VBA model ==

Depending on how your version of OpenOffice.org delivers the VBA feature to you, there are a number of ways to disable it.

If you have an Openoffice.org built by a linux distro (or a windows one from Novell) that has the vba interop feature then all you need do is navigate to the 'Tools.Options.Load/Save.VBAProperties' page and uncheck the 'Load Excelbasic code to edit' option.

If you are using an own build (incorporating) [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fnpower6 cws-npower6] the above method will always work. But if you built the vba interop feature as an office extension then you can of course disable or delete the vbaapi.oxt extension using the Extension Manager.

== How can I help you? ==

We need help in a couple of areas, [[Porting notes|porting]] objects from the [[helperapi]], understanding the VBA usage patterns, implementation and testing; see below.

== Porting Objects from the HelperApi ==

What is the [[helperapi]]?

Have a look at the [[porting notes]]

Have a look at a [[porting example]]

[[Porting_notes#Calc_Objects_to_port|list]] of objects that need porting

[[Porting_notes#Missing_attributes.2Fmethods_to_port|list]] of methods (to be ported from [[helperapi]]) to existing objects

== Understanding the VBA usage patterns ==

VBA model is huge and we need help in understanding the VBA usage patterns for prioritizing as we progress. It's important to receive as many Microsoft Office documents with macros as possible for analysis. '''We are interested in documents from developers and regular people too.'''

=== Dumping the VBA from your MS Office documents ===

==== libgsf ====

If you're worried about the sheet data you can use ''test-msvba'' from the [http://freshmeat.net/projects/libgsf/ libgsf]. Download the latest [http://cvs.gnome.org/viewcvs/libgsf/tests/test-msvba.c test-msvba.c] file and compile it with the following command:

gcc `pkg-config --libs --cflags libgsf-1` -o test-msvba test-msvba.c

Note: you need to have libgsf-devel package installed.

Now, you can dump the VBA from your documents with the following command:

find -name '*.xls' -exec sh -c 'test-msvba {} >> ~/excel-vba-stream-for-noel.bas' \;

==== pole ====

<p>Or you can use [http://pole.berlios.de/ POLE] with GUI. POLE is a portable C++ library to access structured storage. It is designed to be compatible with Microsoft structured storage, also sometimes known as OLE Compound Document.</p>

=== Exporting modules from the Microsoft Excel ===

<p>Open your document and edit associated macros. You can see list of modules on the left side of your screen. Use the right mouse button and select ''Export'' from the context menu. The whole module will be saved as one huge ''*.bas''.</p>

=== Where to send ===

<p>If you are going to send pure VBA streams, send them directly to [Noel dot Power at Novell dot com].</p>

== Implementation ==

=== The desired sequence ===

==== Add an extension to the IDL ====

The IDL lives in oovbaapi/org/openoffice/*, the IDL syntax can easily be gleaned from a few other IDL files. Two things are worth bearing in mind:
* it's important that the argument names are correct, so that the <tt>MsgBox title:="hello"</tt> syntax works correctly.
* for optional arguments, or variant types you need to use the <tt>any</tt> type

Having edited the IDL extension you need to:
* run: <tt>build && deliver</tt> in oovbaapi (perhaps remove types.db first),

==== Add the extension to the implementation ====

The impl. code lives in <tt>sc/source/ui/vba/</tt> - create the right header and source files.
Add the method (with the correct prototype) to the header - often it's easiest to cut/paste that from the compiled C++ headers in <tt>sc/unxlngixxx/inc/org/openoffice/vba/</tt>

Then implement the method itself in the .cxx file. Run <tt>build debug=true</tt>

==== Running it ====

You did use [linkoo] right ? - in which case - just re-run soffice.bin (killall -9 soffice.bin first to ensure there is no lurking factory process).

Now of course - you want to add a new test to exercise it to ooo-build/test/macro/*. And of course loop back to the beginning.
Once you've got something you want to share - a simple <tt>cvs diff -u | tee /tmp/foo.diff</tt> in ooo-build/scratch will yield a patch you can mail to Noel / the ooo-build mailing list to get your code folded in.
NB. it's important you sign the [http://www.openoffice.org/licenses/jca.pdf JCA] first.

== Testing ==

<p>It's extremely important to test the work which is already done. You can use test cases from the ''ooo-build/test/macro'' directory, you can extend them or you can write your own test cases.</p>
It's a good idea to write test cases directly in the Microsoft Excel?

== Accessing the VBA API from other languages ==

The VBA API is implemented by an UNO service, the service is accessible via a singleton. As such it is possible to use the API from any language that has an UNO binding. The main entry points to the API are certain global variables { Application, ActiveWorkbook and ActiveSheet } or methods { WorkSheets, WorkBooks } exported by the service. Using these globals as a starting point the rest of the api can be accessed.

'''NOTE:''' Beaware the idl is not stable, (nor won't be for the forseeable future be 'published') it WILL change, so if you are using a language that has a binary dependency on the interface (like c++ & java) then consider yourselves warned.

=== Python ===

vba = uno.getComponentContext().getByName("/singletons/org.openoffice.vba.theGlobals")
sheet = vba.ActiveSheet
book = vba.ActiveWorkbook

=== Java ===

<pre>
import org.openoffice.vba.*;
"
// getComponentCtxFromSomewhere is a fictional
// routine representing acquisition of the component context
// from e.g. remote ServiceManage if the code is a remote client
// or from the XScriptContext if this were a java ScriptingFramework script

XComponentContext ctx = getComponentCtxFromSomewhere();
Object oGlobs = ctx.getValueByName(
"/singletons/org.openoffice.vba.theGlobals");
XGlobals xGlobs = AnyConverter.toObject(
new Type(XGlobals.class), oGlobs);
XWorkBook xWBook = xGlobs.getActiveWorkbook();
XWorkSheet xSheet = xGlobs.getActiveWorkSheet();
</pre>

=== OO Basic ===

Basic allows access to the global variables automatically just like VBA does, there is no need to create any services or access any singletons to use the API

msgbox "Name of the current document is " & ActiveWorkbook.Path

=== Visual Basic ===

Visual Basic, VBA, VBScript and other COM-enabled languages supports accessing OpenOffice VBA API via COM-UNO bridge

<pre>
Set oServiceManager = CreateObject("com.sun.star.ServiceManager")
Set oDesktop = oServiceManager.createInstance("com.sun.star.frame.Desktop")
Dim aNoArgs()
Set oCalcDoc = oDesktop.loadComponentFromURL("private:factory/scalc", "_blank", 0, aNoArgs)

Set v = oServiceManager.DefaultContext.getValueByName("/singletons/org.openoffice.vba.theGlobals")
Set ooApp = v.Application
MsgBox ooApp.Version
Set cell = ooApp.ActiveCell
cell.Value = "Hello!"
Set r = ooApp.Range("B1", "B1")
r.Value = "Hi1"
</pre>

CHM Help file generated from oovbaapi IDL:
http://community.i-rs.ru/index.php?action=dlattach;topic=6096.0;attach=4431
[[Category:Development]]

Main Page

2008-01-05T15:10:18Z

KAMiKAZOW: /* Hot Topics */

<div style="float:right; padding-left:5px;">
{| style="text-align:left; border:1px solid #aaaaaa; background-color:#f9f9f9;width: 200px;font-family: Verdana, sans-serif;"
|- padding:5px;padding-top:0.5em;font-size: 95%;
|
----
<div style="border:1px solid #ccc; background: #fff; border-right:3px solid #ccc; border-bottom:3px solid #ccc; text-align: center; padding:3px; float:right; font-size: smaller; line-height: 1.3; margin-right: 4px;">
<div style="width:100%">{{CURRENTDAYNAME}}</div>
<div style="width: 100%;">{{CURRENTYEAR}}</div>
<div style="width: 100%;"> {{CURRENTMONTH}}</div>
<div style="font-size: x-large; width: 100%;">{{CURRENTDAY}}</div>
<div style="background: #aaa; color: #000;">'''{{CURRENTTIME}}''' [[wikipedia:UTC|UTC]]</div>
</div>
{{Welcome}}

{{Language|Languages}}
|}
</div>


== Welcome to the OpenOffice.org wiki ==
__NOTOC__
This wiki is for all projects associated with OpenOffice.org (OOo). It is new, so it is mainly focused on resources for developers. As other projects are added to the wiki, they will be listed here. Click a link to go directly to the page you want.
* [[#Getting started with OOo development|Development]] (see below)
* [[Documentation]]
* [[Quality Assurance]]
* [[Marketing]]
* [[Education Project]]
* [[Certification]]
* [[NLC]] ''Native-Language Confederation''
* [[Security]]
* [[Product_Release|Product Releases]]
* [[#Finding general OpenOffice.org user help|User Resources]]
* [[Website]]
Join in contributing to the OpenOffice.org Wiki. Please use your OOo log435in name for the wiki account. Some functionality is available only if you are logged in to avoid [[MediaWiki_Configuration#AntiSPAM_Measures43q5|SPAM]]. Additionally your email address has to be validated. We might be able to avoid the separate user administration later and log you in with the OpenOffice.org site credentials.

To get started editing the wiki see [[Help:Editing]].

== Getting started with OOo development ==
<div style="float:right; background-color:lightyellow; border: 1px solid black; margin:0 1em 0 0.5em; padding:0 0.5em 0 0.5em; ">
<b>Get Started from Scratch</b><br />
you most likely need to:
# [[Getting It|Get it]]
# [[Building|Build it]]
# [[Installing|Install it]]
# [[Running|Run it]]
Click for instructions on <br />
each step!
</div>

[[Building]] and [[hacking]] on [http://www.openoffice.org OpenOffice.org] (OOo) entails climbing a fairly lengthy and steep incline. Hopefully, this wiki will make the learning curve less steep and less abrupt, and will give you a walking stick to help you out.

Much of our documentation assumes that you'll be using a reasonably current Linux system, as this the easiest environment to start. On Linux all prerequisites are available as [http://www.gnu.org Free software]. There is also some information on developing on [[Windows]].

For help setting up your editor or environment to search/edit/compile OOo easily, please refer to the [[:Category:Developer_Tools|developer tools]] area.

Note that you can build either the plain 'up-stream' OOo or use an [[ooo-build]] release which adds some patches & fixes. However, the ooo-build process is destined to being gradually phased out as the various up-stream issues it solves go away.

Remember that learning UNO components development is not an easy task. To help you there is an Eclipse plugin and tutorial. You can install the Eclipse plugin by using the following update site: http://cedric.bosdonnat.free.fr/ooeclipseintegration. The tutorial on how to create a UNO component in Java is available in the [http://api.openoffice.org/files/documents/22/3216/JavaComponentTuto.odt api project docs & files sections]. The document will even be wikified on this page: [[JavaEclipseTuto | Java Tutorial using Eclipse]]

There exists also an [[OpenOffice_NetBeans_Integration|OpenOffice.org API plugin for NetBeans]] that helps a lot to get started with the API and with developing with and for OpenOffice.org. The plugin provides several wizards that simplify the first steps and help to create full working code skeletons for extensions. Try it out and have fun when you want to develop a Java extension for OpenOffice.org. Feedback is always welcome, help us to improve the plugin and send us new ideas what we can do better!

== Going Further ==

* [[IRC Communication|Meet the team on IRC]]
* [[Tutorials]] - hacker tutorials to get the hang of the code
* [[Debugging]] - for when it all goes wrong
* [[Tinderbox]] - test new child workspaces and show your build logfile to others
* [[Environment Variables]] - a description of handy environment variables used at runtime
* [[Source code directories| A description of the source directories]]
* [[Contributing Patches]] - for when you have something to fold back
* [[Commit Rights]] - An overview of how to attain commit rights, and what to do with them once you get them
* [[Tips]] - misc. hints & tips.
* [[FAQ]] - some infrequently asked questions
* [[Using_Cpp_with_the_OOo_SDK|Using C++ with OOo SDK]]
* [[Extensions_development|Extensions development]] (Python, Basic, Java and C++)
* [[Extensions_development#Ideas|Extensions Ideas]] An ideas section for new extensions '''(NEW)'''
* [[:Category:Localisation|Localisation of OpenOffice.org (under construction)]]
* [[OpenOffice_NetBeans_Integration|OpenOffice.org NetBeans Integration]] - program, extend, and customize OO.org in Java with a modern IDE
* [[OpenOffice_Eclipse_Integration|OpenOffice.org Eclipse Integration]] - program, extend, and customize OOo in Java with Eclipse
* [[Extra Software]] - other open source programs

== Hot Topics ==
* [[Extensions development#Ideas|Extensions Ideas]] '''(NEW)'''
* [[To-Dos]]
* [[Performance]]
* [[User:Ericb|Native Mac OS X port]] or for everything related to OpenOffice.org and [[:Category:MacOSX|Mac OS X]]
* [[SCM_Requirements| SCM Requirements]]
* [[SVNMigration| Use SVN instead of CVS]]
* [[SVG_Import_Filter|SVG import]]
* [[Product Release|Product release data]]
* [[Java_and_OpenOffice.org|Java related functionality]]
* [[Writing_warning-free_code|Warning-free Code]] and [[Writing_correct_Cplusplus|Correct C++]]
* [[Syndication|Syndication]] Of OOoAnnouncements
* [[Mono Integration|details on how to get Mono working with OOo]]
* [[Porting_to_x86-64_%28AMD64%2C_EM64T%29|64bit porting]]
* [[VBA|MS Office VBA interoperability]]
* [[Digital Signatures]]
* [[Bibliographic| Bibliographic Project Developer and Documentation pages]]
* [[QA Metrics]]
* [[BuildSpeedup| Make the OO.o build process the coolest on the planet]]
* [[Chart2 | Chart2: The new chart implementation]]
* [[Firefox ODFReader extension]]
* [[Firefox OpenOffice.org extension]] Menu extension with useful OO.o links
* [[Compiler versions used by port maintainers and release engineers]]
* [[Effort/Revise OOo Multi-Threading|Revise OOo Multi-Threading]].
* [[Uno]] on the Wiki.
* [[Framework]] on the Wiki.
* [[Summer_of_Code_2007]] and [[OpenOffice.org_Developer_Article_Contest]]
* [[BetterDatabaseDrivers | Better and simpler infrastructure for database drivers]]
* [http://www.openoffice.org.br/?q=lancamento_do_cogroo Cogroo] grammatical checker in Portuguese
* [[Architecture]] - Description of OOos software architecture.
* [[Metalink]] - An XML format used by OOo for file distribution that stores mirror/P2P locations.
* [[Convert2MediaWiki]] - Informations to convert from OOo to media wiki
* [[Object Inspector]] - Description of an extension to inspect Uno-Objects
* [[OOoCon 2007]] - The OpenOffice Conference 2007

== Finding general OpenOffice.org user help ==

* [[OOoHelpOutline|OpenOffice.org Help Outline]]
* [[OOo OnlineHelp]]
* [http://plan-b-for-openoffice.org/ Technical support] for non technical users
* Free and commercial [[OpenOffice.org_Solutions|Solutions]] to assist in the adoption of OpenOffice.org
* [[Press coverage on OpenOffice.org]]
* [[Wikipedia:List_of_applications_supporting_OpenDocument|List of applications supporting OpenDocument]] from Wikipedia
* [[OASIS]] and [[OpenDocument]]
* The office suite components: [[Writer]], [[Calc]], [[Impress]], [[Base]], [[Math]], [[Draw]], and [[Chart]].
* [http://www.kegel.com/openoffice/triage.html OpenOffice.org Needs YOU! (OLD)]

[[:Category:MainIndex|Main Index of Articles]]

<center>
{|style="border: 1px solid #cfcfbf; padding: .0em .25em .0em; background-color: #f0f0ff; text-align: center;"
|
|-
|
<p style="margin: 0em 0 0 0%; line-height: 1.1">
</p>
| style="font-size: 95%;"|You loaded this Main Page on {{CURRENTDAYNAME}}, {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}} ''T'' {{CURRENTTIME}} '''[[wikipedia:UTC|UTC]]'''.
|-
|style="font-size: 95%;"|
|}
</center>

OOoRelease23

2007-08-03T00:39:40Z

KAMiKAZOW: /* OOo 2.3 */

== OOo 2.3 ==

!! prelimary dates !! need confirmation by release status meeting

* UI and [[Feature freeze]]: July 5th, 2007
* [[Translation for 2.3|Translation update 2.3]] start: July 12th, 2007
* Translation update 2.3 delivery: July 26th, 2007
* [[code freeze]]: August 2nd, 2007
* l10n CWS builds available: August 2nd, 2007
* TCM l10n testing on CWS builds: August 3rd - 9th 2007
* pre release candidate (en_US only): August 9th, 2007
* [[Last cws integration]] for fixes: August 16th, 2007
* release candidate for all languages: August 23rd, 2007
* Product release: September 4th, 2007

=== Release Plan for 2.3 release===

{| border = "1"
|-
! Task !! Who !! Deadline !! Comments
|-
! last cws integration for first RC / SRC680_m2xx
| mh, RE || ||
|-
! release notes
| mh, ja || ||
|-
! Setup Guides
| || ||
|-
! Upload of RC builds
| ja || || full install sets for: en-US da de es fr it ja nl ko pl ru sv pt-BR zh-CN zh-TW

language packs for: af as-IN be-BY bg br bs ca cs da de dz el en-GB en-ZA es et fi fr ga gu he hi-IN hr hu it ja ka km ko lt mk ml-IN mr-IN nb ne nl nn nr ns or-IN pa-IN pl pt pt-BR rw sh-YU sk sl sr-CS ss st sv sw-TZ ta te-IN tg th ti-ER tr ts uk ur-IN ve vi xh zh-CN zh-TW zu

|-
! Trigger QA of final builds
| aschnabel || ||
|-
! Track Status of localized builds
| ja || || http://www.qatrack.org/ooo/view.php
|-
! Publish status of [http://qa.openoffice.org/qatesttool automated GUI testing]
| [[User:jsi|jsi]] || || [[OOoRelease23AutomationTestMatrix]]
|-
! Update of 2.3 pages for RC
| ja || || http://download.openoffice.org/680/index.html
|-
! QA of English RC builds
| ja || ||
|-
! Update of SDK
| ja || ||
|-
! Update of SDK Release Notes and update of redirect page http://download.openoffice.org/sdk.html
| jsc/ja || ||
|-
! Upload of src tarballs
| ja || ||
|-
! msg to announce@ooo content
| louis || ||
|-
! move RC to final
| ja || ||
|-
! download pages
| ja || ||
|-
! upload of solver tarballs
| ja || ||
|-
! notification of mirrors
| ja || ||
|-
! Update of Bittorrents
| (mike!) || ||
|-
! Update of P2P page
| antbryan || ||
|-
! press kit update
| jpmcc/lsp || ||
|-
! press release/alert
| jpmcc, lsp || ||
|-
! homepage
| louis || ||
|-
! release
| all || ||
|-
|}

== Next Release ==
* [[OOoRelease231]]

[[Category:Releases]]

OOoRelease30

2007-08-03T00:39:04Z

KAMiKAZOW: /* OOo 3.0 */

== OOo 3.0 ==

* first translation handover: January 18th, 2008
* UI and [[Feature_freeze]]: March 6th, 2008
* [[Translation for 3.0|Translation update 3.0]] start: March 13th, 2008
* Translation update 3.0 delivery: April 3rd, 2008, code freeze for Beta
* begin TCM testing: April 10th, 2008
* "last cws integration" for Beta: April 17th, 2008
* OpenOffice.org 3.0 Beta: April 30th, 2008
* [[code_freeze]], last regular translation delivery: July 4th, 2008
* [[Last cws integration]] for fixes: July 18th, 2008
* release candidate for all languages: July 25th, 2008, begin of TCM testing
* Product release: September 2nd, 2008 or OOoCon 2008 mid September ?

== Next Release ==

* next bugfix release [[OOoRelease301]]
* next feature release [[OOoRelease31]]

[[Category:Releases]]

User talk:Ericb

2007-05-23T09:59:56Z

KAMiKAZOW:

Have you ever looked at the way you do spacings? You . put . a . space . in . front . of . almost . every . punctuation . mark . That . looks . like . you . are . a . little . kid . who . cannot . write . correct .<br>
I know about French spacing in sentences, but what you do isn’t even correct French spacing (that’s why I refered to it as “Stupid French spacing”). You use normal spaces, but the correct way are thin non-breaking spaces. Not to mention that this Wiki isn’t even French, but English! --[[User:KAMiKAZOW|KAMiKAZOW]] 11:59, 23 May 2007 (CEST)<br>
PS: Sign your comments.

To-Dos

2007-05-23T09:21:01Z

KAMiKAZOW: /* Mac OS X Porting - Work Areas/Tod's */

OpenOffice.org has many things which one could work on ... just see below :-)

=API/To-Dos=
{{:API/To-Dos}}

=Application Documentation and Help Development To Do=
{{:Application Help Development To Do}}

=Architecture/To-Dos=
{{:Architecture/To-Dos}}

=Framework/To-Dos=
{{:Framework/To-Dos}}

=Porting/To-Dos=
{{:Porting/To-Dos}}

=Mac OS X Porting - Work Areas/ToDos=
{{:Mac OS X Porting - Work Areas/Todo's}}

=NLC:whatshot=
{{:NLC:whatshot}}

=Qa/To-Dos=
{{:Qa/To-Dos}}

=Stats/To-Dos=
{{:Stats/To-Dos}}

=SVG Import ToDo=
{{:SVG Import ToDo}}

=Tools/To-Dos=
{{:Tools/To-Dos}}

=Uno/To-Dos=
{{:Uno/To-Dos}}

=Writer ToDo=
{{:Writer ToDo}}

=Eclipse Integration ToDo=
{{:EclipseIntegration ToDo}}

=Base To-Do=
{{:Base To-Do}}

[[Category:Development]] [[Category:To-Do]]

User:Ericb

2007-05-23T08:35:38Z

KAMiKAZOW: Stupid French spacing

==Public Documentation License Notice==

The contents of this Documentation (excepted Native Port Roadmap),are subject to the Public Documentation License Version 1.0 (the "License"); you may only use this Documentation if you comply with the terms of this License. A copy of the License is available at http://www.openoffice.org/licenses/PDL.html.
The Original Documentation is "Mac OS X native port". The Initial Writer of the Original Documentation is (JCA) Eric Bachard (C) 2005-2006. All Rights Reserved. (Initial Writer contact(s): ericb@openoffice.org.)

=='''Mac OS X Native port'''==

<div class="messagebox cleanup metadata" style="border:1px solid blue;background-color:#B3FFF5;padding:7px;">
'''The first Mac OS X native port objective is make OpenOffice.org run without X11 use, to make it a real Mac application.'''

'''The second one is respect Aqua Human interface Guidelines'''

''' This is a long term work, and every help and/or contributions, like donations** are welcome.'''
</div>

**see http://contributing.openoffice.org/index.html

=='''Native Port Roadmap'''==

==='''2006'''===

* June 2006: work in progress

- Basis: frame, instances, threads, drawing, painting, resizing (Stephan Schaefer, Tino Rachui)

Done:
implement threads
create, manage instance
create, manage windows (including parents)
create, manage events
create manage drawing, resizing
create, add menus (Pavel Janik)
toggle window fullscreen (Pierre de Filippis)
make font server work (Stephan Schaefer)

* Current status font support (Stephan Schaefer, 2006/07/28): the following features are basically working now
** font selection
** font size
** simple font attributes (bold, italic)

Next step: document first part, and propose design

- native filepicker (Pavel Janik, Florian Heckl)

- native printing implementation (Oliver?)

- native font implementation (Eric Bachard)

* September 2006:

- first proofs of concept: fonts, filepicker .. (more?)
- show the results (OOoCon 2006?)

==='''2007'''===

* January 2007: first alpha implementation

=='''Strategy for native port'''==

'''Possible Actions''':

Identify us:

#Complete the arrays below
#Update photos on frapr.com?

Share the work:

#Divide the work between little Teams
#Update Todo list regularly -> needs some love these days ... [http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_Work_Areas/Todo%27s]

Help:

#Teach tools between us
#Do a debug party on IRC
#write documentation

Meet us:

#IRC
#Mac Meeting (like nov2005 in Hamburg?)

Inform:

#Update website regularly
#Blogs

'''WHO''':

Mac Team:

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
|Developer \ skills || build || write code || code review || debug/trace (higher is better) || contribute to documentation ||
|-
|ericb|| x || x || || 1 || x ||
|-
|pjanik|| || || || || ||
|-
|ssa|| || || || || ||
|-
|maho|| || || || || ||
|-
|tinor|| || || || || ||
|-
|schmidtm|| || || || || ||
|-
|ebischoff|| || || || || ||
|-
|obr|| || || || || ||
|-
|cl|| || || || || ||
|-
|aliscafo|| || || || || ||
|-
|fheckl|| || || || || ||
|-
|Fridrich|| || || || || ||
|-
|plipli|| || x || || || x ||
|-
|}

'''Other resources''':

fonts:?

events:?

QA: James McKenzie leads QA for the Mac OS X port of OpenOffice.org and is looking for volunteers to spread this effort over several people and needs people from all over the world to test various languages.

graphical:?

Communication:?

'''WHAT''': Status of most important tasks

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Task || Names|| Urgency (1=higher)|| Work in Progress || Done || Code review || Debug || Integration ||
|-
|Get rid of X11||done || 1 || x || x || || || ||
|-
|Bundle|| || 1 || x || || || || | ||
|-
|Drawing|| || 1 || x || || || || || ||
|-
|Fonts||plipli || 1 || x || || || || || ||
|-
|Events management|| || 2 || x || || || || || ||
|-
|Controls (see list) ||ericb, aliscafo || 2 || x || || || || || ||
|-
|Native FilePicker||Florian Heckl, Pavel Janik || 3 || x || x || || || || ||
|-
|Native Printing||Yvan Barthelemy || 3 || x || || || || || ||
|-
|Native SpellChecker|| || 4 || || || || || || ||
|-
|Player|| || 4 || || || || || || ||
|}

Other tasks:

Help for writing bug lists, status of bugs ..etc

Write howto use gdb, leaks, other tools

'''WHEN''':

From Christian Lippka (last meeting, 25th of august 2006):
Aug 26 00:21:38 ChristianL
from my point of view what is missing for point 1:
text layout, complete font support, keyboard support,
fixing repaint issues, having aqua install and run out of the box

'''September 2006'''

Present the current state of the project at the 2006 OpenOffice conference in Lyon and Paris

'''Late 2006'''

fix OpenOffice.org launch
fix drawing (repainting)
Implement missing methods and fix most important bugs (mainly the one leading to crash) in:
ATS
Salgraphics
Salinstance

'''January or February 2007'''

make Java work (works partially)
make intensive debug
present something working as alpha

'''June 2007 '''

Implementation of:
native filepicker
native printing

== '''Become a Domain Developer for Mac OS X port''' ==

People regularly contributing to Mac OS x port with regular and quality patches are, after proposal, invited to become a [[DomainDeveloper]].

The purpose of this document is to clearly define all the steps to become a [[DomainDeveloper]].

Preliminary: step 1 in [[Commit_Rights]] must be completed and checked, and you must be in the list of [[http://www.openoffice.org/FAQs/faq-licensing.html#jca1 JCA Licensed people]]

=== Steps for ssh2 key to be uploaded ===

==== Create the key ====

Everything is described here: [[http://www.openoffice.org/scdocs/ddSSHGuide.html SSH Guide]]

==== Upload the key ====

You must create an issue, like described below :

'''Assign it to "ssh2key" in the "www" component'''

Sub Component: openoffice.org cvs

Title: CVS Commit access request

Add louis (Louis Suarez Potts) or st (Stefan Taxhet) on CC

Upload your ssh2 public key respecting the process (Attach a DSA key, not an RSA)

A project lead will confirm your request

Then the support will upload your key

Once done the issue is set to Fixed , and the next step has to be verified before '''you''' close it.

'''EXAMPLE''': [[http://www.openoffice.org/issues/show_bug.cgi?id=75291 Upload SSH2 Key for Etsushi Kato]]

==== Verify it works ====

You now can try to connect via tunnel, and follow instructions given [[http://www.openoffice.org/scdocs/ddSSHGuide.html SSH Guide]]

If something goes wrong, ask for help to support, with a maximum of details, to solve the problem.

Once it works, the issue can be closed, and you can e.g. test downloading a module from tunnel repository :

First create a tunnel with the command:
<pre>
ssh -2 -x -L 2401:localhost:2401 tunnel@openoffice.org
</pre>

Then in a new window:

<pre>
export CVSROOT=":pserver:your_login@localhost:/cvs"

cvs login (enter)

(your password)

mkdir TEST

cd TEST

cvs -z4 co -r SRC680_m205 vcl

cd vcl

cat CVS/Root -> should indicate: your local repository
</pre>

=== Ask for CVS access for all modules required ===

Two steps: create an issue is mandatory because the concerned project is tools, and because people can have only ssh2 key without being [[DomainDeveloper]].

==== Create an issue ====

You must create an issue, described below :

Component: tools

Sub Component: www

Title: CVS access to all modules required

Assigned to mh + CC for ericb and/or pjanik

Present yourself quickly, and ask the access

A project lead will confirm

An admin will confirm this is ok, and set the issue to Fixed

'''EXAMPLE''': [[http://www.openoffice.org/issues/show_bug.cgi?id=75494 CVS Access all modules for Etsushi Kato]]

==== Verify ====

Create the tunnel :

open a terminal and type :

ssh -2 -x -L 2401:localhost:2401 tunnel@openoffice.org

once logged in, open a new terminal, and do (for example):
<pre>
cd $OOO_SRC_ROOT/

source MacOSXPPCEnv.Set.sh { source MacOSXX86Env.Set.sh for Mac Intel }

cd vcl (for example)

IMPORTANT: be sure vcl has been checked from tunnel, not from anoncvs (cat CVS/Root will give you the answer)

export CWS_WORK_STAMP=aquavcl01 # Only needed for working with [[EIS]], can change for a different CWS ;)

cd aqua/source/gdi

add your changes to your_file.cxx, then commit :

cvs commit -m "#i75689# bla bla ... the reason of the modification(s)" your_file.cxx # The #i75689# is an issue number in the tracker

cvs update

If nothing is wrong, cvs update should not return M for your_file.cxx, means the commit is successfull.
</pre>
In case of problem, use the issue until it is fixed

<big>'''Welcome aboard :)'''</big>

== '''Mac OS X porter Team at WWDC 2007''' ==

=== What is WWDC 2007? ===

See [http://developer.apple.com/wwdc/ Apple WWDC 2007]

====Labs Agenda====

It is extremely important to organize us for Labs.

The rule is extremely simple: bring your laptop, your code, and ask :)

{| border="1" cellpadding="10"
| Days
|monday<br>June 11
|tuesday<br>June 12
|wednesday<br>June 13
|thursday<br>June 14
|friday <br>June 15
|-
|Labs
|<br>Afternoon
|Morning<br>Afternoon
|Morning<br>Afternoon
|Morning<br>Afternoon
|Morning<br>Afternoon
|}

===='''Interesting Labs'''====

The complete list: [http://developer.apple.com/wwdc/tracks/macosx.html Mac OS X Essentials]

*Core Text Lab
Receive one-on-one technical assistance and troubleshooting advice from the Core Text engineering team. Learn how to use the advanced font handling and blazingly fast Unicode layout capabilities of Core Text. Bring your laptop, your code, and your questions.

*HIToolbox Lab
Work on tuning and debugging HIToolbox code in your Carbon application. Receive one-on-one technical assistance and troubleshooting advice from the High Level Toolbox engineering team, Apple DTS engineers, and technology evangelists. Bring your laptop, your code, and your questions.

=== Our Objectives at the WWDC 2007 ===

'''1) Connection OOo Mac team / Apple engineers'''

-Goal 1.1: "Get infos, contacts, human to human conversation :-)"

-> Present our current work, methods and team to Apple people :

-> Meet them during WWDC: give us/them a face, keep contacts

-> Get their impression about what we have already done and what is still ToDo

'''2) Improve from Apple's engineers expertise'''

-Goal 2.1: "Give MacOS X users the OOo suite they deserve"

=> As mac platform and apple's product fans, we are proud to bring the quality and power of OOo to mac users community

=> Make OOo uses all the power of Mac OSX, including upcoming Leopard !

-Goal 2.2: "OO.org Mac port has to be as Apple HIG compliant as possible"

=> Define what is expected for User Interface of OpenOffice.org suite with people from Apple UI project

- FYI: Last year, Apple UI project proposed ericb to help us, once our native menus will be working.
This is now done.

'''3) Get code guidelines, tips, samples'''

-Goal 3.1: "Ask for code review and find code snippets"

- HIView
- Printing
- Drag and Drop
- as muc has possible

=> More than 1000 Apple engineers are present, and can answer our questions regarding the code, during the whole week

-Goal 3.2: "Attend key Labs and Sessions to get full overview of Tiger/Leopard/Core's and useful code"

- Core*
- Tiger / Leopard

'''4) Social Contacts / Team emulation'''

-> Discuss and meet new developers and / or american people working for Mac OS X port (like Michael Sicotte, Vijay Venkatraman , other..)
-> Share ideas, tips, conviviality !

'''5) Visibility'''

OpenOffice.org Native Mac port has to be recognized as the professionnal office suite for Mac users it is !

=== Who? ===

* Sébastien Plisson
* Eric Bachard
* Philipp Lohmann

=== Todo list ===

Please add topics, technical questions you would see asked by attendees to Apple engineers during WWDC

====Suggestions for current issues to be fixed ====

Timers: Current code is obsolete, and compatibility with Leopard won't probably exist. Pavel wrote a patch using recent code. Seems to work fine, excepted a thread issue (crash not easy to be reproduced)

Salframe:

Looot of things:

*Find infos/code sample about parenting

*Code review for HIFrameWork implementation

*Menus: every window creates it's own menu. Redesign it?

*adapt native widget framework

*Use XCode to build OpenOffice.org

Events: code review, tips

ATS: code review, ATS issues

Mike Sicotte:
I understood that implementing printing in aqua OOo was a topic that we didn't get accepted into Google SOC - so remains on the ToDo list. I notice that there are three Sessions specfically related to printing at WWDC:
Leveraging the Common Unix Printing System (CUPS)
Printing with Style in Mac OS X
Printing Lab
If this is judged to be a good use of time at WWDC I would be willing to spend some time to help further develop the questions to be addressed with the Apple engineers.

ericb->Mike Sicotte

Good idea. You are welcome :)

==== Travel ====

*describe the schedule of the travel

ericb :
<pre>
Mulhouse -> Paris -> SF: 9th of June SF scheduled arrival: 7:13 pm
SF -> Paris -> Mulhouse: 16th of June (arrival 17th) SF departure for the return: 3:00 pm

Hotel: King Georges (close to Union Square)

Airport to Hotel transportation: not included
</pre>

sebastien (aka plipli):
<pre>
Paris->SF: 3rd June
SF->Paris: 15th June in the evening

Hotel: to be coompleted
</pre>

==== Misc ====

*don't forget sector adaptator for laptop: US connectors are '''different'''

*don't forget Cameras (and chargers)

*Prepare 50 to 100 business cards : the most simple is to use the model I can provide on demand , and print them with special paper (pre-cut)

== '''Mac OS X porter Team at OOoCon 2007''' ==

=== Who? ===

* Shaun McDonald
* Eric Bachard
* (list to be completed)

Todo: ask for Mickael Sicotte travel (New York <-> Barcelona) + rooms

=== What? ===

The conference is over 3 days. Presentations should last around 45 minutes. http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=320 Papers have to be submitted by 1st June to be considered.

Ideas :

Mike Sicotte: Perhaps the results of the Google SOC could be a presentation.

*create a complete topic for Mac port (one stream for a day or half day)
*How to improve ooo usability though the use of floating palettes instead of modal dialogs

- several presentations / BOF

Eric Bachard: Aqua OpenOffice.org (conf / 1 hour)

Others?

*reserve rooms together? Better rent a house?

* [FIXME]

=='''2nd Mac porters meeting'''==

This section has been moved to [[2nd Mac porters meeting]]

=='''IRC Mac port meetings'''==

This section has been moved to [[MacOSXPortMeetings]].

== '''Mac OS X (X11) Quality Assurance'''==

This section has been moved to [[Mac OS X (X11) Quality Assurance]]

== '''Mac OS X Implementing HIView and Carbon events'''==

This section has been moved to [[Mac OS X Implementing HIView ]]

== '''Debug OpenOffice.org using XCode '''==

[[ MacOSX Debug OpenOffice.org using XCode]]

=='''Description of the Native Port problem'''==

=== How does OpenOffice.org work on Mac OS X? ===

Currently, on Mac OS X, OpenOffice.org uses X11, as "client": X11 is a graphical server, coming from Unix world, and able to run under Linux, *BSD, Solaris, Mac OS X.

- X11 is run as an application, managed like other Apple applications.
- All unix like applications are managed by X11, and from Aqua environment, only X11 is seen as only one applicatiion,
even if other Unix/Linux (e.g.) applications are runing.

OpenOffice.org asks X11 to display a window, waits for X11 acknowledgment, and OpenOffice.org displays the window. All transactions use the network, locally or not. the same mechanism is used for everything to be displayed.

[[User:Ericb|Ericb]] 11:39, 3 June 2006 (CEST)

=== Issues and known problems ===

All events are managed by OpenOffice.org and X11, using the Xlib

Only .ttf fonts type is currently available. Note: '''system fonts are available '''

The rendering is made by X11, not by Mac OS X rendering engine.

X11 and all its clients are seen as one application only: drag and drop protocol does not work because of that (solution: Pasteboard Manager)

==== Other links ====

http://wiki.services.openoffice.org/wiki/List_of_OpenOffice.org_Mac_OS_X_issues_and_problems#

http://wiki.services.openoffice.org/wiki/Printing_problems_with_OpenOffice.org_2.0_for_Mac_OS_X#Reporting_printing_problems

[[User:Ericb|Ericb]] 11:39, 3 June 2006 (CEST)

== What do we have to do?==

* (in progress): Implement direct access to Apple graphical engine, using Apple API: Quartz2D/CoreGraphics (and replacing Xlib use)

like: instantiate, manage events and threads for a graphical instance + all needed objects, drawing: manage all drawing cases

* (in progress): Implement native events management, using CarbonEventManager (replacing Xlib management)

* (in progress): Implement native font use, using Apple Type Server and ATSUI (for Unicode Imagery) (replacing X11 management)

Work in progress: [[Mac OS X Porting - Native Fonts]]

* Implement native sound, using QuickTime (replacing Java Media Framework): [[Mac OS X Porting - Native Audio and Video]]

* Implement native Drag and drop, Implementing Pasteboard Manager: [[Mac OS X Porting - Native Drag and drop]]

* (done experimental) Implement Native Filepicker

* Implement Native Printing: current uses cups, but native printing is mandatory: [[Mac OS X Porting - Native_Printing]]

* Implement Apple Spellchecker

--[[User:Plipli|Plipli]] 09:27, 25 March 2007 (CEST)

=='''Where is located the code to be modified?'''==

Most of the changes are located in vcl (Visual Class Layer), for everything graphical, events, fonts, rendering and printing.

Other, for sound and movies will be in avmedia (where the player is implemented in OpenOffice.org sources).

For drag and drop, dtrans is concerned (Pasteboard Manager implementation)

[FIXME]: Filepicker? Apple Spellchecker?

[[User:Ericb|Ericb]] 11:39, 3 June 2006 (CEST)

=='''How will the new implementation be tested?==

Currently, all openOffice.org code can be compiled without using the Xlib. but of course, a lot of features are missing,

and the final package simply won't work

In vcl module", a '''toy''' called svdem is built at buildtime. This binary is linked to libvcl* and so all new stuff can be tested.

e.g.: draw anti-aliased lines works well.

Everything implemented in aqua vcl code will be included in libvclplug_aqua, and svdem source code will contain a specific part to proceed tests.

<div class="messagebox cleanup metadata" style="border:1px solid blue;background-color:#B3FFF5;padding:7px;">

'''The magic is: when all needed features will work with svdem, it will work in the new version of OpenOffice.org !!'''

</div>

[FIXME]: add more complete list of features to implement and test.

== AquaVCL 01 cws ==

[[http://qa.openoffice.org/issues/buglist.cgi?keywords=aqua Top 10 of Aqua issues]]

[[Aquavcl01 tasks]]

===Changelog ===

====Work in progresss: alpha :-) ====

(scheduled -hdu again :) - text breaking/text measurements)

==== alpha 0.9 ====

<br><div align="left" style="color:grey; font-size:18px">[[User:Ericb/Top10 of Issues | '''Top 10 of Issues with alpha 0.9 (click me to know more) ''']]</div><br><br>

(22th May)

thb: proposed a patch to workaround tjhe missing animations in Impress (issue 77692)

fheckl: fixing problem when switching between OOo picker and native picker

hdu: fixed the refresh and clipping => many problems with wrong clipping and wrong graphics attributes are gone

hdu: fixed the text drawn at bad size when resizing

(19th may)

Begining of Drag and Drop (Tino)

Using Aqua keyword, 123 issues created + macport user created.

user macport assigned means nobody is working on the issue.
Once someone assigned the issue to himself + sert issue as started, means issue has an owner.

Experimental code to test SetThemeWindowBackground to refresh everything (ericb) (18th may)

+: refresh is ok, bitmap refresh is ok when scrolling, typing text works in writer , pulse effect works, refresh checkbuttons works, refresh the window during scrolling works

-: no more cursor, excessive system load (lot of Begin /EndGraphic()

Important infos / WIP

The main work in progress is about refresh not working in all situations. We isolated the cause: very probably the clipping is either missing, or buggy.

Once fixed: pulse effect for buttons, text refresh (blinking cursor, and bitmaps in menus will be ok.

ericb add Aqua look for toolbars and tooltips (17th may)

==== alpha 0.8 ====

Christian Bernd Krippendorf joined the port (16th May)

hdu: memcpy sizeof(data) instead of sizeof(pointer) bytes (16th May)

hdu: fix ATSLayout::GetTextWidth() for multiple glyph-bound-trapezoids

msicotte: added definition for makeCGptArray - helper for AquaSalGraphics::invert

msicotte: added AquaSalGraphics::invert(ULONG nPoints...

hdu: implement stretched/squeezed text

hdu: prepare font rotation directly in ATSUI units

hdu: simplify a little by removing dead code

hdu: enable bold-/italic-emulation for fonts only if needed

mikesic: #77317# - fix for wrong menu displayed when last Writer window closed

ericb: add pulse effect (it will help to verify refresh issues are fixed)

pl: safer yield mutex protection through guards

hdu: default to standard font attributes

pl: protect against dispatching to dead or dying AquaSalFrames

ericb: #i77327# add alpha to user install dir until Aqua version is stabilized

hdu: rewrote ATSUFontID-based font enumeration

mikesic: Workaround for issue 77262 - frames around selected items don't disappear

mikesic: Fix for issue 74392 - aquavcl01: tooltip crash

mikesic: Fix for issue 77261 - Menu disappears when you hover over tooltip

mikesic: Fix for issue 75889 - aquavcl01: Extended tooltips text truncated

fheckl: adapting to changes since resync (aquafilepicker01)

fheckl: enabling fps_aqua lib only for aqua build

pjanik: Reformat for easier reading (according to OOo C++ rules).

Monday 15th May

Changes:

Yvan Barthelemy provided the first screenshot for printing :)

http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_Native_Printing

http://eric.bachard.free.fr/mac/aquavcl/screenshots/printing/native_printing/native_printing_dialog.jpg

F 73688: use default font system (WIP, hdu)

several fixes in salatsuifontutils (hdu)

several fixes in salframe (pl)

defaut user install dir is now ~/Library/Application Support/OpenOffice.org-aqua (ericb)

added pulse effect to help for refresh

Saturday 13th / Sunday 14th

F 74392: tooltip crash (mikesic)

(IMHO fixed with mikesic patch) 72250: toolbar icon click -> crash with aqua menus (not fixed? Worksforme)

F 74392: tooltip crash (mikesic)

==== alpha 0.7 ====

Sun decided to officialy supports the Mac OS x port (3rd May)

Welcome to Philipp Lohmann and Herbert Duerr , who joined the Team (3rd May)

resync m211 (1st May)

[Top 10 of issues] modify Bundle tree (issue 73693): change committed 28th April (ericb)

Google SoC: welcome to Ismael Merzaq and Omer BarOr , our two selected candidates: ismael will work on aqua look (NWF), and Omer will work on Mac OS X Address Book Integration.

resync: m208 (11th April)

(exp / not commited) Ismael proposed a patch for Utility Windows more Aqua compliant + SetMin/MaxSize() (9th April)

Native menus are defaults (ericb) (8th April)

Frederic Barbaise (alias boulifb) joined the port (3rd April)

Work on saltimer.cxx started mikesic (27th March)

Pavel commited Michael patch for invert and drawAlphaRect() (27th March)

Started 27th March

==== alpha 0.6 ====

Damien started to work on drawEPS()

plipli and ericb work on refresh

Michael Sicotte proposed to investigate in timers, and continue [[http://www.openoffice.org/issues/show_bug.cgi?id=75228 Pavel's work]]: objective is to replace obsolete code. (23th March)

[experimental] plipli proposed a patch for a new salframe implementation, using HIView + optionally compositing (21th March)

[commit scheduled] Michael Sicotte proposed a complete patch for invert() (SAL_INVERT SAL_INVERT_50 and SAL_INVERT_TRACKFRAME) (20th March)

Tino proposed to work on code cleanup in salatsuifontutils.cxx, removing obsolete code

ismael and michael work on invert() + drawAlphaRect()

Started (19th March) :

==== alpha 0.5====

Top 10 Summary: 7 issues over 10 are fixed or very close to be:

'''time to code review, tracing, and search for memory leaks'''

[done] Unicode input in salframe (ekato) (19th March)

[experimental, works partially] beginning of HIView + HIComboxes works (text still missing) (ericb + plipli) (14th March)

[done] replace NewRgn() in salframe (ericb (11th March)

[experimental, but very interesting] Improved native windows (ismael) (7th March)

====alpha 0.4====

'''[Informative]''' build runs with Leopard 9A377a (fheckl) (7th March)

Refresh screen issues (plipli) (4th to 10th March)

'''[informative]''' plipli announced progress with refresh screen issues (28th February)

[experimental, not yet commited] Proxy configuration from system (pjanik) (28th February)

[done] highlighted native button (pjanik) (27th February)

Native File Picker works (fheckl / pjanik) (23th February )

====alpha 0.3====

Cursor does appear -> invert() + setting a setBlinkTime value in UpdateSettings() (pjanik /ericb)

[done] mirroring negative images (ismael) + DrawAlphaBitmap() + CreateWithMask()

pjanik patch for Focus Events

[done] scrolling works (pjanik) (17th February)

[done ] carret works (plipli) (17th February)

[done] checkbuttons fix for checkmarks (ericb) (17th February)

'''[Informative]''' Pavel Janik propose to solve offScreen buffer using HIView (17th February)

[experimental, never commited] patch for macosxrc.txt use + UpdateSettings() use in salframe.cxx (ericb (16th February)

Michael Sicotte joined the Team (15th February)

invert(): first try (ericb) (13th february)

====alpha 0.2====

[12th February 2007 ]

[done] calc does not start: bug identified by tino , first workaround (ericb) [[http://www.openoffice.org/issues/show_bug.cgi?id=73691 issue 73691]]

[done] bitmaps in native popup menus (ismael)

[done] replace obsolete code for HandleWindowPaintEvent(), newRgn() .. etc (ericb) (12th February)

correct salatslayout patch (plipli) (11th February)

'''[Informative]''' Michel Renon proposed a summary about his work on fonts issues

[patch] Pavel fixed several menu crashes (09th February)

'''[Informative]''': Pavel posted a mail about several crashes origin

patch for radioboxes and checkboxes (ericb) (9th February)

first complete patch for salatslayout.cxx (plipli) (9th February)

[done] most important crashes fixed (pjanik) (09th february)

Modified baseline for 2.2.: Mac OS X10.4 -> Aqua will be 10.4 and 10.5 compatible only (ericb)

first try with multi line sallayout (plipli) (08th February)

Damien Duportal joined the Team (7th February)

[done] scrollbar changes (ericb) (4th February)

====alpha 0.1====

create Top 10 of issues before alpha 3rd February 2007: See: [[http://porting.openoffice.org/mac/news/2007/20070203toptenbeforealpha.html Top 10 of issues]]

[experimental, not commited] patch for TPT() implementation (ericb) (2nd February 2007)

Pavel Janik proposed to implement TransformProcessType() (2nd February 2007)

[not commited] implement UpdateSettings() (ericb)

Pavel Janik resynchronized aquavel01 cws with m202 (2nd February 2007)

====alpha 0.03====

Michel Renon joined the Team (1st February)

[done] fix checkbuttons and radiobuttons issues: offsets, redrawing of the check marks (ericb)

[done] fix scrollbar buttons (implement correct methods to retrieve dimensions)

[done] implement mapfiles for Mac OS X (Stephan Bergmann, Daniel Boelzle, Tino Rachui , Pavel Janik)

====alpha 0.02====

[done] modify libsalsystools.dylib to be correctly loaded with the bundle (ericb, + pjanik)

[done] add mouse drag events (pjanik)

====alpha 0.01====

[done] add new feature for Aqua windows, to allow QuickTime player use(mox)

[done] replace obsolete code in salframe.cxx with (ericb)

[done] fix correct size for main window (GetOptimaWindowSize() ) (ericb)

[done] fix alpha channel in pixmaps (ismael)

====alpha 0.0====

[done] pushbutton where not correctly drawn (ericb)

[done] fix missing mouse events (pjanik)

[done] fix nRepeat in text entry (ssa)

2nd Mac porters Meeting

===Work in progress ===

URGENT :

Top of issues causing crashes: event issue when tips is enabled causes crashes (well known window / handler / window desctructor / event loop bug)

Salatsuifontutils: replace old code, track leaks: tino

[done] Bitmaps: (isma87)

[running] Crashes: (tino, pjanik, ericb, isma87, plipli)

[???] Drag and drop: (vijay)

[???] Printing (ybart)

Florian Heckl proposed a subject for Google Summer of Code about native printing

Drawing/ windowing (plipli / ericb) -> mainly refresh

[done] Implement cursor

[started] Native Controls (ericb)

[work in progress] partial multiline sallayout (plipli)

To do:

(started, Oliver) - modify the tree to make the bundle start without hack (issue fixed during buildtime)

(started, Florian Heckl) verify Native FilePicker implementation (works , tested in Hamburg )

[done] Ismael Merzaq) implement blit functions in salgdi (important fix: probably apha version to be tested once done)

[done] Sebastien Plisson- update the missing functions list (fonts ... ask hdu & cl

[started] ericb, Mox Soini, Sebastien Plisson, Tino Rachui, Pavel janik continue to replace obsolete code

fix crashes with menus (started: tino)

== '''Sort of documentation about VCL around Native Mac OS X port''' ==

Do we really need to understand how it works? ;-)

vcl content:

ls -laR | wc -l
1750

-> Uff 1750 files to analyse :-/

Our purpose is to describe the vcl organisation. The content of vcl is so important, that at the begining, the content will looks a bit confused. e.g. class names ..etc have nothing to do, only description with words and sense, but this will need some time before we can understand everything.

How analyse with more efficiency? After some months to anlalyse '''"horizontaly"''', it appears that list all the content of a directory is not the solution. Of course, we learned a lot, but we now have to complete with '''"orthogonal"''' method (compared to the previous one). The first method wasn't obviously not the good/best way to describe vcl.

[FIXME] a different approach (will ask confirmation to Philipp Lohman), could be a description of how it work in runtime. First define what an instance is, a frame, and what exactly is concerned by such "objects".

With that, we can write a list of different objects all using the same scheme: empty boxes (means pure virtual methods and classes in generic libvvcl), really implemented in the specific part, and finally, the API "encapsulated".

The most difficult is to see where the API is used. But for all the parts, this is the same.

Finally, '''what is important is the design of vcl'''. Which '''patterns''' are used? What are the dependencies, how works the stack for the events, how works the scheduler, the timers too is very important, even fundamental for Aqua implementation. Will have a look at gsl mailing list, and other resources. Probably everything is already (randomly) written somewhere.

=== VCL organisation ===

Thank's to Philipp Lohmann for this short, but precise description:

Basically vcl is divided in the system dependent and the system independent part. The interface between these two is mostly the Sal interface (every interface name Sal*: SalInstance, SalFrame, SalGraphics, SalPrinter, etc.).

SalInstance is a factory that can create all the other abstracted interfaces of the system dependent part. It also provides the main loop SalInstance::Yield()

SalFrame abstracts any kind of system window.

SalVirtualDevice abstracts an offscreen window (e.g. a Pixmap on X11)

SalPrinter and SalInfoPrinter abstract the system print queues where SalInfoPrinter is for querying and SalPrinter for actual printing.

SalGraphics is an interface produced by either SalFrame, SalVirtualDevice or SalPrinter which is used for actual drawing operations (text, bitmaps, vector graphics)

SalSound is for sound playing.

SalBitmap provides memory for bitmap graphics as well as methods converting this memory to a system handle (e.g. a Pixmap on X11).

SalOpenGL provides OpenGL functionality if available.

SalTimer is an interface for periodically triggering the event queue (to timer implementation).

SalI18NImeStatus handles how the status window of an Input Method Editor (IME) should display (this is mainly X11 specific).

SalSystem has some system specific methods that did not belong anywhere else:-)

Of all these there interfaces is at least one implementation per system (Windows, X11 or Mac). The Unix implementation also has a plugin concept to allow for integration of different native toolkits (currently gtk and Qt) which became necessary for the implementation of Native Widget Framework (NWF) to display controls like their normal desktop counterparts.

Basically the independent part (what is beneath vcl/source directory) has generic methods for drawing, window handling and stuff which it brings into a suitable form and then delegates to the system specific implementation (located beneath vcl/win for Windows and vcl/unx for the X11 platforms).

[[User:Ericb|Ericb]] 16:12, 1 July 2006 (CEST)

===Sub-directories description ===

==== '''Organisation of vcl directories''' ====

[[Image:aquavcl_organisation_complete_02.jpg]]

==== '''Directories in vcl. Short description''' ====

''' aqua ''': The name Aqua means Apple look and feel, and is well known as [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGIntro/chapter_1_section_1.html Aqua Human Interface Guidelines]. This look and feel means Mac OS X. The work was begun by (probably) P. luby, Dan Williams Herbert Duerr (most of fonts stuff) and Ed Peterlin. Currently in ruin, this directory does contain a lot of ideas to investigate. The most important part of needed changes for native version (3.0) will be done inside aqua dir inc: does contain all vcl relative includes [PART1]

''' prj ''': Does contain build.lst and d.lst build.lst give us dependencies: probably a lot for vcl, build 98th module over ~148. Everything graphical depends in vcl.

''' qa ''' does contain all quality assurancy stuff

'''source''': the most important:-) This directory contains common sources for all architectures and OS. Mainly: Windows, Unix: Linux , Mac OS X (X11), Solaris, including generic, kde and gtk plugins, and Aqua (Mac OS X without X11, work currently in progress).

Depending on the OS and the architecture, binaries are built or not.

''' test ''': This directory does contain all the needed stuff for tests. As example, in qa/testdocuments, you'll find three documents (one writer, one calc and one impress) for tests purpose.
Other available tests are about memcheck and persistent window state.

''' unx ''': this directory does contain all unixes stuff. We have to understand what is inside to implement aqua port. For example, a lot of classes/strutures and objects use Xlib calls we have to replace with Carbon/Cocoa call (at least at first time) for Mac OS X native port.

''' win ''': Doing Mac OS X native port, I first believed this directory was not interesting for us, but I was wrong: OpenOffice.org roots are inside this directory, and a lot of comments and resources are inside. Mainly interesting if Carbon is used.

'''workben''': Does contain a toy called "svdem". svdem is a binary, used for new implementations. For example, actual aqua development uses svdem intensively, to verify all important properties we need:

- display a window first (al least ...:))

- close cleanly this window

- display a point

- trace a line

- trace an area

- superpose two areas doing some important graphical operations, (like xor),

- display a character

- display a menu.

- intercept events correctly.

[FIXME] add more tests

[[User:Ericb|Ericb]] 13:21, 3 June 2006 (CEST)

=='''Naming convention''' ==

* Class names start with upper case letters, to improve readability.

* Implemented Class names are derived from the virtual classes but can of course take arbitrary names.
To increase readability, it's recommended to closely follow the base class name.

* '''Impl prefix: means Implementation details'''. The concerned class or method or function is not used outside of this module, so no external code (or other libraries) can see it.

'''[[ Events types using Carbon API (Mac OS X): ]]''' A lot of events have to be managed in runtime. Here is a short description

- do not freeze because bad event loops

- event types implementation: currently, they are defined in vcl/aqua/inc/aquavclevents.hxx

Apart: exact sense of hedabu? -> [FIXME] as far as I understood it: it is like "copy" to deliver software into the solver, with extra magic. The header files for example are manipulated so paths need not be exact. "headabu" is supposed to disappear little by little.

== '''What do we have to build in vcl?'''==

Two libraries, corresponding ressources (localized) and a toy so called « svdem »

'''Common part''':

in grey on right. The result will be a non architecture dependant library, built in all cases: for instance, libvcl680mxi.dylib on Mac Intel.

'''Specific part " a plugin " ''':

Light yellow: aqua part will only concern Mac OS X (non X11) the name will probably be libvcl_aqua680mxi.dylib

As you can see, win means windows part, in blue

For Unix build (Linux, Solaris or current Mac OS X X11), in purple.

Result will be:

libvclplug_PLUGIN680mxi.DLLSUFFIX , where PLUGIN can be iether gen (generic) or gtk (using gtk+) or kde (using qt), and DLLSUFFIX can be either .so (linux) or .dylib (Mac OS X) ...etc (I'm not sure for other cases).

Example: libvcl680mxi.dylib and libvclplug_aqua680mxi.dylib

'''In runtime''', libvclplug_aqua will be linked to libvcl680. the first one will contain the real implementation (respecting the API, e.g. Carbon) while the generic libvcl will only contain pure virtual methods ...etc like "empty boxes".

=== Current Aqua content ===

A more complete description of aqua (Mac OS X / no X11 specific): [[Image:Vcl_aqua_organisation_02_tree.jpg]]

==EXISTING objects to build in aqua==

===Sal APP "everything application"===

[FIXME] add all objects descriptions

==== saldata ====

* '''Defined in plugin exclusively''' (i.e. for headers)

Unix: unx/source/app/saldata.cxx (header in unx/inc)

'''Aqua: aqua/source/app/saldata.cxx (header in win/inc)'''

Windows: win/source/app/saldata.cxx (header in aqua/inc)

* Role: saldata contains various kind of data used by the implementation for the concerned platform. '''It is a bunch of global data collections reserved for the platform'''

It is just completely platform dependent, and nobody except this plugin can see it.

'''Saldata is something like a "second sal", but providing an abstraction regarding windowing and graphics''', while SAL module provides an abstraction more Operating System oriented)

e.g.: have a look at XRequest array in vcl/unx/source/app/saldata.cxx => all calls are for Xlib (X11). Ok, useless there, but interesting:-)

[FIXME]: use Windows implementation could be a good starting point. Nothing is the same, but the current aquavcl cws uses similar objects, and it works very correctly.

saldatax.cxx uses classes SalInstance, SalObject, SalFrame, SalVirtualDevice, SalPrinter and fontList.

Current list of possible objects who can be instantiated/released:

structure SalData: does contain pointers on all kind of objects from other classes used in saldata.

inline functions: [FIXME]: complete the description

- SetSalData:
- GetSalData:
- GetAppSalData:

==== salinst ====

=> implemented in vcl/aqua/source/app/salinst.cxx

Role:

* get environment, mutexes, instantiate AquaSalInstance (Ctor, Dtor),

* instantiates/releases a lot of other objects using Get() / CreateObject() / DestroyObject() methods.

Current list of possible objects who can be instantiated/released:

* VirtualDevice [FIXME]: exact role?

*Printer

- GetDefaultPrinter/ CreatePrinter() / DestroyPrinter - what a name ;-) -

- InfoPrinter (Get/Create/Delete)

- PrinterQueue (DeletePrinterQueueInfo / GetPrinterQueueInfo / GetPrinterQueueState)

* System (Create / Delete) [FIXME]: what means system here?

* Events:

AquaSalInstance::SetEventCallback()

AquaSalInstance::SetErrorEvenCallback()

AquaSalInstance::GetConnectionIdentifier()

* Menu / MenuItem:

AquaSalInstance::CreateMenu() / same for DestroyMenu()

AquaSalInstance::CreateMenuItem / same DestroyMenuItem()

* Sound:

AquaSalInstance::CreateSalSound() => object to a pointer of SalSound type

Note: AquaSalInstance::DestroySalSound is not implemented (?)

* Timer: CreateTimer() /

AquaSalInstance:: DestroyTimer() is not yet implemented (?)

Class MacImeStatus: inherits of SalI18NImeStatus

-> only there to see if there is a window to toggle into menubar [FIXME]??

AquaSalInstance::CreateI18NImeStatus(): instantiates MacImeStatus

'''For futher informations, see: ''' '''[[Content of salinst.cxx]]'''

([[User:Ericb|Ericb]] 16:11, 20 May 2006 (CEST))

==== salmain ====

Role: if possible, runs the standard vcl application code SVMain()

([[User:Ericb|Ericb]] 16:15, 20 May 2006 (CEST))

==== salsound ====

==== salsys ====

==== saltimer ====

==== saltimer ====

The main problem with SalTimer is the code we use is obsolete. To remove this deprecated code, sevarl work have been tried

1) Pavel Janik, in issue 75228

works, but a serious problem is remaining (a thread issue, nothing anybody explained yet)

2) eric bacahrd (code will be attached soon)

3) Michael Sicotte, who proposed to work on that, and continue Pavel implementation.

SalTimer description

AquaSalTimerproc

AquaSalTimer::Start()

AquaSalTimer::Stop()

AquaSalTimer::Restart()

AquaSalTimer::Installtask() // yet needed?

=== Sal GDI (everything Graphical Display Interface) ===

====salgdinativewidgets====

[[native controls]]

==== salatslayout ====

==> implemented in vcl/aqua/source/gdi/salatslayout.cxx

- Handle text layouting :

* Use ATSUI (ATSUCreateTextLayoutFromPtr) to layout the text unicode char buffer
* Use ATSUI (ATSU..) to get informations about glyphs
* Populate different arrays (mpGlyph2Chars, mpChars2Glyph, mpCharsWidths, mpGlyphAdvances)
that are used in various methods.

==== salatsuiutils ====

==== salfontutils ====

==== salmathutils ====

==== sal bmp ====

==== salvd ====

==== salpixmaputils====

==== salprn ====

====salrectangle====

==== salvd ====

=== Sal Window===

==== salframe ====
Documentation in progress, from damiend :
[[User:Damiend|Damiend page]]

====salobj====

== TO BE IMPLEMENTED (missing in Aqua)==

===Audio===

====audioconvert====
(obsolete?)

====devaudio====
(obsolete?)

====native sound====

====salimpsound====

====vsound====

===i18n===

===keysymnames===

===saldisp===

===sm===

[FIXME]: is session manager usefull?

=='''Native Controls'''==

====Scrollbar====

'''Works as expected'''. The most important work is done

See: [[Mac_OS_X_Porting_-_Native_Controls#ScrollBar]]

====DrawThemeButton() documentation====

'''Started'''

See: [[Mac_OS_X_Porting_-_Native_Controls#ComboBox]]

Started
<pre>
DrawThemeButton
Draws a button.

OSStatus DrawThemeButton (
const Rect * inBounds,
ThemeButtonKind inKind,
const ThemeButtonDrawInfo * inNewInfo,
const ThemeButtonDrawInfo * inPrevInfo,
ThemeEraseUPP inEraseProc,
ThemeButtonDrawUPP inLabelProc,
UInt32 inUserData
);
Parameters
inBounds
A pointer to a structure of type Rect. Pass a rectangle specifying the boundary of the button, in local coordinates.

inKind
A value of type ThemeButtonKind. Pass a constant specifying the type of button to draw.
See “Theme Buttons” for descriptions of possible values.

inNewInfo
A pointer to a structure of type ThemeButtonDrawInfo. Before calling DrawThemeButton,
set the structure to contain the new state, value, and adornment for the button.
DrawThemeButton uses the information passed in the inNewInfo and inPrevInfo parameters
to apply transitional animation or sound effects as the button state changes, if such are
specified under the current theme.

inPrevInfo
A pointer to a structure of type ThemeButtonDrawInfo. If the button state is changing,
set the structure to contain the previous state, value, and adornment for the button,
to allow DrawThemeButton to apply any transitional effects. If the button state is not
changing, you can pass NULL.

inEraseProc
A value of type ThemeEraseUPP. If you have a custom background, use this parameter to pass
a universal function pointer to an application-defined function such as that described in
ThemeEraseProcPtr. DrawThemeButton calls this function to erase the background before drawing
the button. If you pass NULL, DrawThemeButton's default behavior is to erase the background
for you.

inLabelProc
A value of type ThemeButtonDrawUPP. If you pass a universal function pointer to an
application-defined function such as that described in ThemeButtonDrawProcPtr, DrawThemeButton
calls that function to draw the label of the button. If you pass NULL, no label is drawn.

inUserData
An unsigned 32-bit integer. Provide any data to be passed in to the callback functions specified in
the inLabelProc and inEraseProc parameters. Pass NULL if you do not wish to provide any data.

Return Value
A result code. See “Appearance Manager Result Codes”.

Discussion
The DrawThemeButton function draws a theme-compliant button. If a ThemeEraseProcPtr is
specified in the inEraseProc parameter, DrawThemeButton uses that function to erase the
background of the button before drawing the button. After the button is drawn, if a
ThemeButtonDrawProcPtr is specified in the inLabelProc parameter, DrawThemeButton calls
that function to draw the button’s label.

Note that DrawThemeButton also draws any appearance adornments for the button and that these
can extend beyond the button’s basic bounding rectangle, as specified in the inBounds parameter,
and may be of variable shape. You may therefore wish to call the function
GetThemeButtonBackgroundBounds to obtain the actual rectangle containing the pixels belonging
to a button under the current theme.

Version Notes
This function is available with Appearance Manager 1.1 and later.

Availability
Available in CarbonLib 1.0 and later when Appearance 1.1 or later is present.
Available in Mac OS X 10.0 and later.
Declared In
Appearance.h
</pre>

====HIComboBoxCreate() documentation====

<pre>
HIComboBoxCreate
Creates a combo box control.

OSStatus HIComboBoxCreate (
const HIRect* boundsRect,
CFStringRef text,
const ControlFontStyleRec* style,
CFArrayRef list,
OptionBits inAttributes,
HIViewRef* outComboBox
);
Parameters
boundsRect
The bounding box of the control.

text
The default text in the editable portion of the control. Can be NULL.

style
The font style of the both editable text and the text in the disclosure list. Can be NULL.

list
The default values available in the disclosure list. Can be NULL.

inAttributes
The default attributes of the combo box. For possible values, see “Combo Box Attributes”.

outComboBox
On exit, a pointer to a reference for the new control.

Discussion
The combo box can be used in compositing mode, as well as traditional Control Manager mode.
When created, this view is invisible. To see the view, you must show the view by calling HIViewSetVisible.
</pre>

== What is used for Linux, Windows, Mac OS X ...build? ==

'''[[Description of the dependencies]]'''

'''[[Windows]]'''

'''[[MacOS X]]'''

'''[[Linux]]'''

'''[[Solaris]]'''

== Content of Aqua ==

'''[[Click here to see the complete list]]'''

'''Content of vcl/inc'''

Notes:

1) Where to find includes

<foo/bar.hxx> means you can find bar.hxx in the foo module. The new style file is foo/inc/foo/bar.hxx, old style is foo/inc/bar.hxx and sometimes the file is somewhere else in the tree or generated. The deliver process copies/generates the file into solver at solver/680/build_type/inc/foo. Good for fixing broken builds. ;-)

2)
suffix .h (for C calls or first version?) or .hxx (C++)

'''A) Family of includes''':

Looking more closely at the list brings to the fore (expression from dictionary ;-)) that include names are
informatives. Most of the time, the name gives the function/role.
What is interesting is the files with name begining with "sal". sal means System Abstraction Layer + include's function (or explicit name).

Partial list, for example:

salatype.hxx

salbmp.hxx

salctrlhandle.hxx

salctype.hxx

salframe.hxx

salgdi.hxx

salgeom.hxx

sallayout.hxx (main header for fonts services)
...
salmenu
salnativewidgets
...etc

Other important families are "sv" and "uno" or "win" (window) prefixed. sal family will be analysed apart.

'''B) Includes of includes'''

Some includes are more important than other. To prove this, just have a look is sufficient: some are always needed, and some more rarely.

To verify, a simple test to do in vcl/inc:

egrep -H "#include" ./* | wc -l gives me 681 lines ! And some of them are the same...

To know more, the precedent command line can be modified to make appear the numerous call
to the same includes files.

egrep -H "#include" ./* | cut -d"#" -f2 | sort > liste.txt

The content of liste.txt is explicit: dllapi.h, sv.h and some other are very important, while some other includes are only one or two times used. We can see too that vos includes are numerous, even if vos is deprecated**

**see http://wiki.services.openoffice.org/wiki/Source_code_directories

I'm nearly sure that a complete analysis of just this result will give us a lot of information.

I propose to change the order of analysis starting with dllapi.h and sv.h.

[to be continued]

'''B1) "sal" includes family'''

[[salinst.hxx]] This seems to be the main include file

[[salatype.hxx]]

[[salctrlhandle.hxx]]

[[salctype.hxx]]

[[salframe.hxx]]

[[salgdi.hxx]]

[[salgeom.hxx]]

'''[[ sallayout.hxx ]]''' <-- see Native Fonts implementation

[[salgtype.hxx]]

[[vcl/inc/salobj.hxx]]

'''B2) Classicals includes'''

file: abstdlg.hxx [ means abstract dialog ]

This includes does contain the following classes definitions:

[FIXME]: choose a precise presentation template for classes

VclAbstractDialog,

VclAbstractTerminateDialog,

VclAbstractRefreshableDialog,

VclAbstractDialogFactory,

uses <tools/solar.h> , <tools/string.hxx> +

"dllapi.h"

Note: dllapi.h is very interesting because when we have to find (for example) a library suffix, SAL_DLLEXTENSSION can replace all suffixes (every OS's and archs). Just including sal/config.h does it !

Classes:

Window -> what? [FIXME]
ResId -> what?

Does contain the prototype of VclAbstractDialog, inherit of VCL_DLLPUBLIC

file: dllapi.h [ dll for dynamic linked library ]
Uses: <sal/config.h> and >sal/types/h>
includes: VCL_DLLPUBLIC macro

file: accel.h [ means accelerator ]

Classes:

Accelerator
{
}
ImplAccelEntry
{
public members:

Names

mnId
maKeyCode
mpAccel
mpAutoAccel
mbEnabled
}

function / returns / parameters

ImplGetKeyCode / void / KeyFuncType eFunc, ref rCode1 , ref rCode2, ref rCode3

file: accel.hxx

Uses: <sv.h> , "dllapi.h" ,<tools/resid.hxx>, <<tools/rc.hxx>

Classes:

ImplAccelData;
ImplAccelEntry;

== Important Links ==
'''[[Progressive implementation]]'''

'''Native Font server Implementation''' '''[[Mac OS X Porting - Native Fonts]]'''

'''Native Sound Implementation''': [[Mac OS X Porting - Native Audio and Video]]

'''Native Printing Implementation''': [[Mac OS X Porting - Native_Printing]]

'''Drag and Drop implementation''': [[Mac OS X Porting - Native Drag and drop]]

'''Data Acquisition''': [[Mac OS X Porting - Data Acquisition]]

This work is part of http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_Work_Areas/Todo%27s

[to be continued:-) ]

== Keyboard comparizon between OpenOffice.org / Mac OS X application ==

[FIXME] redo a cleanest array

{| style="vertical-align:top; text-align:centered; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Modifier||+ key || Result || TextEdit returns
|-
|ALT|| a||æ ||æ
|-
|ALT||b||ß ||ß
|-
|ALT||c||© ||©
|-
|ALT||d||∂ ||∂
|-
|ALT||e||ê ||ê
|-
|ALT||f||ƒ ||ƒ
|-
|ALT||g ||ﬁ ||ﬁ
|-
|ALT||h ||Ì ||Ì
|-
|ALT||i ||î ||î
|-
|ALT||j ||Ï ||Ï
|-
|ALT||k ||È ||È
|-
|ALT||l ||¬ ||¬
|-
|ALT||m ||µ ||µ
|-
|ALT||n ||~ ||~
|-
|ALT||o ||œ ||œ
|-
|ALT||p ||π ||π
|-
|ALT||q ||‡ ||‡
|-
|ALT||r ||® ||®
|-
|ALT||s ||Ò ||Ò
|-
|ALT||t ||† ||†
|-
|ALT||u ||º ||º
|-
|ALT||v ||◊ ||◊
|-
|ALT||w ||‹ ||‹
|-
|ALT||x ||≈ ||≈
|-
|ALT||y ||Ú ||Ú
|-
|ALT||z ||Â ||Â
|-
|ALT||A ||Æ ||Æ
|-
|ALT||B ||∫ ||∫
|-
|ALT||C ||¢ ||¢
|-
|ALT||D||∆||∆
|-
|ALT||F ||· ||·
|-
|ALT||G ||ﬂ ||ﬂ
|-
|ALT||H ||Î ||Î
|-
|ALT||I ||Î ||Î
|-
|ALT||J ||Í ||Í
|-
|ALT||K ||Ë ||Ë
|-
|ALT||L || <nowiki>|</nowiki> ||<nowiki>|</nowiki>
|-
|ALT||M ||Ó ||Ó
|-
|ALT||N ||ı ||ı
|-
|ALT||O ||Œ ||Œ
|-
|ALT||P ||∏ ||∏
|-
|ALT||Q ||Ω ||Ω
|-
|ALT||R ||‚ ||‚
|-
|ALT||S ||∑ ||∑
|-
|ALT||T ||™ ||™
|-
|ALT||U ||ª ||ª
|-
|ALT||V ||√ ||√
|-
|ALT||W ||› ||›
|-
|ALT||X ||⁄ ||⁄
|-
|ALT||Y ||Ÿ ||Ÿ
|-
|ALT||Z ||Å ||Å
|-
|ALT||$ ||€ ||€
|-
|ALT||` ||@ ||@
|-
|ALT||£ ||# ||#
|-
|ALT||* ||¥ ||¥
|}

Sous réserve d'erreur ou omission [[User:Ericb|Ericb]] 00:05, 14 January 2007 (CET)

--[[User:Ericb|Ericb]] 15:00, 22 Jul 2005 (EDT)

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]

Mac OS X ( X11) Quality Assurance

2007-05-23T08:34:16Z

KAMiKAZOW: Mac OS X ( X11) Quality Assurance moved to Mac OS X (X11) Quality Assurance

#REDIRECT [[Mac OS X (X11) Quality Assurance]]

Mac OS X (X11) Quality Assurance

2007-05-23T08:34:16Z

KAMiKAZOW: Mac OS X ( X11) Quality Assurance moved to Mac OS X (X11) Quality Assurance

==Mac OS X Quality Assurance==

===People ===

====Builds====
Maho Nakata posts builds to a File Transfer Protocol (ftp) at ooopackages.good-day.net/pub/OpenOffice.org/MacOSX
====QA (Testing)====
James McKenzie , Alexis Pigeon, Shaun McDonald, Joerg Sievers ([http://qa.openoffice.org/qatesttool Automation]), Martin Srebotnjak (Slovenian) ... [FIXME] : complete the list

===QA for 2.2===

Description of the process: Testing of OpenOffice.org is to reproduce actions taken by the ordinary user, either manually (not preferred) or automatically (preferred) test sequences. The localization project (L10N) also checks all menus and other written items for proper wording for the available languages.

- How can I help QA OpenOffice on the Mac?
First, the OpenOffice.org product is volunteer. So, you are asked to add your efforts to those of hundreds if not thousands of
others who volunteer for coding, testing and production. Please join the mac@porting.openoffice.org developer's mailing list
and post a message explaining your experience and the language you would like to test. Reminder: en_GB is different from
en_US.
- How current tests are processed
The current process for QA of Mac OS X is explained at the TCM site and involves conducting a series of manual tests as well as
automated tests. If a new release candidate is produced with no changes to the Mac OS X version, we conduct a shortened series
of tests called '''sanity testing''' to insure no new problems or the recurrence of old problems.
- clear rules about QA on Mac OS X.
All QA tests should be conducted per instructions on the TCM web site. All final results are to be entered on the QA Tracker
system. The QA Tracker system allows you to '''check out''' a release by language, operating system and platform. You then
may either accept or reject the release candidate. Release candidates should be rejected if a problem is encountered that
cannot be worked around and would cause a user to abandon use of OpenOffice.org IN A PRODUCTION work environment. This means
if Writer suddenly aborts, you must reject the release. If fonts appear strange on the page, but print ok, this would not
result in a reject, but an issue should still be created.
This system is also used to track QA testing in process with the name of the person conducting the tests. Any problems
encountered WILL have an Issue opened for them, if new, or updated, if existing, in the Issue Tracker system. Please input as
much information as possible in the Issue Tracker. At a minimum, you should input the steps needed to replicate the problem
you encountered and which release you were using of OpenOffice.org, Mac OS X and X11. Any additional information you feel
that will help a developer fix the problem can be included, such as crash logs, which are found using the Console application
and opening the local user Library/logs file and looking for soffice.bin.crash logs. Please do not post your logs to NoPaste
and then enter a link in the Issue, but rather upload the log and add it to the Issue.
- links for external information.
- recent *all concerned locales* , with current status
Due to issues with other platforms, the current release candidate rc3 was not approved by Sun as a final release. However, no
issues were found in this candidate that have not been found in prior releases.

All builds are obtained from a site maintained by Maho Nakata, ooopackages.good-day.net. Files are located in the pub/OpenOffice.org/MacOSX/2.2rc3_20070306 directory. Files are named OOo_2.2rc3_20070306_MacOSX<Platform, Intel or PPC>_<iso language code>.dmg.

Status
QA for the 2.2 version is underway. Testing for this version is scheduled to close on March 31, 2007, <br>but we would like to test it quickly to find fixable problems.<br>This date is subject to change as problems are encountered and resolved.

==Mac port Links==

This work is part of http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_Work_Areas/Todo%27s

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Quality Assurance]]

Extensions repository

2007-05-23T08:24:22Z

KAMiKAZOW: /* List of existing Extensions */

{{Extensions}}

This list provides Extensions that are available for deployment. Some have been tested, some not : Be careful when using them. We can not guarantee them at this level.

If you want to submit some Extensions to be relayed at end-user level through embedded tool, complete this list and send an email on the [mailto:users@extensions.openoffice.org users@extensions.openoffice.org] to inform us that something new is available. Your addon will then be reviewed and you may obtain some feedback on it.

A [[Extensions/website-todo|website is being designed]]. Will be announced when ready - any help appreciated :-)

[[Extensions_repository/Design|Design for Extensions website]]. The design elements which could be used in the extensions website.

For the moment any free licensing is accepted to be listed. [[Extensions_charter|Read the charter]] regarding conditions

If you want to translate an extension, please contact the author. A localization framework will be soon available

== List of existing Extensions ==
* [http://people.redhat.com/caolanm/PhotoAlbum PhotoaAlbumMaker]
:Localized: English - Category: Add-On - License: GPL - OOoVersion: 2.02
:Description: Create digital photo albums with OpenOffice.org Impress

* [http://sourceforge.net/project/showfiles.php?group_id=87718&package_id=200846 BorderLiner]
:Localized: English - Category: Tables - License: LGPL - OOoVersion: 2.02
:Description: An Openoffice.org macro to draw borders in Calc and Writer tables and other objects just with a couple of key strokes

* [http://sourceforge.net/project/showfiles.php?group_id=87718&package_id=105792 History Manager]
:Localized: ?? - Category: ?? - License: ?? - OOoVersion: ??
:Description:

* [http://www.danielnaber.de/languagetool/ LanguageTool]
:Localized: English, German, Polish, Dutch, Latvian - Category: Linguistic - License: LGPL - OOoVersion: 2.x
:Description: Grammar and style checker for English, German, Polish, and Dutch. Initial support for Italian, French, and Spanish. Latvian in preparation.

* [http://www.ooomacros.org/user.php#169339 Multipages]
:Localized: English, German - Category: UI tool - License: LGPL - OOoVersion: 1.1, 2.0, 2.1
:Description: An Openoffice.org macro (extension package) to copy, delete, sort, rename and create multiple document pages automatically

* [http://people.redhat.com/caolanm/oooblogger/ OOOBlogger]
:Localized: English - Category: Writer Tools - License: ?? - OOoVersion: ??
:Description :

* [http://sourceforge.net/projects/ooosvn OOoSVN]
:Localized: English - Category: ?? - License: GPL - OOoVersion: 2.0 or later
:Description: A project to provide change control for OpenOffice.org documents (OpenDocument and *.sx*) via subversion. Transparently checks in internal changes in files and allows users to recover any previous version, view logs and compare with older versions.

* [http://kohei.us/ooo/solver/ Optimization Solver] formerly known as ''LPSolver''
:Localized: English - Category: Calc Tools - License: LGPL - OOoVersion: 2.0
:Description: The Linear and Non-Linear Optimization Solver (or simply the Optimization Solver) is designed to compute an optimized solution that either maximizes or minimizes a given objective of a model while, at the same time, satisfying a set of constraints that may be defined in the model.
:In this wiki: [[Optimization Solver]]

* [http://www.ipd.uka.de/~hauma/svg-import/ SVG Import Filter]
:Localized: ?? - Category: Add-On - License: LGPL - OOoVersion: 2.0
:Description: This Add-On provides a filter to enable the importing of SVG images.

* [http://api.openoffice.org/SDK/snippets/SnippetCreator.zip Code Snippet Creator]
:Localized: ?? - Category: Development tool - License: ?? - OOoVersion: ??
:Description :

* [http://www.openoffice.org/issues/show_bug.cgi?id=26397 Multisave]
:Localized: ?? - Category: ?? - License: ?? - OOoVersion: ??
:Description: A Macro to save a document to multiple format in a few clicks

* [http://en.ooo-info.org/documentation/annotation_tool.html Annotation Tool]
:Localized: ?? - Category: ?? - License: LGPL - OOoVersion: ??
:Description: Extension of the note feature in Writer: text highlighting, quick remove of notes

* [http://www.afk-support.no/pakker/afk-it/OpenOffice2/html/ Mathtype Macros]
:Localized: English - Category: Math tool - License: GPL - OOoVersion: 2.0.x - Platform: Windows
:Description: Macros for insertion of Mathtype objects in OOo Writer on the Windows platform

* [http://quasiwiki.sourceforge.net/ QuasiWiki]
:Localized: English - Category: Wiki - License: GPL - OOoVersion: 2.0.x
:Description: QuasiWiki implements some of the basic principles of wiki in OpenOffice.org Writer. It doesn't turn OpenOffice.org into a fully fledged wiki tool (hence the "quasi" prefix), but rather adds some wiki-like capabilities.

* [http://quasiwiki.sourceforge.net/ txt2tags extension]
:Localized: English - Category: Markup - License: GPL - OOoVersion: 2.0.x
:Description: txt2tags extension allows users to apply [http://txt2tags.sourceforge.net/ txt2tags] markup to the currently opened Writer document.

* [http://sourceforge.net/projects/ooop/ OxygenOffice Professional contents for OpenOffice.org as extension]
:Localized: English, German, Hungarian, French, Italian - Category: Templates, Gallery - License: LGPL - OOoVersion: 2.x
:Description: Extension version of OxygenOffice Professional's extra contents for OpenOffice.org like templates and galleries.
:Download: [http://sourceforge.net/project/showfiles.php?group_id=170021&package_id=208656] Direct link for extension downloads
:Last update: February 14, 2007

* [http://de.openoffice.org/unbranded-source/browse/*checkout*/de/documentation/vorlagen/vorlagen_de_opendoc.oxt German template collection]
:Localized: German - Category: Templates - License: LGPL - OOoVersion: 2.1
:Description: a collection of German templates hosted by the [http://de.openoffice.org Germanophone project]

* [http://ooolilypond.sourceforge.net/ LilyPond for OpenOffice.org]
:Localized: English - Category: Music - License: ? Version: 2.1 [OOoLilyPond is a macro for OpenOffice.org that simplifies the integration of music notation in OpenOffice.org Writer of Impress. It can be used to write a book on music theory or to write down exercises for music instruments or voices which need to be commented with lots of text.]

* [http://www.ooomacros.org/user.php#216044 Pagination]
:Localized: French, English - Category: Writer Add-On - License: LGPL - OOoVersion: 2.x
: Description: A macro to simplify the commands to paginate a document. Brings up a dialog box where you can choose among some options (position, first number, etc.)

* [http://www.ooomacros.org/user.php#217442 Calendrier]
: Localized: French, English - Category: Writer Add-On - License: LGPL - OOoversion: 2.0.4
: Description: A tool to create calendar pages for one month or for one year.

* [http://writerforwriters.blogspot.com/2007/03/email-backup-extension-for.html Email Backup extension]
:Localized: English - Category: Markup - License: GPL - OOoVersion: 2.0.x
:Description: Using the Email Backup extension, you can quickly email a backup copy of the currently opened OpenOffice.org document to a specified email address.

== Others Extensions Lists ==
* [http://linguistico.sf.net/wiki/doku.php?id=ext:estensioni Extensions on linguistico wiki] (in Italian language)

[[Category:Extensions]]

Documentation/Building Guide/Building on MacOSX

2007-04-15T20:20:53Z

KAMiKAZOW: Removed plenks http://en.wikipedia.org/wiki/Plenk

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

An important goal is to get the demonstration programs "svdem" up and running. They act as a fairly good starting point to further endeavours, since they are used to test the capabilities of the underlying [[VCL]] layer. If this is achieved, one can build and Install the full-fledged OpenOffice.org Package. The purpose of this document is to describe the cumbersome build process of OpenOffice.org rather than to give a kickstart in the coding involved to get VCL ported to Carbon. A starting point for this is Pierre de Filippis excellent [[Intro To Mac Porting]].

I use the bash shell in all examples, since to my belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html Open OfficeBuild Environment].

Many thanks for help and assistance go to Pavel Janik and Eric Bachard.

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]]. Here I like to outline the things you need to build the Aqua Version (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory '''</div>===

==== Xcode ====

This is (with GNU cp, soon optional) the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is XCode 2.4.1

If you really cannot use XCode 2.4.1 nor XCode 2.4:

Xcode 2.2, 2.3 are known to work for Aqua development. If any earlier versions work as well, please add them here.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xllib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

<pre>This issue should be fixed soon.</pre>

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build several times OpenOffice, you probably can benefit of ccache. ccache will speed up your future builds. The first time you make a build with ccache you won't notice it, but then the build will go up to five times faster.

You can install it using fink. It is simply named "ccache".

If you don't use fink, you can download it and build it yourself using the source provided at http://ccache.samba.org/

Then, in order to use it, you need to change the following environment variables (using bash):

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

=== Optional ===

Means you can safely ignore them.

==== Java ====

Excepted if you really know what you are doing, a correct Java version including SDK is normally installed with XCode.

==== The perl module Archive::Zip (optional) ====

Nothing is needed anymore with recent versions of XCode (means: not needed with XCode 2.4 at least).

If you still have issues doing configure because of that, please install Archive::Zip repecting the instructions below:

<code>[bash,N]
perl -MCPAN -eshell
install Archive::Zip
</code>

==== gpc (optional) ====
GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>
Attention: Direct Link to the download but it's only a few hundred KB.
Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

==== pkg-config (optional) ====

Nothing to install on Aqua build, since --disable-gtk is forced

Called ''pkgconfig'' in Fink.

pkg-config can be found here: http://pkgconfig.freedesktop.org/wiki/

== '''Some Background (what is aquavcl01, EIS)''' ==

=== EIS ===
OpenOffice sources are basically kept in the CVS server located at anoncvs.services.openoffice.org. However this repository is managed by a database on top called EIS (Environment Information System) which is used to keep track of Master- and Client Workspaces. Master Workspaces are used to keep track of changes going back of the mainline trunk and undergo extensive QA-cycles. These Master Workspaces are driven to official releases. Child workspaces in contrast are copies of certain Master Workspaces used to develop and test bugfixes and additional functionality. These Child Workspaces are later (hopefully) merged back to mainlain Master Workspaces. The TX20 Report mentioned in the Links section gives a very good overview about the overall process. To learn more about Childworkspaces (CWS) have a look here: [[CWS]].

Go to EIS http://eis.services.openoffice.org/EIS2/servlet/Logon and Logon as guest/guest to get yourself an impression. You can find information about the different workspaces, their dates and times there.

=== VCL (Visual Class Libraries) ===

Porting OpenOffice.org to a new Windowing Toolkit is mostly porting of the OpenOffice's VCL Layer (Visual Class Libraries) to the new platforms toolkit. The VCL-Layer is responsible of mapping the OpenOffice Application calls to the windowing toolkit.

The (native) OpenOffice port to MacOSX using the Aqua Windowing Toolkit is developed in a child workspace called '''aquavcl01'''. This child workspace consists of the modules (aka subdirs): canvas dtrans extensions freetype padmin scp2 sj2 solenv vcl.

The basic approach to prepare a developer's client system to successfully build OpenOffice/Aqua is the following:

# checkout a given OpenOffice Milestone.
# checkout aquavcl01 Child Workspace.
# merge them together.
# apply the latest patches.

The last point here is a cumbersome but nevertheless necessary operation, since this porting project is in flux. Thanks to Pavel and many others improvements are happening at tremendous pace at the moment. All of these improvements get distributed as patches/diffs against aquavcl01. Aquavcl01 needs to remain stable all the time, therefore the team needs to work on this patch-by-patch aproach at the moment.

== '''Getting the code (checkout, merge and patch the puppy)''' ==

Now let's have a look what to check-out and where. All these milestone numbers below highly depend on the given point-in-time. The current milestone as of now (April 11th 2007) is m208. You may change this to your needs. You can find the current milestone of each cws in the EIS database.

You also need to bear in mind that you have to access to the CVS-Server's default port (2401). If a firewall stop's you here you have to setup a CVS-Tunnel.

==== create a directory for a given milestone, setup CVS access: ====
<code>[bash,N]
mkdir src680-m208
cd src680-m208

export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
cvs login
</code>
Please Enter the password 'anoncvs'

==== checkout Milestone m208 (1,5 GB): ====
<code>[bash,N]
cvs -z3 co -r SRC680_m208 OpenOffice2
</code>
Once done, you'll obtain milestone 208. this not exactly what we want, because all changes concerning aquavcl01 Child workspace are not included. To complete, we need to check aquavcl01 changes.

==== checkout Aquavcl01 (50 MB): ====

1) First possibility: create a dedicated tree (cool backup)

To check aquavcl01 Child workspace, the most simple is to create aquavcl01 directory, and go inside this dir
<code>[bash,N]
mkdir aquavcl01-src

cd aquavcl01-src
</code>
(assuming you already did cvs login ..etc)
<code>[bash,N]
cvs -z3 co -r cws_src680_aquavcl01 OpenOffice2
</code>
The following modules will be present at the end:
<div style="background-color: lightyellow; border: 1px red dashed; padding: 3px 0 3px 15px;">
canvas

extensions

fpicker

padmin

sal

scp2

sfx2

solenv

dtrans

freetype

psprint

sj2

vcl

toolkit
</div>

All these modules are the ones we modified to create the native version: they all are tagged "aquavcl01" (see all CVS/Tag files in the tree) and all you have to do is either rename or delete the one located in src680-m202 and replace them with the one located in aquavcl01-src.

e.g. : canvas in src680-m208 will become canvas_m208 , and then, cp canvas from aquavcl01-src into src-m208

This applies for all the modules listed above.

2) Second possibility: use a little script to extract changes: extract_aquavcl01.sh

This shell script, located in src680-m208 will contain:
<code>[bash,N]
#!/bin/bash
list="canvas extensions fpicker padmin scp2 sfx2 solenv dtrans freetype psprint sj2 vcl sal toolkit"
for i in $list ; do
mv $i $i-m208
cvs -z3 co -r cws_src680_aquavcl01 $i
done
</code>

Then chmod +x extract_aquavcl01.sh

and run it:

./extract_aquavcl01.sh

When finished, and if no problem occurs, you should have a complete tree.

=== One-Time preparations and scripts ===

OpenOffice building gets configured by the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
src680-m182/
src680-m196/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd src680-m208/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' looks like:

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version: $OOVERSION
./configure \
--with-lang="de en-US" \
--with-jdk-home=/Library/Java/Home/ \
--with-epm=internal \
--disable-mozab \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--disable-neon \
--without-nas
</code>

--disable-odk will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf: pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas: nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

This is allowedly a pretty much limited setup, but my overall goal is to get people to have 'svdem' build to start coding rather than to have a production ready build for the final release. Therefore I switched off most of the stuff. How these offical builds are done in the long run is to be decided when we get there.

== '''List of Patches for a given Milestone''' ==

Here is a list of Patches one has to apply against a given Milestone of SRC680 (including CWS aquavcl01). Please keep the older Milestones here, since people are probably still on these Versions.

PLEASE NOTE: '''Current milestone for Aqua build is m208''' (older milestones are deprecated)

{| border="1" cellpadding="5" cellspacing="0"
|-
! Milestone || Patch to apply || Status
|-
| '''deprecated m202''' || '''Modify the Bundle using Oliver's patch''' => see below || Works fine
|-
| '''deprecated m202''' || see [[List of Patches requiring testing before for integration]] || work in progress
|-
|}

== '''List of Patches requiring testing before for integration''' ==

All patches that developers have that need testing or peer review should be added here.

==='''Modify the Bundle'''===

'''Soon included in the sources'''

[[http://www.openoffice.org/nonav/issues/showattachment.cgi/44379/aquabundle3.diff Oliver patch ]]to modify the bundle, and make Aqua build start with a simple double clic

salatslayout.cxx: new implementation of text layout has to be tested.

==='''Native FilePicker''' ===

'''Note: This is experimental stuff, and we suppose aquavcl01 is built and aqua bundle works (X11 backport in progress)'''

1) Download [http://eric.bachard.free.fr/mac/aquavcl/patches/filepicker/23_02_07/aquafilepicker01_complete2.diff this patch]

2) put it in your root sources dir

3) apply it:

test first:
<pre>
patch --dry-run -p0<aquafilepicker01_complete2.diff
</pre>
If no problem occurs, apply it for true:
<pre>
patch -p0<aquafilepicker01_complete2.diff
</pre>

4) replace fpicker from aquavcl01 with fpicker from aqufilepicker01
<pre>
mv fpicker fpicker_aquavcl01
</pre>
(supposing your CVSROOT ..etc is correct)
<pre>
cvs -z4 co -r cws_src680_aquafilepicker01 fpicker
</pre>

5) in scp2, sfx2, fpicker: '''remove''' unxmacx{p | i}.pro , '''rebuild''' and '''deliver'''

6) recreate a new bundle (build instsetoo_native , install the .dmg, run Paval fix_installed_OOO script ..)

7) activate native fpicker:

'''WARNING''': don't use Mac tools for that, but '''correct''' text editor. Else the following changes will FAIL, and corrupt your OpenOffice.org preferences

-> add or '''adjust''' this, keeping in mind '''only one Misc section can be used''' (but several properties are possible in Misc):

<node oor:name="Misc">
<prop oor:name="UseSystemFileDialog" oor:type="xs:boolean">
<value>true</value>
</prop>
</node>
in ~/Library/Application Support/OpenOffice.org/2/user/registry/data/org/openoffice/Office/Common.xcu

If unsure, make a backup of your file and use this: [http://eric.bachard.free.fr/mac/aquavcl/patches/filepicker/23_02_07/Common.xcu Common.xcu]

8) enjoy:)

== '''Known build issues''' ==

'''(deprecated) m200''': Breakage in instsetoo_native

See [http://eric.bachard.free.fr/mac/aquavcl/patches/m200_aquavcl01/instsetoo_native_util_makefile.mk.diff Fix for instsetoo_native breakage]

how apply the patch ?

Place it in <install_dir>/instsetoo_native/util

type:

patch -p0<instsetoo_native_util_makefile.mk.diff

m196: Breakage in pyuno

See [http://www.openoffice.org/issues/show_bug.cgi?id=72372 pyuno not found]

'''Workaround''':

<pre>
1) either use the patch provided in issue 72372

2) or simply do (in the same terminal, or please source the environment before):

cd bridges
build && deliver
cd ../pyuno
build && deliver

-> pyuno should build without any problem

cd .. && dmake

will complete your build

</pre>
[[User:Ericb|Ericb]] 21:43, 11 April 2007 (CEST)

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd src680-m202/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

On PowerPC:

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
time dmake

Or (on Mac Intel):

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
time dmake

The main purpose of the '''boostrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set' should be substituted with 'MacOSXX86Env.Set'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours. Be patient. What can you do meanwhile? Do this:
<code>[bash,N]
while true ; do find . -maxdepth 1 -type d -anewer MacOSXPPCEnv.Set.sh |wc -l ; sleep 5; done
</code>
and wait till the number reaches 174

== '''Creating Debug-Versions of Modules''' ==

<pre> Important: a new section about use XCode for OpenOffice.org debug has been created.
See:</pre>

[[MacOSX_Debug_OpenOffice.org_using_XCode]]

'''Is it possible to build the complete set with symbols included ?'''

Currently not possible, and not advised.

''' is it possible to build some modules with symbols ?'''

Yes, and that's the simplest way to proceed. Some modules, like sal and vcl can be rebuilt using debug.

Example:

To rebuild sal with symbols included, do:

<code>[bash,N]
cd sal
rm -rf unxmacxp.pro
build debug=true
</code>

and recopy the libs into the bundle. gdb will display the symbols, and make your life easier.

Note: debug string is tested, and DEBUG is active when debug string is not empty. So debug=t works too.

''' How change gdb options, and use e.g. -g -ggdb or -gdwarf-2 ?'''

To rebuild the module, you just have to modify the option in solenv/inc/unxmacx.mk, replacing -g with -ggdb

'''Known issues'''

Sometimes a build error, or a runtime error, may be seen in the normal build,
but the error goes away when --enable-debug is used or if the module is compiled with debug=true.

The DEBUG build turns off optimisation, so this is a hint that compiler optimisation causes the error.

The error might be due to incorrect code or a compiler fault. Such errors might not be seen on all platforms,

and might not be seen in different compiler versions on one platform.

If the code can not be fixed there is a workaround using NOOPTFILES to build specified files with no optimisation.

Example:

jvmfwk on Mac OS X: build jvmfwk in m183 on Mac OS X Intel leads to Bus Error when javaldx is run.

Solution: use trial and error to rebuild individual files with debug=true. This proves the problem lies with vendorbase.cxx

Have a look in sc/source/core/data/makefile.mk for an example to use NOOPTFILES

To solve our problem: just add: NOOPTFILES= $(SLO)$/vendorbase.obj in the corresponding makefile.

Take care in case some .IF is needed to prevent interference with other platforms.

There's some additional information around debugging on Christians Page [[User:CL#2006-09-03]]

== Building and running svdem ==

We want to run the demonstration programs called "svdem". There are a couple of binaries called "svdem", which area they cover is still somewhat unclear to me, I hope some of you guys can shed some light here. But hey, this is a wiki! Just correct here:-).

==== svdem from VCL ====
To have the VCL Testprogram build you have to do:

'''[FIXME] replace this scetion with the same, but about svdem from svtools'''

cd vcl; build --all

This should have created a file called "svdem" here: vcl/unxmacxp.pro/bin/svdem. If you managed to build these binaries, you are nearly there. What you need now, is a wrapper directory structure to make this binary a fellow Mac OSX application. I mean the ones which have this structure:

svdem.app/
svdem.app/Contents
svdem.app/Contents/Info.plist
svdem.app/Contents/MacOS
svdem.app/Contents/MacOS/applicat.rdb
svdem.app/Contents/MacOS/svdem

You can basically create this structure anywhere you want. And you can link-in the file you just created (svdem). So you build up this structure once and link-in the freshly created svdem there:

ls -l svdem applicat.rdb
svdem -> /opt/src/openoffice/src680-m202/vcl/unxmacxp.pro/bin/svdem
applicat.rdb -> /opt/src/openoffice/src680-m202/vcl/unxmacxp.pro/bin/applicat.rdb

Now only the Info.plist file is missing, so here we go:

<code>[xml,N]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleDisplayName</key>
<string>SvDem</string>
<key>CFBundleExecutable</key>
<string>svdem</string>
<key>CFBundleIdentifier</key>
<string>com.yourcompany.svdem</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>1.0</string>
<key>LSRequiresCarbon</key>
<true/>
</dict>
</plist>
</code>

If you created the directory structure properly you can do './svdem' in the 'svdem.app/Contents/MacOS/' directory. You should see the svdem coming up.

==== svdem from svtools ====
* Copy the application package you created for the vcl svdem.
* Source your MacOSX[PPC-X86]Env.Set.sh
* Go into svtools/workben
* build svdem using dmake in the workben directory
* link the svdem and applicat.rdb from Contents/MacOS to the ones located in svtools/unxmacxp.pro/bin

You are done: you can now source your environment and run svdem using your usual shell.

== '''Installing, preparing and running OpenOffice.org''' ==

Here I like to outline the steps to run OpenOffice.org after a successful build from the sources. Running the native Aqua Version of OpenOffice.org is somewhat tricky at the moment, since the installation procedure and mode are not in their final state. So right now one has to manually do some preparations to run the Office suite. This will change in the future when we are about to release some Alpha Builds to a wider audience.

=== Drag & Drop Install the Application from the Diskimage ===

When you are one of the lucky few (Don't give up, Eric!), who have a successful build, you are going to see something like this as the last lines of the build:

.
.
.
......................................................................................................................................................
(CRC32 $11685D33: DiscRecording 3.1.3f2 (Apple_HFS: 2))
Ressourcen hinzufügen…
......................................................................................................................................................
Dauer: 15.406s
Dateigröße: 144732418 Bytes, Prüfsumme: CRC32 $14E0BB67
Bearbeitete Sektoren: 773848, 773845 komprimiert
Geschwindigkeit: 24.5M Bytes/Sek
Ersparnis: 63.5 %
created: /opt/src/openoffice/src680-m202/instsetoo_native/unxmacxp.pro/OpenOffice/install/de/OpenOffice.org-2.2_de.dmg

In this final step the ""instsetoo_native"" target creates the install Diskimages using Apple's 'hdiutil'. In my case it gives its output in German. After this disk image(s) have been created, double click the disk image to mount it (or type open <path to the DMG Image>) , and then move the icon named "OpenOffice.org 2.2" to your ''Applications'' folder (or any other folder you want this program to reside). The "OpenOffice.org 2.1" icon shown in the Finder is in fact a subdirectory called "OpenOffice.org 2.2.app". Subdirectories named ".app" (along with some well-know files inside like Info.plist, etc) are called ''Bundles'' in Apple's lingo.

=== Prepare the installation [OPTIONAL]===

'''Use Oliver's patch at buildtime instead (see above) '''

After the OpenOffice 2.2 Application has been copied to its destination, you have to go into this bundle and run a small shell script provided by Pavel Janik to prepare soffice.bin (OpenOffice.org launcher) for running. You have to run this script in the directory where a Universal Binary called "droplet" is located. This "droplet" binary was used to fire-off the X11 version of OpenOffice.org. Expect this to change, but as of now we have to do it like this.

I have put my OpenOffice.org build in my home directory's private "Application" folder (/Users/schmidtm/Applications), so please change this path to your installation. Now go to into the bundle and run the script:

cd /Users/schmidtm/Applications/OpenOffice.org 2.2.app/Contents/MacOS
/opt/src/openoffice/bin/fix_installed_OOo

<code>[bash,N]
#!/bin/bash

[ ! -f droplet ] && {
echo "Please run me in the directory, where binary named droplet is located."
exit 0
}

mv THIRDPARTYLICENSEREADME.html help presets share ..
mv droplet droplet.orig
mv program/* .
rmdir program

cd ..
ln -sf MacOS program
sed 's#droplet#soffice.bin#' Info.plist >Info.plist.new
mv Info.plist.new Info.plist
cd MacOS
</code>

=== Run the soffice.bin ===

We're nearly through, let's fire-off the binary:

==== Native menus, native menubar ====

If you applied Oliver's patch, just double click the Bundle and enjoy.

If you want to trace (using gdb e.g.), just do:

cd <INSTALL_DIR>/OpenOffice.org\ 2.2.app/Contents/program

and run:

./soffice.bin

Note: see below for other possible options

==== Use vcl menubar and / or vcl menus ====

<pre>
Native menus are defaults. If you want to use vcl menus, do:

AQUA_NATIVE_MENUS=FALSE ./soffice.bin
</pre>

Note: options to not recover is -norestore , and to bypass the user informations to fill in, use -nofirststartwizard

AQUA_NATIVE_MENUS=FALSE ./soffice.bin -nofirststartwizard -norestore

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="15" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=FALSE || disable native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

== External links ==

# Bug Database: http://www.openoffice.org/issues/query.cgi
# Mailinglist: mac@porting.openoffice.org
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== Screenshots ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Native Menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_native_controls_03_11_06/aqua_menus_01.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]

Summer of Code 2007

2007-03-16T00:32:30Z

KAMiKAZOW: /* Word macro compatibility */

Similarly to the [[SummerOfCode2006|last year]], OpenOffice.org would like to participate in the [http://code.google.com/soc/ Google Summer of Code](tm) initiative sponsored by Google.

This page is here to collect the suitable suggestions. So - if you have a task that is challenging enough, and are willing to mentor the task, feel free to add it below. Each entry should contain the task description, required skills, proejct mailing list for discussion and personal contact. Links to the [[To-Dos]] are appreciated provided that the task is well described there ;-)

We would be glad to support a few projects. Mentoring capacities are limited, so we depend on your dedication during the preparation of the detailed specification and description of the outcome.

For further general questions about the initiative Google prepared a [http://code.google.com/support/bin/topic.py?topic=10442 FAQ].

=The Task Proposals=

===Example entry===

This is just an example - the real entry must not start with a space at the beginning
of the line.
A full description of the task should be here; one that will help to see that this task
is important, and interesting to hack on. Alternatively it could be an exact link to
the description that is already in [[To-Dos]].

* Required skills/knowledge: Language, technology1, technology2, ...

; Contact
: dev@project.openoffice.org
: The.Mentor at organization com

==API==

===UNO specifications changes in Eclipse Integration===

This project aims at improving the way to develop OpenOffice.org extensions and UNO components using Eclipse. This project should help the developer to changes its specifications easily. This project could be parted into several smaller parts.

See [[EclipseIntegration_ToDo#IDL_files_modification_assistance | the Todo task description]] for further informations.

* Required skills/knowledge: Java, Grammar & Compilers
* Usefull skills: Eclipse API, JavaCC, UNO & UNO IDL

; Contact
: dev@api.openoffice.org
: CedricBosdo at openoffice.org

== Base ==

=== Joins in dBase Queries ===

Queries to dBase files can currently contain one table only. Scope of the project is to enhance Base' built-in simple query engine to be capable of executing statements line <code>SELECT table1.field1, table2.field2 FROM table1, table2</code>. The dBase driver, the text/csv driver, and the Spreadsheet driver would all benefit from this extension.

Be prepared to dig around here before starting the project, the project touches low-level core implementations, including some heavy-to-read STL stuff, so be prepared to invest some time before writing the first line of code.

* required skills C++, SQL knowledge
* useful skills: Lexx and Yacc
* Contact: mailto:dev@dba.openoffice.org
* Mentor: Ocke Janssen - Ocke.Janssen at Sun.Com

=== Dialogs with Form Functionality ===

When creating a form, the user always needs to bother with a Writer document. Very often, this is much too oversized. It would be sufficient to have a simple dialog which contains all the data access controls.

The advantage would be to not slay the user with things she does not bother – a writer document offers a lot of possibilities which are not relevant for a form. In some cases, a full writer document does even contradict to what users expect from a form – one thing to mention here is that documents are always freely sizable, which is nothing you expect from a carefully designed form, where controls are placed at concrete positions and have a fixed size.

The project is to
- extend the dialog runtime engine to (optionally) include data-aware form controls
- create a form designer for dialog-based forms (similar to the existing Basic Dialog IDE)
- implement persistence of dialog-based forms
- embed dialog-based forms into database documents (.odb)

Depending on more fine-grained planning, it might become apparent that not all of this can be done in the scope of a Google Summer of Code project, and reasonable milestones need to be defined.

* required skills C++, UNO
* useful skills: familiarity with OOo's database access and form API, as well as OOo's [http://api.openoffice.org/docs/common/ref/com/sun/star/awt/module-ix.html toolkit API]
* Contact: mailto:dev@dba.openoffice.org
* Mentor: Frank Schönheit - Frank.Schoenheit at Sun.Com

=== Embed Derby into OpenOffice.org Databases ===

OpenOffice.org Base features an abstract mechanism to embed database backend files into OOo databases (.odb). Currently, this is implemented for [http:///hsqldb.org HSQLDB], which is used as OOo's default database engine.

To allow this feature for other engines, one must:

* virtualize the engine's file access, so that it re-routes all its file operations through an abstract API.
* implement this API on the OOo Base side

The project is to do those implementations for [http://db.apache.org/derby Apache Derby database].

* required skills Java, C++
* useful skills: OOo's database access API, OOo's component technology (UNO)
* Contact: mailto:dev@dba.openoffice.org
* Mentor: Ocke Janssen - Ocke.Janssen at Sun.Com

==Calc==

===Integration of R into Calc===

Create an add-on component that allows a Calc user to let the [http://www.r-project.org/ R environment] do calculations on data from Calc cells and put the results into the spreadsheet again.

This should include a dialog to select input parameters and options, and allow results to be values or graph images. Note that the incompatible licenses (R is under GPL) have to be taken care of, possibly by starting R as a separate process.

Some more thoughts on the subject have been collected at [[Statistical Data Analysis Tool#Third Party Library Integration]].

* Required skills/knowledge: Some familiarity with statistical methods

; Contact
: dev@sc.openoffice.org
: Niklas.Nebel at sun.com

: Leonard Mada
: (on statistics and R syntax)
: discoleo at openoffice.org

===Watch Window===

A Watch Window is a separate, small window that remains "on top" and enables users to monitor a selected set of cells, see [http://www.openoffice.org/issues/show_bug.cgi?id=28386 issue 28386].

This could be implemented as an add-on component with a modeless dialog containing the list of watched cells as well as the UI to add or remove cells.

* Required skills/knowledge: Java or C++

; Contact
: dev@sc.openoffice.org
: Niklas.Nebel at sun.com

===Unit Testing Framework for Optimization Solver===

The [[Optimization Solver]] component needs a unit-testing framework for its linear optimizer. This task would involve collecting a load of test cases (small and large) with known solutions, and write an automated unit-testing program for the linear portion of the optimizer code.

* Required skills/knowledge: C++

; Contact
: kyoshida at novell dot com
: jody at novell dot com

===Additional AutoFilter Functionality===

Add core and user interface support for additional forms of filtering
* Date based filters (eg current year/quarter)
* Multiple items without falling back on logical OR.
* Statistical filters (eg within N stddev of mean)

* Required skills/knowledge: C++, Familiarity with OOo frameworks.

; Contact
: jody at novell dot com

===Move Older Spreadsheet formats into an UNO Component===

Support for several formats still lives in the core calc module, and bloat it with little used functionality.
Moving the antiquated filters into a distinct component would be good introduction to UNO and the spreadsheet code.
If time permits the new component could have support for other simple spreadsheet formats, such as Applix.

* Required skills/knowledge: C++, Familiarity with OOo frameworks.

; Contact
: jody at novell dot com

==Extensions==

===OOo connector for External IDE for OOo scripting languages===

This project will solve the problem of lack of IDE for scripting languages in OOo. Scripts can be seen as macros in various languages and are complementary to Extensions.
Actually, only OOoBasic has its IDE embedded in OOo. Javascript and Beanshell have limited ones and python nothing. To avoid implementing different IDE for various languages into OOo, the proposed choice is to provide a connector to any external IDE

The project is dived into 2 complementary parts :
* defining and implementing common tools at OOo side to put the scipts at the correct place and manage OOo scripts menus
* implement an Eclipse extension as an IDE that could handle scripts in python language, using the previously defined OOo tools.

; Requirements
* Required skills/knowledge: java, python, UNO
* Usefull skills: Eclipse API, OOo API, IDE general knowledge

; Contact
: dev@extensions.openoffice.org
: LaurentGodard@openoffice.org

==Framework==

===Shell Extensions for Desktop file search and showing meta data in windows explorer needs to be rewritten for Vista===

Vista changed his mechanism to integrate those shell extensions incompatible. Extensions valid for Win98/2000/XP doesnt work any more. A set of new interfaces was designed. But they are available on Vista only. So OOo has to support two sets of shell extensions: one set for Win98/2000/XP and a new set for Vista and might following windows versions. For this project the new Vista extensions has to be implemented only.
See [https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i71112 71112] and [https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i70944 70944] for further informations.

* Required skills/knowledge: C++
* Useful skills: Windows API knowledge
* Requirements: Windows Vista 32 Bit

; Contact
: dev@framework.openoffice.org, Andreas.Schluens at sun.com

===Status bar control to display/change the language===

Currently the Writer lacks means to display the language in use. There's also no easy way to change the language as the user has to use the menu. A status bar control would help to solve these problems. It should help to determine about the language used at the cursor position or the document. The control should be implemented using existing UNO APIs.

* Required skills/knowledge: C++
* Useful skills: Basic UNO API knowledge

; Contact
: dev@framework.openoffice.org, Carsten.Driesner at sun.com
: dev@sw.openoffice.org, Thomas.Lange at sun.com

===Improving UI editing / coupling===

Currently all dialogs (along with most translated strings) are stored in a rather unusual binary resource file format, that has not had much love in the last decade. We need to write some new code that separates the process of designing & laying out the UI from the code - to allow UE to make our UI more beautiful, and allow future re-factoring. The existing Basic GUI dialog editor and it's XML format should be re-used, a simple C++ compatibility API created, and a number of dialogs converted to the new format.

* Required skills/knowledge: C++
* Useful skills: courage, stickability, X-rated code reading

; Contact
: michael.meeks at novell.com
: hfiguiere at novell.com

==Graphics==

===Draw/Impress: SVG Import Filter===

[http://www.w3.org/Graphics/SVG/ SVG (Scalable Vector Graphics)] is a vector graphics format that describes 2D graphics in XML.

There's no native SVG import filter for OOo. There exists an [http://www.ipd.uka.de/~hauma/svg-import/ external one], but unfortunately it has very strong dependencies - [http://java.sun.com/javase/downloads/index.jsp Java 5.0], and [http://xmlgraphics.apache.org/batik/ Batik]. The goal of this task is to create a new implementation that does not require any too big libraries.

A proof of concept implementation written in C++ using the UNO Draw API, and a lighweight [http://cairographics.org/libsvg libsvg library] exists (see [http://svn.gnome.org/viewcvs/ooo-build/trunk/patches/src680/svg-import.diff here]), but it needs a lot of work to be really usable. Another problem is that libsvg does not seem to be too actively maintained; so ideally the implementation should use OOo's internal XML parser.

More information is available in [http://artax.karlin.mff.cuni.cz/~kendy/blog/archives/monthly/2006-10.html#2006-10-02T17_14_44.htm Kendy's blog].

* Required skills/knowledge: C++, XML knowledge is a plus

; Contact
: Jan Holesovsky - kendy at openoffice org
: Fridrich Strba - fridrich_strba at openoffice org

===Impress: OpenGL rendered transitions===
The goal is to add 3D transitions to the Impress application. Transition is an animation where one page is visible in the beginning and another in the end. It is used during presentation slideshow to switch pages.

In the process of implementing OpenGL transitions an UNO API should be added to slideshow code, so that OpenGL transitions engine might be created as standalone UNO component. Current transitions should be refactored to another UNO component.

The engine will get the previous and next pages and should render the transition at given speed.

The participant should also implement at least 5 OpenGL transitions, rendered by the UNO component.

* Reguired skills/knowledge: C++, OpenGL. familiarity with UNO is welcomed

;Contact:
:Radek Doulik - radekdoulik at openoffice org

==ODF Toolkit==

=== Tools and best practice samples for ODF creation and manipulation===

We already have some code snippets in Java and C# and looking for help to extend these tool sets or to provide tool sets in other languages. These tool sets are designed to offer basic ODF functionality even outside of OO.o.

* Required skills/knowledge: Java or C# or Perl or C++ ...
* Useful skills: ODF, XML

; Contact
: dev@odftoolkit.openoffice.org,
: Dieter Loeschky at sun.com

== Porting: Mac OS X native port ==

=== '''Complete User Interface respecting Aqua Human Interface Guidelines (Aqua Only)''' ===

*Concerns: OpenOffice.org 2.x for Mac OS X Aqua only

*Skills: Knowledge of languages C/C++ Mac OS X APIs and Application frameworks like Carbon

Original OpenOffice.org vcl widgets are not Aqua HIG compliant, and we need to implement all controls, respecting Aqua Human Interface Guidelines, some will use HIView, or HITheme or even other part of Carbon API.

*Tasks: some controls are already implemented, but some are still missing.

The job consists in write the code and implement:

- tabs (implement and bind the TabitemValue class, using Carbon API)

- spinbuttons (implement and bind SpinbuttonValue class, using Carbon API)

- comboboxes (implement and use HICombobox)

- listboxes (work already started)

- texts in comboboxes / listboxes (better task definition to be completed)

- other types of controls: highlight, respect dimensions/spacing ..etc

- Windows background (using Aqua theme)

;Proposed by: Eric Bachard
;Contact: mac@porting.openoffice.org
;ericb at openoffice dot org

=== Mac OS X native printing (Aqua only) ===

Concerns: OpenOffice.org 2.x for Mac OS X Aqua only

Objective: currently, the native printing implementation is missing on Aqua port and needs to be implemented.

The objective is to use the same box users have in any Mac application.

Skills: Knowledge of languages C/C++ Mac OS X APIs and Application frameworks like Carbon and /or Cocoa

Tasks:

Familiarize with the Mac OS X printing APIs

Familiarize with the current OOo printing API

Expected: Write code to Implement native printing with Aqua version of OpenOffice.org:

; Contact
: mac@porting.openoffice.org
: fheckl at openoffice dot org

;Proposed by: Florian Heckl

;Mentor: Florian Heckl

=== Mac OS X Address book integration (Aqua / X11) ===

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 APIs

Familiarize with the current OOo Mozilla address book integration

Make a prototype for OOo Mac OS X address book integration

;Contact
mac@porting.openoffice.org

;Mentor: Florian Heckl

==VBA==

===Word macro compatibility===

Recently Sun and Novell announced to pool resources to provide VBA macro compatability see [http://blogs.sun.com/GullFOSS/entry/sun_and_novell_work_together here].

Currently work in the project is concentrated on providing Excel support by
* providing the framework for the compatibiltiy api via a plugable component
* modifying the basic engine to support more compatibility features
* porting the [http://wiki.services.openoffice.org/wiki/Helperapi helperapi] code (for excel) to c++ (see. [http://wiki.services.openoffice.org/wiki/VBA here] & [http://wiki.services.openoffice.org/wiki/Porting_notes here])

Tasks

* extend the base framework by developing helper objects and implementations to be used by both the excel and writer compatibility object implementations
* port the existing (word) helper api objects from Java to C++

Required skills/knowledge

* C++
* Java
useful skills:

* knowledge of OOo's writer access API
* knowledge of OOo's component technology (UNO)
* experience with VBA macros and Word VBA api

Mentor/Contact
* noel.power at novell dot com

== Writer ==

===Writer: Better "Notes" functionality===

The "Notes" functionality in Writer could be better in terms of usability and does not look very appealing.

* Required skills/knowledge: C++

; Contact
: dev@sw.openoffice.org
: Mathias.Bauer at sun.com

; Resources
[http://blogs.linux.ie/caolan/2007/03/12/notesmarginnotes-in-sw/ hopefully helpful illustrative patch]

===MS Works Import Filter===

Unlike its proprietary derivatives, OpenOffice.org lacks MS Works import filter. The creation of MS Works import filter is one of functionalities requested by our users. There is a basic import filter work started and the result is to be found in CWS wpsimport01. This filter, based on recently started libwps[http://libwps.sourceforge.net] library is offering only limited number of features converted. It is desirable to build on this work and improve this library/filter so that the quality meets industry standards.

* Required skills/knowledge: C++, solid knowledge of MS Works wordprocessing document file-format and of libwps library.

; Contact
: fridrich_strba at openoffice.org
: freuter at novell.com

===RTF Generator===

The current RTF export of OpenOffice.org is not as good as the export to the Word (.doc) format. Parsing the generated Word format stream with a Word tokenizer and handing over the generated events to an RTF generator would lead to an RTF export filter with the same quality as the binary Word export filter. Remark: the tokenizer itself isn't complete today but in its current state covers enough parts of the Word format to make this a valuable project for the planned time span.

* Required skills/knowledge: C++, some knowledge about the Word file format would be a plus

; Contact
: dev@sw.openoffice.org
: Henning.Brinkmann at sun.com

=== Logging framework ===

During the import/export process from alien file formats there might be some features which can not be mapped entirely.
The goal of this project is to provide a loggin framework for the new domainmapper of the writer filter project, which
allow the domainmapper to notify the user of such mapping problems.

* Required skills/knowledge: C++

; Contact
: Florian Reuter (freuter at novell.com)
: Fridrich Strba (fridrich_strba at openoffice org)

Summer of Code 2007

2007-03-16T00:31:25Z

KAMiKAZOW: /* Porting : Mac OS X native port */

Similarly to the [[SummerOfCode2006|last year]], OpenOffice.org would like to participate in the [http://code.google.com/soc/ Google Summer of Code](tm) initiative sponsored by Google.

This page is here to collect the suitable suggestions. So - if you have a task that is challenging enough, and are willing to mentor the task, feel free to add it below. Each entry should contain the task description, required skills, proejct mailing list for discussion and personal contact. Links to the [[To-Dos]] are appreciated provided that the task is well described there ;-)

We would be glad to support a few projects. Mentoring capacities are limited, so we depend on your dedication during the preparation of the detailed specification and description of the outcome.

For further general questions about the initiative Google prepared a [http://code.google.com/support/bin/topic.py?topic=10442 FAQ].

=The Task Proposals=

===Example entry===

This is just an example - the real entry must not start with a space at the beginning
of the line.
A full description of the task should be here; one that will help to see that this task
is important, and interesting to hack on. Alternatively it could be an exact link to
the description that is already in [[To-Dos]].

* Required skills/knowledge: Language, technology1, technology2, ...

; Contact
: dev@project.openoffice.org
: The.Mentor at organization com

==API==

===UNO specifications changes in Eclipse Integration===

This project aims at improving the way to develop OpenOffice.org extensions and UNO components using Eclipse. This project should help the developer to changes its specifications easily. This project could be parted into several smaller parts.

See [[EclipseIntegration_ToDo#IDL_files_modification_assistance | the Todo task description]] for further informations.

* Required skills/knowledge: Java, Grammar & Compilers
* Usefull skills: Eclipse API, JavaCC, UNO & UNO IDL

; Contact
: dev@api.openoffice.org
: CedricBosdo at openoffice.org

== Base ==

=== Joins in dBase Queries ===

Queries to dBase files can currently contain one table only. Scope of the project is to enhance Base' built-in simple query engine to be capable of executing statements line <code>SELECT table1.field1, table2.field2 FROM table1, table2</code>. The dBase driver, the text/csv driver, and the Spreadsheet driver would all benefit from this extension.

Be prepared to dig around here before starting the project, the project touches low-level core implementations, including some heavy-to-read STL stuff, so be prepared to invest some time before writing the first line of code.

* required skills C++, SQL knowledge
* useful skills: Lexx and Yacc
* Contact: mailto:dev@dba.openoffice.org
* Mentor: Ocke Janssen - Ocke.Janssen at Sun.Com

=== Dialogs with Form Functionality ===

When creating a form, the user always needs to bother with a Writer document. Very often, this is much too oversized. It would be sufficient to have a simple dialog which contains all the data access controls.

The advantage would be to not slay the user with things she does not bother – a writer document offers a lot of possibilities which are not relevant for a form. In some cases, a full writer document does even contradict to what users expect from a form – one thing to mention here is that documents are always freely sizable, which is nothing you expect from a carefully designed form, where controls are placed at concrete positions and have a fixed size.

The project is to
- extend the dialog runtime engine to (optionally) include data-aware form controls
- create a form designer for dialog-based forms (similar to the existing Basic Dialog IDE)
- implement persistence of dialog-based forms
- embed dialog-based forms into database documents (.odb)

Depending on more fine-grained planning, it might become apparent that not all of this can be done in the scope of a Google Summer of Code project, and reasonable milestones need to be defined.

* required skills C++, UNO
* useful skills: familiarity with OOo's database access and form API, as well as OOo's [http://api.openoffice.org/docs/common/ref/com/sun/star/awt/module-ix.html toolkit API]
* Contact: mailto:dev@dba.openoffice.org
* Mentor: Frank Schönheit - Frank.Schoenheit at Sun.Com

=== Embed Derby into OpenOffice.org Databases ===

OpenOffice.org Base features an abstract mechanism to embed database backend files into OOo databases (.odb). Currently, this is implemented for [http:///hsqldb.org HSQLDB], which is used as OOo's default database engine.

To allow this feature for other engines, one must:

* virtualize the engine's file access, so that it re-routes all its file operations through an abstract API.
* implement this API on the OOo Base side

The project is to do those implementations for [http://db.apache.org/derby Apache Derby database].

* required skills Java, C++
* useful skills: OOo's database access API, OOo's component technology (UNO)
* Contact: mailto:dev@dba.openoffice.org
* Mentor: Ocke Janssen - Ocke.Janssen at Sun.Com

==Calc==

===Integration of R into Calc===

Create an add-on component that allows a Calc user to let the [http://www.r-project.org/ R environment] do calculations on data from Calc cells and put the results into the spreadsheet again.

This should include a dialog to select input parameters and options, and allow results to be values or graph images. Note that the incompatible licenses (R is under GPL) have to be taken care of, possibly by starting R as a separate process.

Some more thoughts on the subject have been collected at [[Statistical Data Analysis Tool#Third Party Library Integration]].

* Required skills/knowledge: Some familiarity with statistical methods

; Contact
: dev@sc.openoffice.org
: Niklas.Nebel at sun.com

: Leonard Mada
: (on statistics and R syntax)
: discoleo at openoffice.org

===Watch Window===

A Watch Window is a separate, small window that remains "on top" and enables users to monitor a selected set of cells, see [http://www.openoffice.org/issues/show_bug.cgi?id=28386 issue 28386].

This could be implemented as an add-on component with a modeless dialog containing the list of watched cells as well as the UI to add or remove cells.

* Required skills/knowledge: Java or C++

; Contact
: dev@sc.openoffice.org
: Niklas.Nebel at sun.com

===Unit Testing Framework for Optimization Solver===

The [[Optimization Solver]] component needs a unit-testing framework for its linear optimizer. This task would involve collecting a load of test cases (small and large) with known solutions, and write an automated unit-testing program for the linear portion of the optimizer code.

* Required skills/knowledge: C++

; Contact
: kyoshida at novell dot com
: jody at novell dot com

===Additional AutoFilter Functionality===

Add core and user interface support for additional forms of filtering
* Date based filters (eg current year/quarter)
* Multiple items without falling back on logical OR.
* Statistical filters (eg within N stddev of mean)

* Required skills/knowledge: C++, Familiarity with OOo frameworks.

; Contact
: jody at novell dot com

===Move Older Spreadsheet formats into an UNO Component===

Support for several formats still lives in the core calc module, and bloat it with little used functionality.
Moving the antiquated filters into a distinct component would be good introduction to UNO and the spreadsheet code.
If time permits the new component could have support for other simple spreadsheet formats, such as Applix.

* Required skills/knowledge: C++, Familiarity with OOo frameworks.

; Contact
: jody at novell dot com

==Extensions==

===OOo connector for External IDE for OOo scripting languages===

This project will solve the problem of lack of IDE for scripting languages in OOo. Scripts can be seen as macros in various languages and are complementary to Extensions.
Actually, only OOoBasic has its IDE embedded in OOo. Javascript and Beanshell have limited ones and python nothing. To avoid implementing different IDE for various languages into OOo, the proposed choice is to provide a connector to any external IDE

The project is dived into 2 complementary parts :
* defining and implementing common tools at OOo side to put the scipts at the correct place and manage OOo scripts menus
* implement an Eclipse extension as an IDE that could handle scripts in python language, using the previously defined OOo tools.

; Requirements
* Required skills/knowledge: java, python, UNO
* Usefull skills: Eclipse API, OOo API, IDE general knowledge

; Contact
: dev@extensions.openoffice.org
: LaurentGodard@openoffice.org

==Framework==

===Shell Extensions for Desktop file search and showing meta data in windows explorer needs to be rewritten for Vista===

Vista changed his mechanism to integrate those shell extensions incompatible. Extensions valid for Win98/2000/XP doesnt work any more. A set of new interfaces was designed. But they are available on Vista only. So OOo has to support two sets of shell extensions: one set for Win98/2000/XP and a new set for Vista and might following windows versions. For this project the new Vista extensions has to be implemented only.
See [https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i71112 71112] and [https://so-web.germany.sun.com/iBIS/servlet/edit.ControlPanel?tid=i70944 70944] for further informations.

* Required skills/knowledge: C++
* Useful skills: Windows API knowledge
* Requirements: Windows Vista 32 Bit

; Contact
: dev@framework.openoffice.org, Andreas.Schluens at sun.com

===Status bar control to display/change the language===

Currently the Writer lacks means to display the language in use. There's also no easy way to change the language as the user has to use the menu. A status bar control would help to solve these problems. It should help to determine about the language used at the cursor position or the document. The control should be implemented using existing UNO APIs.

* Required skills/knowledge: C++
* Useful skills: Basic UNO API knowledge

; Contact
: dev@framework.openoffice.org, Carsten.Driesner at sun.com
: dev@sw.openoffice.org, Thomas.Lange at sun.com

===Improving UI editing / coupling===

Currently all dialogs (along with most translated strings) are stored in a rather unusual binary resource file format, that has not had much love in the last decade. We need to write some new code that separates the process of designing & laying out the UI from the code - to allow UE to make our UI more beautiful, and allow future re-factoring. The existing Basic GUI dialog editor and it's XML format should be re-used, a simple C++ compatibility API created, and a number of dialogs converted to the new format.

* Required skills/knowledge: C++
* Useful skills: courage, stickability, X-rated code reading

; Contact
: michael.meeks at novell.com
: hfiguiere at novell.com

==Graphics==

===Draw/Impress: SVG Import Filter===

[http://www.w3.org/Graphics/SVG/ SVG (Scalable Vector Graphics)] is a vector graphics format that describes 2D graphics in XML.

There's no native SVG import filter for OOo. There exists an [http://www.ipd.uka.de/~hauma/svg-import/ external one], but unfortunately it has very strong dependencies - [http://java.sun.com/javase/downloads/index.jsp Java 5.0], and [http://xmlgraphics.apache.org/batik/ Batik]. The goal of this task is to create a new implementation that does not require any too big libraries.

A proof of concept implementation written in C++ using the UNO Draw API, and a lighweight [http://cairographics.org/libsvg libsvg library] exists (see [http://svn.gnome.org/viewcvs/ooo-build/trunk/patches/src680/svg-import.diff here]), but it needs a lot of work to be really usable. Another problem is that libsvg does not seem to be too actively maintained; so ideally the implementation should use OOo's internal XML parser.

More information is available in [http://artax.karlin.mff.cuni.cz/~kendy/blog/archives/monthly/2006-10.html#2006-10-02T17_14_44.htm Kendy's blog].

* Required skills/knowledge: C++, XML knowledge is a plus

; Contact
: Jan Holesovsky - kendy at openoffice org
: Fridrich Strba - fridrich_strba at openoffice org

===Impress: OpenGL rendered transitions===
The goal is to add 3D transitions to the Impress application. Transition is an animation where one page is visible in the beginning and another in the end. It is used during presentation slideshow to switch pages.

In the process of implementing OpenGL transitions an UNO API should be added to slideshow code, so that OpenGL transitions engine might be created as standalone UNO component. Current transitions should be refactored to another UNO component.

The engine will get the previous and next pages and should render the transition at given speed.

The participant should also implement at least 5 OpenGL transitions, rendered by the UNO component.

* Reguired skills/knowledge: C++, OpenGL. familiarity with UNO is welcomed

;Contact:
:Radek Doulik - radekdoulik at openoffice org

==ODF Toolkit==

=== Tools and best practice samples for ODF creation and manipulation===

We already have some code snippets in Java and C# and looking for help to extend these tool sets or to provide tool sets in other languages. These tool sets are designed to offer basic ODF functionality even outside of OO.o.

* Required skills/knowledge: Java or C# or Perl or C++ ...
* Useful skills: ODF, XML

; Contact
: dev@odftoolkit.openoffice.org,
: Dieter Loeschky at sun.com

== Porting: Mac OS X native port ==

=== '''Complete User Interface respecting Aqua Human Interface Guidelines (Aqua Only)''' ===

*Concerns: OpenOffice.org 2.x for Mac OS X Aqua only

*Skills: Knowledge of languages C/C++ Mac OS X APIs and Application frameworks like Carbon

Original OpenOffice.org vcl widgets are not Aqua HIG compliant, and we need to implement all controls, respecting Aqua Human Interface Guidelines, some will use HIView, or HITheme or even other part of Carbon API.

*Tasks: some controls are already implemented, but some are still missing.

The job consists in write the code and implement:

- tabs (implement and bind the TabitemValue class, using Carbon API)

- spinbuttons (implement and bind SpinbuttonValue class, using Carbon API)

- comboboxes (implement and use HICombobox)

- listboxes (work already started)

- texts in comboboxes / listboxes (better task definition to be completed)

- other types of controls: highlight, respect dimensions/spacing ..etc

- Windows background (using Aqua theme)

;Proposed by: Eric Bachard
;Contact: mac@porting.openoffice.org
;ericb at openoffice dot org

=== Mac OS X native printing (Aqua only) ===

Concerns: OpenOffice.org 2.x for Mac OS X Aqua only

Objective: currently, the native printing implementation is missing on Aqua port and needs to be implemented.

The objective is to use the same box users have in any Mac application.

Skills: Knowledge of languages C/C++ Mac OS X APIs and Application frameworks like Carbon and /or Cocoa

Tasks:

Familiarize with the Mac OS X printing APIs

Familiarize with the current OOo printing API

Expected: Write code to Implement native printing with Aqua version of OpenOffice.org:

; Contact
: mac@porting.openoffice.org
: fheckl at openoffice dot org

;Proposed by: Florian Heckl

;Mentor: Florian Heckl

=== Mac OS X Address book integration (Aqua / X11) ===

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 APIs

Familiarize with the current OOo Mozilla address book integration

Make a prototype for OOo Mac OS X address book integration

;Contact
mac@porting.openoffice.org

;Mentor: Florian Heckl

==VBA==

===Word macro compatibility===

Recently Sun and Novell announced to pool resources to provide VBA macro compatability see http://blogs.sun.com/GullFOSS/entry/sun_and_novell_work_together here].

Currently work in the project is concentrated on providing Excel support by
* providing the framework for the compatibiltiy api via a plugable component
* modifying the basic engine to support more compatibility features
* porting the [http://wiki.services.openoffice.org/wiki/Helperapi helperapi] code ( for excel ) to c++ ( see. [http://wiki.services.openoffice.org/wiki/VBA here] & [http://wiki.services.openoffice.org/wiki/Porting_notes here]

Tasks

* extend the base framework by developing helper objects and implementations to be used by both the excel and writer compatibility object implementations
* port the existing (word) helper api objects from Java to C++

Required skills/knowledge

* C++
* Java
useful skills:

* knowledge of OOo's writer access API
* knowledge of OOo's component technology (UNO)
* experience with VBA macros and Word VBA api

Mentor/Contact
* noel.power at novell dot com

== Writer ==

===Writer: Better "Notes" functionality===

The "Notes" functionality in Writer could be better in terms of usability and does not look very appealing.

* Required skills/knowledge: C++

; Contact
: dev@sw.openoffice.org
: Mathias.Bauer at sun.com

; Resources
[http://blogs.linux.ie/caolan/2007/03/12/notesmarginnotes-in-sw/ hopefully helpful illustrative patch]

===MS Works Import Filter===

Unlike its proprietary derivatives, OpenOffice.org lacks MS Works import filter. The creation of MS Works import filter is one of functionalities requested by our users. There is a basic import filter work started and the result is to be found in CWS wpsimport01. This filter, based on recently started libwps[http://libwps.sourceforge.net] library is offering only limited number of features converted. It is desirable to build on this work and improve this library/filter so that the quality meets industry standards.

* Required skills/knowledge: C++, solid knowledge of MS Works wordprocessing document file-format and of libwps library.

; Contact
: fridrich_strba at openoffice.org
: freuter at novell.com

===RTF Generator===

The current RTF export of OpenOffice.org is not as good as the export to the Word (.doc) format. Parsing the generated Word format stream with a Word tokenizer and handing over the generated events to an RTF generator would lead to an RTF export filter with the same quality as the binary Word export filter. Remark: the tokenizer itself isn't complete today but in its current state covers enough parts of the Word format to make this a valuable project for the planned time span.

* Required skills/knowledge: C++, some knowledge about the Word file format would be a plus

; Contact
: dev@sw.openoffice.org
: Henning.Brinkmann at sun.com

=== Logging framework ===

During the import/export process from alien file formats there might be some features which can not be mapped entirely.
The goal of this project is to provide a loggin framework for the new domainmapper of the writer filter project, which
allow the domainmapper to notify the user of such mapping problems.

* Required skills/knowledge: C++

; Contact
: Florian Reuter (freuter at novell.com)
: Fridrich Strba (fridrich_strba at openoffice org)

Mac OS X Porting - Work Areas/Todo's

2006-10-14T12:08:08Z

KAMiKAZOW:

This page is intended to serve as a living ToDo list for the OpenOffice.org Mac OS X port. To keep things simple it contains the ToDos for both the X11 version and the upcoming Aqua version of OpenOffice.org for Mac OS X. The page is divided into different work areas which either assigned to a person in charge or are unassigned yet. Below each area there is a detailed list of todos which has to be maintained by the respective people himself.
Persons who are in charge of a certain area are responsible for keeping their respective part of the page up-to-date.

If you're interested in contributing to the project please coordinate with Eric Bachard [mailto:ericb@openoffice.org]

== Areas and ToDos Aqua Version ==
<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Messaging || Tino Rachui [mailto:tra@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement messaging infrastructure || New || Unassigned
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Windowing || Tino Rachui [mailto:tra@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement salframe.cxx || New || Unassigned
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Drawing || [mailto:ssa@openoffice.org Stephan Schaefer]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement drawing support || In progress || [mailto:ssa@openoffice.org Stephan Schaefer]
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native Printing support || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Make some docs || In progress || [mailto:ybart2@openoffice.org Yvan BARTHÉLEMY]
|-
| Native look & feel for Print and Print Setup || New || Unassigned
|-
| Panel for OpenOffice.org specific options || New || Unassigned
|-
| Implement native Print support || New || Unassigned
|-
| Implement native Print setup || New || Unassigned
|}

Work in progress, see: [[Mac_OS_X_Porting_-_Native_Printing]]

Description:

'''OpenOffice.org side''':

AquaSalPrinter class is located in aqua/source/gdi/salprn.cxx

Headers are in:
vcl/inc/salinst.hxx
vcl/inc/salgdi.hxx
vcl/inc/salprn.hxx

Aqua implementation:
aqua/inc/salprn.h (AquaSalPrinter class implementation, inherits from SalPrinter)

'''Mac OS X API side''':

Todo: implement missing methods, using Carbon API

Link for Mac OS X API documentation:

http://developer.apple.com/documentation/Carbon/Reference/CarbonPrintingManager_Ref/index.html

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Key input || Unassigned [mailto: [???@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| ??? || New || Unassigned
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native sound support || Eric Bachard [mailto: Name [mailto:ericb@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement native sound support || Started || Eric Bachard
|}

New page has been updated.

See: [[Native Sound Implementation on Mac OS X]]

Estimation of code remaining to write: 40% (macosxplayer.cxx mainly)

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Image Acquisition || [mailto:ericb@openoffice.org Eric Bachard]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to Unassigned [mailto: [???@openoffice.org]
|-
| Implement Image Acquisition || In progress || [mailto:ericb@openoffice.org Eric Bachard]
|}

'''See''': [[Mac_OS_X_Porting_-_Data_Acquisition Data_Acquisition on Mac OS X]]

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Native font support ||Eric Bachard [mailto:ericb@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| ATS || Started || Eric Bachard
|}

salatslayout.cxx License origin is justified here: http://qa.openoffice.org/issues/show_bug.cgi?id=23283]

'''OpenOffice.org side''':

1) Headers

1.1) '''vcl/inc/salgdi.hxx''', including definition of:
SalGraphics class

1.2) '''vcl/inc/sallayout.hxx''', including definitions of:
classes:
ImplLayoutRuns
ImplLayoutArgs
SalLayout
MultiSalLayout (inherits of SalLayout)
GenericSalLayout

structures:
struct GlyphItem

1.3) '''vcl/aqua/inc/salgdi.h''', including definitions of

classes:
ImplMacFontData (inherits of ImplFontData)

AquaSalGraphics (inherits of SalGraphics, does have ATSLayout as friend class)

2) Implementation

2.1) vcl/aqua/source/inc/salatslayout.cxx

Implements the classes:

ATSLayout (inherits of SalLayout)

existing ATSLayout methods are:
bool ATSLayout::LayoutText()
void ATSLayout::AdjustLayout()
void ATSLayout::DrawText()
int ATSLayout::GetNextGlyphs()
long ATSLayout::GetTextWidth()
long ATSLayout::FillDXArray()
int ATSLayout::GetTextBreak()
void ATSLayout::GetCaretPositions()
bool ATSLayout::GetBoundRect()
bool ATSLayout::InitGIA()

Other class: PolyArgs, implementing:
void PolyArgs::Init()
void PolyArgs::AddPoint()
void PolyArgs::ClosePolygon()
OSStatus MyATSCubicMoveToCallback()
OSStatus MyATSCubicLineToCallback()
OSStatus MyATSCubicCurveToCallback()
OSStatus MyATSCubicClosePathCallback ()

'''Mac OS X API side''':

Carbon API implementation (binding) is made in salatslayout.cxx

ATS and ATSUI starting point: http://developer.apple.com/documentation/Carbon/Conceptual/ATS_Concepts/atsfonts_intro/chapter_1_section_1.html

Apple's starting page leading to deeper docs: http://developer.apple.com/documentation/TextFonts/Typography-date.html

'''Todo-list for native font implementation:'''

- missing methods (to be implemented):

'''bool ATSLayout::GetGlyphOutlines()'''
'''ATSLayout::InitFont()'''
'''ATSLayout::MoveGlyph()'''
'''ATSLayout::DropGlyph()'''
'''ATSLayout::Simplify()'''

- Fix known bugs:
MultiLine does not work (writer cannot be used, because)
Bad keyboard/charset ? (missig chars)
When redrawing, everything is redrawn using the most little font size -> even the dialog boxes on menu bars
Bad values returned

- Implement MultiSalLayout
- Complete implementation
- read Apple API [ Work in progress]
- describe current implementation: organisation / design [work in progress]
- design of new implementation [FIXME] find examples

Estimation of code remaining to write ~40 %

'''Done''' (mainly Stephan Schaefer, with initial salatslayout.cxx file written by Herbert Duerr)

0.4
- adapt salatslayout.cxx to make it match with sallayout.hxx, and salgdi.hxx, saldata.hxx .etc
to make it build with aquavlcl01, and do some tests:
- verify this server can be initialized inside OpenOffice.org (needs a CFRunLoop working to be correctly initialized)
- run it and fix instant crashs and verity there is no freeze

0.3

- fix compilations issues
- rewrite complete salatslayout.cxx
- verify salatsfontutils.cxx definition does match with new salatslayout.cxx content
- define correct naming convention
- replace old SalGraphicsData object implementation (found in pre-aquavcl01 files, and now obsolete, because we won't use QDraw anymore)
- understand current font implementation (using old salatslayout.cxx) (work in progress)
- analyse and describe Carbon binding in salatslayout.cxx (90% done)

'''Resources''': use sample code to test/initialize ATS server (using e.g. ATSUIDirectAccessDemo)

For more informations, see: [[Fonts_starting_point_and_documentation]]

== Areas and ToDos X11 Version ==

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Packaging <br>Packaging related tasks || Oliver Braun [mailto:obr@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Improved packaging for OOo || Done || Oliver Braun
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Installation <br>Installation related tasks || Oliver Braun [mailto:obr@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Provide an improved installer for OOo || New || Oliver Braun
|-
| Error messages during installation when no X11 is installed || Started (messages need to be localised and more info supplied) || Unassigned
|-
| Support language pack instalation || New || Unassigned
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Desktop Integration <br>Desktop integration related tasks || Oliver Braun [mailto:obr@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
|Allow opening of documents with path names that need to be escaped for shell scripts || Needs Tested see [http://www.openoffice.org/issues/show_bug.cgi?id=69143] || Shaun McDonald [mailto:smsm1@openoffice.org]
|-
| Save documents in ~/Documents by default || New || Unassigned
|-
| Use the Mac OS X key chain for document signing || New || Unassigned
|-
| Read proxy settings and user information from the system settings || New || Unassigned
|-
| Mac OS X address book integration || New || Unassigned
|-
| Make use of the Mac OS X spell checker || New || Unassigned
|-
| Improved clipboard support || New || Unassigned
|-
| Support for standard Mac OS X shortcuts according to HI guideline || New || Unassigned
|-
| Integrate native FileOpen/FileSave dialog into OOo || Started || Florian Heckl [mailto:fheckl@openoffice.org]
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Printing || Unassigned [mailto: Name [??@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Improved printing support (CUPS) || Done || Mox Soini, Oliver Braun
|-
| Use the native print dialog in OOo || New || Unassigned
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Ease of use || Unassigned [mailto: Name [??@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Reduce visible toolbars || New || Unassgined
|-
| Suppress icons in OOo menus by default || New || Unassigned
|-
| Suppress xterm window when launching OOo || New || Unassigned
|}

<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Implement NeoLight plugin || Unassigned [mailto: Name [??@openoffice.org]
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Implement NeoLight (spothlight plugin) in OpenOffice.org 2.0. For more informations, please have a look at [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1328&sid=9fb65afa5ca4232a6f8fae420424a3fe]|| New || Unassigned
|}

<br>

== Assurance Quality and Mac OS X port ==
<br>

{| style="vertical-align:top; text-align:left; background-color:#F0F0F0;"
|- style="background-color:#99CCFF; font-weight:bold;"
| Mac OS X QA || unassigned
|}

{| style="vertical-align:top; text-align:left; background-color:#efefef;"
|- style="background-color:#d6d6d6;font-weight:bold;"
| Todo || Status || Assigned to
|-
| Collect informations and manage Mac OS X QA on the wiki || New || Unassigned
|}

<br>

[[Category:Porting]]
[[Category:Aqua]]
[[Category:MacOSX]]

Developer News about porting OpenOffice to Darwin PPC, Darwin Intel and Mac OS X

2006-10-14T11:56:36Z

KAMiKAZOW:

'''September 2006''' Demo of native Mac OS X version of OpenOffice.org 2.0 at OOoCon 2006 (Lyon, France), and Apple Expo (Paris). Native version means running without X11.

'''August 2006''' Mac porting of OpenOffice.org is present at WWDC06 (San Francisco). Thanks to Archibald Horlitz from GRAVIS AG Germany, and Cusoon. with the infos found at WWDC, discussing with Apple engineers, the Event Loop issue ( using WaitNextEvent() and RunApplicationEventLoop() now works ( Christian Lippka). Native version can now run without X11: lot of screenshots are available. Pavel Janik provided experimental version of Native Filepicker. Oliver Braun provided a fix to start OpenOffice.org, simply double-clicking the bundle.

'''June 2006''' Pavel Janik fixed a lot of things, and provided the code for native menubar implementation. Christian Lippka fixed important part for 2D drawing (mainly bitmaps).

'''April 2006''' New donation for Tino Rachui and Stephane Schaefer : two Imac Intel 20". These very fast machines will replace old G3, good but slower.

'''February 2006''' First screenshots of svdem. Stephan Schaefer, Florian Heckl and Tino Rachui have made work svdem, a toy dedicated to experimentations in vcl. The objective is to progressively implement everything for Carbon/Cocoa port.
'''Screenshot of svdem with antialiased lines''' [http://eric.bachard.free.fr/mac/aquavcl/screenshots/test_svdem_ericb_10_mars2006.jpg]

'''January 20th, 2006:''' Starting April 2005, there were several donations made to the MacOSX Porting Team of OpenOffice.org. We would like to extend our thanks to those who made these donations to the MacOSX Porting Team on [http://porting.openoffice.org/mac/donations.html this web page]. Porting OpenOffice.org to MacOSX X11, MacTel (MacOSX for the Intel processor base) and MacOSX Aqua is easier with these donations.

'''January 17th, 2006:''' New [http://porting.openoffice.org/mac/timeline.html timeline]

'''January 14th, 2006''': OpenOffice.org 2.0 now works natively (without use Rosetta) on Mac Intel (Apple machines running Mac OS X with Intel processors ). The port was done by a 4 developers team, including Florian Heckl, Eric Bachard, Daniel Boelzle and Stephan Bergmann. Florian Heckl and Eric Bachard did the necessary changes for the port, using " Mactel " rent by Cusoon and Team OpenOffice.org e.V. , while Daniel Boelzle and Stephan Bergmann helped to solve the bridge. First announce : [http://eric.bachard.free.fr/news ericb's blog]

'''January 5th, 2006''': The Mac OS X Tinderbox is up and running. Thank's to Maxime Petazzoni for his great work !

'''December 25th, 2005''': Maho Nakata provided '''63 locales''' for official 2.0.1 !! Following locales : fr, de, en-US, mk, it and ja have been declared stable, after QA smoke tests.

'''November 17th-18th, 2005''': first Mac Team meeting in Hamburg

'''October 24th, 2005''': Florian Heckl completed the first Aqua build on both Mactel and PowerPC. Just an empty window, but without X11.

'''October 2005:''' OpenOffice.org 2.0 for Mac OS X (X11) is [http://porting.openoffice.org/mac/2.0.0rc3.html here]!

'''October 1, 2005:''' Updated Mac OS X [http://porting.openoffice.org/mac/build_680_X11.html build instructions] to match milestone 130 and recent developments making OOo compile using gcc 4.0 and Mac OS X 10.4.x

'''August 27, 2005:''' It's now possible to use gtk and kde themes with OpenOffice.org on Mac OS X. As experimental work, Eric Bachard provided some screenshoots : Panther theme using gtk plugin . Other screenshots (with other themes) are available here. As you can see here, the new crystal icons set looks interesting too.

'''July 3, 2005:''' Updated [http://porting.openoffice.org/mac/build_680_X11.html build instructions] for Mac OS X 680_m113 and higher. Please review and report mistakes to ''mac@porting.openoffice.org''

'''February 10, 2005:''' At the OOoRegiCon, Simon Phipps called upon the [http://blogs.sun.com/roller/page/webmink/20050209#san_diego_preso OpenOffice.org community] [blogs.sun.com] to recognize [http://www.neooffice.org/ NeoOffice] [neooffice.org] as a part of a wider OpenOffice.org community of collaborators all working to achieve a common goal. Hopefully his message will be heard, hopefully no one will need to "discover" NeoOffice any longer, and hopefully the drastic need for OpenOffice.org X11 will no longer be ignored. Without Mac OS X (X11), there no foundation upon which to even dream non-X11 versions on Mac OS X.

'''January 20, 2005:''' First [http://eric.bachard.free.fr/mac/MacOSX_m71s1/png/ screenshots] of milestone 1.9.71s1 running on Mac OS X (X11) by the great work of Eric Bachard. There is still [http://porting.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14984 much work] to still be done before getting a fully functional version for X11, so drop on by and lend a hand today!

'''October 29, 2004:''' OpenOffice.org 2.0 Aqua port slows. With lack of a dedicated X11 team, 2.0 doesn't even compile "out of the box" for X11, and Cocoa development has slowed as well. The only current Mac OS X non-X11 development is the [http://www.neooffice.org/ NeoOffice/J] [neooffice.org] fork of OpenOffice.org 1.1.2, which is all the time I (Ed) have for myself. We desperately need your help! Go checkout 680 and help Eric Bachard, Eric Hoch, Florian Heckl and all the other Mac OS X diehards port it today! Check out the mailing list archives for the most recent 411.

'''June 27, 2004:''' OpenOffice.org 1.1.2 for Mac OS X (X11) is now available for [http://porting.openoffice.org/mac/ooo-osx_downloads.html download].

'''March 29, 2004:''' Updated 1.1.1 [http://porting.openoffice.org/mac/build_11_X11.html Build Instructions]

'''March 29, 2004:''' OOo 1.1.1 - soon for Mac OS X. We're finalizing pieces of the installer right now, and hope to have builds propagated to the mirrors this week. [http://porting.openoffice.org/mac/big_shot.html See a screenshot].

'''August 19, 2003:''' Screenshot of OpenOffice.org 1.1 running under X11 on Mac OS X 10.2. Click to enlarge.

'''August 18, 2003:''' Development of OpenOffice.org 1.x on Mac OS X has been limited to X11. All development of Quartz and Aqua versions has been postponed to OpenOffice.org 2.x with expected delivery in late 2005 to early 2006. See the [http://porting.openoffice.org/mac/timeline.html timeline] for details.

'''June 23, 2003:''' It's official! After months of testing and bug fixing, OpenOffice.org is pleased to announce the availability of OpenOffice.org Mac OS X (X11). This release runs with X11 graphics provided by either Apple X11 or XFree86. [http://porting.openoffice.org/mac/ooo-osx_downloads.html Download] it now, join the project and ''mac@porting.openoffice.org'' mailing list. Hunt for bugs; test features; make suggestions. Help us deliver the best open source office suite for Mac OS X and Darwin!
[[Category:Porting]]
[[Category:Aqua]]
[[Category:MacOSX]]

User:Ericb

2006-09-24T08:33:06Z

KAMiKAZOW: fix spaces

Extensions development

2006-09-24T08:04:23Z

KAMiKAZOW: /* Tools & Frameworks */

{{Extensions}}
Developing extensions is an efficient way to bring value to OpenOffice.org without diving into core sources. Obviously all developers willing to [[Main_Page|develop at OpenOffice.org sources level]] are welcomed.

OpenOffice.org enables third party tools creation through UNO bridges, allowing using many languages.

The principle is to create UNO packages that can be listed in the OpenOffice.org [[Extensions_repository|Extensions repository]] and installed by end-users easily.

This section wants to give newcomers as well as experienced developers some hints to develop Extensions in their desired languages and provide them with tools and frameworks that ease and homogenize the development.

Finally, popular Extensions may be integrated into OpenOffice.org so it is important to follow common policies from beginning to ease this merging.

==== Starting in a language ====
Addons can be written in various languages. Each section is here to give starting informations that let you create your addons. Each section is dedicated to a language. It deals with specific points concerning the Extensions aspect. Resources regarding the OpenOffice.org API can be found on the [http://api.openoffice.org API project] and UNO bridges languages issues on the [http://udk.openoffice.org UDK project]

The translations of these pages are welcomed and [[Extensions#Translating_these_pages|guidelines are available]].

* [[Extensions_development_python|Starting in Python]]
* [[Extensions_development_basic|Starting in Basic]]
* [[Extensions_development_java|Starting in Java]]
* Starting in C++
* Non programmatic Extensions
* Extensions packaging

==== Tools & Frameworks ====

* [http://codesnippets.services.openoffice.org Code snippets available in many languages]
* [[Extensions_development_translation|Translation framework]]
* [[Extensions_Packager|Extensions Packager]]
* Predefined wizards
* [[Extensions_introspection|Introspection Tools]]: discover the API

[[Category:Extensions]]

Extensions

2006-09-24T08:03:10Z

KAMiKAZOW: /* References/Articles */

__NOTOC__
{{Extensions}}

=== OpenOffice.org Extensions ===

OpenOffice.org offers the possibility to develop independent 3rd party extensions. The categories of extensions reach from Basic libraries, packages with Java/JavaScript or Python macros to more sophisticated extensions in form of UNO components implemented in Java, C++ or Python. Even the last category of extensions subdivide in general UNO components providing new implementations for existing functional areas or specialized components like Calc Add-Ins, Add-Ons, DataPilots, Chart Add-Ins or linguistic components (e.g. Spellchecker, Hyphenator or Thesaurus).

The Extensions project provides
* [[Extensions development|Tools, guidelines and starting informations]] to develop new functionalities for OpenOffice.org
* [[Extensions repository|Repository of existing Extensions]]: listing and classification
* [[Extension Deployement|Deployment to end-users]]

=== Translating these pages ===

The Extension project has to be strongly binded to Native-Lang communities to relay any locale third party development. So it is strongly welcomed to provide translation for the Add-ons but also for the documentation and pages of this site.

The naming convention proposed is to
* Create a new page taking the English page and add your language code as suffix (eg. Extensions_repository_fr)
* Put a link to this translated page at the top of the English page, with the language code
* Be aware that if you start a translation, it would be good to monitor that it remains as in sync as possible

=== Some extension categories ===

* Calc Add-Ins provide new Calc built in functions which can be directly used over the normal function dialog in the Calc application.
* [[Add-ons]] describe components providing some new functionality and normally coming with an UI integration (e.g. new menu entries or complete new menues, new toolbars).
* DataPilots provide a new kind of data pilot which can be used directly over the DataPilot dialog in the Calc application.
* Chart Add-Ins provide a new chart type
* Linguistic components provides new implementations of know interfaces which can be used directly over the normal UI.

In the future it should be possible to deploy a collection of new document templates or a gallery as extensions as well.

=== References/Articles ===

* [http://api.openoffice.org/docs/DevelopersGuide/Components/Components.xhtml#1_7_3_Add-Ons OpenOffice.org Developers Guide]

* [http://www.linuxjournal.com/article/7802 Linux Journal: "Off the Wall: Macros and Add-ons"]

* In this Wiki: [[SimpleCalcAddIn|a simple Calc AddIn]] and [[CompleteAddIn|a complete AddIn]]

[[Category:Extensions]]
[[Category:Source directories]]

Extensions

2006-09-24T08:02:21Z

KAMiKAZOW: /* OpenOffice.org Extensions */

__NOTOC__
{{Extensions}}

=== OpenOffice.org Extensions ===

OpenOffice.org offers the possibility to develop independent 3rd party extensions. The categories of extensions reach from Basic libraries, packages with Java/JavaScript or Python macros to more sophisticated extensions in form of UNO components implemented in Java, C++ or Python. Even the last category of extensions subdivide in general UNO components providing new implementations for existing functional areas or specialized components like Calc Add-Ins, Add-Ons, DataPilots, Chart Add-Ins or linguistic components (e.g. Spellchecker, Hyphenator or Thesaurus).

The Extensions project provides
* [[Extensions development|Tools, guidelines and starting informations]] to develop new functionalities for OpenOffice.org
* [[Extensions repository|Repository of existing Extensions]]: listing and classification
* [[Extension Deployement|Deployment to end-users]]

=== Translating these pages ===

The Extension project has to be strongly binded to Native-Lang communities to relay any locale third party development. So it is strongly welcomed to provide translation for the Add-ons but also for the documentation and pages of this site.

The naming convention proposed is to
* Create a new page taking the English page and add your language code as suffix (eg. Extensions_repository_fr)
* Put a link to this translated page at the top of the English page, with the language code
* Be aware that if you start a translation, it would be good to monitor that it remains as in sync as possible

=== Some extension categories ===

* Calc Add-Ins provide new Calc built in functions which can be directly used over the normal function dialog in the Calc application.
* [[Add-ons]] describe components providing some new functionality and normally coming with an UI integration (e.g. new menu entries or complete new menues, new toolbars).
* DataPilots provide a new kind of data pilot which can be used directly over the DataPilot dialog in the Calc application.
* Chart Add-Ins provide a new chart type
* Linguistic components provides new implementations of know interfaces which can be used directly over the normal UI.

In the future it should be possible to deploy a collection of new document templates or a gallery as extensions as well.

=== References/Articles ===

* [http://api.openoffice.org/docs/DevelopersGuide/Components/Components.xhtml#1_7_3_Add-Ons OpenOffice.org Developers Guide]

* [http://www.linuxjournal.com/article/7802 Linux Journal: "Off the Wall: Macros and Add-ons" ]

* In this Wiki : [[SimpleCalcAddIn | a simple Calc AddIn]] and [[ CompleteAddIn | a complete AddIn]]

[[Category:Extensions]]
[[Category:Source_directories]]