RenderingProject/DemoPlans

From FedoraProject

Jump to: navigation, search

Contents

Demo plans

What do we want people to take out of the demo

hardware to do desktop graphics about rotating CD trays.

EXT_framebuffer_object and accelerated indirect rendering will pay off in cool results.

What do we want to cover

Script

Here's a somewhat ambitious idea for what our presentation / demo should be.

a simple GTK+ application with an interesting Cairo-base theme.

a PDF via Cairo. (Maybe have printed version for handouts as well?)

Demonstrate some flaws:

are running, and shows that we've been running everything so far in a full-screen Xnest/Xvnc style nested session.

the Metacity CM we demo'ed earlier, but with live thumbnailing pagers, maybe a few other things.

luminocity comes up as small scaled down window. When we full-screen it, it smoothly zooms to fullscreen scaling out as it goes.

such as a window smoothly shrinking and docking.

lighting, depth-of-field, or reflections that would be hard or impossible to do using RENDER.

(See RenderingProject/CMArchitecture)

Describe other missing bits of GL briefly

Demo hardware

I don't think we'll be able to run the demo above on a laptop. The laptops we have are either R100 or Savage, which are both a bit marginal in performance for doing cool demos.

(If someone has a R200 laptop, that might be an option, but the recent thinkpads we have are still R100, right?)

So, we'll probably need to bring in a desktop. There we have our choice of:

We'll probably be doing development on a mix of such systems, so we can see how things work. All we need from the server with the above script is:

Software bits

So, what parts of the above demo need writing?

displaying the server in a window or using it as a source for luminocity. Xfake+lightpipe is a possible solution, but we could do better if Xfake could map it's framebuffer shared via shm or mmap.

Another possiblity is Xephyr If it can be made to have little overhead over Xfake when minimized, it's pretty much exactly what we want.

When we start running a compositing manager, we might want to add synchronizations hooks between the display agent and the CM, so that we can redisplay entire frames at once rather than redrawing little bits.

OK. (I think we'll mostly be over text and polygons, so we should be pretty close to fine.)

together a list-of-slides treeview and a menu, really.)

I'm withdrawing my ooimpress objection... I think demoing Cairo is more important than doing complicated slides.

going quickly, we probably want to go flat, vectorial, and geometric, even if that's considerd "been done already".

thing to implement involving things like:

out the side?)

In other words, a UI gadget that needs COMPOSITE.

Scheduling

Some intermediate milestones

Jan 27:: Initial crude GTK+ theme, initial slide app, revive luminocity, do a bit of work on it. xpdf-cairo integrated into evince.

Feb 3:: "cool" luminocity feature, GTK+ theme basically there,

Feb 10:: dress-rehearsal of our complete presentation.

Retrieved from "https://fedoraproject.org/wiki/RenderingProject/DemoPlans"