[Libvisual-devel] Next release cycle plans!

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

Ok, 0.2.0 out the door (almost), what is next!

0.2.0 took awful long to release, so I think we should do quicker 
releases next cycle.

We will bump up to 0.3.0, and use 0.2.0 as a 'stable branch'

The 0.3.0 releases can be seen as 'experimental, unstable'...
but they will probably end up being much better than 0.2.0 anyway.

I want a quick release cycle within 0.3.0, something like a release
every month. What I also think is important is to get libvisual-display
and libvisual-widgets out in the public. We might want to include their 
source trees into that of libvisual itself, not sure how to do that
neatly tho, since they dynamicly link to libvisual, we'll just look
into that.
________________________________________________________________________

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.

	Libvisual:
		Setup our own memcpy/memset wrappers and accelerate
			these with mmx/sse etc etc.
		VisParamSerialize, to make it possible to
			save paramcontainers to a config registry.
		Make sure that VisUI and ParamContainer can live on
			after a plugin has been destroyed.
		Have a dynamic prefered FPS requester in VisActor.
		On the fly depth change request from within plugins.
		VisUI: Color chooser button.
		VisUI: List selection.
		GLIB thread backend.
		.desktop files for plugins (???).
		Flags in plugin type string example:
			"Libvisual:core:actor.[avs]" for special AVS
			plugins.
		BIG/LITTLE endianess fixes!!!
		MMX versions of 24/16/8 bilinear scalers.
		Nearest scalers in MMX (???).
	
	Libvisual-display:
		This will be the first public release!

		Working basics.
		Fullscreen support.
		Fullscreen modes list.
		FPS limiter helper functions
		Any more Vitaly ?

	Libvisual-plugins:
		Unmirror corona.
		Finish the flower plugin (enable notch.c)
		Finish dancing particles (Fix bugs, make reentrant)


	Extra:
		Standalone client using libvisual-display and the
			libvisual input plugins!

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.

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

	Libvisual-plugins:
		Port G-Force over to our own VisScript VM.
		Try and use MMX within G-Force.

0.3.2:
	Libvisual:
		Redo VisAudio.



This is roughly what I want to see done for these releases.


Regarding libvisual-avs:

Libvisual-avs will be our version of the winamp-avs (advanced visual 
studio) system. It will be backwards compatible with winamp-avs,
however it will be capable of doing more than winamp-avs does.

This project is quite some work, so it will take a few months till we 
get some real result in this department.

Well guys, let me know what you think!!!, and let's damn hack on this 
one.

Cheers,
Dennis