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