Difference between revisions of "Documentation/DevGuide/OfficeDev/Framework API"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (1 revision(s))
m
 
(3 intermediate revisions by one other user not shown)
Line 6: Line 6:
 
|NextPage=Documentation/DevGuide/OfficeDev/Frame-Controller-Model Paradigm in OpenOffice.org
 
|NextPage=Documentation/DevGuide/OfficeDev/Frame-Controller-Model Paradigm in OpenOffice.org
 
}}
 
}}
{{DISPLAYTITLE:Framework API}}
+
{{Documentation/DevGuideLanguages|Documentation/DevGuide/OfficeDev/{{SUBPAGENAME}}}}
The framework API does not define an all-in-one framework with strongly coupled interfaces, but defines specialized frameworks that are grouped together by implementing the relevant interfaces at {{PRODUCTNAME}} components. Each framework concentrates on a particular aspect, so that each component decides the frameworks it wants to participate in.
+
{{DISPLAYTITLE:Framework API}}
 +
The framework API does not define an all-in-one framework with strongly coupled interfaces, but defines specialized frameworks that are grouped together by implementing the relevant interfaces at {{AOo}} components. Each framework concentrates on a particular aspect, so that each component decides the frameworks it wants to participate in.
  
 
Currently, there are two of these frameworks: the ''component framework'' that implements the frame-controller-model paradigm and the ''dispatch framework'' that handles command requests from and to the application environment. The controller and frame implementations form the bridge between the two frameworks, because controllers and frames implement interfaces from the component framework and dispatch framework.
 
Currently, there are two of these frameworks: the ''component framework'' that implements the frame-controller-model paradigm and the ''dispatch framework'' that handles command requests from and to the application environment. The controller and frame implementations form the bridge between the two frameworks, because controllers and frames implement interfaces from the component framework and dispatch framework.
Line 14: Line 15:
  
 
{{PDL1}}
 
{{PDL1}}
[[Category: Office Development]]
+
 
 +
[[Category:Documentation/Developer's Guide/Office Development]]

Latest revision as of 17:29, 2 January 2021



The framework API does not define an all-in-one framework with strongly coupled interfaces, but defines specialized frameworks that are grouped together by implementing the relevant interfaces at Apache OpenOffice components. Each framework concentrates on a particular aspect, so that each component decides the frameworks it wants to participate in.

Currently, there are two of these frameworks: the component framework that implements the frame-controller-model paradigm and the dispatch framework that handles command requests from and to the application environment. The controller and frame implementations form the bridge between the two frameworks, because controllers and frames implement interfaces from the component framework and dispatch framework.

The framework API is an abstract specification. Its current implementation uses the Abstract Window Toolkit (AWT) specified in com.sun.star.awt, which is an abstract specification as well. The current implementation of the AWT is the Visual Component Library (VCL), a cross-platform toolkit for windows and controls written in C++ created before the specification of com.sun.star.awt and adapted to support com.sun.star.awt.

Content on this page is licensed under the Public Documentation License (PDL).
Personal tools
In other languages