Un-globalize the rest of platform services
See original GitHub issueThose should be provided by a toplevel:
-
IKeyboardDevice
-
IPlatformSetting
(should be split into two interfaces, one for colors which are required by App.xaml, another for the rest) -
PlatformHotKeyConfiguration
-
IClipboardImpl
(just remove from locator)
We should probably hide the locator as well, but it’s sometimes usable for overriding stuff.
Issue Analytics
- State:
- Created 4 months ago
- Reactions:2
- Comments:8 (8 by maintainers)
Top Results From Across the Web
3 Obstacles to Globalizing a Digital Platform
As technology progresses, it has become increasingly easy for digital platform companies to reach customers around the globe.
Read more >Digital platforms driving shift in supply chains, globalization
U.S., China largest platform markets, while Europe lags, report finds.
Read more >Remote Work and the Globalization of Services
Until recently, globalization has been about the trade of goods, not services. The ability of companies to hire remote workers allows—for the first...
Read more >Globalization and localization in ASP.NET Core
Learn how ASP.NET Core provides services and middleware for localizing content into different languages and cultures.
Read more >Globalization: New Locale Formats and Longer Translations
Enable new and improved formats for international dates and times via a critical update. Read right to left in reports and dashboards, and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just a curiosity? Why did you think about this choice? Wasn’t it better to move these interfaces to Application? Do you plan to instantiate a TopLevel without an App? Will it be possible to instantiate more Applications?
This choice complicates access to services such as the Clipboard in MVVM scenarios, it will force you to pass the View to the ViewModel with the possibility of creating memory leaks. If moved to the application level it could be accessed simply like this:
Technically we do allow customizations like forcing the render timer to tick on the UI thread. But I guess it could be moved to platform options instead