{"action":"opened","issue":{"url":"https://api.github.com/repos/xyzzer/WinRTXamlToolkit/issues/2","labels_url":"https://api.github.com/repos/xyzzer/WinRTXamlToolkit/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/xyzzer/WinRTXamlToolkit/issues/2/comments","events_url":"https://api.github.com/repos/xyzzer/WinRTXamlToolkit/issues/2/events","html_url":"https://github.com/xyzzer/WinRTXamlToolkit/issues/2","id":99264582,"number":2,"title":"Windows 10 support","user":{"login":"xyzzer","id":1753264,"avatar_url":"https://avatars.githubusercontent.com/u/1753264?v=3","gravatar_id":"","url":"https://api.github.com/users/xyzzer","html_url":"https://github.com/xyzzer","followers_url":"https://api.github.com/users/xyzzer/followers","following_url":"https://api.github.com/users/xyzzer/following{/other_user}","gists_url":"https://api.github.com/users/xyzzer/gists{/gist_id}","starred_url":"https://api.github.com/users/xyzzer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xyzzer/subscriptions","organizations_url":"https://api.github.com/users/xyzzer/orgs","repos_url":"https://api.github.com/users/xyzzer/repos","events_url":"https://api.github.com/users/xyzzer/events{/privacy}","received_events_url":"https://api.github.com/users/xyzzer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-05T18:07:18Z","updated_at":"2015-08-05T18:07:18Z","closed_at":null,"body":"There are a few aspects of supporting Windows 10\r\n\r\n1. Make sure the version of the toolkit targeting 8.1 apps still works on PCs and phones running Windows 10 and update the nuget packages if necessary.\r\n2. Add support for Windows 10 UWP/UAP apps.\r\n   1. **Gradual port.** Since UWP apps are a bit different in the sense that a single app should support both PC and phone and in the future also other platforms - while it is still possible to have separate projects for phone and PC - it makes sense that new projects are created to support the new paradigm and while most of the helper classes and extensions should port easily - the XAML code and the new sample app will need to be gradually adapted to support the old controls in refreshed form. It also makes practical sense since a lot of the platform resources have changed for Windows 10 and some XAML might not compile anymore.\r\n   2. **Maintaining support for apps targeting 8.1.** Since the hope is that most 8.1 machines should get updated to 10 really quickly and also due to my limited free time - my plan is to create an archived branch with a version targeting 8.1 and clean up the solution and projects to only support 10 unless I hear a lot of negative comments about that idea. The benefit is quicker load and build times for the solution and so a quicker turnaround on any issues for the UWP version of the toolkit. The drawback is that the 8.1 version will likely not see (m)any updates and they will need to be done in a separate branch. Any issues filed for 8.1 I might first or only fix in the UWP version. If I were to maintain support for 8.1 in the main solution - I probably wouldn't get much work done since I'd have to dig into complicated file linking, shared projects with more dependencies and I couldn't make partial releases until I was done with most of the work. All that while having a huge solution that would take a lot of time every time I'd try to load it or build it, shaving significant amounts of the time that could be devoted to porting all the code, fixing bugs or adding new features.\r\n   3. **Projects organization.** Currently the toolkit has one core library/project and a few separate ones that depend on the core library - that's the chart controls, debugging helpers, the calendar control and the gauge control. I could leave that as is or clean it up a bit as I'm upgrading to UWP. \r\n      1. I'm thinking the chart control should be kept separate from the main toolkit and I might remove the dependency on the core toolkit. The reason is this is a big library in itself and seems to be one of the most popular ones, so perhaps if people need it but don't need the core toolkit - it would make it more light weight for use in production projects.\r\n      2. As for the other controls - I'm thinking of either jamming them all together with the others in the core library or move all controls from the core library and the other projects into a separate toolkit controls library, so that people who just want the helpers and extensions can grab just the core library\r\n3. **Priorities.**\r\n   1. Port the core library without the controls to UWP\r\n   2. Port one of the samples projects to UWP to be able to test the changes\r\n   3. Port the chart control to UWP\r\n   4. Port other controls\r\n   5. NuGet packages for the UWP libraries\r\n   6. Port the debugging library\r\n"}}