| Type | required |
| Title | New classes for embedded objects |
| Posted by | [EMAIL PROTECTED] |
| Affected | ,whole office |
| Effective from | CWS MAV09 |
Summary
The following SO3 classes have been removed:
SvPersist
SvEmbeddedObject
SvInPlaceObject
SfxInPlaceObject
SvOutPlaceObject
The class SfxObjectShell now directly derives from SotObject.
All ObjectShell classes in the applications now only derive from SfxObjectShell.
Two new UNO based services are available, one of them provides the functionality of an embedded object on top of the framework API for documents (service com.sun.star.document.OfficeDocument), the other one on top of the Windows COM API. These implementations can be found in the new module embeddedobj.
Two helper classes are provided that simplify the handling of embedded objects:
comphelper::EmbeddedObjectContainer
svt::EmbeddedObjectRef
All necessary code changes have been done, so action is required only for code that is not integrated into SRC680 m54.
Description
Embedded objects are now handled by a UNO services based
implementation, the application classes that derive from
SfxObjetcShell are not related to embedded objects anymore, instead of
this the whole world of embedding and linking is built upon UNO
interfaces.
The implementation of the object part of this world is built upon the
framework APIs ( css.frame.XFrame, css.frame.XModel etc.) and does not
use any VCL or SFX based code.
An important change is that embedded object are not forced into having
a storage, they can either stream or storage based persistence. OTOH
this leads to the requirement that embedded objects can't have any
persistence outside a container, they always are associated with a
container storage.
Developer documentation is under construction.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
