Tool Name
macos-settings
Homepage / Documentation URL
https://macos-defaults.com/
What should the resource manage?
Create a resource that manages MacOS settings via defaults. It would be really useful for Codify to be able to configure MacOS settings directly
Things to manage:
- Mouse sensitivity
- Mouse scroll direction
- Trackpad sensitivity
- Keyboard repeat rate
- Keyboard mappings
- Function key defaults
- Common dock settings.
This is useful for somebody when setting up a new system to get back all of their previous settings.
We don't need to cover every single setting. Just the most common ones would be good. We'll probably need to maintain a mapping of our custom name and the apple original names for each setting. Add a table in the docs with this data.
Some common use cases:
- Some people prefer natural scrolling. Some people don't
- People with non-apple keyboards usually re-map and swap their ctrl (^) and Command keys (@)
The website: https://macos-defaults.com/
Has all of these options listed. You can crawl through the website to get the most up to date information:
https://macos-defaults.com/mouse/
https://macos-defaults.com/keyboard/
For the design of the resource maybe a schema like this might make sense:
{
"type": "macos-settings",
"mouse": {
"naturalScroll": true
},
"keyboard": {
...
}
}
We should have common names for the most common resources instead of having the user use the complicated original Apple names:
- naturalScroll versus com.apple.swipescrolldirection
Of course make this resource macOS only in both the resource settings and the tests
Installation Notes (optional)
No response
Use Cases (optional)
No response
Tool Name
macos-settings
Homepage / Documentation URL
https://macos-defaults.com/
What should the resource manage?
Create a resource that manages MacOS settings via defaults. It would be really useful for Codify to be able to configure MacOS settings directly
Things to manage:
This is useful for somebody when setting up a new system to get back all of their previous settings.
We don't need to cover every single setting. Just the most common ones would be good. We'll probably need to maintain a mapping of our custom name and the apple original names for each setting. Add a table in the docs with this data.
Some common use cases:
The website: https://macos-defaults.com/
Has all of these options listed. You can crawl through the website to get the most up to date information:
https://macos-defaults.com/mouse/
https://macos-defaults.com/keyboard/
For the design of the resource maybe a schema like this might make sense:
{
"type": "macos-settings",
"mouse": {
"naturalScroll": true
},
"keyboard": {
...
}
}
We should have common names for the most common resources instead of having the user use the complicated original Apple names:
Of course make this resource macOS only in both the resource settings and the tests
Installation Notes (optional)
No response
Use Cases (optional)
No response