Requirement to use Cocoapods to try the demo app is restrictive about canvas

[yas375]

I'd like rather to propose to look forward nice support of pod try command (CocoaPods/CocoaPods#1568) which would be included in the upcoming Cocoapods release by default.

It will make the process of running a demo app much more simpler for developers.
Cocoapods rocks! :)

[PeteC]

But not everyone has the same opinion of Cocoapods (let's not debate the advantages vs disadvantages here ;))

I wanted to submit a pull request to resolve #5 earlier but because I don't use Cocoapods, I couldn't easily fork the project to make the simple changes

[jamztang]

Currently we are using local pods for development, I learnt it recently and that works pretty well for us.

I understand that CocoaPods are not for everyone, that's same as adding full submodule support. We could complicate the setup procedures, especially when we reach the point that have dependancies on other frameworks, this is what we were still struggling to avoid for both contributers and users.

Side notes is that if I were contributing to third party libraries that was on CocoaPods, I would check out as submodules, but instead of setting up like other framework, I would instead simply change the Podfile to point to the local podspec, then I get the best of both worlds. Maybe you can do us a favor and see if that works for you in the mean time?

[mgriebling]

I agree, have a non-pod version. I don't understand pods and don't want to waste my time doing so unless there really is a compelling reason. For now, I'll pass on this because of the pod requirement. I tried to install using your vague instructions but failed.

[jamztang]

Sorry for taking that long. We'll check-in the Pods folder so it don't require us to use CocoaPods for testing out the project.