[02:10] <GnoNayme> can anyone explain the benefits of scopes over the software center?
[05:00] <avi_> my problem is that my app depend on somelib and i have packaged that lib in the click. but this lib has a translation files, i put them in this path data/usr/share/locale/*/LC_ MESSAGES/somelib.mo and the translation are not loaded. what i did wronge?
[05:24] <simosx> avi_, the lib tries to find the translations using the "translation domain" (some name that is defined in the source code). Also, it uses some path to look into. Can you run 'strace' on the app so that you can figure out what files it tries to open?
[05:25] <avi_> simosx, in the emulator i think i cant run it.... i will try..
[05:43] <simosx> avi_, "strace" is preinstalled on the phone (or I installed it easily). You could change the .desktop file so that it runs the command through strace and have an idea what files are being tried to open.
[05:45] <avi_> ok. that idea. i will try it. thank you
[06:46] <Mirv> popey: can you check if the newest comment in bug #1462989 means that the patch shouldn't go in, ie that Renato claims the API should be just used differently?
[07:11] <dholbach> good morning
[07:42] <dpm> mzanetti, good morning! Do you happen to know if there is a way already for app developers to detect if their app is running on unity 8 on a phone or on a bigger form factor (e.g. the desktop)?
[07:49] <dpm> or bzoltan, you might know too? ^
[07:50] <bzoltan> dpm:  as I remember the idea is not to expose such API to the apps.
[07:52] <dpm> bzoltan, oh, I see, so what's the plan to do the detection, if it's not via API?
[07:54] <didrocks> dpm: application width size I guess + other capabilities
[07:54] <didrocks> like mouse, keyboard, sensors…
[07:54] <didrocks> basically you do some progressive enhancement, as in the web
[07:55] <didrocks> and base on capabilities rather on form factor
[07:55] <bzoltan> dpm: The plan is that apps should not care about this.. all happens automagically, layouts, UX, visuals, etc
[07:55] <dpm> didrocks, I do not quite understand. So how does the app dev detect capabilities, if there is no API?
[07:56] <justCarakas> Anybody know why I am still on r19 on my nexus 4 ? It keeps saying software is up to date
[07:56] <didrocks> dpm: ah, for sensors and such, I guess there will (is?) some API
[07:56] <didrocks> dpm: but basically you won't have "get_form_factor()" -> desktop/phone/tv…
[07:57] <seb128> justCarakas, that's rather a question for #ubuntu-touch
[07:57] <justCarakas> ok thx
[07:58] <dpm> didrocks, bzoltan, there is no API that I know of in the SDK to detect whether a mouse is present or the monitor size. So I guess my question is, is there a way to work around it and make a guess at form factor/capabilities, until the full vision is implemented?
[07:58] <seb128> dpm, define "form factor", what part of the program do you want to change and when?
[07:59] <didrocks> really, we should remove the "form factor" part of this question, it's about capabilities really, and on the API, I'll let the sdk team answering, I'm not fluent enough yet to know if there is anything :)
[08:00] <seb128> didrocks, well screen size matters and it's not really a "capability"
[08:01] <seb128> but then it should probably check the width rather than a "form"
[08:01] <dpm> seb128, as an example, the reminders app uses the Layouts API to switch between different layouts if running on a phone or on a tablet. I'd like to know how the app can detect it's running on a desktop with monitor and use the tablet layout, but not at full screen
[08:02] <dpm> seb128, or e.g. the terminal app: it has a button to show the OSK on the phone. If running in a desktop setting, with a monitor and hardware keyboard, it should hide the OSK button
[08:02] <seb128> dpm, those seem different cases
[08:03] <didrocks> seb128: screen size is capability
[08:03] <dpm> right, one is about layout, the other one about hardware detection
[08:03] <seb128> didrocks, k, weird vocabulary
[08:04] <seb128> dpm, layout is just how width is your window, so you know if you have space for several column, no?
[08:04] <didrocks> dpm: I guess you typical example is "I want my app to be fullscreen if screen_size =< 50gu", otherwise, I switch my layout to be 2 columns and request at least 51gu
[08:04] <didrocks> (when the app opens)
[08:05] <seb128> didrocks, it's like "my screen is capable of displaying pixel" wououou ;-)
[08:05] <dpm> :)didrocks, so can I detect "if screen_size"
[08:05] <dpm> sorry, pressed enter too quick
[08:05] <didrocks> seb128: there is a difference between "capable fo displaying pixel and capable of displaying xxx pixels"
[08:05] <didrocks> "wououou"
[08:05] <dpm> can I detect "if screen_size =< 50gu"?
[08:05] <seb128> dpm, didrocks, I would expect the "put things in fullscreen" to be a shell thing rather than a per-application choice?
[08:05] <didrocks> dpm: yeah, that's a question for the sdk team
[08:06] <didrocks> seb128: initial window size? I don't really know…
[08:06] <seb128> didrocks, well, the width is not inherent to the screen, when I resize something on my desktop the display doesn't change properties
[08:06] <seb128> it's not capable of more pixels because I dnd-ed a corner of the win
[08:06] <didrocks> seb128: reread my sentence about "when the app opens"
[08:06] <didrocks> but whatever
[08:06] <dpm> bzoltan, can you perhaps enlighten us on the widh detection question? ^^
[08:07] <seb128> dpm, you can tweak the layout on width < something
[08:07] <seb128> without having to query the screen
[08:07] <didrocks> I don't think it's dpm's question
[08:07] <seb128> just the width of the windows should tell you if you have space for e.g multi columns
[08:08] <dpm> seb128, right, but it's the available width I don't know how to query
[08:08] <seb128> dpm, "available"?
[08:08] <didrocks> dpm: did you try http://doc.qt.io/qt-5/qscreen.html?
[08:08] <seb128> the layout depends of what size you application has no?
[08:08] <seb128> not of the size of the screen
[08:08] <seb128> like on a desktop you wouldn't display the multiple columns if the win is 100 pixels width
[08:09] <seb128> it would rather match the linear layout used on e.g a phone
[08:09] <seb128> so it's the actual win geometry that you want no?
[08:11] <dpm> seb128, right, so if we switch layouts on e.g. "if width >= 100GU" you are saying that I should set the initial size of the app at 100GU and it should just do the right thing?
[08:12] <seb128> well, it's up to you
[08:12] <seb128> on e.g the phone the shell is going to put your app fullscreen
[08:12] <seb128> so you don't get the define the width
[08:12] <seb128> to define*
[08:12] <dpm> yeah, that's what I mean
[08:12] <seb128> well just do if width >= 100 gu
[08:12] <seb128> on a bq you are going to get 40gu or something and be under it
[08:13] <seb128> and if you try on your desktop you can resize to be over 100gu
[08:13] <seb128> or even specify the default width, so it's used on your desktop where things are not maximized
[08:14] <zsombi> dpm: so, if your app is having width: 100GU, your app will run on 40GU on device no matter of what's the size you defined, but on desktop will run on 100GU
[08:14] <dpm> that's what I'm trying to say, so is the guidance to set the default width to be > than a phone layout and then a) on a phone the app will be resized to full screen and b) on the destkop the default width will be used
[08:14] <zsombi> dpm: you can prepare your layout based on this: if mainview.width >= 100GU use this layout, otherwise use that
[08:15] <zsombi> dpm: there is no guideline, but I think these doesn't have to be "guidelined"
[08:15] <dpm> zsombi, yeah, that'd be the condition, but what sets the default mainview.width if the app is not running full screen?
[08:16] <zsombi> dpm: all you need to know is that apps run "fullscreen" on phone, no mater if you've set your app size to (0,0)
[08:16] <dpm> right, so I get the fullscreen case
[08:17] <dpm> zsombi, so when I've got a huge monitor and I don't want the app to run fullscreen on launch, then is the guidance to a) set mainview.width = "something wide" and b) have the layouts switch condition to "if mainview.width >= 'something big'"?
[08:18] <zsombi> dpm: that depends on the app
[08:18] <zsombi> dpm: if the app knows that on desktop it should run on 100/80 GU, then it should set its width.height to that size
[08:19] <dpm> zsombi, so how does the app "know"?
[08:19] <zsombi> dpm: so then on phone it will run fullscreen, and on desktop, or any widnowed mode will run on 100/80 GU
[08:19] <zsombi> dpm: well, I guess designs for desktop have some window metrics, right?
[08:20] <zsombi> dpm: so they can use those metrics to set their app size
[08:20] <zsombi> dpm: you go and set MainView { width: units.gu(100); height: units.gu(80) } right?
[08:20] <dpm> zsombi, I think we're talking about the same thing. So if I as an app developer I want my app to be 100GU wide on a big monitor, I should just set the initial size to that, and that's it
[08:20] <zsombi> dpm: right
[08:21] <dpm> ok, then it's all clear
[08:22] <dpm> zsombi, so the next question is about other capabilities: how do I tell whether there is a phyisical keyboard attached?
[08:22] <zsombi> dpm: why would you need that?
[08:22] <zsombi> dpm: use case pls
[08:22] <zsombi> or more
[08:22] <dpm> zsombi, e.g. the terminal app: it has a button to show the OSK on the phone. If running in a desktop setting, with a monitor and hardware keyboard, it should hide the OSK button
[08:23] <zsombi> dpm: hmm... that's weird... why does it have that?
[08:23] <zsombi> dpm: beside, if you attach a kbd to a tablet, I guess both should work, right?
[08:24] <dpm> zsombi, the osk automatic switching really got in the way of using the terminal. I'm not sure you used it before the button was added, but it was a nightmare for scrolling and screen jumping up and down
[08:25] <dpm> zsombi, why should the OSK work if I've got a hardware keyboard attached? But in any case, we're talking about the desktop case, not tablet
[08:26] <zsombi> dpm: for the presence of the OSK we have an undocumented API... QuickUtils.inputMethodProvider property... perhaps we should expose these...
[08:26] <zsombi> dpm: well, because you may wanna still use the prediction
[08:26] <zsombi> dpm: without OSK there's no predictive text
[08:27] <zsombi> dpm: and haven't you seen touch screen enabled desktops? :)
[08:27] <dpm> zsombi, I definitely don't want to use predictive text while typing CLI commands ;)
[08:27] <zsombi> dpm: ok, that is one use case, but the terminsl app is not teh only app in the world ;)
[08:27] <dpm> zsombi, no, but you asked for the use case I was looking at atm :)
[08:27] <zsombi> dpm: right :)
[08:28] <zsombi> dpm: as said, we have an internal class for that... beside, I think Qt will have something there...
[08:28]  * dpm looks at documentation
[08:28] <zsombi> dpm: otoh, OSK presence can also be detected inm from the input method size
[08:29] <dpm> zsombi, where can I find out how to use QuickUtils.inputMethodProvider? a quick google glance didn't return any doc results
[08:30] <zsombi> dpm: of course not, it's internal
[08:30] <zsombi> it's not documented
[08:30] <zsombi> dpm: and you should not even use that
[08:31] <dpm> oh, so I thought that was the suggestion
[08:31]  * zsombi looks for the Qt.inputMethod.rectangle or whatever property
[08:32] <zsombi> dpm: http://doc.qt.io/qt-5/qml-qtqml-qt.html#inputMethod-prop -> http://doc.qt.io/qt-5/qinputmethod.html -> http://doc.qt.io/qt-5/qinputmethod.html#keyboardRectangle-prop
[08:32] <zsombi> dpm: if keyboardRectangle.size is 0, there's no OSK
[08:33] <zsombi> dpm: so no need to show that button
[08:33] <dpm> awesome, thanks zsombi
[08:34] <zsombi> dpm: in any other cases, the apps shouldn't even know what devices are attached to the computer
[08:35] <zsombi> dpm: toolkit elements would handle all the diffs, i.e. focusing on Tab/Shift+Tab, Scrollbar thumb when hovered over mouse, Bottom edge hint component, MultiColumnView for responsive pagestacks, etc, etc
[08:36] <dpm> cool
[08:38] <zsombi> dpm: if the keyboardRectangle is not giving the desired results, we have to think of a better solution
[08:38] <dpm> ok
[08:41] <popey> 09:22 < dpm> zsombi, e.g. the terminal app: it has a button to show the OSK on the phone. If running in a desktop setting, with a  monitor and hardware keyboard, it should hide the OSK button
[08:41] <popey> dpm: we (me and fillipo) have discussed this at length
[08:41] <popey> I am not convined we perma-hide the OSX on a 'desktop'
[08:41] <popey> (given we already have decided not to go for rigid phone / tablet / desktop form factors - as discussed above)
[08:42] <popey> e.g. what if I _want_ the osk on screen, I don't think we should forcibly hide it and never let it be brought on screen just because there is a hardware keyboard
[08:43] <dpm> popey, well, what I noticed is that button has no effect on the desktop, so there is no OSK at all
[08:43] <dpm> that was what prompted me to file the bug
[08:44] <popey> thats not a terminal bug though
[08:44] <popey> thats the fact that the OSK isn't packaged up in unity8 desktop seed
[08:45] <dpm> popey, aha. In that case, perhaps it could be a setting in the same way "show control keys bar" is
[08:45] <popey> I still don't agree.
[08:46] <popey> I think it should fade out so it's not so obtrusive
[08:46] <dpm> fade out permanently?
[08:47] <popey> no, just be less obvious
[08:47] <popey> it can get in the way sometimes
[08:47] <popey> higher transparency over time if you've not used it
[08:48] <popey> same could apply on tablet/phone uses too
[08:48] <popey> if you're using it for monitoring / tailing a log file, and rarely interact, it's more useful if those buttons fade away
[08:48] <dpm> if I'm using terminal on a big monitor and physical keyboard, and I've made a decision not to use the OSK, why should I have the icon shown at all times obstructing the view, even if it's faded out?
[08:48] <popey> but as a new user you need to know where they are/were
[08:49] <popey> if it's faded out it's not obstructing
[08:49] <dpm> right, I think it's fine to show it on first launch, but why shouldn't I be able to hide it, just as we do with the controls bar?
[08:50] <popey> more settings, more code to maintain, more possibility it gets hidden and not easy to discover how to re-enable
[08:50] <popey> there's 3 buttons, not just the osk one
[08:51] <Mirv> zbenjamin: I kicked another build of Qt Creator 3.5 to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-023/+packages so that it's usable now that Qt 5.4.2 got in to wily
[08:51] <dpm> right, but the other two are settings and tabs
[08:52] <zbenjamin> Mirv: there were new changes in upstream that we need yesterday, does it pull the master or did you create a tarball manually?
[08:52] <zbenjamin> Mirv: the sdk plugin will only compile against the current branch
[08:52] <Mirv> zbenjamin: no it's just the same tarball, if you want the latest git I can do that too
[08:52] <Mirv> zbenjamin: alright
[08:52] <popey> yes, and if you don't have a touch screen you could argue you don't need the tabs button
[08:52] <Mirv> zbenjamin: so, ~test5 upcoming soonish to the same place
[08:52] <zbenjamin> Mirv: :) cool
[08:53] <popey> anway, i think we should discuss this on the bug report
[08:53] <dpm> anyway, so we do have different opinions, perhaps we can ask a designer
[08:53] <dpm> in any case, terminal looks awesome on the unity 8 session :)
[08:54] <dpm> I'm using it on my unity 7 session as my main terminal now
[08:54] <popey> dpm: you using the fat package?
[08:56] <dpm> popey, no, it appears on the store, but I couldn't install it (I'm not sure if store installs are disabled, or if I've got network issues), so I kicked off a wily build on my personal PPA (in order not to mess up the core apps one) and then installed the .deb inside the container
[08:56] <dpm> popey, can you install apps from the store?
[08:58] <mivoligo> davidcalle: hi, IIRC you made a guide about adding translation support for the apps on the phone. Unfortunately I can't find this guide now
[08:58] <popey> dpm: not on my unity8lxc install, i thought it might be my end, but you saying it breaks for you too?
[08:58] <popey> Also, I couldn't login to u1
[08:59] <popey> not sure where these bugs should go, or if they should be filed
[08:59] <davidcalle> mivoligo, https://developer.ubuntu.com/en/apps/qml/tutorials/internationalizing-your-app/
[08:59] <mivoligo> davidcalle: great, thanks :)
[08:59] <davidcalle> mivoligo, yw :)
[08:59] <dpm> popey, I didn't even get to a u1 log in. In my case, I can see apps in the click store, but when I click on the "Install" button, nothing happens
[09:00] <dpm> popey, I noticed the browser crashes on start, so I couldn't check if it was a network issue. But now I've got terminal installed, I guess I could find out if I've got network at all. In any case, the network indicator shows no networks available
[09:02] <popey> yeah, mine is wired, and can go online
[09:05] <dpm> ok
[09:06] <dpm> I need to try if the browser still crashes after I ran an update on the container
[09:06] <popey> dpm: how did you update?
[09:06] <popey> from outside or inside?
[09:07] <dpm> popey, I tried both, as I had a broken package which I couldn't fix from outside. So I first did a 'sudo unity8-lxc-setup --update-lxc'
[09:07] <popey> ok
[09:07] <dpm> (from outside)
[09:07] <dpm> and then a 'sudo lxc-attach -n unity8-lxc' to fix the broken package from inside the container
[09:08] <dpm> and then I went back to doing the update with 'sudo unity8-lxc-setup --update-lxc'
[09:08] <dpm> as I didn't know if that ran other steps, so I preferred to do it this was just in case
[09:08] <dpm> *way
[09:10]  * popey tries that
[09:10] <dpm> seb128, if we find bugs such as not being able to log into ubuntuone to install packages on the unity8 desktop session, is lp:unity8-desktop-session the best place to file bugs?
[09:10] <popey> yeah, you can't install apps from the store because you dont have a u1 account
[09:10] <popey> that's annoying
[09:13] <seb128> dpm, you can, or on the specific packages
[09:13] <seb128> what is not working when you try to log in?
[09:16] <dpm> seb128, in my case I'm not even shown the prompt when trying to install an app from the store, but I haven't tried to explicitly go to the settings app and add the account yet. popey first flagged the issue that he couldn't add the u1 account
[09:17] <seb128> popey, dpm, is there a bug open about not being able to add the account?
[09:17] <seb128> it worked when I tried previous cycle
[09:17] <popey> just updating, will try again and file if not
[09:17] <seb128> we even demoed installing clicks fro u8 in washington
[09:17] <seb128> popey, thanks
[09:17] <seb128> what was the issue?
[09:18] <popey> nothing happens when you click U1 in system settings -> accounts
[09:19] <popey> yeah, still broken
[09:22] <dpm> popey, does the browser work for you?
[09:22] <popey> dpm: no, crashes
[09:22] <popey> will file that one next :)
[09:23] <dpm> same here
[09:24] <dpm> having the browser working and being able to install apps would be two massive improvements
[09:24] <popey> https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1466009 there you go
[09:24] <popey> ya
[09:26] <popey> dpm: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1466012
[09:28] <dpm> popey, thanks. Do you have the browser installed on your unity 7 session too?
[09:29] <popey> looks like it, yes
[09:30] <popey> dpm: can you logout? my session freezes when I try to
[09:30] <dpm> me too, not sure if it makes a difference. The LXC container mounts /home, so I don't know if there are any browser settings that interfere with each other. FWIW, having terminal installed on both systems does not seem to pose any problems
[09:31] <popey> getting segfaults in location service too
[09:31] <dpm> I got a freeze yesterday, but I generally have been able to log out
[09:31] <popey> [Wed Jun 17 10:19:10 2015] ubuntu-location[3106]: segfault at 0 ip           (null) sp 00007ffc0dee1288 error 14 in ubuntu-location-serviced[400000+49000]
[09:31] <popey> lots of those
[09:31] <popey> oh, it finally logged out, was just really slow, probably io bound on mediascanner
[09:32] <popey> dpm: webbrowser-app works fine under unity7
[09:33] <dpm> yeah, here too. And if I try to uninstall it, it wants to remove qtcreator-plugin-ubuntu and ubuntu-sdk, so I'll leave it alone :)
[09:33] <popey> heh
[09:33] <popey> maybe rm .config/webbrowser-app and .cache/webbrowser-app ?
[09:34] <popey> (this, btw, is why I wanted to run Unity8 on a separate machine, the logging out/in all the time is kinda annoying)
[09:34] <popey> also, now I'm getting the welcome thing flickering repeatedly
[09:34]  * popey reboots
[09:35] <dpm> yeah, but I don't have that many machines :)
[09:35] <popey> seems it doesn't like you flipping unity 8 -> 7 -> 8
[09:36] <dpm> oSoMoN, do you have any hints on bug 1466012 - maybe a known bug, perhaps there is a workaround?
[09:40] <oSoMoN> dpm, I marked it as duplicate of bug #1457458
[09:41] <oSoMoN> known bug, no known workaround that I know of
[09:43] <dpm> ok, thanks oSoMoN. Sounds more a bug for Mir rather than Oxide, if I understand it correctly?
[09:43] <oSoMoN> not sure where the bug is, chrisccoulson can you clarify? ^
[09:44] <chrisccoulson> the bug is in oxide
[09:45] <mivoligo> mzanetti: hi, there's something wrong with the sound when playing MvsM after the latest OTA update. The sound sometimes goes up or down suddenly. And I mean the system sound.
[09:50] <mzanetti> mivoligo, yeah... it's a bug in the system
[09:50] <mzanetti> I should probably report it
[09:50] <mivoligo> mzanetti: ah, ok, was it like that before?
[09:51] <mzanetti> don't remember. been using vivid for 3 months now
[09:51] <mivoligo> :)
[10:02] <LemmyK> Can anyone tell my what the status on the new "calendar sync backend" is?
[10:06] <popey> LemmyK: I don't think that'll be ready until July or so.
[10:07] <LemmyK> Thanks, is there a bug to track the progres of this?
[10:07] <karni> What's the advised solution here? "Too many authentication failures for phablet from 127.0.0.1 port 50877 ssh2" -- trying to install a click form beloved QtC ;) to krillin
[10:08] <popey> LemmyK: i dont think so
[10:09] <mzanetti> rpadovani, hey
[10:10] <rpadovani> mzanetti, o/
[10:10] <mzanetti> rpadovani, have a reminders branch to test/review :)
[10:10] <rpadovani> mzanetti, ok, I' ll take a look after lunch :-)
[10:10] <mzanetti> enjoy the lunch
[10:33] <nik90> mzanetti: I am hitting a strange issue on the latest image rc-proposed/ubuntu r163, where shell rotation doesn't happen while app rotates...https://imgur.com/Gs43FQH
[10:34] <nik90> mzanetti: was it disabled or is this a bug?
[10:35] <mzanetti> no... hasn't been disabled
[10:36] <mzanetti> nik90, can't repro here
[10:36] <mzanetti> nik90, any steps to trigger this?
[10:37] <nik90> mzanetti: I just updated to r163 and then opened the system settings app to test shell rotation on my N4. I am going to reboot my phone and see if that helps
[10:37] <mzanetti> nik90, what channel?
[10:38] <nik90> mzanetti: ubuntu-touch/rc-proposed/ubuntu on Nexus $
[10:38] <nik90> Nexus 4*
[10:38] <mzanetti> nik90, I've seen comments on G+ that some other Nexus users complain about not having the update yet
[10:38]  * mzanetti digs out his nexus4
[10:39] <mzanetti> nik90, have you ever seen shellRotation on that device and it stopped working, or you didn't ever see it yet?
[10:39] <nik90> mzanetti: I had it in the before images...just so happens this image it stopped working...strange behavior.
[10:40] <nik90> mzanetti: I was the one who posted screenshots on g+ of shell rotation
[10:41] <mzanetti> nik90, right...
[10:43] <nik90> mzanetti: I think its not unity8's fault..the image is messed up...my calculator and music apps which I updated yesterday have all been reverted to old version. Somehow the image upgrade downgraded everything or something!
[10:43] <mzanetti> weird
[10:44] <nik90> yeah I have no idea wth happened..just going to reflash everything from scratch again to confirm this
[10:45] <nik90> mzanetti: fyi I had unity8 8.02+15.04.20150603.1-0ubuntu1 installed. Is that the latest?
[10:46] <nik90> http://paste.ubuntu.com/11729878/
[10:47] <mzanetti> nik90, 8.10+15.04.20150612-0ubuntu1
[10:48] <mzanetti> nik90, http://paste.ubuntu.com/11729884/
[10:48] <nik90> mzanetti: crazy...let me finish reflashing to confirm the issue and report to sil
[10:48] <mzanetti> nik90, looks like you have a different PPA
[10:48] <nik90> mzanetti: god knows how considering I just did a normal update and nothing else
[10:55] <dropp> Hi, can someone tell me where the PopupUtils.close() function is documented? Thanks!
[10:55] <mzanetti> nik90, I just flashed ubuntu-touch/rc-proposed/ubuntu-developer and it does not rotate indeed
[10:56] <nik90> mzanetti: that is intended..the ubuntu-developer images are not updated regularly.
[10:56] <nik90> mzanetti: sry I meant that is known..not sure why the ubuntu-developer images were not updated
[10:57] <mzanetti> nik90, it does seem to have this ppa tho: stable-phone-overlay
[10:57] <mzanetti> unlike the one you pasted
[10:57] <nik90> hmm
[10:58] <nik90> mzanetti: I just reflashed ubuntu-touch/rc-proposed/ubuntu and it still has unity 8.02+15.04.20150603.1-0ubuntu1!
[10:59] <davmor2> dropp: https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Popups.PopupBase/ not sure if that is what you are after
[11:02] <Mirv> zbenjamin: bzoltan: ok git snapshot of today's Qt Creator built successfully at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-023/+packages
[11:02] <dpm> popey, in the interim, until we have the u1 login fixed, I created a set of daily .deb builds of the core apps at https://code.launchpad.net/~dpm/+archive/ubuntu/ppa?field.series_filter=wily - the first installation needs to happen from the host (as there is no terminal otherwise). If that's the terminal app, then the rest of .debs can be installed from the unity8 session with the terminal
[11:03] <zbenjamin> Mirv: awesome :D, the plugin also needs a rebuild though
[11:03] <popey> dpm: i already have daily builds of clicks
[11:03] <zbenjamin> Mirv: i pushed the changes there yesterday
[11:04] <dpm> popey, ah, cool, with fat packaging?
[11:04] <popey> for those that need it, yes
[11:04] <popey> i just scp them over and use pkcon to install them
[11:04] <dpm> awesome
[11:05] <Mirv> zbenjamin: ok, updating from  lp:~zeller-benjamin/qtcreator-plugin-ubuntu/sdk-refactor2 .. I don't think it'd build successfully in a PPA though due to that "ubuntu" directory requirement
[11:05] <dpm> popey, so these are built with the scripts to create the fat packages you mentioned a while ago, right? Where can I find them?
[11:05] <popey> they build on my laptop at the moment because it requires access to the click chroot
[11:06] <popey> I want to move it to "the cloud" though
[11:06] <dropp> davmor2: okay thanks, but what are the parameters? :)
[11:06] <popey> needs a lot of space for all the chroots
[11:08] <dropp> davmor2: it's used in this example: https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Popups.Dialog/
[11:10] <dropp> davmor2: here is another example which uses a advanced version of it http://askubuntu.com/a/306562
[11:10] <davmor2> dropp: I'm not a dev I just knew how to look for the docs page.
[11:11] <dropp> davmor2: hehe, that's what i did in advance
[11:11] <davmor2> dropp: dpm maybe able to help you more
[11:13] <zsombi> nik90: did you manage to test the alarm thing?
[11:14] <dpm> t1mp, zsombi, perhaps you can help dropp with the question about where the  PopupUtils.close() function is documented? I cannot find it under https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Popups/
[11:15] <zsombi> dpm: for some reason none of the .js file documentation is taken...
[11:16] <dpm> zsombi, is qdoc building the docs?
[11:16] <zsombi> dpm: yes
[11:16] <nik90> zsombi: sry no..I am in the process now though
[11:17] <dropp> zsombi: so the docs will be available soon?
[11:17] <zsombi> dropp: I don't know how to fix that tbh
[11:17] <dropp> oh okay
[11:17] <dpm> zsombi, in that case, the doc should be available locally in the ubuntu-ui-toolkit-doc package
[11:17]  * dpm looks
[11:17] <zsombi> dpm: yes, it should
[11:19] <dpm> zsombi, any hint on which of these it could be? http://pastebin.ubuntu.com/11729978/
[11:19] <zsombi> dpm: none, the qdoc doesn' teven take JS files in
[11:20] <dpm> zsombi, so the docs are not generated in the package, then?
[11:20] <zsombi> dpm: exactly
[11:20] <dpm> ok, so that's what needs to be fixed before they can be published in the site
[11:21] <Mirv> zbenjamin: ok the plugin compiled fine and I installed it in wily, but the plugin is not visible in QtC.. not sure what's wrong this time, the directories etc should be correct
[11:22] <zbenjamin> Mirv: meh, crap.. Did i maybe not merge all of your fixes?
[11:22] <dropp> zsombi, dpm: should i file a bug report somewhere?
[11:23] <Mirv> zbenjamin: tarball of the deb:s at http://people.ubuntu.com/~timo-jyrinki/QtCreator/
[11:24] <zbenjamin> Kaleo: does the Ubuntu.Components somehow change default fonts/ fontsizes / margins for the whole application? Because importing Ubuntu.Components does break the title in the new project wizard in QtCreator
[11:24] <zbenjamin> Kaleo: t1mp suggested you might know about that
[11:25] <Mirv> zbenjamin: sorry, correction, works!!
[11:25] <Mirv> zbenjamin: I've no idea what happened, I had them installed and then they woosh disappeared somehow.
[11:25] <zbenjamin> Mirv: so it works?
[11:26] <dpm> dropp, yes, please on https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+filebug
[11:26] <dpm> thanks!
[11:27] <Mirv> zbenjamin: ah, I accidentally ran dpkg -i *.deb outside of the wily, not inside..
[11:27] <Mirv> zbenjamin: so yes, sorry for the alarm :) seems good!
[11:27] <zsombi> zbenjamin: we set the default font, in the plugin
[11:27] <zbenjamin> Mirv: awesome :D
[11:27] <zbenjamin> zsombi: do you know where?
[11:27] <zsombi> zbenjamin: in the plugin itself, we set Ubuntu family font
[11:34] <zbenjamin> zsombi: sooo should i add the UITK to that bug as well?
[11:36] <zsombi> zbenjamin: you can, but no idea how to fix that
[11:37] <zsombi> zbenjamin: what you can try is not to set the size, perhaps that would be enough
[11:38] <zsombi> zbenjamin: like QGuiApplication::getFont(), set the family, and set it back, perhaps that would be enough for the toolkit and for the QWidgets as well
[11:38] <zsombi> zbenjamin: also, set the weight
[11:38] <zsombi> and try it out
[11:40] <zbenjamin> zsombi: hm yeah i could reset the default font back after i loaded the uitk
[11:42] <Mirv> zbenjamin: tried building the plugin in PPA :D https://launchpadlibrarian.net/209307420/buildlog_ubuntu-wily-amd64.qtcreator-plugin-ubuntu_3.5.0%2B15.10.20150617-0ubuntu1~wily1~test1_BUILDING.txt.gz
[11:42] <Mirv> zbenjamin: that error is because of the directory mangling/hardcoding
[11:47] <zbenjamin> zsombi: that fixes it , indeed
[11:48] <zbenjamin> zsombi: why do we need to set the default font in the first place?
[11:56] <nik90> zsombi: I am unable to get clock app to crash on vivid desktop before applying your fix.
[11:56] <nik90> zsombi: what steps did you take to get it to crash?
[11:57] <nik90> I have one alarm and tried enabling/disabling it a couple of times. Changed the alarm time, labels etc..
[12:02] <nik90> popey: Can you help me test https://code.launchpad.net/~nik90/ubuntu-clock-app/lock-portrait-orientation/+merge/262053
[12:04] <popey> nik90: sure can
[12:04] <nik90> popey: be sure to be on r162 to get shell rotation
[12:05] <popey> kk
[12:05]  * nik90 brb in 5 misn
[12:08] <popey> nik90: hmm, i dont have a device with shell rotation enabled.
[12:13] <nik90> popey: which device and channel?
[12:14] <popey> ubuntu-touch/rc-proposed/meizu.en on arale, 27
[12:14] <popey> ubuntu-touch/rc-proposed/bq-aquaris.en on krillin, 38
[12:15] <nik90> popey: for N4 it seems we have shell-rotation on r262 but not on r163...turns out r163 is a OTA-4 image for testing purposes. The same could have been done for the BQ and Meize rc-proposed images..not sure
[12:15] <popey> I no longer have an n4
[12:15] <nik90> popey: oh wow .. upgrading to newer devices eh ;)
[12:15] <popey> hah
[12:16] <nik90> no worries I will wait for victor since I am not sure about the meizu and bq image status
[12:16] <ogra_> popey, ubuntu-touch/rc-proposed/meizu.en 27 definitely has shell rotation here
[12:17] <ogra_> (since 25 actually)
[12:17] <popey> oh, so it does
[12:18] <popey> sorry nik90, my mistake
[12:18] <nik90> popey: do you need a click?
[12:18] <popey> nah, i can make one
[12:18] <nik90> k
[12:22] <rpadovani> mzanetti, o/
[12:22] <mzanetti> rpadovani, hey
[12:23] <rpadovani> mzanetti, so, improve-viewer and content-hub have to be reviewed, right?
[12:23] <mzanetti> yep
[12:30] <karni> zbenjamin: where can I learn what the load(ubuntu-click) magic does?
[12:33] <zbenjamin> karni: check out the /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/ubuntu-click.prf file
[12:33] <karni> thank you zbenjamin, exactly what I've been looking for
[12:33] <zbenjamin> karni: and /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/ubuntu-click-tools.prf
[12:33] <karni> :)
[12:34] <zbenjamin> karni: the *-tools file is loaded after your project settings have been parsed, the ubunu-click.prf is loaded when load() is executed
[12:34] <karni> zbenjamin: great, thank you :)
[12:50] <zsombi> zbenjamin: we need to set the default font because Qt brings Sans font and not Ubuntu
[12:51] <zsombi> zbenjamin: and setting the font in every label has performance impact, beside text inputs won't use the default font
[12:51] <zsombi> nik90: I had the same: I enabled a disabled alarm...
[12:52] <zsombi> nik90: the alarm did not change its position in the model, then it crashed... not every time, but after I did the changes, I never got it crashing anynore
[12:53] <nik90> zsombi: I am atm testing it on the phone by getting to crash before and then verifying after the patch is applied
[12:53] <zsombi> nik90: cool, thx
[12:53] <zsombi> nik90: I get to finish the MultiColumnView before I leave, so I'm pretty busy now, thx for help
[12:54] <nik90> zsombi: np..I will commment on the MP after I am done
[12:55] <zsombi> nik90: the prob is that I'll be away after that...
[12:56] <nik90> zsombi: oh on hols? Then go ahead with the merge
[12:56] <karni> Is MultiColumnView available somewhere for testing?
[12:56] <zsombi> karni: comin in staging soon
[12:56] <karni> is it the one related to different behavior of PageStack for converged UIs?
[12:56] <karni> zsombi: cheers
[12:56] <zsombi> karni: but Header work is still to come from t1mp
[12:57]  * karni nod
[12:57] <nik90> zsombi: I cannot reliably validate it without taking more time. You should approve it if you're confident.
[12:57] <zsombi> karni: yep
[12:57] <zsombi> nik90: I can be confident if your test shows different thing
[12:58] <zsombi> nik90: beside. it was made against trunk, so it needs a landing...
[12:58] <zsombi> nik90: however, if this goes to ota5, then we have time
[12:59] <zsombi> karni: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/multicolumnview/+merge/261703
[13:01] <karni> zsombi: nice :)
[13:04] <zsombi> karni: note, MultiColumnView with 1 column will be the PageStack
[13:04] <karni> makes sense
[13:04] <zsombi> so most probably PageStack will be based on MultiColumnView
[13:05] <karni> zsombi: when are these expected to be available for testing in staging? (this + usable header, in case current work is required)?
[13:06] <zsombi> karni: the final is expected to be in staging by wk31, but the header work should be there within 2 weeks
[13:07] <zsombi> karni: so stable will be on wk31
[13:07] <zsombi> 32
[13:07] <zsombi> eventually
[13:07] <karni> zsombi: sorry, I don't have week numbers enabled in calendar. what does that translate to in human speech :D?
[13:07] <karni> 2 weeks sounds good :)
[13:08] <karni> great, actually
[13:08] <zsombi> karni: I have a proto for the Messaging app to test it, so you can check that https://code.launchpad.net/~zsombi/messaging-app/prototypeWithMCV
[13:09] <zsombi> karni: the adaptive column handling is good to go actually
[13:09] <zsombi> karni: we are on wk 25 now
[13:09] <karni> oh that's cool!
[13:09] <karni> aha :)
[13:09] <zsombi> karni: we may optimize it, or perhaps redo it if we see that we need some major header refactoring to get the header working properly
[13:10] <zsombi> karni: and header work is the bigger bone in this storry
[13:10] <karni> zsombi: sure, np. it'll be a while before I can lay my hands on it
[13:10] <zsombi> karni: I am writing some tests now and then it is ready for t1mp to continue with the header
[13:11] <karni> :thumbsup:
[13:11] <zsombi> karni: I'd recommend to play with the idea on using it, so we can get early feedback on API if we need to change sthing
[13:11] <zsombi> or if sthing is not clear from the docs
[13:13] <nik90> zsombi: good news..i got it to crash once before applying patch..haven't had it crash after applying patch and reproducing steps again..
[13:13] <zsombi> nik90: huhh...
[13:14] <nik90> zsombi: i had clock app open and changed the timezone manually .. and alarm can be enabled/disabled without any crash
[13:14] <nik90> on the phone that is
[13:14] <nik90> I had no luck on vivid desktop
[13:14] <zsombi> bzoltan: ^
[13:18] <nik90> zsombi: commented and approved in MP
[13:18] <zsombi> nik90: thx!!!
[13:18] <zsombi> nik90: as said, we may need to move this to ota5 :(
[13:19] <nik90> zsombi: that's fine..I am stil going to go ahead with a new clock app release since this crash exists in today's OTA-4 image.
[13:19] <nik90> zsombi: so clock-app is not the cause and shouldn't be blocked. I will take it up with popey and QA later today.
[13:19] <zsombi> nik90: cool!
[13:19] <seb128> nik90, what you said earlier, it means no stopwatch added to the default image before the16.04?
[13:20] <nik90> seb128: I am more or less sure unfortunately. The SDK will provide timer API only in 16.04 and I doubt I will get designs for stopwatch or timer before that happens with current focus on convergence.
[13:21] <seb128> nik90, do we need design to work on that? can't that just be hacked in whatever way you find to work and tweaked/redesigned later?
[13:22] <Elleo> nik90: looks like that menu rotation bug is fixed with the shell rotation stuff, so we can just land the rotation branch without automaticOrientation and then it'll start automatically working with OTA5 (since you no longer need to set automaticOrientation with shell rotation, it's controlled in the .desktop file then)
[13:23] <nik90> seb128: the problem is we don't use a standard tabs navigation model...once I add Tabs, the main clock app will get a page header and pretty much kill the clean look of the clock app. And I don't want to keep rewriting the clock app again and again because of design changes.
[13:23] <seb128> nik90, I see, I guess users can install one of the click store apps then ;-)
[13:23] <seb128> nik90, thanks
[13:24] <nik90> seb128: yeah .. its way too much work with fixing the autopilot, qml tests and so much that it just isn't worth the effort especially when later designs will be completely different :/
[13:25] <nik90> Elleo: it does fix it. I disabled automaticOrientation (as it was by default) in my branch. So yes we can land it as it is.
[13:26] <zsombi> t1mp: I feel we would need a function in MultiColumnView which would clear all the pages added...
[13:27] <t1mp> zsombi: we have removePages(page) already. If you pass the root page there, it clears everything.
[13:27] <seb128> nik90, why do you disable rotation?
[13:27] <zsombi> t1mp: well, the first column can have many "root" pages
[13:28] <nik90> seb128: because the clock app designs that I have up until now indicate that clock app was meant to run in the side-stage.
[13:28] <zsombi> t1mp: if you add a page with null page reference, that means the first column gets a new root, sibling to the other one, as the first colum pages do not have common parents
[13:28] <nik90> seb128: until I get further designs, best just to lock it in portrait mode.
[13:29] <seb128> k
[13:29] <seb128> it seems to work mostly fine in landscape, just miss some scrollable
[13:29] <seb128> but your choice I guess ;-)
[13:29] <t1mp> zsombi: still, you have a stack, even though with multiple columns. Each row in the stack only has one Page. So there is a top-most row (or bottom-most depending how you build it up)
[13:29] <t1mp> (bottom is better, since top() is usually the last page added)
[13:30] <zsombi> t1mp: dude... removePages(page) removes a tree
[13:30] <zsombi> t1mp: it removes all child pages of the given page including the page
[13:30] <t1mp> zsombi: yes
[13:30] <t1mp> zsombi: what would the clear function do?
[13:30] <zsombi> t1mp: so, if you add two pages to the first column, and you remove the first added one, that won't remove the second one
[13:31] <nik90> seb128: I just thought clock, address-book and dialer were similar in that aspect and designed to be in the side-stage, later we can use MultiColumn view and Flickable when we get to that stage.
[13:31] <zsombi> t1mp: because they can be both added with addPageToCurrentColumn(null, page);
[13:31] <zsombi> t1of course we can say that this is not good...
[13:31] <seb128> nik90, k
[13:31] <t1mp> zsombi: if you addToCurrent(page1); addToCurrent(page2), then removePages(page1) should remove both page1 and page2
[13:32] <zsombi> t1mp: and we can say that addPageTo[Current/Next]Column should always get a valid sourcePage property
[13:32] <zsombi> t1mp: you keep forgetting the second parameter man
[13:32] <zsombi> t1mp: the sourcePage
[13:33] <t1mp> zsombi: the sourcePage should be the first parameter, so you cannot leave it out
[13:33] <zsombi> t1mp: we are no longer working a s a stack, we are working as a tree
[13:33] <t1mp> zsombi: that's how you have it in the doc also
[13:33] <zsombi> t1mp: heh???!
[13:33] <zsombi> yes
[13:33] <zsombi> t1mp: but you can set it as null
[13:33] <zsombi> t1mp: in which case it adds to the first column
[13:33] <t1mp> let's not allow that, that will mess up everything
[13:33] <zsombi> t1mp: without having any parent page
[13:34] <zsombi> t1mp: ok, that's what I wanted to say
[13:34] <t1mp> ok
[13:34] <zsombi> t1mp: so the first page must then be set with primaryPage, right?
[13:34] <t1mp> yeah
[13:34] <zsombi> t1mp: deal
[13:34] <zsombi> :)
[13:34] <t1mp> and when adding a new page, its parentPage must be in the tree already
[13:35] <t1mp> not sure if parentPage is the best name though, because we have parents in the tree of Items already
[13:35] <t1mp> hmm
[13:35] <White> Hi everyone
[13:35] <t1mp> well parent is a very generic name that makes sense often to use
[13:35] <White> What's the topic?
[13:36] <zsombi> t1mp: sourcePage is we call aint we
[13:37] <t1mp> zsombi: https://docs.google.com/document/d/1bSoEynFzD3VAB8kLJW4lcVgtlEzwEF5_RicNQTIA-RY/edit# needs to be updated then
[13:37] <t1mp> zsombi: also the API at the top does not match the API a bit further down
[13:37] <zsombi> ah, ok
[13:45] <zsombi> t1mp: updated
[13:45] <zsombi> t1mp: also, should we allow to remove the primaryPage?
[13:45] <zsombi> t1mp: I think we shouldn't
[13:45] <t1mp> zsombi: don't forget https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/100-SectionBar/+merge/260502
[13:45] <t1mp> zsombi: no we don't allow to remove primaryPage
[13:46] <zsombi> t1mp: ok
[13:46] <zsombi> t1mp: update components.api
[13:46] <t1mp> zsombi: I did. The jenkins results are not from the latest revision
[13:46] <zsombi> t1mp: your MR fails
[13:46] <t1mp> FAILED: Continuous integration, rev:1558
[13:46] <t1mp> the last revision is 1564
[13:47] <zsombi> aha
[14:25] <zsombi> t1mp: happroved
[14:28] <t1mp> zsombi: great, thanks!
[14:30] <zsombi> t1mp: MultiColumnView MR is ready for you
[14:31] <t1mp> zsombi: ok, I was just checking it
[14:31] <t1mp> zsombi: you may want to change the commit message :)
[14:31] <zsombi> t1mp: yes, I will: )
[14:31] <zsombi> t1mp: done :)
[14:42] <t1mp> zsombi: https://docs.google.com/document/d/1bSoEynFzD3VAB8kLJW4lcVgtlEzwEF5_RicNQTIA-RY/edit#
[14:42] <t1mp> zsombi: ^ColumnViewConfiguration should be ColumnMetrics?
[14:43] <vitimiti> Can I set the parent of a pop up by using PopupUtils.open(component, parent)?
[15:08] <t1mp> vitimiti: no. The parent is always the root window, otherwise the popup cannot position itself freely in that window. But you can set the caller of the pop up
[15:10] <vitimiti> t1mp, I am trying to open a second dialog from a first dialog, but if I close the first dialog while doing so, the second one will be completely blocked, I can't press any buttons on it and have to close the window. The dialogs end up stacking up on the screen. Is there a solution for this? (can give the code)
[15:17] <t1mp> we don't support stacking of dialogs
[15:17] <t1mp> are there any designers around to give advice here?
[15:18] <t1mp> Femma_: ^?
[15:21] <Femma_> Stacking of dialogs is not a good idea
[15:22] <t1mp> vitimiti: what is your use case?
[15:23] <vitimiti> t1mp, I have a help dialog that would have two buttons: one is a "OK" button that should simply close the dialog, and the other one is an "About" button that opens a second dialog. If I don't close the Help dialog I can clearly see how the screen goes darker and darker as they stack on top of each other and the Help dialog is there after closing the About dialog. But if I close the Help dialog when opening the About dialog, the About
[15:23] <vitimiti> dialog's buttons won't work
[15:31] <t1mp> Femma_: ^do we have a pattern for cases like that?
[16:37] <mihir> hey popey
[16:37] <mihir> popey: could you suggest something on this https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1464459 ?
[16:37] <mihir> like which color would be better, or should we wait for the UX input ?
[16:42] <popey> hey mihir
[16:42] <popey> mihir: will ask design :)
[16:43] <mihir> popey: okay :)
[16:43] <popey> thanks mihir
[16:43] <popey> how you doing ?
[16:43] <mihir> popey: doing good , i know after long time was struggling for settling in new phase of life , finally kind of set up
[16:45] <popey> All settled in now?
[16:45] <JMulholland> mihir popey i’ll check on the latest from Visual Design
[16:45] <popey> thanks JMulholland
[16:45] <popey> See, I didn't even have to ask
[16:45] <JMulholland> theire doing some substantial work on overhauling style atm
[16:45] <JMulholland> *theyre
[16:47] <mihir> JMulholland: great just comment on that bug once you have final call for the same.
[16:51] <JMulholland> will do!
[16:52] <JMulholland> ^ mihir
[18:42] <rarara> hi people. I am trying to get started with app development in touch. However, all the examples in qtcreator contain an include of "../shared/shared.h" which is not present. How can I get it working? locate doesn't find any file like that and i didn't find anything on google. care to help?
[18:47] <nik90> rarara: yeah I have the same issue as well. I ended up just following the tutorial at developer.ubuntu.com when I started long time ago.
[18:58] <rarara> nik90: is the tutorial up to date? I will do it but the sdk is still installing
[18:59]  * nik90 checks
[19:00] <nik90> rarara: more or less they are..they are using some older imports but those will still work.
[19:01] <nik90> rarara: once you install ubuntu-sdk and use qtcreator, it has further detailed API information that you can read to know more about using a specific component.
[19:01] <nik90> rarara: how familiar are you with qt/qml programming?
[19:18] <nik90> mzanetti: Fixed portrait orientation for fahrplan at https://github.com/smurfy/fahrplan/pull/213. I had to lock it since it breaks badly in some places in landscape mode.
[19:18] <nik90> mzanetti: I think it would be best to wait for MultiColumnView to land in the Ubuntu SDK before we start work on landscape mode.
[19:19] <mzanetti> nik90, wow. that was fast
[19:20] <mzanetti> ah, you locked it down
[19:20] <mzanetti> nik90, works for me
[19:21] <nik90> mzanetti: had too..the OSK takes way too much space in landscape mode for the stations page to be of any use
[19:21] <nik90> s/had too/I had to
[19:21] <mzanetti> right... have this problem in more places
[19:22] <nik90> yes.
[19:23] <nik90> mzanetti: I tried to make a slightly fancier design by using icons to denote duration, station etc..but the listview starts crawling slowly..seems performance is good only without any icons.
[19:24] <mzanetti> huh
[19:24] <mzanetti> icons shouldn't be *that* bad
[19:26] <nik90> not sure what went wrong when I tried that..I will create like a demo branch to prove it :)
[20:30] <dubstar_04> is there any documentation for creating layouts with OptionSelector?
[20:38] <dubstar_04> Anyone here?
[20:40] <ogra_> it is more busy during the european workday ...
[20:43] <dubstar_04> Where are we supposed to get support as developers?
[20:53] <ogra_> here
[20:58] <dubstar_04> no one ever answers questions in here.
[20:59] <ogra_> thsi afternoon it was very busy ... in europe is is simply late and most devs seem to be in that timezome
[22:53] <totojay> hi
[22:55] <totojay> i'm french and i want to install touch on my nexus 5 under hammerhead anyone know xhere i can find a wikihow