Quoting Sven Neumann ([EMAIL PROTECTED]):
> Hi,
>
> Hallvar Helleseth <[EMAIL PROTECTED]> writes:
>
> > How about IDirectFBVideoProvider::GetChannels()
> >
> > which returns something like DFBVideoChannels:
> >
> > typedef enum {
> > DVF_NONE = 0x000,
> > DVF_TUNER = 0x001,
> > DVF_CHAPTERS = 0x002,
> > DVF_ANGLES = 0x004
> > DVF_SUBTITLES = 0x010,
> > DVF_AUDIO = 0x020
> > /* More ?*/
> > } DFBVideoChannelsClass;
>
> [...]
>
> no way we will ever integrate all this into the DirectFB API.
>
> > IMHO, this would be very usefull for a DirectFB developer.
> > I know you want a small library, but if you've first decided to have
> > IDirectFBVideoProvider you might as well make it very usefull.
>
> I do believe that the current IDirectFBVideoProvider API sucks and
> needs to be changed but we should limit it to graphics-related
> stuff. Anything that is not closely related to bringing the video
> data to a DirectFB surface should be implemented outside DirectFB.
There could be a package outside of DirectFB adding all this stuff,
I wouldn't add that to the DirectFB core api. Besides that tuning v4l
and dvb is totally different.
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
Convergence GmbH
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-dev" as subject.
