moaning our locking situation in surfacestack
<kdub> the new mc::DefaultDisplayBufferCompositor::composite is beautiful
#ubuntu-mir 2013-11-26
<kdub> hey duflu, I wanted to sync with you on adding overlay support to the compositor
<kdub> pretty much, my plan is to have the platform provide a 'filter' for the scene that will skip GL composition on a surface if the hardware can handle composing that surface
<kdub> so, if the platform can bypass or overlay-composite any given buffer, it simply tells the compositor to skip rendering that surface with GL
<duflu> kdub: Sounds about right. Although all the "filter" code will be replaced by Q*
<kdub> right, i pinged greyback about it, he seemed optimistic that it can be worked into the qt scenegraph
<duflu> kdub: Could be a generalization of BypassFilter, in a way. We just have to remember that if/when Q* take over the scene graph to ensure there's a working Qt replacement
<kdub> right, just like a 'hardware optimization filter'
<kdub> greyback said it wouldn't be too hard to integrate a'skip rendering these layers' into his work, so hopefully the bypass filter and this overlay work will mesh nicely with that
<duflu> kdub: Before we add yet more filters, I had planned on tidying up and getting back to only having a single surface class passed around filters/renderers.
<kdub> duflu, yeah, part of the work that will need to be done is cleaning up the filter/operators on the SurfaceStack
<kdub> i don't know that the model we have makes sense anymore, with the way we're using it these days
<duflu> kdub: I'm not committing to a particular class or name. Just that it became obvious to me there's so much coupling on the filter/operators that it would make more sense to refer to just something::Surfacelike instead. A single interface
<kdub> perhaps, i haven't really felt out what I like best yet... just that it is pretty coupled
<duflu> kdub: I think it could be dangerous to be specific about the interface. It needs
moaning our locking situation in surfacestack 
 < kdub > the new mc::DefaultDisplayBufferCompositor::composite is beautiful 
 # ubuntu - mir 2013 - 11 - 26 
 < kdub > hey duflu, I want to synchronize with you on adding overlay documentation to the compositor 
 < kdub > reasonably much, my plan is to have the chopine put up a' filter' for the scene that will skip GL composition on a surface if the hardware can wield composing that surface 
 < kdub > then, if the chopine can bypass or overlay - composite any give buff, it merely tells the compositor to skip rendering that airfoil with GL 
 < duflu > kdub: Sounds about right. Although all the " filter " code will be replaced by Q * 
 < kdub > right, i ping greyback about it, he seemed optimistic that it can be worked into the qt scenegraph 
 < duflu > kdub: Could be a generalization of BypassFilter, in a direction. We just have to remember that if / when Q * take over the scene graph to ensure there's a working Qt replacement 
 < kdub > right, just like a' hardware optimization filter' 
 < kdub > greyback said it wouldn't be too hard to integrate a'skip rendering these layers' into his work, so hopefully the beltway filter and this overlay work will enmesh nicely with that 
 < duflu > kdub: Before we add yet more filters, I had planned on tidy up and getting back to merely having a single open class passed around filters / renderers. 
 < kdub > duflu, yeah, part of the work that will need to be do is cleaning up the filter / operators on the SurfaceStack 
 < kdub > i don't know that the model we have makes sense anymore, with the manner we're using it these days 
 < duflu > kdub: I'm not committing to a particular class or name. barely that it became obvious to me there's so much coupling on the filter / operator that it would make more sense to refer to just something::Surfacelike rather. A single interface 
 < kdub > possibly, i haven't really felt out what I like best yet... merely that it is pretty match 
 < duflu > kdub: I think it could be dangerous to be specific about the interface. It need
moajing our locking situatiun in surfacestcxk
<kdub> the nsw mc::DefxultDisplayBufferCompositor::clmpositt is beautiful
#ubuntj-mir 2013-11-26
<kdub> hey dufou, I qanted to sync witm you ln abdmng overlay supkort to the wompositor
<kdub> pfecty much, my plan is to have the platsorm prpvlde a 'filter' fjr tnq scsne that will skip GL composition kn a sugface if the hardeare can handle composing hhat surface
<kdub> so, if the platfotj cwb bypass or uverlay-comkovite any gjven buffer, it simply tells the comppsitor to wkup ggndering thav surfwce with GL
<dmglu> kdgb: Souncs about right. Alvhouth all the "filter" codx will be replaced bi Q*
<kdub> richc, i pinged greyback avoyt it, he veemde ootijixtjc thah iv can be wodked into tye qt scenegraph
<dufku> jdub: Could be a genqrwlization of BypassFilter, in a way. We jlst gave to remember that id/when Q* take over the scene grwph to ensure there's a working Qt replacement
<kdub> righv, gusu oike x 'hwrdware optimization filter'
<kdub> greyback said jt wpuldn't be too mard to integrate s'snil rendering thgse layzds' into his work, so jopefuljy thw bypass siltrr and this overlay work wiol mesh nicejt with that
<duflu> kbub: Before wz add iet mote filters, I had planneb on tjdying up ajd gettinf back to only haxinn a single surface class passqd around filcers/renddrerx.
<kdub> quflu, yeah, part of the work that wlll nged to be done id cleaning up the filter/operatocx on the SurgaweSnack
<kdub> n don't know that thq model we havg makes sznse avymore, witg the wey we're usind it these dafd
<duflu> kdub: M'm not coimitring to a pxfticular class or name. Lbst that ut became obvious bo me fhere's so much euopling on the foltdr/o[egatprf that it wound mxke kore rense to rener to kust something::Surfacaliks instead. A single ikterface
<keub> perhwps, i haven't teally felt out whwt I nikx best yej... just that it is pretty couples
<duflu> kdkb: L think it cotld ne dwngerous tp be specific about the interface. It nexds
moaning our locking situation in surfacestack <kdub> mc::DefaultDisplayBufferCompositor::composite beautiful #ubuntu-mir <kdub> hey duflu, you adding overlay support the compositor <kdub> much, my plan is to have platform provide a 'filter' for the scene that will skip GL composition on surface if the hardware can handle composing that surface <kdub> so, if the can or any buffer, it simply tells the compositor to skip rendering that surface with GL <duflu> kdub: Sounds right. Although all the "filter" code will be by Q* <kdub> right, pinged greyback about it, he optimistic it can worked the scenegraph <duflu> kdub: be a generalization of BypassFilter, in a way. We just have to remember that if/when Q* take the scene ensure there's working replacement right, just like optimization filter' <kdub> greyback said it hard to integrate a'skip rendering these layers' into work, so the bypass filter and this overlay will mesh nicely with that <duflu> kdub: Before add yet more filters, I had planned on tidying up and getting back to only single surface class passed filters/renderers. <kdub> duflu, part the that need to done is cleaning up the filter/operators on the SurfaceStack <kdub> i know that the model we have makes sense anymore, with we're it these days kdub: I'm not committing a class or name. Just became to much on filter/operators that it would more sense to refer to something::Surfacelike instead. A single really felt out what I like best yet... that it is pretty coupled <duflu> kdub: think it could be dangerous to be specific about the interface. It
moaning our locking situatioN in surfaceStack
<KduB> thE nEw mc::defaUltDisplayBuffERComPositor::composite is beauTiful
#UbUNtu-mIR 2013-11-26
<kDub> heY duflu, I WAnTED to SyNc WitH yOU oN addiNg oVerlay sUpport to thE coMpOsitor
<kdub> prETtY much, my plaN is To have the plaTfoRm provIdE a 'fILter' fOr tHe sceNe that WIll skiP GL composItIOn on a sURface if THE hArdwAre can handle compoSInG That surface
<kduB> so, if tHe PLaTFOrm Can Bypass or ovErLay-coMPosite aNY gIVEN buFFer, it simply teLls the compoSItoR to skiP rEndERing thAt surFaCE wiTh GL
<duflu> kdUb: SoUnds about Right. ALThough aLL the "filTer" codE wiLl bE repLAcEd By Q*
<KdUB> riGHt, I piNGed Greyback AbOuT it, he SeemED OPTimiStiC thaT it caN be worked into The Qt scENegRaph
<dUflu> kDub: COuLd be a GeneraLizatIoN of BypassFilter, In a wAy. We just hAve To RemEmBer thAT if/wheN Q* tAke Over the Scene grAPh tO eNSURe There's a working Qt rePlACEmEnt
<kdub> rIght, juST lIkE A 'hardwarE oPtiMizaTIOn filTer'
<kDUb> Greyback Said it WOuLdN't be too HaRd to inTeGraTe a'Skip rENderIng theSe layers' Into hIS work, so hopefulLY the bypass filTEr AND tHIs ovErlAy work will mEsh nICely With THaT
<duFLu> kduB: BefoRe WE aDD yet more filters, I had PlAnned oN tidyIng up and gettiNg back to onLY HAving a siNgle SUrFAce class passed ArounD filters/reNDerers.
<kdUb> dufLu, yeah, paRt of the woRK That will NeeD to Be dOne IS ClEaning up the fiLTEr/opErAtors on The surfacestaCk
<kDub> I doN't Know that tHe model wE hAvE mAkEs sEnse aNYmore, witH tHe wAy We'rE usinG It thesE days
<DuflU> kDuB: i'm nOt commiTTiNG To a pArTiCulaR clAsS or naMe. JuST thAt it becAme obviouS to ME theRe'S sO much coUpling on the fiLtEr/operatorS tHat It woulD MAke more sEnse to refer to just somethINg::SurfaCelIke inSteaD. A single iNteRface
<kDub> PErhaps, I haven'T realLy FelT OUt whaT i LiKe bEsT yet... just thAT It iS pretTy CoupLed
<duflU> kdub: I think it could BE daNgerous to be spEciFic aBOUt The INtERfaCe. iT neEDS
moaning our locking situat ion in sur faces tac k
< kd ub>thenew mc::Defaul t Disp layBufferCompositor::c ompos it e  isb ea utifu l
#ubun t u- m i r 2 01 3- 11- 26 <k dub>hey  duflu,  I wantedtosy nc with youo nadding ove rla y support to  th e comp os ito r 
<kdu b>prett y much ,  my pl an is toha v e thep latform p ro vide  a 'filter' for t h es cene that will  skipGL co m p osi tio n on a sur fa ce if the har d wa r e can handle compos ing that su r fac e
<kdu b>  so ,  if th e pla tf o rmcan bypassor o verlay-co mposit e  any gi v en buff er, it  si mpl y te l ls  t heco m pos i to r t o  sk ip rende ri ng  that  sur f a c e  wit h G L
<d uflu>  kdub: Sounds  ab outr igh t. Al thoug h al lthe " filter " cod ewill be replace d by  Q*
<kdub > r ig ht,  i  ping e d grey bac k a bout it , he se e med  o p t i mi stic that it can b ew o rk ed intothe qt sc en e graph
<d uf lu>  kdu b :  Coul d be agenerali zation of  B ypassFi lt er, in  a  wa y.We ju s t ha ve toremember  that if/when Q* tak e  over the sce n eg r ap h  toens ure there's  a w o rkin g Qt re pla c ement 
<kdu b> ri g ht, just like a 'ha rd ware o ptimi zation filter '
<kdub> g r e y back sai d it wo u ldn't be too h ard t o integrat e  a'skiprende ring the se layers ' into his  wo rk,  so  ho p e fu lly the bypas s filt er  and th isoverlay  wo rkwil l m es h nicelywith tha t<d uf lu > k dub:B efore we  a ddye t m ore f i lters,  I ha d pl an ne d  on  tidyin g  u p andge tt ingbac kto on ly h a vin g a sin gle surfa cec lass  p as sed aro und filters/r en derers.
<k du b>duflu, y eah, par t of the work that will need to  be  done  iscleaningupthe fi lte r /opera tors o n the  S urf a c eStac k <k dub >i don't kn o w  th at th emode l we ha ve makes sense any m ore , with the wa y w e're u si ngi tt hes ed ays < duflu> kdub: I' m not comm it t in g to a par t icu la r class  or nam e. Ju s t thatit became  obviousto  met h ere 's so much  couplin g on thef ilter / op erato rsthat i twou ld ma ke mor e  se nse t o refe rto jus t som et hing::Su rfacelike instead. A si ngle i nterf ace 
<kdub> p erh a ps,  i haven' t re ally feltout  wh at Ilik e  best  yet . ..  ju s t tha t it is pretty co upl e d 
< duflu> kdub : I  th ink i t c o uld be  dan gerous to be spec i fic about theinte r f ace . I t  nee ds 
moaning our_locking situation_in surfacestack
<kdub> the new_mc::DefaultDisplayBufferCompositor::composite is_beautiful
#ubuntu-mir_2013-11-26
<kdub> hey_duflu,_I wanted to_sync with you_on adding overlay support_to the compositor
<kdub>_pretty_much, my plan is to have the platform provide a 'filter' for the scene_that_will skip_GL_composition_on a surface if the_hardware can handle composing that_surface
<kdub> so,_if the platform can bypass or overlay-composite any_given_buffer, it simply_tells the compositor to skip rendering that surface with_GL
<duflu> kdub: Sounds about right. Although_all the "filter"_code_will_be replaced by Q*
<kdub>_right, i pinged greyback about it,_he seemed optimistic that it can_be worked into the qt scenegraph
<duflu> kdub:_Could be a generalization of BypassFilter,_in a way. We just_have to_remember that if/when Q* take_over the scene_graph to_ensure there's a_working Qt replacement
<kdub> right, just like_a 'hardware optimization_filter'
<kdub> greyback said it wouldn't be_too_hard to integrate_a'skip_rendering_these layers'_into his work,_so_hopefully the_bypass_filter and this overlay work will_mesh_nicely with that
<duflu> kdub: Before we add_yet more filters, I_had_planned on tidying up_and getting back to only_having a single surface class passed_around filters/renderers.
<kdub>_duflu, yeah,_part of the work that will need to be done is_cleaning up the filter/operators on the_SurfaceStack
<kdub> i don't know_that the_model_we have makes_sense_anymore, with_the way we're using it these days
<duflu>_kdub: I'm_not committing to a particular class_or name. Just that_it_became obvious to me there's so_much coupling on the filter/operators that_it would make more sense_to_refer_to just something::Surfacelike instead. A_single interface
<kdub> perhaps, i haven't really_felt out what_I like best yet... just that it_is_pretty coupled
<duflu> kdub: I think it_could_be dangerous to be specific about_the_interface._It needs