[Wvware-devel] Re: [libwmf] Upcoming version 0.1.19!

[Frederic V. <vi...@lc...>]

Martin Vermeer <mar...@hu...> writes:

> > cell.wmf is now fully and correctly processed. Martin said this
> > afternoon : the day we will be able to process cell.wmf, we will ship
> > 0.2. You know what you have to do (if my commit worked) !
>  
> Actually I said v. 1.0 (IIRC). But before the other back-ends
> catch up with .fig, perhaps we should be modest ;-)

Especially as it looks like it will take time to wmftopng and xwmf to
be able to process cell.wmf. It looks like there is something wrong
with the "userdata" stuff in them (the clever wmftofig is just
ignoring the "userdata" :-)). 

> So I propose that those people that *have coding going on* that
> they want into 0.1.19, to either commit/submit it today or tomorrow,
> or tell me to wait for them. I want to bring out libwmf-0.1.19
> latest this weekend.

I should be able to fix the text angle problem this evening (I will
have a good test wmf). Perhaps I should also quickly implement some
lacking features as arcs... 


> ...and then: code freeze, and libwmf-0.2!
> 
> I think this is justified given the huge progress and maturity
> of .fig output. You can always get bitmapped formats through
> fig->eps->png etc. so the eps, png work is not quite as urgent
> now any more. (Although we want it!)

I would not say "maturity" as there are a lot of features lacking in
wmftofig (a lot of functions have no code at all). I agree we should
do as soon as possible a 0.1.19 release. But I am not sure we should
do a code freeze, and libwmf-0.2 release before at least all the
simple functions in wmftofig are implemented (we can perhaps forget
the flood paintings and stuff like that for the moment).

These were my 2 cents.


Frédéric.