Moved bundle into its own target

[DerAndereAndi]

• Provides Xcode processing/optimizations of image resources
• Easier integration of the bundle into apps by using the target product when adding the Xcode project into a workspace
• Podspec adjusted based on HockeySDK, would need some testing

[robertwijas]

Thanks for contribution!

1. For small console images I don't think image preprocessing is necessary.
2. Can you explain what difficulty you have with current solution?
3. Cococapods will move to Yaml eventually and I believe post processing hooks will be deprecated.

In other words, I'm not convinced :)

[DerAndereAndi]

Hi Robert,

let me answer your doubts :)

1. Not necessary or not, that part of the process is missing :) It's a hack, and I like to make things clean :) This would use the normal Xcode system of assigning files to products, instead of relying on the file system to assign which file goes into which product. And resource bundles are a proper Xcode product :)
2. Currently the bundle will be copied/references into my project, where I have to make sure it doesn't copy. I only care that the bundle is copied into the app bundle.
3. Right, the process hook for the HockeySDK was done by @alloy maybe he can help there :)

Of course the current system works, but it feels like working around the way this is meant to be handled in Xcode.

Best, Andreas

[alloy]

Cococapods will move to Yaml eventually and I believe post processing hooks will be deprecated.

Right, the process hook for the HockeySDK was done by @alloy maybe he can help there :)

While this is true, there will most definitely be support for resource bundles. In fact, in the near future this will be our preferred approach.

The hooks are basically there so that we can get a good idea of what features we still have to add for v1.0.

HTH