**** BEGIN LOGGING AT Sat Aug 28 02:59:57 2010 Aug 28 09:19:30 2D session fix uploaded, we should have only one panel with the right applets now (still need to figure out how to get the shutdown applet there, but given that shutdown hangs anyway on bringing down usb0 ...) Aug 28 09:19:55 Cool. Aug 28 09:20:07 was just a copy paste job :) Aug 28 09:20:38 (less than 10min including testing, i just couldnt do it without working session) Aug 28 09:20:53 * ogra vanishes again Aug 28 09:21:08 Awww.... Aug 28 16:08:13 * dcordes needs to find a way to have onboard popup when text input is expected and have it appear afterwards Aug 28 16:08:23 s/appear/disappear/ Aug 28 16:08:49 is it expected no input help appears in oem-config ? I am missing the possibility to show keyboard Aug 28 16:13:02 dcordes: I don't think the image is geared towards touch screens yet. It is mainly derived from the x86 Netbook image. While we are working on multitouch in a different group, I don't think it will make Maverick, and I know it won't be tested on arm very much. Aug 28 16:13:58 GrueMaster: utouch I have seen it. very interesting Aug 28 16:14:10 GrueMaster: I even have a touchscreen driver with multitouch support Aug 28 16:14:34 Drivers exist, yes. Hardware, not so much. Aug 28 16:14:42 Well I got both Aug 28 16:14:56 Maybe I can help testing Aug 28 16:16:52 One thing you can do is file a bug against oem-config for adding touch screen support. Make sure the bug report is as detailed as possible. Add me to the subscribers list, and I can triage it and tweak as needed. Aug 28 16:17:13 GrueMaster: Awesome, will do that. Aug 28 16:18:11 I am also a bit worried about evtouch screen rotation. A bug exists for a while but it's not solved yet Aug 28 16:19:26 Lack of hardware for developers to work with. I have a Motorola Droid, which is the same base hw as the beagleboard, but I really don't want to sacrifice my cell phone for development yet. These cost a lot of $$$. Aug 28 16:21:09 That's what I'm doing htc hd2 is my day to day and development phone :) Aug 28 16:46:19 Awesome now I have working backlight control in ubuntu :) Aug 28 18:24:56 any Utouch contributors present ? Aug 28 20:58:23 hmm, when setting up an arm environment for qemu via: https://wiki.ubuntu.com/ARM/RootfsFromScratch , is it normal for the process to stall a very long time w/ libbonoboui2-common ? Aug 28 21:50:10 devilhorns: probably not Aug 28 21:55:25 lool, yea, turns out my image was too small for everything Aug 28 21:55:31 got it sorted out now tho, thanks Aug 28 21:56:58 devilhorns: stumbled across same problem few times with first rootstock attempts Aug 28 21:57:30 dcordes, hehe :) Aug 28 21:57:32 devilhorns: be aware it is currently impossible to rootstock a full ubuntu image. it will fail installing mono Aug 28 21:57:56 dcordes, that's ok, just doing arm netbook stuff :) don't need a full desktop image :) Aug 28 21:58:57 devilhorns: I am not sure but I think ubuntu-netbook will install mono as well Aug 28 21:59:19 ugg, I hope not :) Aug 28 21:59:21 devilhorns: The savest thing is to roostock ubuntu-minimal and do anything else natively Aug 28 21:59:25 devilhorns: That's what I did Aug 28 21:59:55 dcordes, ok, thanks for the tip :) Seems to be working so far tho...we'll see Aug 28 22:01:38 https://launchpad.net/project-rootstock Aug 28 22:02:27 https://wiki.ubuntu.com/ARM/RootStock/KnownIssues Aug 28 22:02:32 devilhorns: good read Aug 28 22:03:19 dcordes, k, yea first one is of little use to me, but the Known Issues is good to know, thanks Aug 28 22:04:45 all this rootfs stuff is a little new for me ... not normally a *buntu user Aug 28 22:06:57 Ok don't hesitate to ask if you got any questitions Aug 28 22:07:08 thx :) Aug 28 22:07:14 questions even Aug 28 22:07:28 hehe Aug 28 22:14:40 dcordes, You ought be able to get onboard to do the right thing: investigate under the accessibility menu. Aug 28 22:37:02 persia: Is it expected to autohide ? Aug 28 22:38:29 I believe so, as it can take up a chunk of the screen. Aug 28 22:38:32 * persia enables to check Aug 28 22:42:27 it doesn&t autohide for me, but there is a mismatch between the onboard display layout and the keypresses sent to my irc client '* Aug 28 22:42:52 Seems to use a US layout internally, for some reason. Aug 28 22:42:56 * persia files a bug Aug 28 22:46:47 persia: You think I should file an improvement bug for the autohide ? Aug 28 22:47:18 persia: As an option I thought about using a tiling window manager like matchbox. But that will cut good screen area permanently and I only have 800x480 Aug 28 22:49:52 I'd recommend getting in touch with upstream to make sure they are happy with using it also as a touchscreen base. Aug 28 22:50:11 They're active folks, but concentrated on accessibility, which may have different driving requirements. Aug 28 22:52:05 https://wiki.ubuntu.com/Accessibility/Projects/onBoard/ seems to document some of the ideas they've had to date. I don't seem to find their mailing list offhand, but you might with a bit of digging. Aug 28 22:54:14 persia: Ok I will contact them. One big improvement over previous versions is the new layout. And in case they really don't aim for touchscreen use, it is still the best option I found so far Aug 28 22:58:13 Yeah, although the modeswitch buttons are a bit confusing Aug 28 22:59:06 And I can't think of any good reasons why we shouldn't be collaborating between touchscreen and accessibility stuff: both groups have similar needs (can't use a real keyboard). Aug 28 22:59:31 And high pixel densitys map well to poor motor control (e.g. using a wand in one's mouth) Aug 28 23:04:17 I'm all for it Aug 28 23:04:59 persia: The wand in one's mouth metaphor is pretty nice if you want to describe my capcitive touchscreen :) Aug 28 23:05:48 It's not a metaphor for lots of people, which is the target audience for the accessibility folk. Aug 28 23:05:58 That's why I think there's scope for collaboration. Aug 28 23:07:00 I have many other thoughts about how to improve the interface for my device Aug 28 23:25:12 https://bugs.launchpad.net/ubuntu/+bug/626055 Aug 28 23:25:14 Launchpad bug 626055 in oem-config (Ubuntu) "oem-config: make on-screen keyboard available (affects: 1) (heat: 6)" [Undecided,New] Aug 28 23:25:25 hehe first bug report I filed from my phone :) Aug 28 23:25:50 I have to admit I connected a usb keyboard though Aug 28 23:30:01 There's a way to do that for normal install images (using the accessibility prompt at the first screen). Getting that sorted for preinstalled images is trickier. ogra may know better, but I suspect that's really a jasper bug. Aug 28 23:31:22 Ok it might not be a bug at all as I doubt it's expected on any device jasper is cut Aug 28 23:32:21 i.e. maybe jasper enables it Aug 28 23:34:24 I don't see much oem-config related in the jasper scripts though except for the semaphore write Aug 28 23:34:56 The bug would be that there exists no way to enable accessibility features prior to oem-config launch on a jasper-based system. Aug 28 23:35:11 One ought be able to turn on that stuff, if needed, so that it's available later. Aug 28 23:36:24 Well if there is an option to enable that in oem-config the bug is still valid Aug 28 23:36:33 Because it's disable currently Aug 28 23:37:52 Hrm. Interesting point. Because those needing accessibility features might need to turn them on for preinstall devices that have keyboards (which can't be used). Aug 28 23:38:06 yeah, I guess oem-config isn't a bad place. Aug 28 23:38:44 persia: Actually GrueMaster suggested it ;) Aug 28 23:38:55 * dcordes looking at oem-config package Aug 28 23:41:44 Well wherever the oem-config configuration is I guess the best solution will be to write one with accessibility feagures turned on in all netbook builds Aug 28 23:41:57 s/feagures/features/ Aug 28 23:42:05 good night Aug 28 23:42:21 persia: Thanks for the advise Aug 28 23:47:06 * persia doesn't think everyone needs them enabled, but everyone needs the ability to start them Aug 29 00:03:38 Say, I sure hope the Linaro stuff will result in those TI DSP-accelerated codecs being packaged. Aug 29 00:03:54 As it is right now, getting the DSP stuff to compile is cryptic and confusing. Aug 29 00:50:22 DanaG: indeed **** ENDING LOGGING AT Sun Aug 29 02:59:57 2010