**** BEGIN LOGGING AT Sat Mar 25 03:00:04 2017 Mar 25 08:31:09 morning Mar 25 08:49:59 Morning! Mar 25 08:57:07 Sorry for not being around much, been to Berlin for some days this week :P Mar 25 09:23:49 :) no pb, there is always much to do Mar 25 10:32:10 Herrie, HaDAk: quick mockup: https://www.dropbox.com/s/pti8i1yxnvqxz4h/luneos-camera-usage-newprefs.mkv?dl=0 Mar 25 10:34:12 (of course, I didn't spend much time on how the buttons and menus look like, it's just a tech preview of how it behaves) Mar 25 10:41:45 huh, lots of refinement to do on device :p https://www.dropbox.com/s/r819boy5ep67l62/19700308151444.png?dl=0 Mar 25 12:02:52 Tofe: Looks sweet Mar 25 12:03:04 Though the Galary should be in a separate app I'd say Mar 25 12:03:10 But not 100% sure Mar 25 12:03:20 I guess this could be easily used to create a separate app as well? Mar 25 12:03:46 I guess sticking it in LuneOS-Components and then using it in Camera app and also in Photos & Videos app might be the cleanest solution? Mar 25 13:26:36 Herrie: it's not really a gallery, it's just a preview of the last photos taken during this session Mar 25 13:30:00 Tofe: Ah Mar 25 13:30:24 But anyway the current Photos & Videos app we have is Enyo and not working, so we'd better make something in QML Mar 25 13:30:33 Hence my thoughts Mar 25 13:33:25 well, currently I'm doing one app, if someone steps up for a gallery app, welcome then :) Mar 25 13:34:09 PS: the "gallery" in the camera app is really a 10min thing, not really worth a component. If you find it disturbing, we can just cut it off Mar 25 14:44:45 Tofe: No I didn't look at the code, just "looked" like a galary to me ;) Mar 25 14:44:48 Doesn't bother me ;) Mar 25 15:17:28 Herrie: for the gallery page, I just thought I would let the user zoom on the image, but that's quite all Mar 25 15:18:10 Because you're right, browsing the images is the job of a separate app Mar 25 15:30:49 Tofe: It just looked very familiar to me ;) Maybe that's what I got confused :P Mar 25 15:36:33 Herrie: for a gallery app, what would you think of a media preview flow à-la-flicker ? Mar 25 15:55:49 Herrie: something like this: http://i.imgur.com/4YWlwkD.png Mar 25 15:59:50 Herrie: I would also like to help bringing Qt 5.7 to LuneOS, having the QtQuickControls2 LuneOS theming would be quick interesting; what's the status currently? Mar 25 16:00:07 s/quick/quite/ Mar 25 16:04:45 For 5.7 I remember it builds, however QtWebEngine tweaks would need to be ported again Mar 25 16:05:26 ok Mar 25 16:05:29 The Media Preview Flow looks OK, I'm just personally not a big fan of all the different sizes of images Mar 25 16:06:11 I understand Mar 25 16:07:12 I proposed it because, well, the code for it is lying out there; maybe we'll propose it someday through a tweak Mar 25 16:08:15 Tofe: Yeah Mar 25 16:08:25 THen again, might be worthwhile to go to 5.8 right away? Mar 25 16:08:43 Main work is always the webengine bits when upgrading QT Mar 25 16:09:06 I know 5.7 is key for the QtQuickControls2 and the wayland bits changed quite a bit Mar 25 16:09:14 The webengine bits, I can manage Mar 25 16:09:25 But I'd say going 5.6->5.8 is probably less work in the end then 5.6->5.7->5.8? Mar 25 16:10:26 The meta-qt5 layers are ther Mar 25 16:10:28 +e Mar 25 16:12:57 We'd need pyro for both, right? Mar 25 16:13:37 I guess so Mar 25 16:13:39 What are the blocking points for pyro? kernel support only? Mar 25 16:13:41 ANd that's another issue :S Mar 25 16:13:48 Tofe: Yeah kernel for Maguro & TP Mar 25 16:13:55 It boots otherwise to GUI Mar 25 16:13:59 Just have issues on FirstUse Mar 25 16:14:24 TP and Maguro don't build and/or run ? or you didn't try yet? Mar 25 16:14:36 Build but bootloop due to glibc Mar 25 16:14:43 ah, bummer Mar 25 16:14:45 & kernel incompatibility Mar 25 16:15:05 ok, so that's not only a matter of EOL support, it's a real dependency Mar 25 16:17:04 We did find some experimental kernels for both, right? Mar 25 16:18:22 I can try uprading maguro, the porting effort I did for CM12.1 is still fresh Mar 25 16:18:36 Tofe: Yeah might be worth it Mar 25 16:18:47 I can try to downgrade to glibc 2.23 as a test as well Mar 25 16:19:05 That's also an option yes Mar 25 16:19:33 But that is likely to cause havoc :P Mar 25 16:19:36 But can try Mar 25 16:19:45 Personnally it wouldn't be a drama to drop maguro support, but we should keep TP Mar 25 16:19:53 Tofe: Yeah Mar 25 16:19:57 Maguro is slow as hell :P Mar 25 16:20:09 But well ;) Mar 25 16:20:19 When you compare it to N4/N5 Mar 25 16:24:45 I got a pyro build here prebuilt anyway, will try the glibc downgrade to see if that does anything at all Mar 25 16:33:52 mmh the Ziyan 3.4 kernel for maguro doesn't seem to have been ever published publicly (i.e. probably still not working well) Mar 25 16:42:34 Tofe: Let me check Mar 25 16:43:11 Tofe: https://github.com/Ziyann/omap Mar 25 16:43:19 "Updated Galaxy Nexus kernel suitable for AOSP and CM based ROMs." Mar 25 16:43:43 https://github.com/Ziyann/omap/blob/cm-12.1/Makefile Mar 25 16:43:46 https://github.com/Ziyann/omap/tree/exp Mar 25 16:43:54 Tofe: Yeha that one is old Mar 25 16:44:04 But I thought you said you could use newer kernel with older CM? Mar 25 16:45:11 Well we use CM12.1, which isn't that old :) most kernels work for 4.4 - 7.0 with the same code Mar 25 16:45:34 (depending on drivers, though) Mar 25 16:45:39 Tofe: THere's also https://github.com/Unlegacy-Android/android_kernel_ti_omap4 Mar 25 16:45:49 Which is a generic 3.4 base for the omap4 Mar 25 16:46:21 Unlegacy seemed to say their kernel was not made to work with CM, I don't know to which extend Mar 25 16:46:59 I think both are fine, I'll begin with the one from Ziyann, it very up to date Mar 25 16:47:02 it's* Mar 25 16:47:27 ah, well, they're both the same :D Mar 25 16:47:47 Herrie: what's your preferred one? Mar 25 16:47:59 Tofe: No preference Mar 25 16:48:06 Try what you think might work Mar 25 16:48:18 Well we don't really use CM, so just kernel might be fine Mar 25 16:49:02 Ziyann seems to be the upstream, I'll take his Mar 25 16:51:30 Yeah he's the main maintainer of the Maguro kernel it seems' Mar 25 17:54:09 uh... what defconfig are they using? Mar 25 17:54:39 the last modification was done in espresso_defconfig, but that looks wrong Mar 25 17:59:56 espresso is galaxy tab 2 Mar 25 18:03:13 Herrie: I fear there is no 3.4.x kernel for maguro... Mar 25 18:11:00 FYI: http://forums.webosnation.com/hp-pre-3/331636-qt5-webos.html Mar 25 18:11:35 Guessing dkirker will be the most interested... Mar 25 18:18:58 Tofe, I love your radial menu! Would it be possible to have the second menu level also be radial? Mar 25 18:33:53 DougReeder: thanks :) well, yes, but then it'll be a bit different, as sometimes it'll be strings (like "4:3 8MP") Mar 25 18:36:35 Instead of icons? Mar 25 18:36:42 yes Mar 25 18:37:12 Can the text radiate out from the center? Mar 25 18:37:37 nothing is implemented, so, I'll say yes Mar 25 18:37:58 [smiles] a “mere matter of implementatioin” Mar 25 18:38:39 The radial items of the menu are actually drawn using HTML5 Canvas Mar 25 18:38:51 (for the background) Mar 25 18:42:35 Let me see how it looks like if I had a radial submenu Mar 25 18:42:46 [nods] Mar 25 18:44:19 Tofe: Hmmmz :S Mar 25 18:45:10 Herrie: but, well, it may be we now have a patched 3.4 kernel for the galaxy tab 2 ;) Mar 25 18:45:41 More seriously, I agree it doesn't look good for maguro here Mar 25 18:58:52 DougReeder: http://i.imgur.com/yFZFdZS.png ? Mar 25 18:59:25 That works; if text is long, can it wrap? Mar 25 18:59:35 Yes, we can Mar 25 18:59:57 (sorry, that's an outdated joke now) Mar 25 19:00:59 DougReeder: but it won't wrap in a nice curvingingly way, it'll be just a box wrapping Mar 25 19:02:09 However the text won't be that long; it has to stay concise, so that the user catch the meaning quickly Mar 25 19:02:52 HaDAk: an opinion on http://i.imgur.com/yFZFdZS.png ? Mar 25 19:09:54 DougReeder: I agree it looks good; I'll fill in the menus and submenus, and we'll see Mar 25 19:12:18 Tofe, we won’t ever need more than 8 items on one menu, right? Mar 25 19:13:15 Maybe on the main menu, but that's not an issue. On the submenu, I do hope it'll stay only a few options Mar 25 19:13:26 Actually 8 is for full circle, 4 or 5 is probably the limit for half-circle. Mar 25 19:13:51 The main menu can be rotated as much as we want Mar 25 19:14:01 And the rotation looks cool, but we should avoid that, to support muscle memory. Mar 25 19:14:04 the submenu, right now, is more static Mar 25 19:15:40 I'd say we have 4 settings that make 90% of use cases, and 3-4 more for the rest Mar 25 19:17:50 Flash & Timer are the ones I always use; maybe HaDaK has more stats on his own Mar 25 19:18:37 Can we vary the position, based on where the swipe enters the screen? Mar 25 19:19:30 not I understand what you mean Mar 25 19:19:32 We’d like the user to have muscle-memory for things like “swipe to 2-o-clock, then 4-o-clock” Mar 25 19:19:33 +sure Mar 25 19:20:06 Can the center of the radial menu, be the location where the swipe starts? Mar 25 19:20:51 Sorry, gotta go! Mar 25 19:20:53 ah, mh, I don't know, currently it's much more basic than that Mar 25 19:21:08 DougReeder: no pb, see you later :) **** ENDING LOGGING AT Sun Mar 26 03:00:03 2017