Re: [Libvisual-devel] Next release cycle plans!

[Duilio J. P. <dp...@fc...>]

> That said, the plan:
> 
> 0.3.0:
> 	General:
> 		Code reviewing.
> 		Bug fixes.
> 		Speed improvements (aka more mmx hacking).
> 		A better autogen.sh, and review our build trees.

I can work on autogen.sh this weekend.

> 	Libvisual:
> 		Setup our own memcpy/memset wrappers and accelerate
> 			these with mmx/sse etc etc.

I see on the Linux kernel (include/asm-i386/string.h):

static __inline__ void *__memcpy3d(void *to, const void *from, size_t
len)
{
	if (len < 512)
		return __constant_memcpy(to, from, len);
	return _mmx_memcpy(to, from, len);
}

so it looks like MMX pays well on buffers > 512 bytes long

> 0.3.1:
> 	Libvisual:
> 		Introduce VisScript, our math expression evaluator, to 
> 			be used by libvisual-avs and G-Force.
> 			(This is the initial VM version, after this
> 			it will have a long development cycle to go)
> 		Introduce VisPipeline, advanced pipeline connection of
> 			VisActors, VisMorphs, VisTransforms.
> 		Rewrite VisBin using VisPipeline.

Really good!

> 	Libvisual-widgets:
> 		Good working gtk2 widget.
> 		Good working gtk1 widget.
> 		Good working QT widget.

I must finish the gtk1-widget!!! I will work on this


Bye,
Duilio.