-
Notifications
You must be signed in to change notification settings - Fork 780
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
IBAnimatable App #238
Comments
👍 Love this idea! It's joining what @JakeLin starts with the transition demo (hidden in "forgot password" ). Moreover, a technical demonstration will be a nice way to avoid some issues about how to use our
That's a good point, but there's one big difference between both: playground can be used to play quickly with the library while a sample like |
Yes I prefer to make another app too. Since IBAnimatable is moving to an organisation, it could even be in a standalone Repo. |
Great idea, @lastMove . I don't mind to extend the existing IBAnimatable Playground or create another repo. If we can publish it to App Store. We can put a link in As we don't know For example: For how to use INAnimatable in code, I don't have concrete ideas how to do it. Maybe provide some pickers to modify the parameters for Animatable type for animations? We may be able to improve it step by step since the library is not small. I am going to put a checklist in the original post, please feel free to modify it. |
Not sure that is a good idea, most of the users won't see it if it's not in the main project.
We can definitely do the same as |
@tbaranes That's is a good point for using main repo for the demo / companion app. Another benefit if we keep it in the main repo is when we implement new features, we can valid them in demo app directly. One of the demo app I really like is https://github.com/scotteg/LayerPlayer, we can download it from App Store https://itunes.apple.com/us/app/layer-player/id949768742?mt=8 It will be great if we can publish our app on App Store. |
Another idea is if we keep the demo app in the main project, shall we display the IBAnimtable Playground as the initial scene? And have an item call "Prototyping in Interface Builder" for the existing Todo app. Then display other items like "Animation", "Transition", etc. Or some items like "Animation in code"? |
Yes, nice. The playground part of the existing app is completely in the spirit of what I thought. |
Demo for how to use in Interface Builder
RefreshTableViewController
already ready to be used, just need to add an entry in the storyboard)Demo for how to use in code
------- Original post -----
Companion App
We could maybe add a “companion” App like Spring ’s one.
It allows to show all Masks, Animations, Transitions, Gradients etc doable with IBAnimatable.
Moreover it’s also a Support for testing those animations / transitions etc directly on-device.
Users could see the code that generate it.
Advantages :
Demo the animations, gradients, mask, transitions,
Help to show in context
It could help to choose an animation while editing
It could simplify regression detection since we can use Xcode UITests
We could even put it on the app store ;)
Disadvantages or alternative :
One more thing to keep updated
It maybe, at least partially, serves the same purpose than the Playground support
How do you think about it ?
The text was updated successfully, but these errors were encountered: