Re: Controller class for documents/textView classes in Open Office (NSDocument like?)
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 signature.asc Description: Digital signature
CVE-2015-1774: OpenOffice HWP Filter Remote Execution and DoS Vulnerability
CVE-2015-1774 OpenOffice HWP Filter Remote Code Execution and Denial of Service Vulnerability A vulnerability in OpenOffice's HWP filter allows attackers to cause a denial of service (memory corruption and application crash) or possibly execution of arbitrary code by preparing specially crafted documents in the HWP document format. Severity: Important Vendor: The Apache Software Foundation Versions Affected: All Apache OpenOffice versions 4.1.1 and older are affected. Mitigation: Apache OpenOffice users are advised to remove the problematic library in the program folder of their OpenOffice installation. On Windows it is named hwp.dll, on Mac it is named libhwp.dylib and on Linux it is named libhwp.so. Alternatively the library can be renamed to anything else e.g. hwp_renamed.dll. This mitigation will drop AOO's support for documents created in Hangul Word Processor versions from 1997 or older. Users of such documents are advised to convert their documents to other document formats such as OpenDocument before doing so. Apache OpenOffice aims to fix the vulnerability in version 4.1.2. Credits: Thanks to an anonymous contributor working with VeriSign iDefense Labs. signature.asc Description: OpenPGP digital signature
Re: Aranese spell checker
Andrea wrote: Does Aranese have a ISO 639-1, ISO 639-2 or ISO 639-3 code? I find conflicting information online. If it does have an ISO code, we can include it as a document language in the next release (and your dictionary will work in future versions of OpenOffice). Aranese is a dialect of Gascon, which had an ISO 639-3 code of GSC. However, that code was retired in April 2007, with Gascon being merged into Occitan, which has an ISO 639-3 code of OCI. Occitan is a current option. My suggestion would be to have oci_AD (ISO 3166 country code for Andorra), oci_FR (ISO 3166 country code for France), and oci_ES (ISO 3166 country code for Spain). If one wants to push a point, oci_IT (ISO 3166 country code for Italy.) That way one can have a spell checker for Occitan, Gascon, and Aranese, with a slot left over for another dialect of Occitan. All that said, what is the _current_ procedure to get a new language/locale in the format settings? Andreas response implies that https://wiki.openoffice.org/wiki/Adding_a_new_language_or_locale is no longer valid. I'm also assuming that completing the form at http://www.it46.se/localegen/select_country.php no longer suffices.Is that assumption correct? jonathon - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Controller class for documents/textView classes in Open Office (NSDocument like?)
Le 24/04/2015 21:48, ANTHONY CRUZ a écrit : Hi Anthony, 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). 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?) I’d like to learn more about the primary C++ classes used in the app since it is quite easy to interoperate with C++ from Objective-C. From my very incomplete understanding of the LibreOffice code (I haven't looked at the AOO codebase recently so there may be some differences in repo structure), there is a very thin Cocoa wrapper around a maze of C++ classes. Most of the low level quartz/osx stuff is in VCL. Alex - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
