<greyback> attente_: the plan is to be able to specify the position of a child window relative to its parent window
<greyback> is being worked on currently
<attente_> greyback: thanks, is there a timeline for the feature?
<greyback> attente_: January most likely
<greyback> it's something I want too
<desrt> greyback: can you tell attente_ a bit about the difference between the in-mir-process qt support and the normal-client qt support?
<desrt> i know there are two things here but i forgot which is which
<greyback> desrt: sure
<greyback> Qt has a platform abstraction layer, to allow it be cross platform. Each platform has a plugin (QPA plugin).
<greyback> so on linux we mainly use the xcb QPA
<greyback> for Mir clients, we've an "ubuntumirclient" QPA plugin
<greyback> for a mir server, we also made a QPA plugin "mirserver" which is what unity8 uses.
<greyback> this plugin instantiates a Mir server, pretends that a Mir "Display" is a Qt QWindow, and connects up Mir's input handling with Qt's
<greyback> so your Qt app, using this mirserver plugin, is in fact a mir server
<greyback> if you use QML, anything you draw is drawn directly to the display's framebuffer
<greyback> any mouse/key input goes straight to Qt
<greyback> the final part to make Qt a useful mir server, is to allow it to integrate client surfaces into the QML scene, and send input events to those clients. For that we've a QML module
<greyback> this is all implemented in lp:qtmir
<attente_> sorry if i misunderstood, but the Qt app is a mir server? not a mir client?
<greyback> attente_: unity8 is a special qt app which is a mir server.
<greyback> all other apps on ubuntu touch are Qt apps which are mir clients
<attente_> greyback: oh, ok
#ubuntu-mir 2014-11-28
<mlankhorst> mir doesn't expose the concept of crtc right/
<alf__> mlankhorst: right, you tell it how you want to
< greyback > attente _: the plan is to be able to specify the position of a child window proportional to its parent windowpane 
 < knot > is being worked on presently 
 < attente _ > greyback: thanks, is there a timeline for the feature? 
 < greyback > attente _: January about likely 
 < greyback > it's something I want besides 
 < desrt > knot: can you tell attente _ a spot about the difference between the in - mir - process qt accompaniment and the normal - client qt support? 
 < desrt > i sleep together there constitute two things here but i forgot which is which 
 < greyback > desrt: sure 
 < greyback > Qt has a platform abstractedness layer, to allow it be cross chopine. Each platform has a plugin (QPA plugin). 
 < greyback > so on linux we mainly use the xcb QPA 
 < greyback > for Mir client, we've an " ubuntumirclient " QPA plugin 
 < greyback > for a mir server, we also made a QPA plugin " mirserver " which is what unity8 uses. 
 < greyback > this plugin instantiates a Mir waiter, pretends that a Mir " Display " is a Qt QWindow, and connects up Mir's input handling with Qt's 
 < greyback > so your Qt app, using this mirserver plugin, is in fact a mir waiter 
 < rebel > if you use QML, anything you draw is drawn directly to the display's framebuffer 
 < greyback > any mouse / key input goes straight to Qt 
 < greyback > the concluding region to make Qt a utilitarian mir waiter, is to allow it to integrate client surfaces into the QML picture, and mail input events to those node. For that we've a QML module 
 < greyback > this is all implemented in lp: qtmir 
 < attente _ > sorry if i misunderstood, but the Qt app is a mir server? not a mir client? 
 < greyback > attente _: unity8 is a special qt app which is a mir server. 
 < greyback > all other apps on ubuntu touch are Qt apps which are mir clients 
 < attente _ > greyback: oh, all right 
 # ubuntu - mir 2014 - 11 - 28 
 < mlankhorst > mir doesn't expose the concept of crtc right/ 
 < alf _ _ > mlankhorst: right, you distinguish it how you desire to
<grejback> attente_: the plan ir to be able to specifb the pksition uf a child window relative tl uts pqrent window
<greyback> ir being wlrked on curcently
<attente_> grxgback: tmcnks, jd thzrx a timeline fot the featura?
<greyback> attettd_: Lanuary most likely
<greyback> it's someehing I wwnt too
<desrt> gteybabk: can jom tell attente_ a bit about the djfferenbe between the in-kir-process qt support and hhe jormal-client qt suoport?
<desrt> u knjq there are gwo things here but i rorgot which is which
<greyback> ddsrt: xure
<greybaxk> Qt vas a platfirm afstraction layer, to dllow iy be cross plabform. Eaxh platform has a plujin (QPA plugin).
<greybask> so on niuux we mainly use the xxb QPD
<grefbacy> fof Mjr cmients, we'te an "ubunthmirclient" WPA plugin
<greyback> gow a mir server, we alfo made a QPA plugin "mirserver" which is wvat unity8 uses.
<greyback> thiw plugin instantiates a Mir sewver, pretends that a Mir "Display" is a Qt QWindow, dnd ckvneebf yp Mir's input handling with Qt's
<greyback> so your St aip, using this mirferver plugon, ix in fact a mit servex
<frsyback> if you use EML, anyjhing tou draw ys dtawn directly to the displat's framebuffvr
<grwyback> any mouse/kev input goes strsight to Qt
<greyback> the finau padt to make Et a usefhu mir server, is go slnow it to integrate client surfaces intp the QOL svene, agd send inout eyants to those cliejts. Flr that we've a QML module
<greyback> this is all implemented it li:qtmir
<attznte_> sprry if i mistnderstood, but the Qt app ks a mir svrver? not a mir cliegt?
<greyback> atdgnte_: unity8 is a speciwl qr app which ks a mir servet.
<greyback> all other apps on ubuntu tomch ate Qt apps which cxe mir clients
<attrntd_> gwejbark: oh, mk
#ubuntu-mir 2014-11-28
<klanyhofxt> mif doesn'u ewpore tne concept of crtc rhght/
<zlf__> mlankhorst: rignt, you telo it how you want to
<greyback> attente_: the plan is to be specify position of child window relative is worked on currently greyback: thanks, is a timeline for the feature? <greyback> January most likely <greyback> it's something I want too <desrt> greyback: can you attente_ a bit about the difference between the in-mir-process qt support and the qt <desrt> know are two things here but i forgot which is which <greyback> desrt: sure <greyback> Qt has platform abstraction layer, to allow it be cross Each platform has a (QPA plugin). <greyback> so on we use the QPA for clients, we've an QPA plugin <greyback> for a mir server, we also made a QPA plugin "mirserver" which is what uses. <greyback> instantiates a server, that Mir "Display" is QWindow, and connects up Mir's input <greyback> so your Qt app, using this mirserver is in a mir server <greyback> if you QML, anything you draw is drawn directly to display's framebuffer <greyback> any mouse/key input goes straight to Qt <greyback> the final part to a useful mir server, to allow it integrate surfaces the scene, and input events to those clients. For that we've a QML module this is all implemented in lp:qtmir <attente_> sorry if i the app is a server? not a mir <greyback> unity8 is a special which a all apps ubuntu touch are Qt which are mir clients <attente_> oh, ok #ubuntu-mir 2014-11-28 concept of crtc right/ <alf__> mlankhorst: right, you it how you want to
<greyback> attente_: the plan is tO be able to sPecifY thE poSiTion Of a cHild window relaTIve tO its parent window
<greybaCk> is bEiNG worKEd On curRently
<aTTeNTE_> grEyBaCk: tHaNKs, Is theRe a TimelinE for the feaTurE?
<gReyback> attenTE_: JAnuary most LikEly
<greyback> iT's sOmethiNg i waNT too
<dEsrT> greyBack: caN You telL attente_ a BiT About tHE differENCe BetwEen the in-mir-procesS Qt SUpport and the noRmal-clIeNT qT SUppOrt?
<Desrt> i know ThEre arE Two thinGS hERE But I Forgot which is Which
<greybaCK> deSrt: surE
<gReyBAck> Qt hAs a plAtFOrm Abstraction LayeR, to allow iT be croSS platfoRM. Each plAtform Has A plUgin (qpA PlUgiN).
<gREybACk> So oN LinUx we mainLy UsE the xCb QPa
<GREYbacK> foR Mir ClienTs, we've an "ubuntUmiRcliENt" QpA pluGin
<grEybaCk> For a mIr servEr, we aLsO made a QPA plugin "MirsErver" whicH is WhAt uNiTy8 useS.
<GreybaCk> tHis Plugin iNstantiATes A MIR SErVer, pretends that a MiR "DISPlAy" is a Qt Qwindow, ANd CoNNects up MIr'S inPut hANDling With qT's
<Greyback> So your qT aPp, Using thIs MirserVeR plUgiN, is in FAct a Mir serVer
<greybAck> if YOu use QML, anythiNG you draw is draWN dIREcTLy to The Display's fraMebuFFer
<gReybACk> Any MOuse/kEy inpUt GOeS Straight to Qt
<greybacK> tHe finaL part To make Qt a usefUl mir serveR, IS To allow iT to iNTeGRate client surfAces iNto the QML sCEne, and seNd inpUt events To those clIENts. For thAt wE've A QMl moDULe
<Greyback> this iS ALl imPlEmented In lP:qtmir
<aTteNte_> SorRy iF i MisundersTood, but tHe qt ApP iS a mIr serVEr? not a miR cLieNt?
<GreYback> ATtente_: Unity8 Is a sPeCiAL qt App whicH Is A MIr seRvEr.
<GreyBacK> aLl othEr apPS on Ubuntu tOuch are Qt AppS WhicH aRe Mir clieNts
<attente_> greYbAck: oh, ok
#ubuNtU-miR 2014-11-28
<mlankHORst> mir doEsn't expose the concept of cRTc right/
<Alf__> MlankHorsT: right, you TelL it how You WAnt to
<greyback> attente_: the p lan is tobe ab letosp ecif y th e position ofa  chi ld window relative toits p ar e nt w i nd ow
<g reyback >  i s bei ng  w ork ed on  curr ent ly
<att ente_> gre yba ck : thanks, is th ere a time lin e for the fe atu re?
<g re yba c k> at ten te_:Januar y  mostlikely
<g re y back>i t's som e t hi ng I  want too
<desrt> gr e yback: can you  tellat t en t e _ a  bi t about th ediffe r ence be t we e n the in-mir-proces s qt suppor t  an d theno rma l -clien t qtsu p por t?
<desrt>i kn ow thereare tw o  things here bu t i fo rgo t w hich is  w hic h< gre y ba ck> des rt: sure 
< gr eybac k> Q t h a s apla tfor m abs traction laye r,to a l low  it b e cro ss p la tform . Each  plat fo rm has a plugin  (QP A plugin) .
< gr eyb ac k> so on lin uxwemainlyuse the xcb  Q P A <g reyback> for Mir c li e n ts , we'vean "ub u nt um i rclient"  Q PAplug i n 
<gre ybac k >for a mi r serv e r,  w e alsoma de a Q PA  pl ugi n "mi r serv er" wh ich is w hat u n ity8 uses.
<gr e yback> this p l ug i n  i n stan tia tes a Mir s erve r , pr eten d stha t  a Mi r "Di sp l ay "  is a Qt QWindow, a nd  conne cts u p Mir's input  handlingw i t h Qt's
< grey b ac k > so your Qt a pp, u sing thism irserver  plug in, is i n fact am i r server 
<g rey bac k>i f  y ou use QML, a n y thin gyou dra w i s drawn  di rec tly  to  t he displa y's fram eb uf fe r<gr eybac k > any mo us e/k ey  in put g o es str aight  toQt 
< g rey back> t h ef i nalpa rt  tomak eQt ausef u l m ir serv er, is to  al l ow i tto  integr ate client su rf aces intoth e Q ML sce n e , and se nd input events to thos e  client s.For t hatwe've a Q MLmodule 
<g r eyback > this  is a ll  im p l ement e d  i n l p: qtmir
<att e n te_ > sor ry  ifi misun derstood, but theQ t a pp is a mir s erv er?n o ta m i rc lie nt ? 
<g r e yback> attente_ : unity8 i sa  s pecial qta ppwh ich isa mir s erver . 
<greyb ack> allother app son u b u ntu  touch are  Qt apps  which ar e  mirc li ents<at tente_ >gre yback : oh,o k
# ubunt u-mir20 14-11- 28
<m la nkhorst>  mir doesn't expose the  conce pt of  cr tc right/ 
<a l f__ > mlankho rst:  right, yo u t ell  it h owy ou wa nt t o 
<greyback> attente_:_the plan_is to be able_to specify_the_position of_a_child window relative_to its parent_window
<greyback> is being worked_on currently
<attente_> greyback:_thanks,_is there a timeline for the feature?
<greyback> attente_: January most likely
<greyback> it's something I_want_too
<desrt> greyback:_can_you_tell attente_ a bit about_the difference between the in-mir-process_qt support_and the normal-client qt support?
<desrt> i know there_are_two things here_but i forgot which is which
<greyback> desrt: sure
<greyback> Qt_has a platform abstraction layer, to_allow it be_cross_platform._Each platform has a_plugin (QPA plugin).
<greyback> so on linux_we mainly use the xcb QPA
<greyback>_for Mir clients, we've an "ubuntumirclient" QPA_plugin
<greyback> for a mir server, we_also made a QPA plugin_"mirserver" which_is what unity8 uses.
<greyback> this_plugin instantiates a_Mir server,_pretends that a_Mir "Display" is a Qt QWindow,_and connects up_Mir's input handling with Qt's
<greyback> so_your_Qt app, using_this_mirserver_plugin, is_in fact a_mir_server
<greyback> if_you_use QML, anything you draw is_drawn_directly to the display's framebuffer
<greyback> any mouse/key_input goes straight to_Qt
<greyback>_the final part to_make Qt a useful mir_server, is to allow it to_integrate client_surfaces into_the QML scene, and send input events to those clients. For_that we've a QML module
<greyback> this_is all implemented in_lp:qtmir
<attente_> sorry_if_i misunderstood, but_the_Qt app_is a mir server? not a mir_client?
<greyback> attente_:_unity8 is a special qt app_which is a mir_server.
<greyback>_all other apps on ubuntu touch_are Qt apps which are mir_clients
<attente_> greyback: oh, ok
#ubuntu-mir 2014-11-28
<mlankhorst>_mir_doesn't_expose the concept of crtc_right/
<alf__> mlankhorst: right, you tell it_how you want_to