Fun fact: the latest version of this software uses SwiftKey under the hood - http://swiftkey.com/en/blog/swiftkey-reveals-role-professor-... (Disclaimer: I used to work for SwiftKey)
As a loyal SwiftKey on Android user, the prediction engine for SwiftKey is unnervingly good. Glad to see it's put to a better use than helping me write Facebook and HN posts. It begs the question though, why isn't there a proper SwiftKey keyboard for Windows? The OSK on 8.1 is awful compared to SwiftKey on Android. The Windows 10 is a improvement, but I'd still pay for a better one.
Intel open sourced Stephen Hawking’s speech system
31–40 of 66 posts
Re: Intel open sourced Stephen Hawking’s speech system
#32Earlier quoted context omitted.
I don't know, I've done both (Silverlight MVVM and Winforms) plenty and I prefer the manual approach. Databinding is cool until you have any sort of complexity in your app, and then it becomes unwieldy quickly.
Databinding (and MVVM by extension) is ok only in very simple scenarios. Once you hit some complexity you end up in a world of hurt. Databinding is not a leaky abstraction ,it's a fucking flood abstraction.
Databinding is indeed a leaky abstraction, but at the same time it's a very powerful one. I'm willing to learn the inner workings of the binding system to avoid performance pitfalls and other weirdnesses. I'm also willing to continually wrap all sorts of not MVVM-ready components to make them data-binding friendly. When people talk about databinding being a leaky abstraction, what I hear is "I was promised magic and it's not actually magical."
Also - there's many different approaches to how it's done with various tradeoffs. Compiled bindings on Android and the new Windows platforms look interesting, and you should also check out how ReactiveUI approaches it.
In the end though, I've never been able to achieve a satisfactory level of loose coupling, testability, and portability without databinding. Despite the overhead and occasional surprises, it's paid off in spades as far as quality and productivity.
Re: Intel open sourced Stephen Hawking’s speech system
#33WinForms is still a great way to write desktop software if you don't need all the features of WPF, I just started a new project with it and have been really productive.
WinForms is not simple. There are so many core classes that have counterintuitive edge-cases and overcomplicated behavior, and so many things you'd expect to work by default don't. Databinding is a complete trainwreck, the Combo-box class is horribly overcomplicated by its double-duty as text-entry and drop-down-list, the DataGridView is a complete beast of leaky abstractions, and the layout engine completely falls a…
Data binding is not solid, but it is a quick hack to display data, the solution is using a business model and mvp or mvc.
What do you find complicated about the combo class?
Data grid view... It is a train wreck, but then again, there is not much need to use it if you have a proper model behind.
The layout engine does sucks... The only alternative I found is to use the dev express layout control. The rumor is that 4.6 solves this.
Win forms is solid and it has very little chance of disappearing. Areas of the screen can be controlled independly, which means ui encapsulation is there... Something not easily done in html.
Re: Intel open sourced Stephen Hawking’s speech system
#34Re: Intel open sourced Stephen Hawking’s speech system
#35WinForms is still a great way to write desktop software if you don't need all the features of WPF, I just started a new project with it and have been really productive.
WinForms is still the easiest way to write desktop software quickly and easily. If you don't need a fancy UI for customer facing work, its a great platform for internal use.
Re: Intel open sourced Stephen Hawking’s speech system
#36Re: Intel open sourced Stephen Hawking’s speech system
#37We looked at some software called EZ Keys from a company called Words Plus. (I don't think she used it specifically, at least for long--I know she used another program, a DOS-based one called Living Better that ran in 40-col. mode that I can't anything about on the Internet.) EZ keys looked more or less like Intel's thing -- scan rows, scan items in a row, completions/predictions over at left. It even had an option to use a frequency-sorted keyboard like the Intel one, with the common letters pushed to the top left (since those are the first rows/cols to be scanned). Hawking apparently used EZ Keys, so it's possible the Intel folks intentionally gave their thing a similar interface to make the transition easy.
It is worth remembering that no user cares if it's WinForms or whatever. Some folks might like a nicer voice if they haven't gotten used to theirs like Hawking ;), but the main concern is just getting the message across. Intel seems to have worked on the right stuff: better prediction (Presage http://presage.sourceforge.net/, which looks interesting) and context-sensitive controls. The infrared-laser-based input method sounds cool, too.
This is a neat space: an optimization/prediction problem where improvements can be a significant help to someone. (There are also practical optimizations that don't have much to do with the general word-prediction problem: sometimes people have to say things about their care, food, etc., or generic 'hi' and 'bye', and it's good if those are fast.) A Web page or Chrome extension can do a lot--how close can you get to smoothly operating the Web with just the spacebar? the arrow keys and Enter? or plain old typing, but slowed down and using 0-9 for completions?
I've heard that nowadays, people with communication trouble and enough movement use text-to-speech on mobile gadgets with their nifty and highly refined predictive input and that's awesome.
Re: Intel open sourced Stephen Hawking’s speech system
#38Bear in mind this project was started around the same time there was a ton of uncertainty around the future of Silverlight and WPF. Alas, one did die, one lives on for now. But nobody knew that at the time, including Intel, or apparently Microsoft. WinForms has never faced any forward compatibility uncertainty so it is a good long-term bet.
A) Microsoft still mantains and updates silverlight.
B) It's mentioned as one of the components of Windows 10[1].
So I'm really confused here as whether Microsoft will kill it already, or keep it alive. They seem to be willing to kill it[2][3], but Netflix alone is enough reason to keep it alive.
[1] https://www.microsoft.com/en-us/privacystatement/default.asp...
[2] http://www.digitaltrends.com/computing/microsoft-wont-includ...
[3] http://www.windowscentral.com/microsoft-confirms-its-new-edg...
Re: Intel open sourced Stephen Hawking’s speech system
#39Fun fact: the latest version of this software uses SwiftKey under the hood - http://swiftkey.com/en/blog/swiftkey-reveals-role-professor-... (Disclaimer: I used to work for SwiftKey)
Re: Intel open sourced Stephen Hawking’s speech system
#40Earlier quoted context omitted.
As a loyal SwiftKey on Android user, the prediction engine for SwiftKey is unnervingly good. Glad to see it's put to a better use than helping me write Facebook and HN posts. It begs the question though, why isn't there a proper SwiftKey keyboard for Windows? The OSK on 8.1 is awful compared to SwiftKey on Android. The Windows 10 is a improvement, but I'd still pay for a better one.
Have they improved performance of SwiftKey? I had the paid version for years, was even a VIP (won a t-shirt and everything), but I switched off last year in favor of Fleksy as a faster, more lightweight alternative.