Hello,
yesterday, a lot of changes have been checked in for childworkspace
"ooxml03". Obviously these changes are the result of weeks or even
months of "private" work, without giving others the chance to give
comments early.
As already discussed for childworkspace "ooxml02", the code module "oox"
has been introduced to contain filter code for the OOXML file format,
and has been designed to be independent from other core modules and
application code. This included the requirements to be independent
during build and to be independent during runtime.
The childworkspace ooxml02 already broke the latter in the first run by
becomming dependent from sc, but we found a compromiss by separating
filter code contained in sc into an own library. Nevertheless, sc still
contains a build dependency to oox (which is part of the compromiss of
course).
Now, I see that ooxml03 introduces dependencies to svx, and that it has
been started to use core classes (vcl Graphic, svx filter code, tools
String) inside oox. I strongly disagree to do so. Especially the toiols
String class is deprecated and its use in new code is discouraged. In
the past, we have prevented this with a lot of effort, by using and
extending the OOo API and related helper modules (e.g. comphelper and
related). Please consider to rework the changes to ged rid of these
dependencies.
Regards
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
