Hard to work with when using dynamic resources

[pkluz]

First of all: Absolutely great work on the library.

I've got some food for thought for you and if desired, I can submit a pull request as I've already done most of the heavy lifting.

In order to get this library working, I had to rewrite certain portions of the codebase to use UIImages instead of NSStrings with the names of the respective resources.

I believe this is a significant flaw in the architecture for one simple reason:
If one uses dynamically generated resources (drawn at runtime) to achieve resolution independence instead of static bitmaps from the application bundle, ... you're well - screwed.

Now it's kind of impossible to use this library with code generated UIImages, well because I cannot address them by using a NSString.

Cheers

[alikaragoz]

Hi @pkluz thanks for you feedback, you are right about the difficulty to work with dynamically generated images. Ive almost finished working on a major release of the library and will release it in a few days. The release adds the ability to use images instead of images file names. 👍