=== API is now known as Guest46209 === Guest46209 is now known as apinheiro === apinheiro is now known as apinheiro_lunch === apinheiro_lunch is now known as apinheiro [16:40] no on screen keyboard for oneiric? [16:40] https://bugs.launchpad.net/bugs/739812 [16:40] Ubuntu bug 739812 in unity "Must use hardware keyboard to perform search for applications in Unity" [Medium,Confirmed] [16:40] see last comments [16:40] charlie-tca: I think the on screen keyboard is there, it's the part about having it work with the Dash that won't be there? [16:41] Maybe, but doesn't that say "to hell with a11y, what works, works, and the rest is too bad"? [16:42] is this anything new? [16:42] We only been pushing this very thing since they announced unity back in natty UDS [16:42] accessibilty always gets the backburner to shiny [16:42] Yeah, back to "Accessibility is very important, as long as it doesn't get in the way again" [16:43] Oh, yeah. I forgot. I won't complain about that no more. I promised. [16:44] on the plus side it does work in unity 2d [16:44] and I have been asking about it in #ayatana [16:45] 17:23 < DBO> AlanBell, it's actively being worked on, I have done the part I could do (make it so that the dash doesn't grab mouse/keyboard) [16:45] 17:24 < DBO> IM support in dash is up to the dash guys now (they have some test work done) [16:47] and this is a problem shared by everyone who wants to use Ubuntu on a tablet [16:47] * AlanBell likes sharing problems [16:53] According to the blueprints, we aren't even defaulting to 2d? [16:53] probably not, no [16:54] Doesn't that kind of kill accessible installations? [16:54] the 3d one should be accessible to orca now (there is loads of code for it) [16:54] since 3d doesn't work with orca [16:54] have you tried it? [16:54] No, I just been looking at the ML [16:55] I will be trying it this weekend, so we know whether or not to include it in the ISO testing [16:55] http://bazaar.launchpad.net/~unity-team/unity/trunk/files/head:/services/ [16:55] loadsa ATK code stuff [16:56] I am not testing that right now, but I saw all that code earlier, if it doesn't work it should do [16:57] not sure if unity 2d will be accessible to orca (I suspect not) [16:57] yeah, that was the goal this cycle, though [16:57] the plan was always to go for a fully accessible 3d before dropping the classic option [16:58] unity2d accessibility was more likely to be next cycle with the QML stuff upstream done this cycle [17:04] Then I must have misunderstand this blueprint - https://blueprints.launchpad.net/ubuntu/+spec/desktop-dx-o-unity-a11y [17:07] charlie-tca: jsut pretend you see the word "POSTPONED" at the end of each line :) [17:11] Apparently from the day after UDS? [17:15] "Hard target: Unity must have accessibility in Oneiric" [17:15] I think that refers to Unity 3d [17:15] there is a work item for setting unity-2d to be the default, but that might not be a good idea [17:17] all the items were for 2d, because we would not be able to make orca work correctly in 3d [17:17] why not? [17:17] gnome3 and gtk3 [17:18] which should be fine [17:18] it was the Qt stuff that was the major toolkit problem [17:19] anyhow, it needs testing [17:19] yes it does [17:19] but the original blueprint really does say 2d, not 3d [17:52] charlie-tca: I made a dummy speech dispatcher module the other day which doesn't speak out loud, but logs a transcript of everything it would say [17:53] so you can have a terminal window open with tail -f speech.out to see it scroll past if you want to test stuff with orca silently, or if you want a transcript of the session for structured testing purposes [18:07] I don't honestly know yet how to set up automatic tests [18:07] Will be working on them, since we can now automate any tests I can figure out [18:11] I will be wanting that, when I get tests automated [21:04] are y'all talking with fregl about qt a11y? [21:04] because he's a genius, and very committed, and working really hard [21:05] he lives in #kde-accessability [21:06] he and Harald / apachelogger can accomplish miracles, if asked [21:07] and by y'all, I mean Pendulum, AlanBell and charlie-tca, since you are the movers and shakers [21:09] valorie: thats for unity 2d, which is pretty dandy at this point [21:09] valorie: trouble is unity 3d still cant work with onscreen keyboards and is supposed to be default [21:09] right, I read up [21:09] " it was the Qt stuff that was the major toolkit problem" [21:09] fregl's in the channel,ya know :P [21:10] was what I was responding to [21:10] yes, "was"...past tense :) [21:10] heh [21:10] oh well, he gets a compliment then [21:10] :-) [21:10] are you ready for the storm, maco? [21:11] i have lots of wool to spin if the power goes out [21:11] so....yes? [21:11] well, water to drink, food to eat [21:12] candles, board games [21:12] :-) [21:12] who needs board games? i have wool and a spindle! [21:12] but yeah i have candles. was camping recently ;) [21:12] you have the skillz, for sure [21:12] and food...im one of those people who keeps lots of beans around [21:13] i dont really expect much disruption beyond maybe a day or two of lost power [21:13] if that happens...go to boyfriend's apartment. that building's got a giant diesel generator that can go at least a day [21:13] cool [21:13] if the power's out at my place, i can still cook *real* food, just no microwave burritos :P [21:14] lol [21:14] we're set up, out here, since occasionally it's out for up to 6 days [21:14] that was the longest [21:17] maco: so unity2d should work with orca now? [21:19] AlanBell: idk about orca. i know i was able to use some kde apps with kde's screenreader. fregl'd know about the state of the gnome<->kde accessibility communications stuff [21:20] anything qt *should* work with kde's screenreader i think though