added defines to prefix all the class names with the contents of the ClassPrefix preprocessor macro so that plugin/bundle developers can avoid namespace collisions with the app and other plugin authors that make use of Sparkle.
Introduces the ability to prefix the sparkle classes in a simple way …
…that makes Sparkle safely useable in bundles/plugins
Remove ClassPrefix from the commit
This could potentially be useful. @pornel, thoughts?
It's a hack, so I'd rather not do this unless there's a clear need for it, and given that there hasn't been a ton of +1s on this issue since 2011, it may not be worth it.
Current Apple's recommendations are to use 3-letter name prefix (which won't collide with Sparkle's 2-letter prefix), and Swift will be immune to this problem.