[00:00] totally agree [00:00] but I do recall we were discussing whether Mark Shuttleworth was a cosmonaut or an astronaut so I used this link to make my point [00:00] http://lmgtfy.com/?q=billionaire+cosmonaut+bachelor [00:01] well if i ask for what it means i reither like to get 1 other word what means the same not page to read [00:02] i just get lost on that moment in very many lines [00:03] if i have a better day i can read it .difficult but i can. [00:03] then i also do not ask [00:03] because i don't need it [00:04] i understand AlanBell what you mean [05:25] I was discussing the Dasher-crashing issue with a friend who's into accessibilty stuff and can code (attempting to recruit), and he pointed out that adding a watchdog script to restart it when it crashes would help the immediate situation til all the bugs can be fixed [05:34] maco: That sounds effective. [07:47] maco: that is a good idea [09:43] Is Qt a development system that Ubuntu Accessibility would recommend? [10:05] maco: ^^ [10:11] as QT might end up in the default install it will need to work, right now I understand it is not as complete as GTK in terms of A11y APIs [10:15] AlanBell: Hm, in an attempt to improve voice recognition, I've started this. (https://www.launchpad.net/cmusphinx-train) [10:15] It's in C++ and Qt. [10:16] AlanBell: If there's anything about it that needs tweaking or work, please tell me. :) [14:03] JackyAlcine: screen readers can't handle it, period [14:03] and fixing this is not on Nokia's roadmap [14:03] >_< [14:03] they just say "patches welcome!" ... but it needs someone (or two or three) working full time for a year [14:04] So it's GTK all the way? [14:07] http://www.markshuttleworth.com/archives/568#comment-343659 Mark does not appear to have responded to this [14:09] full time developers working on it is not outside the bounds of possibility, but so far there is no commitment to do that [14:09] even luke's got accessibility only part of his fulltime job.. [14:10] I know [14:42] AlanBell: It said on this page that Qt 4 supports at-spi (http://en.wikipedia.org/wiki/Assistive_Technology_Service_Provider_Interface) [14:44] And I've noticed a few "accessibility" components when it comes to creating a Qt GUI application.. [14:56] JackyAlcine: if I understand correctly, they have an interface for at-spi support, but to make widgets accessible you have to wrap them and implement some things yourself? [14:56] Yes, JanC. [14:57] e.g. standard QPushButton etc. is derived from QWidget, not from QAccessibleWidget... [14:58] well, accesibleName & accesibleDescription are implemented in QWidget [14:59] that should help if the developer sets them [14:59] And I've set those values as fully as possible. [14:59] but I'm not familiar enough with at-spi & a11y to know if that is "enough" [15:00] Hopefully, it is, JanC. [15:00] if you need to wrapp all basic widgets yourself to get full at-spi support, that would not be fun for application developers ;) [15:01] >_< If it's required, then by all means. [15:47] JackyAlcine: i saw a press release from ... oh it was probably Trolltech back then...that was like "hey, new Qt! and now with at-spi!" and mentioned it to one of the Qt guys at the last UDS and he said something about having to have a talk with the PR people :-/ [15:49] PR? [15:56] public relations [15:56] the people who write press releases [22:25] jcastro just started this page https://wiki.ubuntu.com/Unity/KeyboardShortcuts [22:30] great. He said he would do that for us [22:31] great AlanBell [22:31] that is a work in progress, there should be more key bindings to follow [22:32] i am looking foreword tto that [22:32] to i mean [22:35] yes, there will be. But that was to help us get started [22:41] well work in progress is better then not at all thought :)