Wednesday, 2018-05-30

*** jjarven is now known as Guest8337200:39
*** ersatzmaus is now known as Guest2447400:39
*** xenu_ is now known as xenu02:44
*** frinring_ is now known as frinring03:04
*** birdzhang is now known as birdzhang_pc05:33
*** ecloud is now known as ecloud_wfh08:13
*** dch_ is now known as dch09:35
*** popey_ is now known as popey09:45
*** Guest24474 is now known as fledermaus11:49
FloR707Sorry for asking this again but last night I got no response.11:56
FloR707I figured out how to have ListItems with different heights depending on their content. But now I ran into a new issue. The SilicaListView needs to have a hight. Since the ListView is not the only component on the page I cannot say fill parent but I do not know the content height. Can I tell the ListView to be as tall as required to show all items or can I calculate the hight with Component.onCompleted?11:57
r0kk3rzFloR707: it sounds like you dont really want a listview12:04
r0kk3rzperhaps a repeater would more suit your situation12:04
FloR707Thanks for the hint. Have not been working with repeaters but I will try.12:09
FloR707Hmm it does not know sections12:11
r0kk3rzthey are quite basic12:11
elrosFloR707: you can use  ListView { height: contentHeight}12:26
FloR707Indeed you can. Thanks so much. This should be in the SilicaListView help12:30
FloR707I believe this page needs some updating anyway. It says you have to use Item for a delegate but that is not a good idea is it?12:31
r0kk3rz? everything in qml inherits from item12:32
elrosI don't think so, it's not specific for Silica components. It's here
FloR707ListItem works much better than Item.12:34
r0kk3rzits just an example12:35
nh1402[m]r0kk3rz: how goes the firefox dependency stuff?13:52
r0kk3rzmerobs is a little screwed at the moment which is annoying though13:53
r0kk3rzi got clang to clang, and i think that should be most of it13:55
nh1402[m]I've now dived into firefox extension development, so once I'm done with the current extension that I'm working on, I can work on a mobile view extension14:00
r0kk3rz[m]yeah i was hoping someone would sort that out14:01
r0kk3rz[m]i'll be quite surprised if the thing works at all tbh14:03
*** Nokius_ is now known as Nokius14:36
*** Guest37885 is now known as zumbi14:49
nh1402[m]I think what would be needed is a combination of a userChrome.css file and an extension, the extension for tab management, and the css file to move and scale UI stuff.15:03
r0kk3rz[m]i wonder how they implemented the fennec ui, and if you can tell desktop FF to use it15:08
leszekr0kk3rz[m]: you can't. You need to compile fennec on your own.15:22
nh1402[m]r0kk3rz: don't think you can anymore it used the old XUL thing15:23
leszekand that too15:24
r0kk3rzcompiling it is fine, but does it even work on things that arent android?15:25
nh1402[m]the other thing we could do is use the android backend, and link it to our own UI15:25
r0kk3rzfrom what ive gleaned the backends are the same15:26
leszekr0kk3rz: I think the version that came for Meego N9 wasn't touched by mozilla and should work fine with everything pre quantum as engine15:26
r0kk3rzwell the point of this is to use latest firefox-wayland15:27
leszekah hmm... then I am not sure. Needs its own UI I think and then you end up basically with what is already in SailfishOS in parts I fear15:28
r0kk3rzon tablet it shouldnt be too bad15:29
nh1402[m]I think fiddling with userChrome.css could be enough to make the UI mobile friendly15:32
r0kk3rzworth a go if i get that far atleast :D15:49
*** tadzik1 is now known as tadzik16:02
nh1402[m]you say the backends are the same but Android supports PWA16:10
r0kk3rzwont that mostly be an OS thing?16:41
r0kk3rzor do PWAs know which browser created them and use that engine16:42
*** apsilva1 is now known as apsilva18:13
*** feodoran is now known as Guest5270623:07
*** feodoran_ is now known as feodoran23:07

Generated by 2.17.1 by Marius Gedminas - find it at!