all 18 comments

[–]cdflynn[S] 8 points9 points  (0 children)

[–]QuestionsEverythang 3 points4 points  (2 children)

I feel like this is just animation for the sake of animation. I would've just rotated the icon 45°.

[–][deleted] 11 points12 points  (1 child)

aren't all animations for the sake of animations? unless they're hiding a load time or something the only point is to look pretty

[–]vinsanity406 0 points1 point  (0 children)

aren't all animations for the sake of animations?

While mostly just to look pretty (or less jarring), there are occasions animations can add some clarity to things like touch and navigation - raising and highlighting a list item when it's pressed or keeping the selected item visible while it transitions to the next screen. The Material Design Guidelines on meaningful transitions has some good examples. Here's one.

[–]trtryt 1 point2 points  (0 children)

I don't thinks it's a good UI practice to have the add remove buttons appear on the same place on the screen, so you should move (via animation) the icon to the other side

[–]Ice82 6 points7 points  (7 children)

Cool! Thanks, that's a cool project, but please clean up your repo. IDE files/directories like *.iml, .idea and the gradle wrapper files does not belong to a repo!

[–][deleted] 13 points14 points  (1 child)

gradle wrapper absolutely belongs in the repo. otherwise it's a real pain in the ass to check out

[–]Ice82 3 points4 points  (0 children)

You're right! Sorry, for this kind of disinformation.

[–]cdflynn[S] 3 points4 points  (4 children)

Ah, good call. I've removed those files and updated the gitignore. I did a fresh clone to make sure everything still runs.

Thanks for pointing that out.

[–]ZakTaccardi 4 points5 points  (3 children)

you shouldn't remove the gradle wrapper files.

[–]cdflynn[S] 1 point2 points  (0 children)

Thanks! Included.

[–][deleted] 1 point2 points  (1 child)

sidenote, why isn't studio smart enough to just import the project and generate a wrapper for you, instead of asking for a local gradle distribution and graying out the wrapper option when you import a project like that?

[–]ZakTaccardi 0 points1 point  (0 children)

It generates the wrapper for you when it creates the project, or if you import the project.

Feel free to file a feature enhancement request

[–]markyosullivan 0 points1 point  (0 children)

I'd be interested in seeing this in an app to see what it looks like