Difference between revisions of "Documentation/DevGuide/JavaBean/Using the OOoBean"
m |
|||
Line 6: | Line 6: | ||
{{Documentation/DevGuideLanguages|Documentation/DevGuide/JavaBean/{{SUBPAGENAME}}}} | {{Documentation/DevGuideLanguages|Documentation/DevGuide/JavaBean/{{SUBPAGENAME}}}} | ||
{{DISPLAYTITLE:Using the OOoBean}} | {{DISPLAYTITLE:Using the OOoBean}} | ||
− | The Java class <code>OOoBean</code> can be instantiated directly, or application classes can be derived from this class. If a real Java Bean is to be created, which for example can be used in Java Bean UI builders, it has to be subclassed. The application class then might use the UNO bootstrapping mechanism to find the <code>OOoBean</code>, {{ | + | The Java class <code>OOoBean</code> can be instantiated directly, or application classes can be derived from this class. If a real Java Bean is to be created, which for example can be used in Java Bean UI builders, it has to be subclassed. The application class then might use the UNO bootstrapping mechanism to find the <code>OOoBean</code>, {{AOo}} and its API classes. This mechanism is not built into <code>OOoBean</code> itself because it can not be used to find itself. And once the <code>OOoBean</code> class has been found, you intrinsically also find the {{AOo}} installation and the API classes. |
− | A standard {{ | + | A standard {{AOo}} is a prerequisite. The {{AOo}} executable, as well as the UNO libraries and runtime, is found using the Java Class Loader. Moving or copying the needed class files will not result in a working <code>OOoBean</code>. |
− | {{Warn|Since the Office Bean uses a native peer to render {{ | + | {{Warn|Since the Office Bean uses a native peer to render {{AOo}} documents, Swing components, such as drop-down menus or list boxes appear behind it, or they are not displayed at all. One way to avoid this is by exclusively employing AWT components when using the Office Bean. Another, but only partial, solution is to tell Java Swing to create heavy weight windows for popup menus: <tt>JPopupMenu.setDefaultLightWeightPopupEnabled</tt>.}} |
{{Warn|Currently the Office Bean is not available for Mac (see issue 54172 for more details).}} | {{Warn|Currently the Office Bean is not available for Mac (see issue 54172 for more details).}} |
Latest revision as of 17:26, 21 December 2020
The Java class OOoBean
can be instantiated directly, or application classes can be derived from this class. If a real Java Bean is to be created, which for example can be used in Java Bean UI builders, it has to be subclassed. The application class then might use the UNO bootstrapping mechanism to find the OOoBean
, Apache OpenOffice and its API classes. This mechanism is not built into OOoBean
itself because it can not be used to find itself. And once the OOoBean
class has been found, you intrinsically also find the Apache OpenOffice installation and the API classes.
A standard Apache OpenOffice is a prerequisite. The Apache OpenOffice executable, as well as the UNO libraries and runtime, is found using the Java Class Loader. Moving or copying the needed class files will not result in a working OOoBean
.
Content on this page is licensed under the Public Documentation License (PDL). |