61–66 of 66 posts
Earlier quoted context omitted.
Interesting, since Presage is GPL 2 but this project is Apache licensed. Intel says "Integration with Presage is through the Windows Communication Framework" which I guess is a roundabout way of avoiding the GPL?
The Apache license v2 is GPL-compatible, which was actually one of the major reasons for having a v2.
Earlier quoted context omitted.
The Apache license v2 is GPL-compatible, which was actually one of the major reasons for having a v2.
Apache licensed code can be included in a GPL project, not the other way around. If the project includes any GPL code, the whole thing is GPL.
Earlier quoted context omitted.
@acqq: Shameless plug. This doesn't seem to have speech. However, I've tried to build a text to speech synthesizer in www.voiceclonr.com. Appreciate if you could try and leave feedback.
If I understood correctly the open-sourced version uses as an example the Microsoft's Speech API. Searching for which I find the gems like this: https://connect.microsoft.com/VisualStudio/feedback/details/... "System.Speech has a memory leak - by eoghanoh Status: Closed as Won't Fix" I see your work is based on http://hts.sp.nitech.ac.jp/ Can you tell us what are your changes? Edit: I see HN already commented your wo…
That's a shame really, I was really looking forward to try it out. And the title is grossly misleading.
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.
Earlier quoted context omitted.
... for some definition of "easiest." Maybe I would agree if you don't need to support a custom look-and-feel (Win32-looking apps don't really fly anymore), responsive layout, high DPI, touch/pen input, system theme colors, accessibility, localization, and haven't learned XAML. WPF and UWP apps are both far easier.
Win32 is the style that Windows apps are supposed to be and what people expect in a Windows app. What are you talking about? In what way does the win32 look "not fly"? I've tried to use WPF and it was just a major pain and felt like a mess. There is no impediment to "responsiveness". Where did you get the idea winforms apps don't follow the system colors?
Maybe in the Windows XP era. None of the built-in apps in Windows 10 look like Win32 apps, apart from legacy stuff that hasn't been ported yet and now looks sorely out of place.
https://msdn.microsoft.com/en-us/library/dn894631.aspx?f=255...
Much of the Windows shell isn't even written in Win32 anymore, it's all UWP (source: I work on the start menu).