Recently Browsing 0 members
No registered users viewing this page.
By Abhay V
Google brings Flutter to Windows in Alpha form, aims to add UWP support soon
by Abhay Venkatesh
Just a day after popular Apple-developed programming language Swift made it to Windows, Google has announced that it is bringing Flutter – its open-source, cross-platform framework – to Windows in Alpha form. The search giant has been working to bring the development platform to Windows for some time and there has even been a technical preview since June. The Alpha is supported on Windows 7 and newer.
Flutter provides developers the ability to reuse code when building apps for multiple platforms while also leveraging the native capabilities of each platform. The Mountain View giant says that as per its own statistics, more than half of Flutter developers use Windows and that the addition of support for native desktop elements and APIs further expands the reach of the cross-platform framework.
While the platform began with touch-based OSes like iOS and Android, it has added support for other input methods such as keyboards, mice, and more, while also adapting for larger screen sizes. This also includes support for plugins that work in unison with native code, bringing more capabilities to apps developed using the framework. The list of added components for the alpha version includes:
The company has also created sample apps for developers to reference, which can be downloaded from GitHub here. Interested users can also head here to read more about how the app was built. The firm has also updated the Flutter Gallery app with support for desktop platforms to exhibit the prowess of the framework. The Flutter SDK can be downloaded from here. Google also recommends that developers read the additional requirements here and has provided a detailed document on getting started in its blog post.
The firm has also created a few plugins, such as the URL launcher for launching URLs in the browser from Flutter apps, and more. Developers can also build their own plugins for Windows. There are various other resources that have been listed in the document here.
With the Alpha release now out, Google says that it is working towards “completing the feature set and stabilizing the product for release”. It is working to improve “accessibility, globalization and localization, enhanced keyboard and text handling, support for command line arguments, and more”.
In addition to supporting Win32 APIs, the company said that it is also working to bring a UWP version of the Flutter shell to add support for platforms such as Xbox and Windows 10X. It has also released a UWP version of the Flutter Gallery app in the Microsoft Store as a proof of concept.
By Usama Jawad96
Swift makes its way to Windows 10, toolchain images now available
by Usama Jawad
Swift is a general-purpose programming language that is developed by Apple and was launched back in 2014. Although initially a proprietary language, Swift went open source for Apple platforms and Linux in 2015.
Today, the Swift team has announced that support for the language has arrived on Windows 10, with new toolchain images now available to download for the operating system.
In a blog post, Saleem Abdulrasool who is a member of the Swift Core Team and a software engineer at Google Brain, has stated that the process of porting Swift to Windows does not only include shipping the compiler but also standard and core libraries since these reduce the coding complexity for developers. With version 5.3 of Swift, development on Windows purely in Swift is now possible, and is at a point "where early adopters can start using Swift to build real experiences". It also allows developers to take advantage of existing Windows libraries.
Abdulrasool has demoed a Calculator app written in Swift that utilizes application code as well as Windows system libraries. Early adopters such as Readdle have also been testing the development of cross-platform applications and have been fairly successful in their endeavors as well.
Swift Package Manager is currently not supported on Windows, but Abdulrasool says that it is coming soon as well. He goes on to say that:
Those interested in trying out Swift on Windows can refer to the "Getting Started" page here. People interested in working on core tooling can check out the Swift Bug Tracker here.
By Rich Woods
Microsoft announces new platform features coming to Windows
by Rich Woods
Today at its Ignite 2020 conference, Microsoft actually has some Windows news to share, and it's all about developers. New versions of products are coming, such as WinUI 3 Preview 3, which lets you make apps for ARM64 now.
First up is MSIX. Developers can now deploy files to a shared container instead of a standalone single MSIX container. This is a big deal for apps that rely on shared files or registry settings. MSIX apps will also be able to automatically update; devs will just have to add metadata with update settings to the app package. There's also a new Azure DevOps extension that automates the process of creating an MSIX package.
For C# .NET 5 developers, you'll now be able to create Windows Runtime components with a new CsWinRT tool, coming to public preview this month. Also, the Windows SDK team is going to be releasing NuGet packages that help you to build Windows apps in "a more cloud-friendly way". The idea is that it will not require a full SDK install, using CI/CD pipelines instead.
There's a new version of React Native for Windows, bringing it to version 0.63. It adds navigation support, better theming support, automatic linking of native modules, and more. WSL is getting new features, with users of Windows 10 versions 1903 and higher getting support for WSL 2. GUI apps in WSL are in testing in the Windows Insider Program, and you can now install WSL by running 'wsl --install'.
Finally, Windows Terminal is getting improvements. It now has hyperlink support, letting you click on things in Terminal and having them open in the browser. It's also adding a jump list to you can launch right into a specific profile, and there's a new command palette to easily navigate your terminal.
By Abhay V
Samsung might expand Galaxy Tab S7's Second screen feature to more Windows PCs
by Abhay Venkatesh
Apple debuted a feature in macOS Catalina called Sidecar back in 2019 that let Mac users extend their computer displays to iPads and other touchscreens. This allowed for users to use the secondary touch and stylus enabled displays – like the iPad Pro – as an input device for the Mac, making it easy to run touch-supported apps on devices without support for such input devices.
Now, a new report suggests that Samsung is working to bring a similar feature to its flagship Galaxy Tab S7 tablets. The feature, internally codenamed ‘Sidekick’, aims to let users extend their Windows PC screens to the tablets and enable the S Pen to work as an active stylus for the devices. The feature is expected to also support different pressure levels from the S Pen.
Interestingly, the South Korean giant detailed this very feature – called Second Screen – during the launch of its Galaxy Tab S7 devices. However, at the time, the firm claimed that the feature would work with Samsung PCs and that it will be available later this year. It is not clear if project Sidekick refers to the same feature, or if it is part of an effort to bring support to all Windows PCs.
While the original announcement suggests that the tablets will connect wirelessly to Windows PCs, it is also not known if the capability will extend to support wired connections. This could greatly improve adoption owing to the addition of support for desktop PCs. Many Windows laptops already offer touchscreen and stylus support. Another advantage for PCs is that users can leverage the tablet’s hardware for input while running resource-heavy creative applications on the desktop.
Second screen will be enabled for the Galaxy Tab S7 and Galaxy Tab S7+ via a firmware update “later this year”. It will be interesting to see how the company pegs this offering, and if ‘Sidekick’ happens to be more than what the company has already revealed.
Source: Android Police
By Abhay V
Recent Windows 10 version 2004 Patch Tuesday updates are reportedly breaking WSL 2
by Abhay Venkatesh
Microsoft released its regular suite of Patch Tuesday updates to all supported versions of Windows 10, Windows 8.1, and Windows 7 ESU customers yesterday. However, users of Windows Subsystem for Linux 2 (WSL 2) have begun reporting that the updates are causing issues with the environment. The troublesome update seems to be the one released for the May 2020 Update (version 2004), filed under KB4571756.
Installing the cumulative update that bumps up the build to 19041.508 supposedly causes WSL2 to not load and display an “Element not found error”. It is not clear how widespread the issue is, and if there are any specific configurations that are causing the issue. Users on GitHub report that the problems began surfacing after installing the update, and that uninstalling the quality update fixed the problem.
Interestingly, though users claim to be able to get WSL 2 working post uninstalling KB4571756, the problem with WSL prompting an error has existed since late July and also plagues users when they try to upgrade from WSL 1 to WSL 2. Another thread suggests that the errors are being served in Insider Preview builds, suggesting that the problem is not specific just to current production versions of the OS.
It is not clear what exactly causes the issue since it affects multiple versions of the OS. It is also not clear if it was fixed with a previous patch for the production versions that reappeared with the latest round of updates. There are no reports on whether the error is seen on Windows 10 versions 1903 and 1909 since WSL 2 was backported to those versions last month.
While the known issues on the KB article does not list the WSL 2 problems, a response on GitHub suggests that the company is working on a fix. For those running production builds that rely on WSL 2, it is best to pause the latest updates from installing. The only workaround for those that are facing issues after the update is to uninstall the cumulative patch by heading to Settings > Update & Security > Windows Update > View update history > Uninstall updates and uninstalling KB4571756..
Source: GitHub via Techdows