Automatically converts binary property lists to XML when opened and writes them back out to binary when saved.
- Total 2K
- Win 418
- OS X 1K
- Linux 75
|Oct 18||Oct 17||Oct 16||Oct 15||Oct 14||Oct 13||Oct 12||Oct 11||Oct 10||Oct 9||Oct 8||Oct 7||Oct 6||Oct 5||Oct 4||Oct 3||Oct 2||Oct 1||Sep 30||Sep 29||Sep 28||Sep 27||Sep 26||Sep 25||Sep 24||Sep 23||Sep 22||Sep 21||Sep 20||Sep 19||Sep 18||Sep 17||Sep 16||Sep 15||Sep 14||Sep 13||Sep 12||Sep 11||Sep 10||Sep 9||Sep 8||Sep 7||Sep 6||Sep 5||Sep 4|
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.