office-gobmx/svx
Stephan Bergmann b1141fa610 Cut down on -pthread/-lpthread proliferation
Building against libstdc++ effectively always requires -pthread anyway (as
various standard C++ headers require it, see the comment added to
solenv/gbuild/platform/unxgcc.mk), so many explicit uses of -pthread/-lpthread
can be removed.

Doing a (partial) test build on Linux with Clang -stdlib=libc++ suggests that
libc++ indeed doesn't need -pthread as libstdc++ does.

The remaining uses of -pthread/-lpthread are mostly in configure.ac for the
various BSDs (which somebody else might want to clean up now), and related to
external projects.  I tried to be careful to remove -pthread/-lpthread from
makefiles only when C++ object files are involved (so -pthread will now be
included on the link command line by default).

Change-Id: I936e082839cb9a434bd273ce5a1f187a4245dfa1
Reviewed-on: https://gerrit.libreoffice.org/71291
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2019-04-25 21:27:43 +02:00
..
doc
inc remove or change salbtype.hxx includes with the specific one 2019-04-15 12:32:52 +02:00
qa tdf#124740 Handle position is already scaled for ooxml-foo shapes 2019-04-16 12:05:43 +02:00
sdi
source WIP: Further preparations for deeper Item changes 2019-04-25 19:59:04 +02:00
uiconfig/ui tdf#124197 Improve "Unexpected error" user-visible error message wording 2019-04-24 10:30:37 +02:00
util
AllLangMoTarget_svx.mk
CppunitTest_svx_dialogs_test.mk
CppunitTest_svx_unit.mk
Executable_gengal.mk Cut down on -pthread/-lpthread proliferation 2019-04-25 21:27:43 +02:00
JunitTest_svx_unoapi.mk
Library_svx.mk WIP: Further preparations for deeper Item changes 2019-04-25 19:59:04 +02:00
Library_svxcore.mk
Library_textconversiondlgs.mk
Makefile
Module_svx.mk
Package_gengal.mk
README
UIConfig_svx.mk Add new list panel to Impress Properties deck 2019-04-15 11:24:43 +02:00

Contains graphics related helper code. Lots of the draw and impress code is in this shared library.

xoutdev
this is where a lot of wht work would happen to move to the canvas. (what does that mean?)

svdraw
transparent gradient stuff. [seriously? surely much more, too]

== SdrObject ==

The shapes you can see in LibreOffice (like rectangle, etc.) are SdrObjects.
They are declared as a hierarchy:

SdrObject <- SdrAttrObj <- E3dObject <- E3dCompoundObject <- E3dCubeObj
    ^ ^ ^             ^            ^              | | ^ ^
    | | |             |            |              | | | +--- E3dExtrudeObj
    | | |             |            |              | | +----- E3dLatheObj
    | | |             |            |              | +------- E3dPolygonObj
    | | |             |            |              +--------- E3dSphereObj
    | | |             |            +--- E3dScene...
    | | |             |
    | | |             +--- SdrTextObj <- SdrObjCustomShape...
    | | |                   ^ ^ ^ ^ ^
    | | |                   | | | | +--- SdrEdgeObj...
    | | |                   | | | +----- SdrMeasureObj...
    | | |                   | | +------- SdrPathObj...
    | | |                   | +--------- SdrRectObj...
    | | |                   +----------- SdrTableObj...
    | | +--- SdrObjGroup...
    | + ---- SdrPageObj...
    +------- SdrVirtObj...

The above is incomplete of course.

== SdrModel / SdrView ==

Copied from svdview.hxx:

  First of all the app creates a SdrModel.
  Then it opens a Win and creates a SdrView.
  ShowSdrPage() announces a page at SdrView.
  It's possible to show SdrView in any Wins at once.

  SdrView can show as many Wins as it wants at once. Pages are announced
  or checked out with the help of ShowSdrPage()/HideSdrPage(). For every announced
  page there is a SdrPageView instance in container aPages. If more than one page
  is showed, you have to pay attention that the offset parameter of ShowSdrPage()
  is conformed to the size of the page (to prevent overlapping of two pages).

SdrView itself is inherited from many objects in a chain of inheritance (all
that starts with SdrPaintView - that is itself inherited from few classes
too):

SdrPaintView <- SdrSnapView <- SdrMarkView <- SdrEditView <- SdrPolyEditView
                                                                   ^
  +----------------------------------------------------------------+
  |
  SdrGlueEditView <- SdrObjEditView <- SdrExchangeView <- SdrDragView
                                                                   ^
  +----------------------------------------------------------------+
  |
  SdrCreateView <- SdrView

From SdrView on, it is not flat, but a real hierarchy again.

== Drawing Layer / SdrObject(s) ==

See drawinglayer/README for general information about drawinglayer.

Below is the class diagram that comes from
http://www.openoffice.org/marketing/ooocon2006/presentations/wednesday_g11.odp,
slide number 6.

.------- Model --------------.      .------- View -----------------------------------------.
| SdrObject - ViewContact    | 1..* | ViewObjectContact                                    |
|              getChild()    |------|    getPrimitiveList()  -----> Object(s) ---> SdrView |
|              getVOC()      |      |    getRecPrimitiveList()      Contact                |
|              getViewInd... |      |________|_____________________________________________|
| ...ependentPrimitiveList() |               |
|____________________________|            generates
                                             |           ______
                                             V          /      |
                                   .----------------------.    |
                                   | basePrimitive        |    |
                                   |   getRange()         |<---'
                                   |   getDecomposition() |
                                   |______________________|

For SdrObjects, there are own DrawingLayer primitives in
svx/source/sdr/primitive2d

The ViewContact / ViewObject / ViewObjectContact are in svx/source/sdr/contact
Decomposes the SdrObjects, and does all sort of operations on them.

If the number of visualizable objects (e.g. SdrObjects) is X, and the number of
SdrViews is Y, then:

- there are X ViewContact instances (1:1 relation with a visualizable object)
- there are Y ObjectContact instances (1:1 relation with an SdrView)
- there are X*Y ViewObjecContact instances (1:N relation to both
  visualizable objects and SdrViews)