**** BEGIN LOGGING AT Thu Oct 17 02:59:58 2013 Oct 17 05:49:45 Morphis: Ah OK, can happen ;) Oct 17 06:34:30 Herrie, do we have all the entries for the WOCE logo still in the wiki? Oct 17 06:50:34 ka6sox: Yes we should, didn't remove any of them, why? Oct 17 06:51:28 http://webos-ports.org/wiki/LogoContest Oct 17 06:51:49 just checking :) Oct 17 07:07:06 morning Oct 17 08:45:25 morning! Oct 17 08:50:18 morphis: if you see any remaining layout issue, please tell; for me it seems quite ok now Oct 17 08:50:29 Tofe: will test it today Oct 17 08:53:38 mmmh maybe I could make the gesture area bigger. Oct 17 08:56:40 Tofe: one minor remark about the launcher layout Oct 17 08:56:52 a margin left and right would be good Oct 17 08:57:07 otherwise it looks really good Oct 17 09:04:54 morphis: ok, no problem Oct 17 11:29:43 morphis: jenkins switched to dora branches which were updated a bit today to match with latest master Oct 17 11:30:12 there is some issue with login to root without password Oct 17 11:30:22 I'm debugging why Oct 17 11:33:22 but builds are running already, because they will take quite long again Oct 17 12:15:54 good morning Oct 17 12:33:00 JaMa: great Oct 17 12:33:03 HaDAk: morning Oct 17 12:33:09 how's it goin? Oct 17 12:33:21 JaMa: you saw https://github.com/webOS-ports/changelog? Oct 17 12:33:29 HaDAk: like yesterday Oct 17 13:16:30 morphis: i did a bit of testing last night, and came up with a list of shit that i found broken in this build. i'm fairly certain you know about most of it, but i'm not sure how much has been added to the bug tracker. Oct 17 13:16:39 and, for the life of me, i can't remember the link to the bug tracker. Oct 17 13:16:55 Hahttp://issues.webos-ports.org/projects/ports Oct 17 13:17:02 s/Ha/HaDAk/ Oct 17 13:17:21 HaDAk: if you find a duplicate just extend the description of it Oct 17 13:17:32 ok. Oct 17 13:17:36 i'll look through the open ones. Oct 17 13:17:40 so many things broken/missing. Oct 17 13:17:50 i really, really wish i could code in whatever language you're coding in. Oct 17 13:17:57 i feel like i could tackle a lot of these issues myself. Oct 17 13:20:53 HaDAk: if you create the bug reports and document as best as possible you help me already very much Oct 17 13:21:00 HaDAk: btw. you know QML? Oct 17 13:21:10 nope Oct 17 13:23:17 if you know HTML and CSS you should be able to get to it very fast Oct 17 13:23:29 thats what we're using to implement the whole UI Oct 17 13:23:46 HaDAk: https://github.com/webOS-ports/luna-next-cardshell Oct 17 13:24:19 doesn't look awful Oct 17 13:24:27 lemme ask you this Oct 17 13:24:42 how hard would it be to segment off card view, and add a second card view above it? Oct 17 13:24:45 two rows of cards Oct 17 13:25:47 should be possible with less effort Oct 17 13:26:36 HaDAk: would be a good thing to enable with a simple tweak setting Oct 17 13:26:47 i had something else in mind. Oct 17 13:26:48 so the user can enable/disble it as he wants Oct 17 13:27:31 HaDAk: ? Oct 17 13:28:43 still thinking about this guy's mockup Oct 17 13:28:49 see the top of the image Oct 17 13:28:49 http://cl.ly/image/3U002L1k1L32 Oct 17 13:28:53 ack Oct 17 13:28:54 wrong one Oct 17 13:29:02 this one: http://cl.ly/image/2a1a0N2H272s Oct 17 13:30:14 my thought is... Oct 17 13:30:36 if we had a "second card view", we could have apps as widgets. Oct 17 13:30:43 That's a widget deck ;) Oct 17 13:30:54 it's something we've talked about in here before, and not hte first time i've advocated it. Oct 17 13:30:59 i think people are coming around to the idea though :P Oct 17 13:31:29 The first one with side-by-side is cool too in landscape! I already added both to the wiki as nice to have :P Oct 17 13:31:39 quite some time ago ;) Oct 17 13:31:58 yeah, i know Herrie|Work :) Oct 17 13:32:02 and i agree Oct 17 13:32:05 http://webos-ports.org/wiki/Luna_Next Oct 17 13:32:07 side-by-side would be *awesome* on a tablet. Oct 17 13:32:25 Would make a unique feature! Oct 17 13:32:40 No other OS has it afaik Oct 17 13:32:43 http://webos-ports.org/wiki/File:NewDeviceMenu-preview1.png <-- HATE the color icons. i think they need to be more simple, and less colorful. Oct 17 13:32:58 i think some samsung builds of android have something similar Oct 17 13:33:42 Color is details, idea of the device menu is a lot nicer compared to original device menu Oct 17 13:34:06 Icons well you could make those part of a skin if needed :P Oct 17 13:34:45 skins Oct 17 13:34:47 * HaDAk shudders Oct 17 13:34:55 i actually prefer the old device menu Oct 17 13:35:25 and if it's invoked the same way, it should be right justified Oct 17 13:35:32 It's cumbersome for me if you use it a lot to switch stuff on/off. Could have both and switch with Tweaks option? Oct 17 13:35:57 use tweaks to enable/disable certain toggles, i'd say. Oct 17 13:36:09 like, if you ALWAYS have wifi on, no matter what… i wouldn't want a wifi toggle there. Oct 17 13:36:23 or if you never change the automatic brightness…why put a toggle? Oct 17 13:36:28 Anyway I don't like skins either :P My webOS is stock with custom bg only :P Oct 17 13:36:37 :) Oct 17 13:37:14 morphis: when playing with the n7 build last night, i felt like the gesture area is too small. Oct 17 13:37:17 it's like…15 px high Oct 17 13:37:24 i'd rather see it about 4x as tall. Oct 17 13:37:34 tbh, i'd like it to be about as tall as the android soft button area Oct 17 13:37:46 Well I toggle them all quite often to be honest :) Wifi, data, BT and brightness multiple times/day! Brightness on my Veer is around 15 normally but that doesn't cut it outside :P Oct 17 13:38:59 with als, i never touch mine Oct 17 13:39:30 I'm all for flexibility and options. Could loose some of the options myself too but would be cool if we had the flexibility! Oct 17 13:39:51 flexibility is king. that's what tweaks is for. Oct 17 13:40:01 but consider this: Oct 17 13:40:19 you're a user that's *never* seen webos before. you turn it on for the first time, and you're greeted with…………….every option under the sun already enabled? Oct 17 13:40:22 or, simplicity? Oct 17 13:44:34 Herrie: i dont' see anything in here (or i'm not looking hard enough) about the keyboard not being visible *at all* Oct 17 13:44:38 is that a known issue? Oct 17 13:46:35 Keyboard as in on-screen? I guess this is Maliit that's still not functional? Oct 17 13:46:52 on-screen, yes. nexus 7 build. Oct 17 13:47:08 if i tap in a textarea, it doesn't come up. Oct 17 13:47:08 ever. Oct 17 13:47:24 Quite sure that's broken Maliit... morphis can confirm Oct 17 13:47:37 what's Malitt? Oct 17 13:48:13 WOP switched from keyboard that was there to Maliit framework for input but migration/ports wasn't fully done yet Oct 17 13:48:37 i have no idea what you're talking about. Oct 17 13:48:39 www.maliit.org Oct 17 13:51:43 oh Oct 17 13:52:04 are we going to make sure to skin it properly, as webos? Oct 17 13:52:11 also 5th row for tablets? Oct 17 13:53:03 although, i suppose that's neither here nor there until it actually WORKS Oct 17 13:53:37 was swype based off of this? Oct 17 13:53:39 http://www.youtube.com/watch?v=JOI5g129rtM Oct 17 13:58:30 HaDAk: we sure are going to make it nice to use :) It just takes some time to integrate it, plus the fact that Maliit only migrated lately to Qt5, afaik Oct 17 14:06:57 suer. Oct 17 14:07:05 so, it doesn't work but that's a known issue Oct 17 14:07:11 and is actively being worked on Oct 17 14:07:12 right? Oct 17 14:07:59 right Oct 17 14:11:26 other assumptions i'm going to make: Oct 17 14:12:57 no lock screen, no notifications, no volume display, no automatic brightness control, screen dimming while i'm actively using it, justtype doesn't do anything when you tap it, tap ripple appears to be off-center from where you actually touch (perhaps the origin tap is the top left pixel of the animation?), and tossing a card off the top isn't fluid Oct 17 14:12:59 all known issues? Oct 17 14:18:57 the tap ripple has been fixed yesterday, but apart from that, yes, we have a lot to do Oct 17 14:20:05 I didn't find yet a good way to implement the physics for tossing a card off in QML Oct 17 14:24:35 If you want to try QML, you're welcome :) It's actually quite easy to try LunaNext UI on a desktop machine with simply Qt 5.1 installed Oct 17 14:37:35 HaDAk: yeah, we've a lot to do Oct 17 14:39:21 oh, another thing that's been driving me nuts Oct 17 14:39:31 when you swipe, it creates a tap ripple where you first touch the screen. Oct 17 14:39:46 i don't think webos did that before. Oct 17 14:42:11 HaDAk: the tap ripple currently doesn't respect any gestures Oct 17 14:42:20 when you put your finger somewhere it creates one Oct 17 14:42:23 yep, that's what said. :) Oct 17 14:42:25 it drives me nuts. Oct 17 14:42:32 feel free to open a bug Oct 17 14:45:57 morphis: yes I've seen changelog Oct 17 14:46:36 i opened a bug on it Oct 17 14:47:05 JaMa: I think just wget it when we open a new stage should be enough for now Oct 17 15:04:07 morphis: if we can ensure that it will be always updated before new stage is started then yes :) Oct 17 15:04:40 JaMa: I think we have until we find a better, automatic way Oct 17 15:04:47 morphis: I can add grep, checking that version included in it is matching Oct 17 15:04:59 but problem is that the jenkins job isn't reentrant at least now Oct 17 15:04:59 JaMa: that would be good Oct 17 15:05:36 because it really renames workspace and does last sync to wip "stage" before renaming it on server too Oct 17 15:06:06 so easiest way would be to just show error and the fix would require manual wget from file server Oct 17 15:06:38 do I understand correctly that version here will match with latest staging number, right? Oct 17 15:08:29 ah or I'll do it before calling staging_new.sh Oct 17 15:08:38 and fail soon enough Oct 17 15:13:20 JaMa: platformVersion should be the number of the feed Oct 17 15:14:34 morphis: can you add entry for stage 2 so I can see what you mean or even also for 3, because I think that current changelog is actually from stage 3 Oct 17 15:14:37 JaMa: version is just the version number of the manifest format Oct 17 15:15:03 JaMa: I can update the number ot 3 Oct 17 15:15:24 did someone already started building from dora branches (except jenkins)? Oct 17 15:15:43 there are 2 changes for oe-core which invalidate most checksums, but are needed to support newer tar version Oct 17 15:15:55 which is on many builders now (including mine :)) Oct 17 15:16:47 JaMa: updated Oct 17 15:17:01 JaMa: no Oct 17 15:17:25 ok, killing pending builds and updating oe-core branch Oct 17 15:17:40 JaMa: ok Oct 17 15:17:58 Tofe|Away: I need your help when you're back Oct 17 15:21:40 morning Oct 17 15:26:01 Garfonso: hey Oct 17 15:47:54 ah, morphis. How about the update service? Oct 17 15:48:36 Garfonso: you want to work on it? Oct 17 15:50:03 yes. :) Oct 17 15:51:43 Garfonso: ok, give me some minutes Oct 17 15:56:32 Garfonso: you saw http://www.webos-ports.org/wiki/System_Upgrade? Oct 17 15:56:47 yes Oct 17 15:57:19 ok Oct 17 15:57:36 Garfonso: you know what the staging feeds are? Oct 17 15:59:01 not 100% sure. I think they are package feeds, not yet stable but some kind of beta, or better release candidate. Right? Oct 17 16:00:37 somehow Oct 17 16:00:43 it looks like this: Oct 17 16:00:48 we have one public feed Oct 17 16:00:54 which contains packages and images Oct 17 16:01:00 and is considered stable Oct 17 16:01:08 and we have one development feed called wip Oct 17 16:01:27 every build will push it's packages/images to wip Oct 17 16:01:41 if we're fine with it we create a new stage Oct 17 16:01:45 and call for testers Oct 17 16:02:04 the testers can now switch to the new staging feed and test things Oct 17 16:02:18 if the feed is fine it will be merged to the public one Oct 17 16:02:25 if it's not fine we need to do another one Oct 17 16:03:46 ah, so there are possibly multiple staging feeds Oct 17 16:03:53 like for different features? Oct 17 16:04:01 no Oct 17 16:04:10 they are all incremental Oct 17 16:04:27 ok Oct 17 16:04:36 but sometimes they are closed after some "feature" is considered to be finished Oct 17 16:04:38 Garfonso: so you can't merge a specific one you have to merge all in a row Oct 17 16:05:01 but featureB will always contain also featureA etc in chronological order Oct 17 16:06:20 Garfonso: next thing is that every feed contains a manifest which looks like https://github.com/webOS-ports/changelog/blob/master/manifest.json Oct 17 16:07:20 morphis: I've added manifest.json to 003 Oct 17 16:07:25 JaMa: great Oct 17 16:08:03 Garfonso: the manifest contains the platformVersion and a changelog Oct 17 16:08:27 that's the JSON which is also described in the wiki. Oct 17 16:09:17 right Oct 17 16:09:50 so the update service needs to check for a new version of the manifest in the public feed and needs to compare it's version number against the platformVersion Oct 17 16:10:12 that way for example we can merge a feed to the public feed but prevent clients from updating Oct 17 16:10:27 if it's still not ready or something like this Oct 17 16:12:09 morphis: wait, platformVersion is always matching staging number, right? Oct 17 16:12:30 morphis: so when we merge new staging, it will show as possible upgrade to target devices, no? Oct 17 16:12:55 JaMa: yes Oct 17 16:13:09 now the check does: Oct 17 16:13:11 if ! grep -q '"platformVersion": ${CURRENT_STAGING}$' manifest.json; then echo "ERROR: https://raw.github.com/webOS-ports/changelog/master/manifest.json doesn't have changelog for staging ${CURRENT_STAGING} yet, update it first and then re-execute this job" exit 1 Oct 17 16:13:15 fi Oct 17 16:13:23 for the new-stage job? Oct 17 16:13:29 yes Oct 17 16:14:05 thats fine Oct 17 16:14:17 to be concrete, the check in the updateService would be local platformVersion against remote platformVersion. Right? Oct 17 16:14:18 so I don't see how we "prevent clients from updating" unless we change manifest.json after webos-ports_setup_sync-to-public-feed Oct 17 16:14:33 my tought was that we can manually change the version number down to the last one when we need it once we merge it to public Oct 17 16:14:45 ah OK Oct 17 16:14:47 Garfonso: right Oct 17 16:14:59 JaMa: currently it's manual work .. but that was the idea Oct 17 16:15:07 I don't think that will happen very often Oct 17 16:15:20 hmm but that will remove or replace .ipk files required for upgrade to older version Oct 17 16:15:21 Garfonso: thats the check if an update is available Oct 17 16:15:48 so I think we'll need to keep them outside public feed until we have staging which is good enough for target devices Oct 17 16:15:59 and then merge it with corresponding platformVersion Oct 17 16:17:09 once you merge stage 5 to public feed with 4, you cannot upgrade to just 4 from public feed Oct 17 16:17:22 right Oct 17 16:17:29 you can stay on 4 if you had it already Oct 17 16:17:56 we need some dirty flag in that case Oct 17 16:17:57 but if you have 3 on device and updateService shows 4 as possible upgrade it won't work because some .ipk files will be gone Oct 17 16:18:27 dirty flag is "N" on wiki Oct 17 16:18:30 why some ipk files are gone? Oct 17 16:18:48 http://wiki.webos-ports.org/wiki/Staging_feeds Oct 17 16:19:23 if stage 5 is dirty than it will wait for good stage 6 and then both will be merged together Oct 17 16:19:57 JaMa: if a device is at version 3 and public feed says 4 but 5 is merged but not proposed a update yet then we have to mark the public feed as dirty so the device doesn't update until either 5 is marked as ok or 6 is merged Oct 17 16:20:22 but why should we merge dirty 5 to public feed? Oct 17 16:20:42 so we're merge 5 and 6 together? Oct 17 16:21:02 that's how it worked with SHR and I don't see why not use the same Oct 17 16:21:08 hm Oct 17 16:21:16 webos-ports_setup_sync-to-public-feed even supports multiple params to do it with one call Oct 17 16:21:24 so what should be the problem then with the public feed if we merge 5 and 5 together? Oct 17 16:21:40 as if the device is always pointing to the public feed and never directly to 5 and 6? Oct 17 16:22:02 if we merge both together, devices will jump from 4 to 6 directly Oct 17 16:22:11 should be ok Oct 17 16:22:17 or from [123] to 6 Oct 17 16:22:33 but public feed will be just 6, nothing else Oct 17 16:22:41 yes Oct 17 16:22:57 and every device will update to 6 regardless if it has 1,2,3, or 4 Oct 17 16:23:07 I can possibly remove this: Oct 17 16:23:08 # sync ipk feed and remove missing, in this case we can, because all supported MACHINEs were built before staging was closed Oct 17 16:23:11 ssh ${REMOTE} rsync -avi --delete ${SOURCE_DIR}/ipk/ ${TARGET_DIR}/ipk/ Oct 17 16:23:36 it was required without PR service (where some .ipk files could be overwritten, so it was safer to say that only latest feed is there) Oct 17 16:23:57 with PR service it could possibly work (if we trust always unique AUTOPR values) Oct 17 16:24:06 but still it will grow very quickly Oct 17 16:24:17 you mean AUTOPR values? Oct 17 16:24:30 we had 70G ipk feed after 2 months or so Oct 17 16:25:04 hm, why do we still need the old ones? Oct 17 16:25:30 we don't with current scheme (without merging dirty feeds to public) Oct 17 16:26:00 ok Oct 17 16:26:02 I'm just explaining why we want to remove old and don't merge dirty to public without following clean stage ready Oct 17 16:26:20 ah ok Oct 17 16:26:47 we can still flag some feeds dirty to prevent staging testers to trying them manually Oct 17 16:27:35 but the wiki page could be enough at least for start Oct 17 16:28:04 testers should watch it closely and update it asap Oct 17 16:28:23 yes Oct 17 16:28:40 the update service should only support the real users Oct 17 16:28:50 ok Oct 17 16:29:01 if someones starts to act as tester he's off until he's back in sync Oct 17 16:29:25 hmm password-less issue reproduced again with new image Oct 17 16:29:33 JaMa: we still need the platform version within the image Oct 17 16:29:42 so be careful with new dora builds Oct 17 16:29:47 ok Oct 17 16:29:53 btw do we want pam support? Oct 17 16:30:07 currently not Oct 17 16:30:08 last time I was hit by this issue it was caused by pam Oct 17 16:30:30 Garfonso: I hope you could follow our discussion :) Oct 17 16:31:11 sorry for hijacking thread.. Oct 17 16:31:12 I did not understand all of it. Oct 17 16:31:14 ;) Oct 17 16:33:09 but the update service has to handle staging feeds? Or only public? Oct 17 16:33:18 Garfonso: only public Oct 17 16:33:40 ok. that makes it easier then. Oct 17 16:33:56 JaMa: so what about webos-version recipe which adds the platformVersion to the image but needs to be updated before we do a new feed? Oct 17 16:34:34 Garfonso: yes, I think it's the best way as if you're a tester you need to know anyway what you're doing and it will mean to much work for us to implement this case too Oct 17 16:35:20 Garfonso: so the idea was for the service that it checks for an update (triggered in specific time intervals by the activitymanager) and once it found an update it notifies the user Oct 17 16:35:31 the user then opens the update app Oct 17 16:35:42 gets the changelog and can press the update button Oct 17 16:36:36 if do that the service is called again with the command to update and then executed a shell script which prepares the update, restarts the device which will then boot into a special mode where the updates (which are fetched in the step before) are applied to the system Oct 17 16:36:51 after that the system is resarted again and the user can continue to use the device Oct 17 16:36:53 so a service and an app Oct 17 16:37:28 yes Oct 17 16:37:30 most work would be to get the download progress show nicely or something. ;) Oct 17 16:37:38 I think the app will be very simple Oct 17 16:37:46 rest should be fairly simple Oct 17 16:37:48 Garfonso: yeah :) Oct 17 16:39:12 do you have a repository for that already? Oct 17 16:40:08 let me create one Oct 17 16:40:22 morphis: my plan is pass both in WEBOS_DISTRO_BUILD_ID Oct 17 16:40:35 morphis: what about STAGING-BUILD_NUMBER? Oct 17 16:40:41 JaMa: why not Oct 17 16:40:51 Garfonso: https://github.com/webOS-ports/org.webosports.update Oct 17 16:40:54 any favourite codename for WEBOS_DISTRO_RELEASE_CODENAME? Oct 17 16:41:01 banana is kind of old :) Oct 17 16:41:54 JaMa: hm Oct 17 16:42:05 anyone a good idea? Oct 17 16:43:02 morphis: heh "base-passwd: update passwd to use bash instead of sh for root" nobash had one interesting sideeffect of also removing :*: from shadow Oct 17 16:43:12 JaMa: oh no Oct 17 16:43:21 morphis: I belive that's the reason why my passwordless images don't allow ssh login now Oct 17 16:43:26 :) Oct 17 16:43:40 let me try to fix it Oct 17 16:47:13 Garfonso: I think app and service should be go into the same repo Oct 17 16:48:00 yes, sure. Oct 17 16:52:23 morphis: I'm back Oct 17 16:53:32 Tofe: I need support soon for special window types within the cardshell Oct 17 16:53:37 like the launcher Oct 17 16:54:25 it's already started but need to be controlled differently then card windows Oct 17 16:54:48 okay sure. Is that type property exposed at QML level ? Oct 17 16:55:15 I think so Oct 17 16:55:33 CompositorWindow::windowType Oct 17 16:55:48 and there is the WindowType enum Oct 17 16:56:51 well well well. Looks like we didn't take it into account since now Oct 17 16:56:56 until* Oct 17 16:57:30 yes Oct 17 16:58:38 Tofe: the launcher will be the just type app and there will be only one ever Oct 17 16:59:07 Ok, so I'd better create a container a bit like the one for the maximized card Oct 17 16:59:09 so this one needs to be hidden until the user touch the just type bar and then presented as maximized app Oct 17 16:59:22 yeah Oct 17 16:59:34 and the app will stay forever Oct 17 16:59:38 it will be never closed Oct 17 16:59:43 yes, I guess so Oct 17 16:59:48 so swipe up will hide it only Oct 17 17:01:21 Do you already have something nearly running you want to test ? In that case, I could sketch quickly a container, just so that you see the content Oct 17 17:01:57 morphis, so not rolling upgrades but public "release" points instead for SystemUpdates? Oct 17 17:02:02 Tofe: I am mostly done with that part, it currently only fails to set the window type Oct 17 17:02:12 ok Oct 17 17:02:30 ka6sox: yes Oct 17 17:02:34 kk Oct 17 17:02:45 it will be mostly rolling as we will not that much testing on the feeds Oct 17 17:03:00 but it's good to have them as stage to see if things don't crash etc. Oct 17 17:03:03 will we have a beta branch for testers or just public only? Oct 17 17:03:09 just public Oct 17 17:03:15 hmmm Oct 17 17:03:32 as hoping between branches will be hard Oct 17 17:03:45 and rolling releases are better for our small project Oct 17 17:03:55 how will testing happen..or is it "testing is for users"? Oct 17 17:04:07 it's testing for developers Oct 17 17:04:17 you have to point your opkg to another feed and upgrade Oct 17 17:04:34 and use SystemUpgrade still? Oct 17 17:04:47 yes Oct 17 17:04:50 okay Oct 17 17:05:04 ah, a bit like it's done for maemo community Oct 17 17:05:14 ka6sox: http://www.webos-ports.org/wiki/System_Upgrade is what we will use Oct 17 17:05:14 so testing is WIP feed? Oct 17 17:05:35 ka6sox: somehow Oct 17 17:05:45 WIP is what gets populated by our builds Oct 17 17:06:01 once we are fine with the current state we create a new stage and mark it as testable Oct 17 17:06:08 if tests are fine we merge it to public Oct 17 17:13:53 what do you guys use to mount vmdk images in linux (e.g. to edit something without rebuilding)? Oct 17 17:14:14 losetup/afflib? Oct 17 17:15:46 JaMa: never mounted a vmdk yet Oct 17 17:17:53 Herrie, feeds all good again? Oct 17 17:25:02 morphis: what is the app to start for the just type launcher app ? Oct 17 17:45:31 Let me check Oct 17 17:45:36 Needed to do some groceries Oct 17 17:45:49 For name: How about "zen" from "Zen of Palm"? Oct 17 17:45:57 Instead of Banana? Oct 17 17:46:43 morphis/jama: I can test a vmdk when needed Oct 17 17:47:04 ka6sox: Yup looks OK :) Oct 17 17:47:34 Got MojoWhatsup, Gas&Oil Mix, GC-gog beta, Eye of Horus, Isis Web for TP 3.1.0 :) Oct 17 17:47:41 good Oct 17 17:49:04 Let me check patches as well Oct 17 17:51:05 Patches still no new ones it seems.... Oct 17 17:51:10 At least for 3.0.5 Oct 17 17:51:10 Herrie: I've just tested locally built qemux86 and qemux86-64 I'll ask you when jenkins is finished with them too, thanks Oct 17 17:51:20 it will take ~ 1 day to finish Oct 17 17:51:22 JaMa: No problem Oct 17 17:51:32 Dora = successor of Dylan? Oct 17 17:55:22 yes Oct 17 17:56:07 Herrie, let me see if I know how to log into patch portal anymore to push some thru Oct 17 17:56:19 btw are you also seeing some issues on first boot (2nd boot working fine)? Oct 17 17:58:47 If you need help with patches approval, if someone can give me instructions, happy to help out.... Got Pre2, Pre3, Veer and TP's laying around for testing ;) Oct 17 18:00:40 JaMa: Directed at me or.... ? Oct 17 18:01:43 Herrie: yes Oct 17 18:15:10 JaMa: yes used to be but recent builds seem better :) Oct 17 18:15:21 One from 10th or 11th was booting in 1 time with me :) Oct 17 18:15:32 The ones before I needed to start Luna Next manually Oct 17 18:41:48 morphis: I think I have a working just type launcher container Oct 17 18:42:21 morphis: there only one piece missing: what to launch when the JustType field has been triggered the first time Oct 17 18:42:39 or will it be started by WAM at startup ? Oct 17 19:42:31 Tofe: it will be started by LSM once WAM starts Oct 17 19:42:38 oki Oct 17 19:46:40 ok, I think I've got something that should be working. How can we test this ? Oct 17 19:47:01 I'll push my dev onto tofe/work, for a start Oct 17 19:47:17 Tofe: ok, I will test that tomorrow Oct 17 19:47:27 there are changes for LSM and WAM needed which are not yet in the build Oct 17 19:47:32 but I will merge them tomorrow Oct 17 19:49:30 Tofe: and will let you know wether your code works Oct 17 19:49:40 Tofe: whats next for you then feature-wise? Oct 17 19:50:25 well, not sure. I can implement other indicators, or I can make the launchbar more functional Oct 17 19:50:39 Tofe: I would vote for the launchbar Oct 17 19:50:48 let's go for the launchbar then Oct 17 19:50:55 Garfonso: can you use the same design for the update app as it was in the old webOS? Oct 17 19:51:16 Tofe: maybe also that you can drag-and-drop items in it Oct 17 19:51:26 what can *I* do to help right now? Oct 17 19:51:39 and what's the easiest way for me to test your changes? Oct 17 19:52:45 HaDAk: hm Oct 17 19:53:11 i'm happy to QA the hell out of this stuff, but it's gotta be relatively easy to update. Oct 17 19:53:22 HaDAk: one thing about your N7: be carefull that it never gets an empty battery, we're currently not suspending! Oct 17 19:53:37 morphis: i just powered it off completely Oct 17 19:53:46 also, i noticed that it wasn't suspending…it gets HOT Oct 17 19:53:58 HaDAk: it would be nice to a small set of tests we can do to quick check if a image is "working" Oct 17 19:54:16 such as? Oct 17 19:54:23 documented in the wiki Oct 17 19:54:30 1. check launcher as items Oct 17 19:54:34 2. check launchbar has icons Oct 17 19:54:40 3. check device is suspending Oct 17 19:54:41 ... Oct 17 19:54:46 what makes sense Oct 17 19:54:50 have to leave Oct 17 19:54:54 lets talk tomorrow Oct 17 19:54:55 gn8 Oct 17 19:55:19 we'll put a pin in that one then. Oct 17 19:55:21 nite. Oct 17 19:56:10 n8 Oct 17 19:56:23 Tofe…tofu…gross. Oct 17 19:56:29 i bet Tofe is white and squishy, too. Oct 17 19:56:50 squishy, not so much Oct 17 19:57:55 * HaDAk grabs a meat tenderizing hammer Oct 17 19:58:25 * Tofe jumps on the nearest tree Oct 17 19:58:50 oops, that would be out of the window... maybe not then... Oct 17 20:19:52 morphis: I've pushed my tofe/work tree, it contains the work on the justtype launcher. I didn't have time yet to test it on gnexus so I don't ask for a PR yet. Oct 17 20:26:36 n8 all ! Oct 17 21:15:10 morphis: the same design? Maybe... I'm not really an design guru, my plan was to keep the app as simple as possible. Will see, what I can do. ;) Oct 17 21:25:08 Garfonso, Good Plan(tm) **** ENDING LOGGING AT Fri Oct 18 02:59:58 2013