Hi Daniel,
On Fri, 2008-11-21 at 17:15 +0100, Daniel Rentz wrote:
> > 1. Leave the dependency, merge ooxml02 for 3.1, and work to remove it
> > for 3.2+.
..
> I don't like (2). I think best thing is to do (1), and think about (3)
> for 3.x as you suggested.
That sounds great; just to give a quick rational as to why this
approach. While clearly a separate UNO component, or things living in
oox is the end-goal, I'm a fan of step-wise re-factoring - such that we
can prove that nothing broke during the process, and such that there is
only one copy of the code to maintain and develop at any time.
My hope is that by adding OOX export here, then going on to re-factor
the existing combined filter to use the UNO interfaces to build it's
model, we can incrementally move to the point that chipping that whole
export chunk off into it's own component (or into oox) becomes easy -
while still being to prove that nothing broke.
That way, hopefully we get where we want to go, while keeping
everything working in the meantime; that is the thinking anyway - does
it make sense ?
Regards,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
