-
Notifications
You must be signed in to change notification settings - Fork 177
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
Recreated demo project. #38
Conversation
Hey @benjohnde, I downloaded your branch and got this: |
I guess you need to select the framework scheme at first and build it. Am 19.09.2016 10:03 vorm. schrieb "Lucas Farah" notifications@github.com:
|
Now it worked. What if instead of making the framework necessary for the example app, we just add the |
Again, really thanks for helping the lib! 😄 |
I really hate that because changing the library means copying the file into Am 19.09.2016 10:24 vorm. schrieb "Lucas Farah" notifications@github.com:
|
@benjohnde I completely understand your point of view. I think that there are many developers that wouldn't know what building the framework scheme is, so by providing an example app that just works is very important for beginners. |
True. Maybe we can create a hard dependency so that the framework gets Am 19.09.2016 10:29 vorm. schrieb "Lucas Farah" notifications@github.com:
|
Now it should work like magic :) I only missed to add the framework to "Linked Frameworks and Libraries" as "required" in the demo target. You can verify it by doing the following:
Cheers! |
Perfect! Merging this, bumping the version and sending to CocoaPods 👍 |
Hey @lfarah I am not familiar with CocoaPods. I will give Carthage a try later on. But your bug report does not sound like it could be our fault. |
It's working now... |
A bit of restructuring and got the demo project back to work. Reformatted some comments to work with recent Xcode. Closes #33.
Sry for the huge amount of changes. I recreated the whole demo project and cleaned it up (especially removed localization shizzle and all the AppDelegate stubs to focus only on the actual example invocation of the DatePickerDialog).
I also created a shared scheme for the DatePickerDialog itself. Now you have all three parts (Sources, Tests and Demo) in one Xcode project. It is also more feasible to write unit tests and directly see the changes in the demo application.
Cheers!