Re: [Libvisual-devel] libvisual-display updates, and some extras

[Dennis S. <sy...@yo...>]

On Fri, 2004-10-15 at 00:49 -0300, Duilio Javier Protti wrote:
> > On the list for 0.2.0:
> > * Good error reporting.
> > * VisUI.
> 
> Good for both!
> 
> > * Gtk1 and Gtk2 VisUI builder.
> 
> This surprise me. I was believed that final UI building would be 
> responsibility of the programmer.

It is, but since we have to write these widgets anyway, in gtk1 for
xmms and in gtk2 for bmp, I don't think it hurts to generalise them
in a separated libvisual-widgets package, so everyone can use them
easily. Aka that way we make the code reusable.

> > * API reviews.
> > * Portability fixes.
> > * VisVideo it's scaler.
> > * Libvisual-display support in clients.
> > * All kind of things that come up.
> > 
> > When the error reporting stuff is in place, Gustavo
> > will be working on the python bindings, which will
> > enable the freevo (http://freevo.sf.net) project to
> > use libvisual.
> > 
> > This is our plan of universal domination, anyone comments ?
> > 
> > Cheers,
> > Dennis
> 
> Just one more comment. I think would be better to keep release on 0.1.8.
> Why? just because of the future libtool versioning system. Remember that
> when we switch to the libtool system, we must start from 0.0.0. The
> question is, what we will do with the current 0.1.x series? I was
> thinking on just skip this series and jump to 0.2.x series (0.1.x would
> became like a devel series, which exactly was it is). This way there
> would be no confusse with people using old packages.

Maybe it's better to use #defines for setting version anyway, so we have
more control regarding that, I'd like to do a 0.2.0 to sign it's 
significancy, and because it will be major API incompatible.

> Other possibility would be to introduce libtool versioning right now,
> but I think is not the moment yet. Remember the current:revision:age
> scheme of libtool (which is reflected on the package number). 'current'
> must be incremented every time you change an actual API function, and
> that will happen for a while on libvisual, so we will have
> libvisual-10.0.4 really soon :-)

Maybe we should use a different versioning scheme after all... not sure