I see. When i was looking at the source I was wondering what all that “sal” stuff was. I’ve been unable to find more info on the VCL (documentation wise). I see some of the C++ classes that are wrapping Cocoa stuff. When I see Objective-C, I feel at home. Is there any class documentation for the VCL stuff.
Is there any document that exposes what system dependent part is used when you use the VCL API? It would be easier for me, to get something started, if I can think of the application in the context of the API I already know pretty well (Cocoa APIs). I see where recent document URLS are pinned to the recent documents list with the document controller, but I’m having a hard time finding the “meat” of the application (for example, a Writer window controller, that takes a document and shows it on screen…the save as PDF button code, etc). While I realize it’s a cross-platform project and doing it this way avoids repeat code, have you guys ever thought of making the project more accessible to those who are familiar with native APIs? I imagine there would be a lot more contributors from programmers who have spent there time learning native API (iOS/Mac developers are everywhere now). > On Apr 25, 2015, at 1:42 PM, Ariel Constenla-Haile <arie...@apache.org> wrote: > > Hello Anthony, > > On Fri, Apr 24, 2015 at 03:48:19PM -0400, ANTHONY CRUZ wrote: >> Ideally, I’d like to work with the Open Office source code for the >> main app on OS X. I was attempting to set up a working Xcode project >> (which I prefer over Eclipse and I’m interested in the Aqua build), so >> I’d be able to run and debug the application like a typical Cocoa app >> but there isn’t an obvious way to set up an project since there is >> quite a bit of source code and the class documentation is a bit hard >> to find (for me, navigating the Wiki to find relevant info was not >> easy). > > I never tried to use Xcode as an IDE with OpenOffice source code, so > I can't tell; you should see if it can create a project from existing > sources using an external build system. > >> Piecing it all together by looking through the source code with no >> knowledge of a project of this size is going to be quite time >> consuming so I was hoping someone could point me in the right >> direction. Is there only a thin native Cocoa layer in the main app? Is >> the textview used for documents native (does it use NSTextView?) > > OpenOffice is a multi-platform project, so the system-dependent parts > are plugged-in and not used directly through the whole source code; > there is a system abstraction layer in the VCL module, these classes are > used all over the source code, the system dependent part is confined in > plugins and not exposed to the applications; the following documentation > is rather outdated, but it explains the concept of VCL plugins: > http://www.openoffice.org/gsl/ > http://www.openoffice.org/gsl/vcl/plugins/index.html > > > Regards > -- > Ariel Constenla-Haile > La Plata, Argentina --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
