fenfire-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fenfire-dev] The Fenfire demo


From: Benja Fallenstein
Subject: Re: [Fenfire-dev] The Fenfire demo
Date: Wed, 16 Feb 2005 07:36:42 +0100

On Mon, 14 Feb 2005 23:46:35 +0200 (EET), Matti Katila
<address@hidden> wrote:
<<AWT and GL behave differently, AWT inherits square size, GL doesn't>>

Yes, this is a problem and we need to think carefully about what to do
about it. It seems nicer and simpler not to inherit the w/h, but I
think the problem is interpolation of w/h in SHOW_IN_INTERP child cs.
I.e., you have something like

    foo = box(0, x, y, w, h);
    matcher.add(0, foo, key);
    ...
    bar = translate(foo, 0, 0, 1);
    scene.put(FilledRectVob(), bar);

where 'bar' is not put into the matcher. We used to do it so that we
just put bar into the matcher with a key like

    matcher.add(foo, bar, "background");

but this doesn't work for interpolation between different views: then
both views would have to have a cs with a "background" key, or the bg
will not be interpolated! That's not acceptable. But we need the
translate() cs, because we need the background to be behind the
content.

Any ideas how to solve this?

I have only one right now: Get rid of all the w/h stuff in the vob
system, and instead use a second cs as a parameter to the vobs. This
could be the unitSq cs. I.e.,

    foo = translate(0, x, y);
    matcher.add(0, foo, key);
    box = scale(foo, w, h);
    matcher.add(foo, box, BOX);
    scene.put(content, foo, box);
    ...
    bar = translate(foo, 0, 0, 1);
    scene.put(FilledRectVob(), bar, box);

This would still require the BOX key, but that's ok because it can be
a standard across all views: currently all views understand w/h, so
there's nothing wrong with all views understanding the BOX key which
is just a different implementation of the same functionality...

I think Tuomas might even like this. ;-)

What do you think?

For the moment (i.e. until we've agreed on a real solution), you can
just make a box(cs, 1,1) in PanZoomLob I suppose...

BTW, could you make a 'real' center() cs which uses the scale of its
parent? The center cs with the unitSq scale is quite annoying. -- I
can't make it myself at the moment because I don't have GL installed
and can't install it during the trip ;-)

Cheers,
- Benja (nyt Tukholmassa)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]