Open preaction opened 9 years ago
The more I think about this, the more I want it to be a Document subclass. In theory, it could have other prereqs even, for example to enable auto-filling metadata from the file itself.
But for ease-of-use, it needs to be supported from the default themes. Which likely means that the Podcast document should be in the main distribution.
It also means that the Document class should probably have more control over how it is inflated from the raw data from the Store. A clearer division here will improve the flexibility and power of Document classes. Once again, proper OO techniques demonstrate their value.
http://www.apple.com/itunes/podcasts/specs.html
It'd be nice to be able to write podcasts with this thing