Update: François Beaufort’s told me in a Google Plus conversation that this is “structural changes only”.
I have been noticing code commits around this for a few days now. However, I am writing this post with only 60% confidence. So, I’ll need your help to figure out what the actual deal is.
Or, we might soon see an experimental flag with this feature. Let’s get started.
Here is the commit description:
Remove chrome/browser dep from Chrome OS settings
InstallAttributes and the “Chrome” Schema both have few deps and are
needed in Chrome OS settings code, in code that should be servicified.
See go/ash-settings-split. However, getting a useful instance of
either class currently means depending on chrome/browser to get
browser_process and all of its global services.
This CL makes InstallAttributes and the Chrome Schema singletons that
can also be obtained directly, and so removes one of the dependencies
on chrome/browser from the Chrome OS settings code.
The bug associated with this change is also public:
Make CrosSettings available outside src/chrome
We should move CrosSettings to src/chromeos/settings where it can be accessed by code in src/ash and src/ui without the use of delegates.
Here is what I think is going to happen. Just like in Android (no surprises there) you will be able to access Chrome OS settings separate as an app. Google Chrome settings will be another app.
This could be Google beginning to treat Chrome as just another app running on Chrome OS. Well, if that’s the case, this will be THE biggest change in Chrome OS since its inception.
As I said, I am not 100% sure about these things yet. I would love to hear what you guys think. Let me know in comments. We could figure out more together!