Consider how we read and write plists about recipe-robot HOT 7 CLOSED

So what I'm talking about is that if you open a plist and parse it, you're
committing to only supporting that file. It means that configuration
profiles cannot be used.

When a mac app checks for a preference, it does a
NSUserDefaults.stringForKey("prefyourinterestedin"), which checks the
preferences system for the value. It doesn't open a file, parse it, and
then look for a particular key in that file object. It lets the CFPrefsD
system handle that. CFPrefsd has all of that stuff cached and aggregated.

Now, do we need Recipe Robot to be able to use a configuration profile? No.

Is it so heinous to include FoundationPlist? No (python-jss does... for
now).

Is it trivial to just use PyObjC to set and get the preferences directly?
Yes.

The above things don't really swing it one way or the other for me.

BUT... If you want to have preferences for the GUI, AND you want them to be
in the same preference domain as the recipe robot python script, it would
make sense to have them do everything through NSUserDefaults since the
Swift or ObjectiveC code won't have a choice.

from recipe-robot.

OK, I'm convinced. Let's switch to PyObjC / NSUserDefaults. Want to search for references to FoundationPlist and make the appropriate changes?

from recipe-robot.

If your doing this maybe we should us nsurlconnection

On Oct 7, 2015, at 1:25 PM, Elliot Jordan [email protected] wrote:

OK, I'm convinced. Let's switch to PyObjC / NSUserDefaults. Want to search for references to FoundationPlist and make the appropriate changes?

—
Reply to this email directly or view it on GitHub.

from recipe-robot.

@eahrold Do you mean add NSURLConnection for GET requests? I'm not smart enough to do that... But I know munki has gurl.py which is a very nice python wrapper around it.

from recipe-robot.

@homebysix I removed the TODO since we have an issue for this.

I'm not feeling like making this change is super critical, unless someone feels really strongly about changing it.

from recipe-robot.

Yes, use gurl. My point was more to the effect that if we're using pyobjc for defaults there's no reason not to use other NS classes where we can.

from recipe-robot.

I mean-that would solve the SSL issues that are TODO'ed up in the code.

from recipe-robot.