Re: pidgin and twitter
Hi. Did you add the your twitter account to pidgin? You do that in the same way you add other accounts. On 05/14/2011 06:33 PM, Milton wrote: Hi, In Lucid and Maverick I tried Skype through Pidgin and now I would like to use Twitter in Pidgin. I installed pidgin-microblog. But when I start Pidgin I only get the list of Skype contacts. Do somebody knows how I can get to set my twitter account in Pidgin? Thanks in advance. Milton -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Trouble with Pidgin-skype plugin in Natty
I can confirm part of Dave's problem with the pidgin-skype plugin in Natty. I have no problems with audio calls, but when I try and text chat with someone on skype, I can see the messages I send out, but no incoming messages are displayed. Is there a work around for seeing the messages people send you? Any help would definitely be appreciated. Thanks, Guy On 05/16/2011 06:34 PM, Dave Hunt wrote: Hi, all! I recently upgraded to Natty and installed Skype, Pidgin, and the subject plugin, all from the official repositories. I am able to make Skype calls and, sometimes, be heard. When my recipient picks up, I also get a dialogue asking me to accept or reject, as if the call were in-coming. When someone tries calling me, I get the ring and in-coming call dialogue. When I choose accept, the call does not get answered. In an exchange of Skype text messages, I can see my messages in the conversation window, but not those from the other party. Is there something I haven't set up right? This arrangement works in all Ubuntu versions up to and including Maverick. I cannot access Skype without this protocol plugin, since Orca screen reader does not work with QT4 objects. Thanks for any help, Dave Hunt -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Proposal: DBus activation of Accessibility
On Mon, May 16, 2011 at 5:29 PM, Frederik Gladhorn gladh...@kde.org wrote: Hi, sorry for cross-posting. I would just like to have this looked at by everyone so we can simply implement it. During the ATK/AT-SPI hackfest it came up a few times that we have no solution to enable accessibility (eg Screen Readers) on the fly. The conclusion was that using DBus would fit everyones needs and make it easy for third partys to adapt. Proposal: DBus activation of Accessibility I'm not sure how things work on the KDE side, but for GTK+ based applications, this does not really solve the problem. Since GTK+ a11y implementation lives in a module that needs to be loaded by all applications before a11y tools talk to it. We can load the module at runtime, but at that time widgets may already have instantiated no-op a11y implementations. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Proposal: DBus activation of Accessibility
Hi, sorry for cross-posting. I would just like to have this looked at by everyone so we can simply implement it. During the ATK/AT-SPI hackfest it came up a few times that we have no solution to enable accessibility (eg Screen Readers) on the fly. The conclusion was that using DBus would fit everyones needs and make it easy for third partys to adapt. Proposal: DBus activation of Accessibility Problem description: We need a cross-desktop solution to dynamically activate the accessibility framework. Ideally we could switch on accessibility functionallity by default. At the moment it seems that most solutions use quite a few resources, therefor the best short-term solution would be to find a way to enable accessibility on the fly. As an example this is helpful when on first time use or when the computer is shared with users that have no accessibility needs. Currently Gnome requires the user to log out and back in. KDE has no solution. Proposed solution: To activate accessibility, a dbus notification is sent to inform about the state of the accessibility framework. The enabled status of the accessibility framework can be queried via the same mechanism. A setter is also provided to activate the accessibility framework desktop wide. The DBus interface contains a property that says whether accessibility is enabled, has a notification signal and a method to enable accessibility. Currently the at-spi2 dbus registry would be the best place for this functionallity. DBus service: org.a11y.Bus Proposed DBus interface: ?xml version=1.0 encoding=UTF-8? node name=/node interface name=org.a11y.status property name=IsEnabled type=b access=read/ method name=Enable arg direction=in name=enabled type=b/ /method signal name=NotifyEnabled arg name=enabled type=b/ /signal /interface /node Gnome could couple this with the existing gconf notification. For KDE the system settings module will have to be extended. Greetings, Frederik -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
