The nice thing is that you can add or remove the file extensions recognized by the gadget, change where specific extensions should be put, and you add your own folder locations. gif, and other image files go to the Pictures folder. You just drag your files to the magic folder and it examines the file extensions and sends the files to the “right” folder. But for those who always seem to end up with dozens of files sitting on the desktop because they never get around to moving them into appropriate folders, Magic Folder could be a godsend. And many folks won’t like the idea of having a folder make decisions about where to save their files. And if third-parties want to create their own ones, they can easily add them to PowerToys.Okay, granted, the icon isn’t the most professional looking, as you can see in Figure I. I love the idea of having individual gadgets written in WPF/WinUI3 added as PowerToys without the Trident engine of Win7. This would enable animations and such in the UI, and it would also help with high-DPI scenarios (as the Windows 7 gadgets’ visuals were nothing more than one big folder of PNG files). I would suggest that they be reimplemented in WPF (or, over the long term, WinUI 3). That being said, many of the gadgets in the screenshots that posted above would make excellent PowerToys. IMHO, attempting to recreate this would be a huge timesink for little gain. Even if the original gadget platform code was open-sourced (which likely won't ever happen, as it was part of Windows core, and Microsoft is very allergic to open-sourcing parts of that codebase), such a project would run into a number of unavoidable bugs related to Internet Explorer being a newer version than what shipped with Windows 7 RTM. Keep in mind the original gadget platform implementation was very dependent on an outdated version of the Trident rendering engine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |