@@CodeWithCypert You could have used animated_do . But once in a while knowing about Flutter is also essential rather than heavily relying on libraries.
@@tusharchander8935 I generally try to avoid libraries for one off type things, but I haven’t explored animation packages for Flutter. That might be a fun thing to do, too!
@@CodeWithCypert Well you would just require a SlideUp property from this library. You would be simply wrapping your widget to be animated, be it text widget, Quite easy.
Yeah, that doesn't sound bad, but I factor in the cost to maintain the dependency, too -- which might sound weird, but hear me out: When you pull in a dependency for anything, you're pulling in that package and it's dependencies. Thankfully, dart is compiled so we can only pull in the pieces we need, but we also can run into version conflicts between our dependencies' dependencies. My main app, Luna Journal, uses a LOT of third party dependencies and upgrading certain dependencies is often a nightmare because of this (and upgrading the Flutter version ALWAYS is too, for the same reason). So generally, I just try to avoid extra deps when I can because I find that overhead isn't worth it for small, one-off things. Things like Bloc though, I think the overhead is worth it when it's used all throughout the app :) What are your thoughts, Tushar?
So with animation being that simple when are we getting fulling animated skills and spells for all of Memories of Sheol
When the game is profitable enough to hire someone to animate all of that :)
neat.
I’m glad you think so!
@@CodeWithCypert You could have used animated_do . But once in a while knowing about Flutter is also essential rather than heavily relying on libraries.
@@tusharchander8935 I generally try to avoid libraries for one off type things, but I haven’t explored animation packages for Flutter. That might be a fun thing to do, too!
@@CodeWithCypert Well you would just require a SlideUp property from this library. You would be simply wrapping your widget to be animated, be it text widget, Quite easy.
Yeah, that doesn't sound bad, but I factor in the cost to maintain the dependency, too -- which might sound weird, but hear me out:
When you pull in a dependency for anything, you're pulling in that package and it's dependencies. Thankfully, dart is compiled so we can only pull in the pieces we need, but we also can run into version conflicts between our dependencies' dependencies. My main app, Luna Journal, uses a LOT of third party dependencies and upgrading certain dependencies is often a nightmare because of this (and upgrading the Flutter version ALWAYS is too, for the same reason).
So generally, I just try to avoid extra deps when I can because I find that overhead isn't worth it for small, one-off things. Things like Bloc though, I think the overhead is worth it when it's used all throughout the app :)
What are your thoughts, Tushar?