From: Dennis S. <sy...@yo...> - 2004-10-14 22:45:35
|
I mate a list of things I would like to see for 0.2.0. 0.2.0 is going to be a big release and I suspect that we're going to need some time to get it all out, for that reason we can use all the help, also with the 'little' things. If someone likes to add things to this list, please go ahead. 0.2.0 goals: libvisual: Good error reporting through VisError. VisVideo scaler. visual_video_overlay fixen, simplifyen. VisUI. API review here and there. Portability fixes: The issue on freeBSD. BIG/LITTLE ENDIAN still pending!!! libvisual-display: Basic functionality working so it can be used in clients. A plain X11 plugin as well. libvisual-widgets: Gtk1 VisUI Builder. Gtk2 VisUI Builder. libvisual-bmp: Good Beep Media Player client. with config dialog. libvisual-python: Work further on the bindings (this depends on VisError). libvisual-xmms: The about dialog for plugins in the same style as that of the xmms plugin itself. Fiddling, stop quit stop quit, config stuff etc, stress testing can cause crashes still I suspect this is due thread synchronize problems. libvisual-plugins: Port corona. Port dancing particles. Use plugin flags. Look at how to deal with alsa issues when the resource 'is already used'. Cheers, Dennis |
From: Duilio J. P. <dp...@fc...> - 2004-10-15 03:35:14
|
> I mate a list of things I would like to see for 0.2.0. > > 0.2.0 is going to be a big release and I suspect that we're > going to need some time to get it all out, for that reason > we can use all the help, also with the 'little' things. > > > If someone likes to add things to this list, please go > ahead. > > 0.2.0 goals: > libvisual: > Good error reporting through VisError. > VisVideo scaler. I can optimize more my ugly prototype :-) > visual_video_overlay fixen, simplifyen. > VisUI. The hardest work. > API review here and there. I want to start here with the const pointers I have suggested. May I can? > Portability fixes: > The issue on freeBSD. This is for me. > BIG/LITTLE ENDIAN still pending!!! Oh yes. My video_scaler have to define his owns macros. > > libvisual-display: > Basic functionality working so it can be used in > clients. > A plain X11 plugin as well. > > libvisual-widgets: > Gtk1 VisUI Builder. > Gtk2 VisUI Builder. Oh, now I understand... > libvisual-bmp: > Good Beep Media Player client. with config dialog. > > libvisual-python: > Work further on the bindings (this depends on VisError). > > libvisual-xmms: > The about dialog for plugins in the same style as that > of the xmms plugin itself. Good idea! > Fiddling, stop quit stop quit, config stuff etc, stress > testing can cause crashes still > I suspect this is due thread synchronize > problems. > > libvisual-plugins: > Port corona. > Port dancing particles. > Use plugin flags. > Look at how to deal with alsa issues when the resource > 'is already used'. There are any plans for the website? Bye, Duilio. |
From: Andrew G. <and...@bl...> - 2004-10-15 06:42:55
|
On Friday 15 October 2004 04:50, Duilio Javier Protti wrote: > > There are any plans for the website? > I still have to get the menu editors, page editors and gallery up yet... after that there may be some more stuff to do. |
From: Dennis S. <sy...@yo...> - 2004-10-15 12:50:57
|
On Fri, 2004-10-15 at 00:50 -0300, Duilio Javier Protti wrote: > > I mate a list of things I would like to see for 0.2.0. > > > > 0.2.0 is going to be a big release and I suspect that we're > > going to need some time to get it all out, for that reason > > we can use all the help, also with the 'little' things. > > > > > > If someone likes to add things to this list, please go > > ahead. > > > > 0.2.0 goals: > > libvisual: > > Good error reporting through VisError. > > VisVideo scaler. > > I can optimize more my ugly prototype :-) Please do so, make it modulair, so you can start different scalers using a define. like visual_video_scale (VISUAL_VIDEO_SCALE_NEAREST, ...).. I'd like to have a NEAREST and BILINAIR scaler :).. Also make sure that the actual scale function won't be super big, split up in smaller static functions, that append at the end of lv_video.c > > visual_video_overlay fixen, simplifyen. > > VisUI. > > The hardest work. Yep, will start on the basic API really soon. > > API review here and there. > > I want to start here with the const pointers I have suggested. May I > can? You can, but please send patches to the list first so I can review them! > > Portability fixes: > > The issue on freeBSD. > > This is for me. Great, thank you :) > > BIG/LITTLE ENDIAN still pending!!! > > Oh yes. My video_scaler have to define his owns macros. I doubt if it's needed for the scalar, but lv_bmp still needs to be adjusted. > > libvisual-widgets: > > Gtk1 VisUI Builder. > > Gtk2 VisUI Builder. > > Oh, now I understand... Aah, alright!, cool :). Eventually we could have a QT widget and VisVideo inbuffer method as well. > > libvisual-xmms: > > The about dialog for plugins in the same style as that > > of the xmms plugin itself. > > Good idea! You're on that I assume ? Cheers, Dennis P.S. upcoming release is going to rock guys ;) |
From: Vitaly V. B. <vit...@us...> - 2004-10-15 09:25:57
|
On Fri, 15 Oct 2004 00:45:42 +0200 Dennis Smit <sy...@yo...> wrote: > 0.2.0 goals: > libvisual-display: > Basic functionality working so it can be used in clients. > A plain X11 plugin as well. I think it's possible. More todos: Carefull error and input params checking. Critical. Ability to runtime configuration of render targets (VisParam?) ...something I forgot :) -- Vitaly GPG Key ID: F95A23B9 |
From: Dennis S. <sy...@yo...> - 2004-10-15 12:54:42
|
On Fri, 2004-10-15 at 12:26 +0300, Vitaly V. Bursov wrote: > On Fri, 15 Oct 2004 00:45:42 +0200 > Dennis Smit <sy...@yo...> wrote: > > > 0.2.0 goals: > > libvisual-display: > > Basic functionality working so it can be used in clients. > > A plain X11 plugin as well. > I think it's possible. More todos: > Carefull error and input params checking. Critical. > Ability to runtime configuration of render targets (VisParam?) Cheers to that, VisParam is indeed the way to do runtime configuration! You could define a set of standard parameters, and document those, I'm sure you get this nailed :) Cheers, Dennis |