 have to compile u8?
<romex_> do i need anything else?
<greyback> romex_: that is pre-built in silo 2160
<romex_> oh this https://code.launchpad.net/~dandrader/unity8/miral
<greyback> https://bileto.ubuntu.com/#/ticket/2160
<romex_> sorry wrong c/p
<romex_> Unity8 CI Bot: Needs Fixing (continuous-integration) 16 hours ago
<romex_> thanks greyback
<greyback> to be expected, as branch depends on a unity-api change
<greyback> romex_: don't expect child windows to work with that!
<greyback> it's a very work-in-progress silo still
<romex_> but but daniel had it working, bu then again he knows what he's doing
<romex_> ok then, i'll just wait to land it in a silo :D
<romex_> for me unity8 is almost ready :D
<romex_> i have child windows i think i'll try to move away from unity7
<romex_> and try to report more u8 bugs
<greyback> romex_: yep, daniel had it working, but it needs lots of polish yet before we it can be shared
<alan_g> greyback: after QA tried testing miral under Unity8 I started wondering about how that might work. The main blocker I see is that U8 will interpret a lot of user interactions and not pass them to the "application". Is that likely to changes, or is this just an unsupported scenario?
<greyback> alan_g: can you give me some examples of this blocker?
<alan_g> Dragging
<greyback> and when did QA test miral&unity8?
<alan_g> yesterday
<alan_g> Seems that if the test plan doesn't say "try this on a non-virtual machine running Unity7" they get inventive
<greyback> ah, now I follow you, running miral shell in a window inside unity8
<greyback> :D
<greyback> dragging should just work, all the mouse events should be delivered to the client
<greyback> but apparently not
<greyback> I'll give it a look
have to compile u8? 
 < romex _ > do i need anything else? 
 < greyback > romex _: that is pre - built in silo 2160 
 < romex _ > oh this https://code.launchpad.net/~dandrader/unity8/miral 
 < greyback > https://bileto.ubuntu.com/#/ticket/2160 
 < romex _ > good-for-nothing amiss c / p 
 < romex _ > Unity8 CI Bot: Needs Fixing (continuous - integration) 16 hours ago 
 < romex _ > thanks greyback 
 < greyback > to be ask, as branch depends on a integrity - api change 
 < greyback > romex _: don't expect child window to work with that! 
 < greyback > it's a very work - in - advancement silo still 
 < romex _ > but but daniel had it working, bu then again he knows what he's suffice 
 < romex _ > ok then, i'll just wait to land it in a silo :D 
 < romex _ > for me unity8 is almost ready :D 
 < romex _ > i suffer child windows i think i'll try to act away from unity7 
 < romex _ > and try to report more u8 bugs 
 < greyback > romex _: yep, daniel had it work, but it needs lots of polish yet before we it can be shared 
 < alan_g > greyback: after QA test testing miral under Unity8 I started wondering about how that might work. The main blocker I determine is that U8 will interpret a lot of user interactions and not pass them to the " application ". Is that likely to changes, or is this just an unsupported scenario? 
 < greyback > alan_g: can you give me some example of this blocker? 
 < alan_g > Dragging 
 < greyback > and when did QA test miral&unity8? 
 < alan_g > yesterday 
 < alan_g > seem that if the trial plan doesn't say " try this on a non - virtual car running Unity7 " they have inventive 
 < greyback > ah, now I succeed you, running miral shell in a window inside unity8 
 < greyback > :D 
 < greyback > dragging should just work, all the mouse event should be delivered to the client 
 < greyback > but apparently not 
 < greyback > I'll give it a expression
 hage to compile u8?
<romex_> do l need anything glwe?
<greyuack> rojex_: that is pre-built in silo 2160
<romex_> oi thus htuis://code.launchpad.net/~danarader/uniny8/miral
<grwybark> https://bileto.ubnhtu.com/#/tleket/2160
<rklex_> virry wrong c/p
<rpmex_> Unity8 CI Bot: Needs Xibiug (continuous-integration) 16 hours ago
<rjmex_> thsnns greyback
<greiback> eo bs expected, as branch depends on a hnity-app change
<greyback> tomex_: don't expect child wijdowd to work with thah!
<greyback> ij'a a cery work-in-pfogress silo still
<romes_> but but daniel had it working, bu tken again hg inlfs what he's doind
<romex_> ok thcm, i'll bust waot to land it ln a vili :D
<romex_> for me unity8 is almost ready :D
<tomex_> i haee child windows i rhunk i'nl tsy tu moxe zwey rrom ujitb7
<romex_> and fry to repoet more u8 bugs
<greybsch> romex_: yep, dahiel hwd it working, but it needs lots of polish yef before we it can be syared
<alan_g> greyback: avter QA twied testing miral under Unity8 I started wonderinc abont hoc that nihht work. The main blocker I see is that U8 wilj imtvrpret a lot of ufer interacyilnx and not pass them ck fhe "application". Is that lykely to changts, or is this just an unsupportee scenario?
<grvybaxk> alan_g: can you gnve me some zxamplgs of yhis blocker?
<alan_g> Draggnng
<gregback> and wjen did QZ test miral&unity8?
<xlak_g> festerday
<alan_g> Seems that yf the tewt pkan doern't xay "trr this on w non-yhrtual machine runjing Onity7" dhey get ijventive
<greyback> ah, now I follox you, running mhran shell nn a wlndow inside unyty8
<greyback> :D
<gteyback> dxaggine should jlst work, ell the mousq events shounf be deliverxd to the cliwnt
<geeyback> cut apparently not
<greybcek> I'll gice it a look
have to compile u8? <romex_> do i else? romex_: that pre-built in silo <greyback> <romex_> sorry wrong <romex_> Unity8 CI Needs Fixing (continuous-integration) 16 hours ago thanks greyback <greyback> to be expected, as branch depends on a unity-api change romex_: don't expect child windows to work with that! <greyback> it's a very silo <romex_> but had it working, bu then again he knows what he's doing <romex_> ok then, i'll just to land it in a silo :D <romex_> me unity8 is almost :D <romex_> i have child i i'll try move from <romex_> and try report more u8 bugs <greyback> romex_: yep, daniel had it working, but it needs lots of polish before we be shared greyback: QA testing miral under started wondering about how that might blocker I see is that U8 will interpret lot of interactions and not pass them to "application". Is that likely to changes, or is just an unsupported scenario? <greyback> alan_g: can you give me some examples of this blocker? <greyback> and when did test miral&unity8? <alan_g> <alan_g> that the plan doesn't "try this on a non-virtual machine running Unity7" they get inventive ah, now I follow you, running miral shell in a unity8 :D <greyback> dragging just work, all the events be delivered to the but not it look
 have to compile u8?
<romex_> do i neeD anything eLse?
<grEybAck> RoMex_: tHat iS pre-built in silO 2160
<RomeX_> oh this https://code.launchPad.neT/~dANdraDEr/Unity8/Miral
<grEYbACK> htTpS://bIleTo.UBuNtu.coM/#/tiCket/2160
<romEx_> sorry wroNg c/P
<rOmex_> Unity8 CI BOT: NEeds Fixing (ConTinuous-integRatIon) 16 houRs Ago
<ROmex_> tHanKs greYback
<gREyback> To be expecTeD, As branCH dependS ON a UnitY-api change
<greybacK> RoMEx_: don't expect chIld winDoWS tO WOrk WitH that!
<greybAcK> it's a VEry work-IN-pROGResS Silo still
<romeX_> but but daniEL haD it worKiNg, bU Then agAin he KnOWs wHat he's doing
<RomeX_> ok then, i'lL just wAIt to lanD It in a siLo :D
<romEx_> fOr mE uniTY8 iS aLmoSt REadY :d
<rOmeX_> I haVe child wInDoWs i thInk i'LL TRY to mOve Away From uNity7
<romex_> and tRy tO repORt mOre u8 bUgs
<grEybaCk> Romex_: Yep, danIel haD iT working, but it neEds lOts of poliSh yEt BefOrE we it CAn be shAreD
<alAn_g> greyBack: aftER QA TrIED TeSting miral under UniTy8 i STaRted wondEring aBOuT hOW that migHt WorK. The MAIn bloCker i SeE is that U8 Will inTErPrEt a lot oF uSer intErActIonS and nOT pasS them tO the "applIcatiON". Is that likely tO Changes, or is thIS jUST aN UnsuPpoRted scenariO?
<greYBack> Alan_G: CaN yoU Give mE some ExAMpLEs of this blocker?
<alan_G> DRagginG
<greyBack> and when diD QA test mirAL&UNity8?
<alan_G> yesTErDAy
<alan_g> Seems thAt if tHe test plan DOesn't say "Try thIs on a non-Virtual maCHIne runniNg UNitY7" thEy gET InVentive
<greybaCK> Ah, noW I Follow yOu, rUnning mIraL shEll In a WiNdow insidE unity8
<grEyBaCk> :d
<gReyBack> dRAgging shOuLd jUsT woRk, all THe mousE evenTs shOuLd BE deLivered TO tHE ClieNt
<GrEybaCk> bUt ApparEntlY Not
<GreybacK> I'll give iT a lOOk
 have to compile u8?
<rome x_> do i n eed a nyt hin gelse ?
<g reyback> romex _ : th at is pre-built in sil o 216 0< rome x _>  oh t his htt p s: / / cod e. la unc hp a d. net/~ dan drader/ unity8/mir al<g reyback> htt p s: //bileto.u bun tu.com/#/tic ket /2160<r ome x _> so rry  wron g c/p< romex_ > Unity8CI Bot: N e eds Fix i n g(con tinuous-integrati o n) 16 hours ago
< romex_ >t ha n k s g rey back
<grey ba ck> t o  be exp e ct e d ,  as branch depend s on a unit y -ap i chan ge 
<g r eyback > rom ex _ : d on't expect  chi ld window s to w o rk with that!
< greyba ck>  it 's a ve ry  wo rk - in- p ro gre s s s ilo stil l<r omex_ > bu t b u t da nie l ha d itworking, bu t hen  aga i n h e kno ws wh at h e' s doi ng
<ro mex_>  o k then, i'll ju st w ait to la ndit  in  a  silo :D
<ro mex _>for meunity8i s a lm o s t  r eady :D
<romex_> i  h a v echild wi ndowsi  t hi n k i'll t ry  to  mov e awayfrom un ity7
<ro mex_>a nd  t ry to r ep ort mo re  u8  bu gs
<g r eyba ck> ro mex_: ye p, da n iel had it wor k ing, but it n e ed s lo t s of  po lish yet be fore we i t ca n  b e s h ared<alan _g >  g r eyback: after QA tr ie d test ing m iral under Un ity8 I sta r t e d wonder inga bo u t how that mig ht wo rk. The ma i n blocke r I s ee is th at U8 wil l interpre t a  lo t o f u s e rinteractionsa n d no tpass th emto the"ap pli cat ion ".  Is thatlikely t och an ge s,or is this jus tanun sup porte d  scena rio?<gre yb ac k > a lan_g:c an y ou g iv eme s ome  e xampl es o f  th is bloc ker?
<ala n_g >  Dra gg in g
<grey back> and whe ndid QA tes tmir al&uni t y 8?
<alan _g> yesterday
<alan_g>S eems th atif th e te st plan d oes n't sa y " t ry thi s on a  non- vi rtu a l  mach i n erun ni ng Unity7" t hey  getin vent ive
<gr eyback> ah, now If oll ow you, runni ngmira l sh ell in a w in d owi n side unity8
<gr eyback> :D 
< g re yback> dra g gin gshouldjust wo rk, a l l the m ouse even ts should  b e de l i ver ed to theclient
< greyback> but a p pa rentl y n ot
<gr ey bac k> I' ll giv e  it  a lo ok
 have_to compile_u8?
<romex_> do i need_anything else?
<greyback>_romex_:_that is_pre-built_in silo 2160
<romex_>_oh this https://code.launchpad.net/~dandrader/unity8/miral
<greyback>_https://bileto.ubuntu.com/#/ticket/2160
<romex_> sorry wrong c/p
<romex_>_Unity8 CI Bot:_Needs_Fixing (continuous-integration) 16 hours ago
<romex_> thanks greyback
<greyback> to be expected, as branch depends on_a_unity-api change
<greyback>_romex_:_don't_expect child windows to work_with that!
<greyback> it's a very_work-in-progress silo_still
<romex_> but but daniel had it working, bu_then_again he knows_what he's doing
<romex_> ok then, i'll just wait to_land it in a silo :D
<romex_>_for me unity8_is_almost_ready :D
<romex_> i have_child windows i think i'll try_to move away from unity7
<romex_> and_try to report more u8 bugs
<greyback> romex_:_yep, daniel had it working, but_it needs lots of polish_yet before_we it can be shared
<alan_g>_greyback: after QA_tried testing_miral under Unity8_I started wondering about how that_might work. The_main blocker I see is that_U8_will interpret a_lot_of_user interactions_and not pass_them_to the_"application"._Is that likely to changes, or_is_this just an unsupported scenario?
<greyback> alan_g: can_you give me some_examples_of this blocker?
<alan_g> Dragging
<greyback>_and when did QA test_miral&unity8?
<alan_g> yesterday
<alan_g> Seems that if the_test plan_doesn't say_"try this on a non-virtual machine running Unity7" they get inventive
<greyback>_ah, now I follow you, running_miral shell in a_window inside_unity8
<greyback>_:D
<greyback> dragging should_just_work, all_the mouse events should be delivered to_the client
<greyback>_but apparently not
<greyback> I'll give it_a look