Updated devel_notsofun (markdown)

punto- 2014-12-18 11:52:12 -08:00
parent 6b01ac9ff3
commit 8c83374588

@ -39,4 +39,4 @@ What kind of AI APIS are the most useful in the industry? Help defining this wou
### Windows Phone / Windows 8
The current "winrt" platform is mostly ready, but needs a couple of key features to become a proper "first class citizen" supported platform. On the code side, the main one is an Audio driver, and a few minor issues with the threading classes (Thread is implemented using std::thread, I'd prefer using native winrt APIs, semaphores are not implemented). There's also the usual "app lifecycle" stuff missing (dealing with screen rotation, events like focus lost, back button, etc), and keyboard input (and possibly dealing with the on-screen keyboard). On the "workflow" side, we need to add "one click deploy" from the editor, which means packaging the app and launching it to a connected device (or launching as a "windows store app" from a local directory on the local machine), and eventually packaging for submission to Windows Store.
The current "winrt" platform is mostly ready, but needs a couple of key features to become a proper "first class citizen" supported platform. On the code side, the main one is an Audio driver, and a few minor issues with the threading classes (Thread is implemented using std::thread, we'd prefer using native winrt APIs, semaphores are not implemented). There's also the usual "app lifecycle" stuff missing (dealing with screen rotation, events like focus lost, back button, etc), and keyboard input (and possibly dealing with the on-screen keyboard). On the "workflow" side, we need to add "one click deploy" from the editor, which means packaging the app and launching it to a connected device (or launching as a "windows store app" from a local directory on the local machine), and eventually packaging for submission to Windows Store.