Its all about choice. If you want to use the Skype App with the normal program, and yes, it does work with skype 6, drop down to 3.4 of the scripts, so ya don't get that message. Otherwise, either use GWC, which works with all screen readers, or Skype CLISK, , via the command line: http://kirk.dlee.org:13380/skype/clisk/ , which works with all! screen readers, and all Operating systems. Keep in mind, NVDA does work with Skype interface as well, and ya do not need an app for it! No, it doesn't talk, however if ya know the interface well, it works nicely! Yes, Jeff himself said that the Skype app for the skype client would be discontinued, and urges people to use GWSkype, (Called that, at the Time,) but can certainly still use Skype 6 with the current scripts, and they too also work with Facebook chat, and with Messenger contacts, since Windows Live Messenger is disappearing, which I mentioned in another posting. And skype Talking is also still around, and it certainly works with all windows screen readers. Will it work with FB Chats in skype 6 now? No idea if skype actually fixed that themselves, but who knows! Give it a shot!
So, to sum it all up, ya got choices, use them! On 11/10/12, Patrick <[email protected]> wrote: > going back to Skype and again why I said I don't mind apps. Connect has bugs > > that the skype program itself does not have. This is the reason I stopped > using connect, and instead use the Jaws scripts with the regular skype app. > > I know it may seem as if I say one thing and say another, but this is an > example of why I said I see the point of apps, for times like these. Again, > > what you said about waiting for an upgrade, Connect falls now into that > category, and unless I want to use Jaws with skype, Jaws is my other option > > since again, there's no more app updates for skype. > > -----Original Message----- > From: Aaron Smith > Sent: Friday, November 09, 2012 11:49 AM > Cc: [email protected] > Subject: Re: A Feature I'd Like. > > If the developers of the GW Micro apps (which is what we're talking > about) suddenly go away, then don't expect any future Window-Eyes > updates. <grin> We're all part of the same team. Yes, we stopped working > on the Skype app because we decided to make GWConnect again. Why would > we continue to pour resources into keeping something updated that we > ultimately didn't want people to use? The Insert Key Layout is the > perfect example of why it should remain in app form: it's been updated > about eight times since it was released. If it were native, you'd still > be working with, and dealing with the bugs of, version 1.0. > > Aaron > > On 11/9/2012 12:38 PM, Patrick wrote: >> I see better stability when it comes to native support rather than relying >> >> on a script. I'm not saying wineyes never crashed when we had to upgrade >> for a feature, but we wouldn't need to deal with an app crashing because >> something loaded incorrectly which in turn caused errors starting the app. >> >> I also feel that while this is true that we wouldn't need to wait for an >> upgrade, a lot of the time if an app is supported by a script, if a dev >> vanishes, or should I say, stops developing an app, we're left out if >> something breaks in the app until you decide to finally put support in for >> >> it. People say, well if you want it so bad make it yourself. Not everyone >> >> has the time or brains to program an app. Many times since scripting came >> >> out, I'm seeing a lot of, sorry, we didn't make such and such app, contact >> >> the developer directly. Again, if that developer is gone, or not >> developing anymore, we are again, left out. The Skype scripts for >> instance. They were discontinued because of GW Connect. Meaning, that >> unless you want skype to work with wineyes, either you use connect, or >> deal with the discontinued scripts that may or may not work. >> Now I don't mind apps. But I feel they are being too heavily relied on, >> making it look like a volunteer effort. The insert key layout for things >> like browse mode commands, comes to mind. >> I just would at least like to see a focus on features being natively >> supported after the apps that supported them have been made, and you, >> seeing the usefulness of the app, then support it in a future upgrade. I >> hope this makes sense. >> Patrick >> >> -----Original Message----- From: Aaron Smith >> Sent: Friday, November 09, 2012 9:51 AM >> Cc: [email protected] >> Subject: Re: A Feature I'd Like. >> >> On 11/9/2012 10:31 AM, Patrick wrote: >>> I'd rather it be supported natively rather than relying on an external >>> app. >> >> Just curious what the rational is behind this. What does it matter >> whether the ones and zeros come from a Window-Eyes supported app, or >> Window-Eyes itself, as long as the job is done? GW Micro app developers >> work right along side of Window-Eyes developers. Ideas are often >> discussed amongst the whole team before any implementation takes place. >> In addition, the benefit of putting features in apps is that they can be >> released and updated at any time without having to wait for an official >> Window-Eyes upgrade. >> >> Aaron >> > > -- > Aaron Smith > Web Development * App Development * Product Support Specialist > GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 > 260-489-3671 * gwmicro.com > > To insure that you receive proper support, please include all past > correspondence (where applicable), and any relevant information > pertinent to your situation when submitting a problem report to the GW > Micro Technical Support Team. > If you reply to this message it will be delivered to the original sender > only. If your reply would benefit others on the list and your message is > related to GW Micro, then please consider sending your message to > [email protected] so the entire list will receive it. > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can > manage your list subscription at http://www.gwmicro.com/listserv. > If you reply to this message it will be delivered to the original sender > only. If your reply would benefit others on the list and your message is > related to GW Micro, then please consider sending your message to > [email protected] so the entire list will receive it. > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can > manage your list subscription at http://www.gwmicro.com/listserv. > > If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
