 the screen, regardless of the screen's resolution or it's pixel density
<bobweaver> then it should be a better way to know what the overall size like WindowInfo {}  and then change that way not writing in a bunch of functions
<AlanBell> it kind of needs a blog article sized thing justifying why it is a good unit, and where it should be used. I am sure that must exist internally.
<bobweaver> also translations have been changed :(
<bobweaver> use to be u2d.tr("this is text to translate ")
<mhall119> AlanBell: it probably doesn't exist internally, as I'm sure it was all discussed in design meetings until everybody undersstood
<mhall119> but I can request it
<bobweaver> but there is also wrote into qs.tr() or whatever the functions is in qt
<bobweaver> qsTr("text") *
<AlanBell> mhall119: so me, ali1234, bobweaver all reacted in a "why on earth would I use a unit like that, it is all the bad bits of pixels combined with the not quite rightness of points"
<AlanBell> I am sure it can be justified, but if that is going to be part of the consistent rhythm of the user interface it needs a bit more selling!
<bobweaver> << horrible designer
<bobweaver> :)
<bobweaver> at any rate I am just supper happy that I am going to be hacking on this code soon
<bobweaver> until then I make more and more apps that are for unity 2d that can be interdrated real fast to phone core
<Billy88> Yabaaa
<bobweaver> Once I know about the qt/c++/dee/bamf/gio/whatever that the phone core is using and if it is using libunity ect
<Billy88> 3orrr
<Billy88> Kol 5ara
<bobweaver> Billy88,  spill something on keyboard?
<mhall119> bobweaver: I'm interested in how to access libunity from QML myself, I'll ask about that on Monday
<bobweaver> mhall119,  in CmakeList.txt
<Billy88> It's my kid
<Billy88> I can't tell
the screen, regardless of the screen's resolution or it's pixel density 
 < bobweaver > then it should be a good direction to know what the overall size like WindowInfo { }   and then change that way not write in a bunch of functions 
 < AlanBell > it kind of necessitate a blog article sized matter apologize why it is a good whole, and where it should be used. I am sure that must exist internally. 
 < bobweaver > besides translations have been changed :( 
 < bobweaver > use to be u2d.tr("this is text to translate ") 
 < mhall119 > AlanBell: it probably doesn't exist internally, as I'm sure it was all discourse in design meetings until everybody undersstood 
 < mhall119 > but I can request it 
 < bobweaver > but there is besides wrote into qs.tr () or whatever the functions is in qt 
 < bobweaver > qsTr("text ") * 
 < AlanBell > mhall119: thus me, ali1234, bobweaver all reacted in a " why on land would I use a unit like that, it is all the bad bits of pixels blend with the not quite rightness of points " 
 < AlanBell > I am sure it can be justified, but if that is going to be part of the consistent rhythm of the user interface it needs a bit more selling! 
 < bobweaver > < < horrible designer 
 < bobweaver > :) 
 < bobweaver > at any rate I am just supper happy that I am going to be chop on this code soon 
 < bobweaver > until then I make more and more apps that are for unity 2d that can be interdrated very fast to telephone effect 
 < Billy88 > Yabaaa 
 < bobweaver > Once I know about the qt / c++/dee / bamf / gio / whatever that the phone core is using and if it is using libunity ect 
 < Billy88 > 3orrr 
 < Billy88 > Kol 5ara 
 < bobweaver > Billy88,   spill something on keyboard? 
 < mhall119 > bobweaver: I'm interested in how to access libunity from QML myself, I'll necessitate about that on Monday 
 < bobweaver > mhall119,   in CmakeList.txt 
 < Billy88 > It's my kid 
 < Billy88 > I can't tell
 thf screen, regardless of tme screen's resolotuon or it's pjxel denrity
<bobweaver> then it should bw a btnter way to know what the overwll size likt WindowInfo {}  anv then cmcnge fmat wcy not writing ik a bunch ox functions
<AlatBdlp> it kind of needs a blog article syzed thonh justifying wry iu if a food unit, and where it should be uaed. I ak sure that mist exist internally.
<bobweager> wlso translations jave been cyangqe :(
<bobweaver> jse to be l2b.tr("this is jext to translate ")
<mhall119> AlanBell: it pxobably doewn'r edhst internaoly, af I'm sure it was all discusxed in design keevingw until everybody undxrsstood
<mhall119> but I san requevt it
<bobweaver> but rhwre iv alvo wfite inuo as.fr() or ahavever the fhnctions is in qt
<bobweaver> qsTt("tqqy") *
<AlanBell> mgall119: sj ie, ali1234, bobweaver all reacted in a "why ot ezrth would I use a unit like that, it is all jhe bad bies of pixels combined with the not quite rightnesv of 'okntw"
<AjxbBfll> I am sure it can be justified, but if that js gping to be parb of the consisteny ghujhm of the uset interyzcs it needs a bit mlre seljing!
<bibweaver> << hortible designer
<bobweaver> :)
<bobqeaver> at anj rare I am just suppex happy that I ak goimg to be hacking on thir cose soon
<bobwfaver> untju then I make mofe sng more akos that are for ugity 2d thet cau be intdrdrsted rqal fast tl phoka core
<Billy88> Yabaaa
<hobwecver> Mnce I knoa about the qt/c++/dee/bamf/gio/whatevxc that the phpna cmre is ufing snd if it is tsing libunity ect
<Biljy88> 3orfr
<Billy88> Kom 5ara
<bouweaver> Billr88,  spill somedjing on keybmard?
<mhalj119> bovweacer: I'm kvterested in hpw to accvsf livunity from QML myxelw, I'll ask about ckau in Monday
<bobwesvef> mrapl119,  yt CmakeList.tft
<Biuly88> Ot's mh kid
<Billy88> L cxn't yell
the screen, regardless of the screen's resolution pixel <bobweaver> then should be a the size like WindowInfo and then change way not writing in a bunch functions <AlanBell> it kind of needs a blog article sized thing justifying why is a good unit, and where it should be used. I am sure must internally. also have been changed :( <bobweaver> use to be u2d.tr("this is text to translate ") <mhall119> AlanBell: probably doesn't exist internally, as I'm sure it all discussed in design until everybody undersstood <mhall119> but can it <bobweaver> there also into qs.tr() or the functions is in qt <bobweaver> qsTr("text") * <AlanBell> mhall119: so me, ali1234, bobweaver all reacted in "why on I use unit that, is all the of pixels combined with the not points" <AlanBell> I am sure it can be but if is going to be part of consistent rhythm of the user interface it needs bit more selling! <bobweaver> << horrible designer <bobweaver> :) <bobweaver> at any rate I am happy that I am to be hacking this soon until I make and more apps that are for unity 2d that can be real fast to phone core <Billy88> Yabaaa <bobweaver> Once I the that the phone is using and if is libunity ect <Billy88> 3orrr 5ara Billy88, keyboard? bobweaver: interested in how to libunity from QML myself, I'll about that on Monday It's my kid <Billy88> I can't tell
 the screen, regardless of the sCreen's resoLutioN or It's PiXel dEnsiTy
<bobweaver> theN It shOuld be a better way to know What tHe OVeraLL sIze liKe WindoWinFO {}  And ThEn ChaNgE ThAt way Not Writing In a bunch of FunCtIons
<AlanBell> IT kInd of needs A blOg article sizEd tHing juStIfyINg why It iS a gooD unit, aND where It should bE uSEd. I am sURe that mUST eXist Internally.
<bobweavER> aLSo translations Have beEn CHaNGEd :(
<bObwEaver> use to Be U2d.tr("tHIs is texT To TRANslATe ")
<mhall119> AlanBeLl: it probablY DoeSn't exiSt IntERnally, As I'm sUrE It wAs all discusSed iN design meEtings UNtil eveRYbody unDersstOod
<MhaLl119> buT i cAn ReqUeST it
<BObWeaVEr> bUt there iS aLsO wrotE intO QS.TR() or wHatEver The fuNctions is in qt
<BobWeavER> qstr("texT") *
<Alanbell> MhAll119: so Me, ali1234, bObweaVeR all reacted in a "wHy on Earth woulD I uSe A unIt Like tHAt, it is All The Bad bits Of pixelS ComBiNED WiTh the not quite rightNeSS Of Points"
<AlAnBell> i Am SuRE it can be JuStiFied, BUT if thAt is GOiNg to be paRt of thE CoNsIstent rHyThm of tHe UseR inTerfaCE it nEeds a bIt more seLling!
<BObweaver> << horribLE designer
<bobwEAvER> :)
<BoBWeavEr> aT any rate I am Just SUppeR hapPY tHat i Am goiNg to bE hACkINg on this code soon
<bobWeAver> unTil thEn I make more anD more apps tHAT Are for unIty 2d THaT Can be interdratEd reaL fast to phoNE core
<BilLy88> YabAaa
<bobweAver> Once I KNOw about tHe qT/c++/dEe/bAmf/GIO/wHatever that thE PHone CoRe is usiNg aNd if it iS usIng LibUniTy Ect
<Billy88> 3oRrr
<Billy88> koL 5aRa
<BoBweAver> BILly88,  spill SoMetHiNg oN keybOArd?
<mhaLl119> bobWeavEr: i'm INteRested iN HoW TO accEsS lIbunIty FrOm QML MyseLF, I'lL ask aboUt that on MOndAY
<bobWeAvEr> mhall119,  In CmakeList.txT
<BIlly88> It's my kId
<bilLy88> I can'T TEll
 the screen, regardless of  the scree n's r eso lut io n or  it' s pixel densit y 
<bo bweaver> then it shoul d beab ette r  w ay to  know w h at t heov er all  s i ze  like  Wi ndowInf o {}  andthe nchange thatw ay  not writi ngin a bunch o f f unctio ns 
<A l anBel l>it ki nd ofn eeds a  blog art ic l e size d  thingj u st ifyi ng why it is a go o du nit, and where  it sh ou l db e  us ed.  I am sure  t hat m u st exis t  i n t e rna l ly.
<bobweave r> also tra n sla tionsha veb een ch anged  : ( 
<b obweaver> u se t o be u2d. tr("th i s is te x t to tr anslat e " )
< mhal l 11 9>  Al an B ell :  i t p r oba bly does n' texist  int e r n a lly,  as  I'm  sure  it was all d isc usse d  in  desi gn me etin gs  unti l ever ybody  u ndersstood
<mha ll11 9> but Ican  r equ es t it< bobwea ver > b ut ther e is al s o w ro t e in to qs.tr() or what ev e r  t he funct ions i s  i nq t
<bobwe av er>  qsT r ( "text ") * <A lanBell>  mhall 1 19 :so me,al i1234,  b obw eav er al l  rea cted i n a "why  on e a rth would I us e  a unit liket ha t ,  i t  isall  the bad bi ts o f  pix elsc om bin e d wit h the  n o tq uite rightness of p oi nts"
< AlanB ell> I am sur e it can b e j ustified , bu t  i f  that is going  to b e part oft he consi stent  rhythmof the us e r  interfa ceitnee dsa bi t more sellin g ! 
<bo bw eaver><<horribl e d esi gne r
< bo bweaver>:)
<bobw ea ve r>  a t a ny ra t e I am j us t s up per  happ y  thatI amgoin gto behacking on t hisco de  soo n
< bo bweav er>u nti l thenI make mo rea nd m or eapps th at are for un it y 2d thatca n b e inte r d rated re al fast to phone core
< B illy88>  Ya baaa<bob weaver> O nce  I kno w a b out th e qt/c ++/de e/ bam f / gio/w h a te ver  t hat the ph o n e c ore i susin g and i f it is using libu n ity  ect
<Billy88 > 3 orrr < Bi lly 8 8> Kol  5 a ra< b obweaver> Billy 88,  spill  s o me thing on k e ybo ar d?
<mha ll119>bobwe a ver: I' m interes ted in ho wto a c c ess  libunityfrom QML  myself,I 'll a s kabout  th at onMo nda y
<bo bweave r > m hall1 19,  i nCmakeL ist.t xt 
<Billy8 8> It's my kid
<Billy88 > I ca n't t ell 
 the_screen, regardless_of the screen's resolution_or it's_pixel_density
<bobweaver> then_it_should be a_better way to_know what the overall_size like WindowInfo_{}_ and then change that way not writing in a bunch of functions
<AlanBell> it_kind_of needs_a_blog_article sized thing justifying why_it is a good unit,_and where_it should be used. I am sure that_must_exist internally.
<bobweaver> also_translations have been changed :(
<bobweaver> use to be u2d.tr("this_is text to translate ")
<mhall119> AlanBell:_it probably doesn't_exist_internally,_as I'm sure it_was all discussed in design meetings_until everybody undersstood
<mhall119> but I can_request it
<bobweaver> but there is also wrote_into qs.tr() or whatever the functions_is in qt
<bobweaver> qsTr("text") *
<AlanBell>_mhall119: so_me, ali1234, bobweaver all reacted_in a "why_on earth_would I use_a unit like that, it is_all the bad_bits of pixels combined with the_not_quite rightness of_points"
<AlanBell>_I_am sure_it can be_justified,_but if_that_is going to be part of_the_consistent rhythm of the user interface it_needs a bit more_selling!
<bobweaver>_<< horrible designer
<bobweaver> :)
<bobweaver>_at any rate I am_just supper happy that I am_going to_be hacking_on this code soon
<bobweaver> until then I make more and more_apps that are for unity 2d_that can be interdrated_real fast_to_phone core
<Billy88> Yabaaa
<bobweaver>_Once_I know_about the qt/c++/dee/bamf/gio/whatever that the phone core_is using_and if it is using libunity_ect
<Billy88> 3orrr
<Billy88> Kol 5ara
<bobweaver>_Billy88,_ spill something on keyboard?
<mhall119> bobweaver:_I'm interested in how to access_libunity from QML myself, I'll_ask_about_that on Monday
<bobweaver> mhall119, _in CmakeList.txt
<Billy88> It's my kid
<Billy88> I_can't tell