[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[paragui-users] Some questions - developer feedback please :)
From: |
Teunis Peters |
Subject: |
[paragui-users] Some questions - developer feedback please :) |
Date: |
Thu, 27 Feb 2003 13:16:11 -0800 (PST) |
on 3D and/or video contexts:
What parameters are needed?
How should a 3D system interact with ParaGUI event-wise?
What information would such a system need?
How SHOULD paragui interact within another visual system...
example: paragui window inside 3D app
or even paragui surface on 3d texture :)
actually as I've been playing with multimedia contexts (movie playing :) as
well, above applies to that too....
Also, am thinking of some additional components for ParaGUI:
Layout manager:
- to manage and rearrange widget/window layouts....
bits to manage:
background attribs (eg: solid|transparent)
window location and size
"dirty rectangle" list (send refresh events -here-)
manging -when- objects are repainted
- there could be one for every drawing context...
Texture manager:
- (note: this doesn't apply outside of the opengl tree :)
goal: to manage texture memory onboard videocard and manage when
textures are updated or removed from videomemory (LRU algo :)
These two components (both of which -would- be core changes) I'm likely to
add anyways. They simplify some issues and add some neat possibilities
later... I'm just looking for feedback on how they should work / what
they should handle / where they should be added. Neither of these would
be appropriate for an add-on library.
Also - on threading:
- How should one build a widget that would contain a 'main thread'
of it's own? :) I think it'd be pretty trivial except that
I'm not sure what developers here think of threading...
Thank you for any/all helpful feedback and answers in advance :)
I have and am building these components so....
G'day, eh? :)
- Teunis
- [paragui-users] Some questions - developer feedback please :),
Teunis Peters <=