To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=107450





------- Additional comments from m...@openoffice.org Wed Dec  9 14:07:21 +0000 
2009 -------
An EditEngine/Outliner library should contain at least the content of the
current svx/source/editeng and svx/source/outliner folders.

This automatically will also include the XML Im/Export in
svx/source/xml/xmltxtimp.cxx and svx/source/xml/xmltxtexp.cxx, this again will
pull in symbols from svx/source/unoedit and svx/source/unodraw. The latter
definitely contains a lot of stuff that shouldn't be included as it depends on
the svdraw code. So it is clear that as a first step we have to clean up the uno
mess.

An obvious problem is the SvxItemPropertySet implementation. Deep inside it uses
SdrObject::GetGlobalDrawObjectItemPool() and so binds itself to svdraw. If this
implementation shall be shared between EditEngine and svdraw, we must first have
a global item pool for the EditEngine and then initialize each
SvxItemPropertySet with the pool it shall use.

The first is easy as there already is a method to create an item pool for an
EditEngine. We just miss a static instance of it that can be created on demand
(like the global DrawObject item pool). 

Changing interface and implementation of SvxItemPropertySet is simple but needs
some work as it is also used in other modules (forms, reportdesign, sd, sc, sw).

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to