Suggested additional features about aloestackview HOT 6 OPEN

Hi @ParkGwangBeom, I’m so sorry for the slow review of this last PR - I have only had access via my phone for the past week, no computer unfortunately. I’ll review this ASAP. Thank you for your patience!

from aloestackview.

Hi. If you have time, please take a look at PR (#12 )! Thank you!

from aloestackview.

I like this idea, great suggestion!

I’d want to balance this with making sure the library doesn’t become too complicated though.

If you could provide some concrete examples of use cases where this would be very valuable, I think that would help.

If it’s just for one particular use case that doesn’t happen very often, then it might be better to extend AloeStackView and add this behavior as a customization.

For example, one way might be to override the addRow etc. methods in a subclass of AloeStackView and have them call your own custom protocol method on the row if animated is true.

The idea with AloeStackView is to keep the core very small and simple, but provide extensive support for customization. That way many things can be achieved with it, but the core library won’t become too big or complicated by having lots of features that only address niche use cases.

I’m not sure where this feature fits on that scale yet, so some concrete examples would help!

Thanks again for the great suggestion 😄

from aloestackview.

What I think is that the contentView of the StackViewCell will each be able to handle animation related. (Animatable (?) Protocol such as Highlightable, Tappable, etc.)

For example, when a view is addRow, you will have its own effect of whether the imageView inside the contentView is flashing or not.

I think AloeStackView's own code will not get complicated.
I will give you PR after simple implementation :)

tell me your opinions!
Thanks you.

from aloestackview.

Sounds good. Please feel free to put up a PR demonstrating your ideas and approach!

from aloestackview.

any news on this? :)

from aloestackview.