You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can this be created in a way that after user clicks on checking for updates and download an build update, before it continues to installation procedure to actually apply patches to that ISO files (uup files) so that even from the core (Windows bootloader size, booting logo and etc...) will set automatically mobile-friendly resolution if the mobile hardware is detected. Also some changes to the core should be added so that performances could be good and drivers to be more adaptive and responsive on any type of mobile hardware that meets minimum/recommended requirements of running Windows 11.
This requires a lot to be done but it could be worth it since this type of modifications, installer and service that runs automatically after each windows update has been started could migrate changes after each update and keep all mobile friendly from the windows bootloader to the metro-like UI.
Also, some explorer API changes needs to be done too so that Window-like UI could be modified to be also mobile friendly. For example, instead of using close, minimize/maximize and hide buttons, we can use "mobile-friendly" taskbar (if the mobile hardware doesn't have built-in taskbar controls since some mobile devices have these touchable-buttons physically accessible) where only 3 icons will be in the bottom of the screen. Since taskbar is an part of explorer.exe, modifying explorer.exe libraries that loads taskbar could be very interesting. So the look of those icons could be the same just like Windows phone devices had and for each icon they are replacing touchable window-like icons for closing apps, minimize/maximize and hide/show switch. The Windows logo button will have two purposes for example. If it's clicked it will just hide the window of that app and open the home screen but if it's holded, it will open window-like screen just like Android phones that will be capable in the bugging times to forcefully close the app.
Also window name and icon elements should be moved to that window-like screen and when the user is in the app it will only see above the screen an status bar and in the bottom of the screen the buttons, nothing else. If the app is forcing full-screen. That mode should be full-screen but an touchable-shortcut for showing status bar and taskbar should be implemented just like Android devices have.
With all those modifications I explained here in this friendly suggestion to the devs this AdaptiveShell project could turn basically any desktop OS into mobile OS without any issues and without any legal problems with Microsoft since the closed source code of Windows are not leaked but instead via other ways these modifications has been done.
This could be community-based Windows Phone OS that can be maybe even the best unofficial mobile OS in the mobile market.
And most of Windows Mobile/Phone concepts can become real if this gets an success. We need really good devs who are willing to take their time to do this and who are capable of taking their time to build this. This is very big project but it could be worth it.
Even this project is an perfect start - one step closer to this goal - thank you so much for giving us an hope! If Microsoft doesn't really care, there is always someone who actually cares : )
Have a good day/night and bless you all and your familly
The text was updated successfully, but these errors were encountered:
Can this be created in a way that after user clicks on checking for updates and download an build update, before it continues to installation procedure to actually apply patches to that ISO files (uup files) so that even from the core (Windows bootloader size, booting logo and etc...) will set automatically mobile-friendly resolution if the mobile hardware is detected. Also some changes to the core should be added so that performances could be good and drivers to be more adaptive and responsive on any type of mobile hardware that meets minimum/recommended requirements of running Windows 11.
This requires a lot to be done but it could be worth it since this type of modifications, installer and service that runs automatically after each windows update has been started could migrate changes after each update and keep all mobile friendly from the windows bootloader to the metro-like UI.
Also, some explorer API changes needs to be done too so that Window-like UI could be modified to be also mobile friendly. For example, instead of using close, minimize/maximize and hide buttons, we can use "mobile-friendly" taskbar (if the mobile hardware doesn't have built-in taskbar controls since some mobile devices have these touchable-buttons physically accessible) where only 3 icons will be in the bottom of the screen. Since taskbar is an part of explorer.exe, modifying explorer.exe libraries that loads taskbar could be very interesting. So the look of those icons could be the same just like Windows phone devices had and for each icon they are replacing touchable window-like icons for closing apps, minimize/maximize and hide/show switch. The Windows logo button will have two purposes for example. If it's clicked it will just hide the window of that app and open the home screen but if it's holded, it will open window-like screen just like Android phones that will be capable in the bugging times to forcefully close the app.
Also window name and icon elements should be moved to that window-like screen and when the user is in the app it will only see above the screen an status bar and in the bottom of the screen the buttons, nothing else. If the app is forcing full-screen. That mode should be full-screen but an touchable-shortcut for showing status bar and taskbar should be implemented just like Android devices have.
With all those modifications I explained here in this friendly suggestion to the devs this AdaptiveShell project could turn basically any desktop OS into mobile OS without any issues and without any legal problems with Microsoft since the closed source code of Windows are not leaked but instead via other ways these modifications has been done.
This could be community-based Windows Phone OS that can be maybe even the best unofficial mobile OS in the mobile market.
And most of Windows Mobile/Phone concepts can become real if this gets an success. We need really good devs who are willing to take their time to do this and who are capable of taking their time to build this. This is very big project but it could be worth it.
Even this project is an perfect start - one step closer to this goal - thank you so much for giving us an hope! If Microsoft doesn't really care, there is always someone who actually cares : )
Have a good day/night and bless you all and your familly
The text was updated successfully, but these errors were encountered: