[MPlayer-dev-eng] life after the 0.90 release...

[Jiri Svoboda]

Hi,

> 2. cleanup libvo  [Pontscho, ???]
> 
> - we should finally review query_format() answers, most of 
> the drivers still don't set flags they should
> - all vo drivers should follow the libvo.txt api std, 
> especially allowing zero, 1 or more than one calls to 
> config() between init/uninit.
> - add mpi (draw_image) support to main vo drivers, remove old 
> draw_slice/draw_frame
> - remove redundant code from vo drivers, like osd (only where 
> the same functionality can be reached using -vop expand), sw 
> scaler etc.
> - cleanup X11 stuff - move more common code to x11_common, 
> like window opening.
> - better interfacing between libvo and gui - the gui 
> shouldn't control the vo window directly, but via control() 
> calls. i mean fullscreen etc here.

Could there be call after frame is decoded? Like
VOCTRL_FRAME_RENDER_COMPLETE. To allow background transfer/(stretch)blit
of buffer as preparation for osd drawing and flip.

> 8. sub/osd fonts
> 
> - support for libft2-supported fonts (ttf,etc)
>   and generate font table+bitmap at mplayer startup
> - color subtitles?
> - subtitle bitmap cacheing?
> 
> Comments? :)

Following comments are maybe obsolente (I saw some code for OSD but
didn't found vo driver using it)

Support for color keying - subtitles can be drawn into another surface.
This is possible with current api, but there are still some issues.
-> export bouncing boxes to vo_driver - in current state vo_driver
doesn't know them and cleaning whole surface is not good solution -
common code wellcome (I think already at least partly implemented - is
there any example / doc?) 
    Or make some callback stuff which will for each bbox call vo_driver
cleaning rutine.

->maybe it would be good to remember osd state for last 2 or 3 frames -
in double/triple buffering are buffers constanty reused so if we have
buffer 2/3 frames old we will be able to do just update instead of
drawing whole OSD.


						JS