[GEM-dev] Gemwiki updates

[james tittle]

hey ben,

On Dec 18, 2005, at 11:25 AM, B. Bogart wrote:
> What methods does the gemcontrol object accept, and the gemwindow?

http://puredata.info/dev/gemwiki/GemcontrolGemoutput
...this is kinda old, but we've got revision 2 working atm...subject  
to change, of course...

> I'm having trouble understanding where gemwin functionality is split
> between the objects?

...so far, [gemcontrol] doesn't seem to do much that can be  
manipulated...

> create,destroy,0,1,color,dimen,offset,border,view are all in gemwindow
> and can be controled from each gemwindow seperatly? Is the  
> framerate the
> only method the gemcontrol object has?

...yup...

> Also I think a combination of render priorities work best for  
> rendering
> to both pbuffers and windows:
>
> [gemhead 1 mywindow]
>
> [gemhead 2 mywindow]
>
> [gemhead 1 mybuffer]
>
> [gemhead 2 mybuffer]

...ok, it took me a second glance to see what the diff was here, but  
you're suggesting that each "windowed context" has it's own render  
priorities, which I think has been brought up before, and certainly  
is still on the table...this also means that we'd need to figure out  
a way of determining which gets rendered to first, "mywindow" or  
"mybuffer"...?  Seems obvious to us, but not so obvious if we just  
allow anyold name for a buffer...here's where we might have uses for  
multiple [gemcontrol]'s, such that some are for buffers while others  
are for outputs...

> I find the idea of using only render priority ranges to specify which
> offscreen buffer that gem-head gets rendered to quite awkward.
>
> Since its a new argument to [gemhead] then it should not break any
> patches, and no argument would simply default to the first gemwindow.
>
> What do you think?

...yes, this is all how we've discussed, except for the offscreen  
windows, which the more I work with and think about, the more my  
ideas change about how they should be treated...besides the fact that  
they have no border/titlebar and are never seen, they're also  
different in that they may be rendered to many times per render cycle  
(if reused), whereas the onscreen windows are only rendered flushed  
once per fps...

...I'll definitely be mulling this over the holidays...

jamie