Noel Grandin 2b3de550ef remove pParentFrame from SfxFrame
Found by the singlevalfields loplugin.

Dead as least as far back as
  commit 93a7b55858
  Author: Frank Schoenheit [fs] <frank.schoenheit@sun.com>
  Date:   Fri Nov 27 21:16:24 2009 +0100
  [CWS autorecovery] merged SfxTopFrame into SfxFrame
  SfxTopFrame was the only class deriving from the abstract class SfxFrame, so both
  can effectively be treated as one class.

Arguably when that commit was done, SfxFrame should also have been renamed
to SfxTopFrame, since that it was it now seems to be.

Expanding the nullptr value off that field means that:
    SfxFrame::GetTopFrame
       always return this
    SfxFrame::IsParent
       always returns false
    SfxViewFrame::GetTopFrame
       is now the same as SfxViewFrame::GetFrame
    SfxViewFrame::GetParentViewFrame
       now returns null

Change-Id: Iac088fa485c3d7299d1553845ced2f5ced3c85f2
Reviewed-on: https://gerrit.libreoffice.org/30485
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
Tested-by: Noel Grandin <noel.grandin@collabora.co.uk>
2016-11-03 06:30:11 +00:00
2016-11-01 04:11:44 +00:00
2016-10-18 06:15:55 +00:00
2016-11-02 13:06:37 +00:00
2016-10-16 14:19:32 +00:00
2016-10-16 14:19:31 +00:00
2016-11-01 04:11:44 +00:00
2016-10-16 14:19:28 +00:00
2016-11-02 07:54:20 +00:00
2016-10-23 17:17:01 +00:00
2016-11-02 10:33:49 +01:00
2016-11-03 06:30:11 +00:00
2016-11-02 07:54:20 +00:00
2016-10-08 20:48:35 +00:00
2016-10-23 17:17:01 +00:00
2016-11-02 13:06:37 +00:00
2016-10-16 14:19:18 +00:00
2016-11-01 18:07:59 +00:00
2016-10-30 21:07:52 +01:00
2016-11-02 12:13:24 +00:00
2016-11-02 18:42:47 +00:00
2016-11-02 18:42:47 +00:00
2016-10-26 11:56:21 +02:00
2016-11-03 06:30:11 +00:00
2016-10-03 23:29:12 +03:00
2016-11-01 22:28:37 +01:00
2016-11-02 13:06:37 +00:00
2016-11-02 13:06:37 +00:00
2016-10-25 17:09:46 +02:00
2016-10-18 14:58:41 +02:00
2016-11-02 07:54:20 +00:00
2016-11-03 06:30:11 +00:00
2016-11-02 13:06:37 +00:00
2016-11-03 06:30:11 +00:00
2016-10-31 20:16:04 +01:00
2016-11-02 20:26:28 +00:00
2016-11-01 13:25:08 +00:00
2016-11-03 06:30:11 +00:00
2016-11-01 04:11:44 +00:00
2016-10-21 12:51:51 +00:00
2016-10-28 08:52:47 +02:00
2016-11-01 04:11:44 +00:00
2016-11-02 16:56:11 +01:00
2016-11-02 23:56:12 +02:00
2016-11-01 13:02:53 +02:00
2016-11-02 20:04:23 +00:00
2016-11-02 19:11:14 +00:00

LibreOffice

Coverity Scan Build Status CII Best Practices

LibreOffice is an integrated office suite based on copyleft licenses and compatible with most document formats and standards. Libreoffice is backed by The Document Foundation, which represents a large independent community of enterprises, developers and other volunteers moved by the common goal of bringing to the market the best software for personal productivity. LibreOffice is open source, and free to download, use and distribute.

A quick overview of the LibreOffice code structure.

Overview

You can develop for LibreOffice in one of two ways, one recommended and one much less so. First the somewhat less recommended way: it is possible to use the SDK to develop an extension, for which you can read the API docs here and here. This re-uses the (extremely generic) UNO APIs that are also used by macro scripting in StarBasic.

The best way to add a generally useful feature to LibreOffice is to work on the code base however. Overall this way makes it easier to compile and build your code, it avoids any arbitrary limitations of our scripting APIs, and in general is far more simple and intuitive - if you are a reasonably able C++ programmer.

The important bits of code

Each module should have a README file inside it which has some degree of documentation for that module; patches are most welcome to improve those. We have those turned into a web page here:

http://docs.libreoffice.org/

However, there are two hundred modules, many of them of only peripheral interest for a specialist audience. So - where is the good stuff, the code that is most useful. Here is a quick overview of the most important ones:

Module Description
sal/ this provides a simple System Abstraction Layer
tools/ this provides basic internal types: 'Rectangle', 'Color' etc.
vcl/ this is the widget toolkit library and one rendering abstraction
framework UNO framework, responsible for building toolbars, menus, status bars, and the chrome around the document using widgets from VCL, and XML descriptions from /uiconfig/ files
sfx2/ legacy core framework used by Writer/Calc/Draw: document model / load/save / signals for actions etc.
svx/ drawing model related helper code, including much of Draw/Impress

Then applications

Module Description
desktop/ this is where the 'main' for the application lives, init / bootstrap. the name dates back to an ancient StarOffice that also drew a desktop
sw/ Writer
sc/ Calc
sd/ Draw / Impress

There are several other libraries that are helpful from a graphical perspective:

Module Description
basegfx/ algorithms and data-types for graphics as used in the canvas
canvas/ new (UNO) canvas rendering model with various backends
cppcanvas/ C++ helper classes for using the UNO canvas
drawinglayer/ View code to render drawable objects and break them down into primitives we can render more easily.

Finding out more

Beyond this, you can read the README files, send us patches, ask on the mailing list libreoffice@lists.freedesktop.org (no subscription required) or poke people on IRC #libreoffice-dev on irc.freenode.net - we're a friendly and generally helpful mob. We know the code can be hard to get into at first, and so there are no silly questions.

Description
LibreOffice mirror (not auto-updating).
Readme 1.9 GiB
Languages
C++ 82.4%
Java 5.3%
Rich Text Format 2.3%
PostScript 1.9%
Python 1.9%
Other 5.7%