Automatically converts binary property lists to XML when opened and writes them back out to binary when saved.
- Total 4K
- Win 959
- Mac 3K
- Linux 174
|Jul 5||Jul 4||Jul 3||Jul 2||Jul 1||Jun 30||Jun 29||Jun 28||Jun 27||Jun 26||Jun 25||Jun 24||Jun 23||Jun 22||Jun 21||Jun 20||Jun 19||Jun 18||Jun 17||Jun 16||Jun 15||Jun 14||Jun 13||Jun 12||Jun 11||Jun 10||Jun 9||Jun 8||Jun 7||Jun 6||Jun 5||Jun 4||Jun 3||Jun 2||Jun 1||May 31||May 30||May 29||May 28||May 27||May 26||May 25||May 24||May 23||May 22|
I'm an Objective-C developer by trade and a Ruby developer at heart, so excuse my poor python skills. This is my take at a plist plugin for Sublime Text 3 that should make working with plists feel a lot more first-class. It provides:
- Automatic conversion of binary plist to XML. You can then edit the XML file in Sublime and it will automatically convert back to binary when you save.
- Cross platform support. The solution is pure python. No calls to the command line, no foreign-function shenanigans, just 100% python goodness.
- Plist syntax highlighting from TextMate.
The python plist support is taken from the Python 3.4 standard library, with a few modifications to support running in the Python 3.3 that ships with Sublime Text 3. This library therefore has a heavy dependency on Python 3.x which is why it'll probably never work with Sublime Text 2. Seriously, just use Sublime Text 3, it's awesome.
Sublime Text is by far my favourite text editor. It has a fantastic package manager in Package Control which allows you to manage the installation of plugins that extend the functionality of Sublime. Sublime doesn't support binary plists out of the box, but a kind sir by the name of relikd made a plugin that can convert to and from binary plist. I have a couple of problems with his implementation, though:
- The UX leaves a lot to be desired. It requires you to manually press some arcane key combination to toggle between binary (useless) and XML (useful). I can't imagine any situation where'd you want to edit the binary in a binary plist by hand, so why open it as binary by default?
- Internally, it just calls the
plutilcommand line tool that ships with OS X. This means it requires OS X to work. Ideally, this should be an entirely python native solution, which would work on any platform, on the off-chance you encounter a plist file on a non-Apple computer. Having to start up a command line app doesn't strike me as particularly efficient either.
- It doesn't ship with a plist syntax definition. XML plists can of course just use the built-in XML highlighter, but that isn't nearly as strict as plists are, and it doesn't support the “old-style” plist format which you sometimes still see.