guglbuster.blogg.se - Xmenu user defined location

XMENU USER DEFINED LOCATION WINDOWS

The name of this service and the interface name .XDesktop were kept for compatibility reasons. The root frame of this hierarchy was called the desktop frame.

XMENU USER DEFINED LOCATION WINDOWS

The name of this service originates at StarOffice 5.x, where all document windows were embedded into a common application window that was occupied by the StarOffice desktop, mirroring the Windows desktop. From the desktop you can load viewable components, access frames and components, terminate the office, traverse the frame hierarchy and dispatch command requests. The desktop is the root frame for this hierarchy.

All LibreOffice application windows are organized in a hierarchy of frames that contain viewable components. The .Desktop service is the central management instance for the LibreOffice application framework. The dispatch framework handles command requests sent by the GUI. The component framework follows a special Frame-Controller-Model paradigm to manage components viewable in LibreOffice. The framework API has two parts: the component framework and the dispatch framework. The desktop environment's functions are carried out by the framework API. The desktop environment consists of the desktop service and auxiliary objects. The LibreOffice application environment is made up of the desktop environment and the framework API. All these things are discussed in this chapter. It is also possible to extend the functionality of LibreOffice by replacing the services mentioned here by intercepting the communication between objects or by creating your own document type and integrating it into the desktop environment. The interfaces and services common to all document types and how documents are embedded in the surrounding application environment are discussed.

In most cases, users use the functionality of LibreOffice by opening and modifying documents. It assumes that you have read the chapter First Steps, and that you are able to connect to the office and load documents. This chapter describes the application environment of the LibreOffice application.

2.9.16 Removing metadata from a document.

2.9.15 Mapping from URIs to document entities.

2.9.14 Reading metadata from a document.

2.9.11 Finding in-content metadata at a cursor position.

2.8.2 Implementing the LibreOffice SSO API.

2.4.15.6.4 TypeDetection.xcu DetectServices Entry.

2.4.15.6.3 The ExtendedTypeDetection Service Implementation.

2.4.15.6.2 Extending the File Type Definition.

2.4.15.6.1 Requirements for Deep Detection.

2.4.15.5.1 Evaluating XExportFilter Parameters.

2.4.15.4.1 Evaluating XImportFilter Parameters.

2.4.15.3 Writing the Filtering Component.

2.4.11 Sample configuration for an xslt based filter.

2.4.10 Sample configuration for an XML based filter.

2.4.9.1 Sample configuration for an API based filter.

2.4.7 Type Detection and its Configuration.

2.4 Integrating Import and Export Filters.

2.2.3.10 A Comment on Search and Replace.

2.1.2 LibreOffice Clipboard Data Formats.

1.7.3.2 Listening for Status Information.1.5.3 Setting Components into Frame Hierarchies.1.4.3.5 Document Specific Controller Services.1.4.2.3 XDispatchProvider and XDispatchProviderInterception.1.4.1 Getting Frames, Controllers and Models from Each Other.1.2.2.2 Communication through Dispatch Framework.1.2.1 Frame-Controller-Model Paradigm in LibreOffice.