On Thu, Nov 19, 2009 at 6:23 PM, Scott Granneman sc...@granneman.com wrote:
Plist files are just XML files. I can read or edit or script them with the
normal bash tools; in fact, I've done just that before. No biggie.
Apparently, that's what gconf uses by default, too. It's a collection
of
On Thu, Nov 19, 2009 at 12:03 PM, Scott Granneman sc...@granneman.com wrote:
I guess my first question would be, why replace conf files?
You wouldn't necessarily have to replace conf files, just provide an
API to them. That way you wouldn't have to edit the config files by
hand. Instead you
Secrets was created to expose hidden Preferences that one normally accesses via
the command line because they're not present in the plist files.
Plist files are just XML files. I can read or edit or script them with the
normal bash tools; in fact, I've done just that before. No biggie.
Also,
I wasn't meaning to say that Mac's system is like Windows. I was
saying it suffers from similar problems:
# Centralizing configurations makes it difficult to back up and
recover individual applications.
/Applications, ~/Library, ~/Library/Application Support, ~/Library/Preferences
# In
My guess is that it is supposed to be an auxiliary to (or replacement
for) the ~/.*rc files. That's not a bad thing, if done well. gconf
doesn't seem to be done well. Or if it is done well, it is poorly
documented.
Regards,
- Robert
On Wed, Nov 18, 2009 at 11:24 AM, Scott Granneman
