Re: [Freevo-devel] Re: DirectFB, G400, CRTC2, overscan and skins

[Brian J. M. <bff...@in...>]

On Wed, Dec 18, 2002 at 11:06:56AM +0100, Dirk Meyer wrote:
>=20
> Interessed *jumpupanddown* Please send the patches, I would like to
> use the real tv out.

Sent to the list, in this thread.

> The DXR3 people have the same problem. I will change the skin rescale
> soon (when I use the DirectFB-stuff with 720x576 (PAL)). I want the
> skin to know it's resolution. We will have _one_ skin file for
> blue_round1. It's 800x600 and in the xml file I want:
>=20
> <skin include=3D"..." width=3D"800" height=3D"600">

OK.  This concept of width and height gets interesting when you use
the CRTC2 in TV-Out mode.  It's not selectable.  It's only ever two
values, 720x480 for NTSC and some other single value that I don't
recall, for PAL.

So the whole idea of the user specifying screen dimensions does not
make sense with TV-Out.  But the question becomes how to handle this
within freevo?  In non-TV-Out modes, it can be user selectable, in
TV-Out modes, it cannot.  This needs to be resolved.  It also needs to
query for dimensions in the case of TV-Out mode.

> When you load this skin with a different resolution, all values should
> be scaled down.=20

Yeah.  That works.  I just created the following skin file
(skins/xml/type1/blue_round1_720x480.xml):

<?xml version=3D"1.0" ?>
<freevo>
 =20
  <skin include=3D"blue_round1_800x600" scale=3D"0.8">
   =20
    <!-- Settings for a normal menu -->
    <menu type=3D"all">
      <background image=3D"../../images/aubin_bg2.png"/>
    </menu>
   =20
    <mp3>
      <background image=3D"../../images/aubin_bg2.png"/>
    </mp3>
   =20
    <extendedmenu type=3D"tv">
      <background image=3D"../../images/aubin_bg2.png"/>
    </extendedmenu>
  </skin>
</freevo>

but it's just smaller with the same left margin.

Really, this whole skin-scaling thing would work much better if the
skin was always drawn around the center-point of the screen rather
based on the left.

Scaling both vertically and horizontally would be an added bonus.

> This problems will be gone with the new skin resize stuff. And all
> skins shouldn't use the border-pixel because of the overscan.=20

I hate to sound impatient, but any ETA on the new skinning stuff?

> There are some recording facilities in the CVS version by Krister. I
> don't have a tv card, so I never tested it.

I must have missed them.  Where 'bouts?  I will go code trawling in
the meanwhile...

> Looks nice.

Thanks.  A lot of work has gone into the scheduler.  It's on it's 3rd
or 4th rewrite now, so hopefully I have got it correct now.

> I agree (without testing and only browsing the CVS).

The only files of interest are schedule.c, record, seendb.c.

> OK, there are some python files in the CVS, so I guess you can access
> some information from python.

Yeah, I don't recall what those are.  The co-maintainer committed
them.

> But it's ok if some code is in C. But
> the user interface should be in python to fit into freevo.=20

That is fine with me.  I can agree that if the GUI is in Python
currently, it should maintain that status, where possible.  I think
that where necessary, divergences from Python should be allowed, like
in the case of the scheduler.

> Maybe I have some free time next weekend. Please send me the SDL
> patches till than. I will try to solve the overscan/resize problem.=20

Done.

b.

--=20
Brian J. Murrell