Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Pod example apps to quickly try a Pod. #1568

Closed
alloy opened this issue Nov 9, 2013 · 4 comments
Closed

Use Pod example apps to quickly try a Pod. #1568

alloy opened this issue Nov 9, 2013 · 4 comments
Labels
t1:enhancement Enhancements that have not been picked up yet. Please comment if you plan to work on it t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future.

Comments

@alloy
Copy link
Member

alloy commented Nov 9, 2013

Most libraries have example apps, we should make it easy for CP users, but also current non-user to try these libs/examples through CP.

  • This needs a spec change to specify the example(s). Maybe it should just be a shell command that builds the app as needed, or opens the project in Xcode?
  • Add a command to the CLI to use this. E.g. pod try NAME ?
  • Or should this be a plugin? And if so, how do we deal with the spec change?
@orta
Copy link
Member

orta commented Nov 9, 2013

Nice idea. How I could see it working. Using ORStackView as an example. ( https://github.com/orta/ORStackView )

I do pod try ORStackView

It clones that to a temporary folder. Then CP / a plugin, looks for something like s.demo = "Project" if that fails it searches for the first xcproject. If it cannot find one it bails ( in an ideal world this would be a good time to turn it into an IRB like experience ) but if it does it performs pod install in the xcode directory and opens the new xcworkspace.

IMO this entire thing could be made without changes to the DSL, it'd be a bit less elegant though ( dealing with multiple xcodeprojects ) - not making DSL changes means that it could easily be handled outside of CP.

@fabiopelosin
Copy link
Member

This is an awesome idea!

@fabiopelosin
Copy link
Member

To be clear the purpose of this is to open the project used by the spec. This assumes that if a Podfile is found in the dir integration with CocoaPods is required. So we:

  1. checkout the source of the Pod in a temporary directory
  2. don't clean it
  3. perform pod install if needed
  4. open the workspace/project

@swizzlr
Copy link
Contributor

swizzlr commented Nov 11, 2013

This would make an excellent plugin. Could it be as simple as cloning an entire git repo to a temp folder, running any bootstrap commands and then opening the designated proj/workspace? Easier to implement off the bat, and would work right away with AFNetworking, RAC and others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t1:enhancement Enhancements that have not been picked up yet. Please comment if you plan to work on it t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future.
Projects
None yet
Development

No branches or pull requests

4 participants