Hi Gerrit,
Gerrit Voss wrote:
>
> ok, the generic contained exclusive, which I missed in the original. I
> was more thinking along the line of having a thread per context which
> has exclusive access and everything else has to go through it. So the
> render action will submit the stages for execution as it sees fit,
> similar the app would be allowed to submit things too. The only thing
> left is to synchronize app parts and the stage that depends on it, but
> that should not be to big a problem as there will be something in the
> tree that can setup this part for the stage properly.
OK. So to do that you'd have to queue a callable object that does the OpenGL
calls you want to do. Hm, might be useful as a general mechanism to handle
OpenGL calls. In a sense the GLObjects in the Window try to something like it,
so maybe this would be a way to make that part simpler (going back to the
roots,
that's what Y did a long time ago ;).
> that not, what I was thinking about was executing stages that completed
> their traversal immediately. Determining if they are depending on
> something else is quite easy. I agree that interrupting the traversal
> itself should have a very very good reason ;-)
In general I think so too. There are some interesting papers out though that do
just that. I think the drivers have gotten a LOT better about context switching
than they used to.
> Yes I already did, it is a reference as to how the infrastructure has
> to look like. But it is not in a condensed state right now it is more
> a set of floating ideas ;-) I see finalizing this is the last step,
> actually besides providing something I would like to keep it as open
> as possible so different ideas could be tried.
It's the last step, true, but I think it's going to be a fairly significant
one,
so starting to think about it early might not be a bad idea, even if it can't
be
tested yet.
> Publish, at least the infrastructure for now, yes, but it's hard to find
> a place, I was thinking a little bit about SEARIS but I'm not sure if
> this really fit's in.
It's a little too focused for SEARIS, but worth a try. SEARIS this year is much
more discussion-based though, so it's not much of a publication.
Yours
Dirk
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
