office-gobmx/sfx2
Caolán McNamara 8c809777e6 coverity#705886 Dereference before null check
Change-Id: I707dcfb324760a7058cb0abcb2eca7819e0568e4
2014-03-20 15:38:41 +00:00
..
doc
inc sfx2,svl: prefer passing OUString and OString by reference 2014-03-13 11:05:53 +02:00
qa sfx2: simplify deprecated XTypeProvider.getImplementationId 2014-03-10 17:39:58 +01:00
sdi Remove visual noise from sfx2 2014-02-26 08:12:10 -06:00
source coverity#705886 Dereference before null check 2014-03-20 15:38:41 +00:00
uiconfig/ui convert load template dialog to .ui 2014-03-11 12:18:55 +00:00
util constructors: Fix typo preventing extensions loading. 2014-03-06 10:05:38 +01:00
AllLangResTarget_sfx2.mk convert load template dialog to .ui 2014-03-11 12:18:55 +00:00
CppunitTest_sfx2_metadatable.mk
JunitTest_sfx2_complex.mk
JunitTest_sfx2_unoapi.mk
Library_qstart_gtk.mk
Library_sfx.mk
Makefile
Module_sfx2.mk
README sfx2: add link to SFX2 dispatch documentation on OOo Wiki 2014-03-14 12:29:46 +01:00
UIConfig_sfx.mk convert load template dialog to .ui 2014-03-11 12:18:55 +00:00

SFX is the "old" framework, used for historical reasons.

An attempt of documentation of this module is located in [git:sfx2/doc].

It contains base classes for document model, view and controller, used
by "old" applications like sw, sc, sd (while "new" applications
are based on the "new" UNO based framework in "framework").

The SFX framework is based on dispatching slots identified by integers
(SlotIDs) to SfxShells, and there is a dedicated IDL compiler (svidl)
involved that generates C++ slot headers from SDI files in modules' sdi/
subdirectory.

Documentation about SFX dispatch, SDI etc.:
https://wiki.openoffice.org/wiki/Framework/Article/Implementation_of_the_Dispatch_API_In_SFX2

Document load/save code is maintained in [git:sfx2/source/doc/docfile.cxx]
SfxMedium class, which handles all the twisty load and save corner cases.

[git:sfx2/source/appl/sfxhelp.cxx] Start procedure for the online
help viewer top level window; handling of help URL creation and
dispatch.

There are also some UNO services here that could really be implemented
anywhere, e.g. the DocumentProperties or DocumentMetadataAccess.