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

Animtable Material elements #7

Open
22 of 26 tasks
JakeLin opened this issue Jul 13, 2016 · 8 comments
Open
22 of 26 tasks

Animtable Material elements #7

JakeLin opened this issue Jul 13, 2016 · 8 comments
Milestone

Comments

@JakeLin
Copy link
Member

JakeLin commented Jul 13, 2016

There are some Animtable Material elements we may support for IBAnimatable-Material

  • AnimatableMaterialButton
  • AnimatableMaterialFabButton
  • AnimatableMaterialFlatButton
  • AnimatableMaterialRaisedButton
  • AnimatableMaterialIconButton
  • AnimatableMaterialCardView
  • AnimatableMaterialImageCardView
  • AnimatableMaterialCollectionViewCell
  • AnimatableMaterialControlView
  • AnimatableMaterialSearchBar
  • AnimatableMaterialMenuView
  • AnimatableMaterialNavBar
  • AnimatableMaterialTableViewCell
  • AnimatableMaterialTextField
  • AnimatableMaterialErrorTextField
  • AnimatableMaterialTextView
  • AnimatableMaterialLabel
  • AnimatableMaterialPulseView
  • AnimatableMaterialView? (supper class?)
  • AnimatableMaterialBarView
  • AnimatableMaterialTabBar
  • AnimatableMaterialToolbar

Not supported yet

  • AnimatableMaterialCollectionView
  • AnimatableMaterialCollectionReusableView
  • AnimatableMaterialSwitch? (Animtable doen't use UIControl for Switch)
  • AnimatableMaterialBottomTabBar? (Animtable hasn't supported UITabBar yet 😓)

@damtsnkff @gkye please have a look and feel free to prioritize or modify the list.

@JakeLin JakeLin added this to the 1.0 milestone Jul 13, 2016
@damtsnkff
Copy link
Member

@JakeLin Perfect, thanks for the list 👍

@gkye
Copy link
Member

gkye commented Jul 13, 2016

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)

@damtsnkff
Copy link
Member

damtsnkff commented Jul 13, 2016

@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 ?

@gkye
Copy link
Member

gkye commented Jul 13, 2016

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.

@JakeLin
Copy link
Member Author

JakeLin commented Jul 17, 2016

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 IBAnimatable/IBAnimatable#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.

@JakeLin
Copy link
Member Author

JakeLin commented Jul 20, 2016

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
#7 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjBoHkD0hYlnnTWvq5b1CcKlBjgFQvBks5qXV2tgaJpZM4JLV89
.

@multinerd
Copy link

Is this still being worked on?

@JakeLin
Copy link
Member Author

JakeLin commented Oct 16, 2017

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants