Animtable Material elements
There are some Animtable Material elements we may support for IBAnimatable-Material
- [x] AnimatableMaterialButton
- [x] AnimatableMaterialFabButton
- [x] AnimatableMaterialFlatButton
- [x] AnimatableMaterialRaisedButton
- [x] AnimatableMaterialIconButton
- [x] AnimatableMaterialCardView
- [x] AnimatableMaterialImageCardView
- [x] AnimatableMaterialCollectionViewCell
- [x] AnimatableMaterialControlView
- [x] AnimatableMaterialSearchBar
- [x] AnimatableMaterialMenuView
- [x] AnimatableMaterialNavBar
- [x] AnimatableMaterialTableViewCell
- [x] AnimatableMaterialTextField
- [x] AnimatableMaterialErrorTextField
- [x] AnimatableMaterialTextView
- [x] AnimatableMaterialLabel
- [x] AnimatableMaterialPulseView
- [x] AnimatableMaterialView? (supper class?)
- [x] AnimatableMaterialBarView
- [x] AnimatableMaterialTabBar
- [x] AnimatableMaterialToolbar
Not supported yet
- [ ] AnimatableMaterialCollectionView
- [ ] AnimatableMaterialCollectionReusableView
- [ ] AnimatableMaterialSwitch? (Animtable doen't use
UIControlfor Switch) - [ ] AnimatableMaterialBottomTabBar? (Animtable hasn't supported
UITabBaryet 😓)
@damtsnkff @gkye please have a look and feel free to prioritize or modify the list.
@JakeLin Perfect, thanks for the list 👍
Would it be okay to add all similar elements to the same storyboard or viewcontroller (if programmatic)? It will be a lot cleaner than creating a storyboard and reference for each element. (ie. All button or textField elements could be grouped together in one storyboard)
@gkye I really think so. Maybe by group ? For example we could group them like this
- [ ] -- Button -- (2/5) AnimatableMaterialButton AnimatableMaterialFabButton *AnimatableMaterialFlatButton *AnimatableMaterialRaisedButton AnimatableMaterialIconButton
- [ ] -- View -- (0/3) AnimatableMaterialCardView AnimatableMaterialImageCardView AnimatableMaterialControlView
- [ ] -- Bar / Navbar -- (0/7) AnimatableMaterialBarView AnimatableMaterialSearchBar AnimatableMaterialToolbar AnimatableMaterialMenuView AnimatableMaterialTabBar AnimatableMaterialBottomTabBar? (Animtable hasn't supported UITabBar yet 😓) AnimatableMaterialNavBar
- [ ] -- TableView / CollectionView / Cell -- (1/4) *AnimatableMaterialTableViewCell AnimatableMaterialCollectionView AnimatableMaterialCollectionViewCell AnimatableMaterialCollectionReusableView
- [ ] -- Label / Textfield / Other Components -- (1/7) AnimatableMaterialTextField AnimatableMaterialErrorTextField *AnimatableMaterialTextView AnimatableMaterialLabel AnimatableMaterialPulseView AnimatableMaterialSwitch? (Animtable doen't use UIControl for Switch) AnimatableMaterialView? (supper class?)
What do you think ?
This would work. For View, Bar/NavBar and TableView / CollectionView / Cell we could create multiple viewcontrollers within that storyboard and add options to segue to each viewcontroller? or a static tableviewcontroller which links them.
I like the idea to group them into different sections. I found out the examples in Material are hard to experiment. I prefer to have an example app to demonstrate all features.
@gkye I am not sure which way is better, maybe we can try some and find the best practice. It is not easy to make a good demo app. We also discuss that in https://github.com/JakeLin/IBAnimatable/issues/238 . I used code to demonstrate different subtype of the type before like MaskType and Transitions. And I used Interface Builder to demonstrate elements like Placeholder.
Are UICollectionVIew and UICollectionReusableView supported by IBAnimatable yet?
-- Not yet, 😅
On 20 July 2016 at 09:28, George Kye [email protected] wrote:
Are UICollectionVIew and UICollectionReusableView supported by IBAnimatable yet?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JakeLin/IBAnimatable-Material/issues/7#issuecomment-233796956, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjBoHkD0hYlnnTWvq5b1CcKlBjgFQvBks5qXV2tgaJpZM4JLV89 .
Is this still being worked on?
@multinerd I don't have time to work on that at that moment. It is almost done for Swift 3. But haven't upgraded to Swift 4 yet. Could you like to give it a try?