@edvin What do you think of this for the SO question?

@User uploaded a file: SequentialTransition Mixed In

@carlw That looks like a good solution, and an easy one to create a builder for! Nice work!

ok. i'll post it. if you want to double-back over the question with a SNAPSHOT fix, keep the question bookmarked

posted

Great! Thank you 🙂

I don't have time to add it now, maybe somebody else want to give it a try?

I'll write up an issue. I may be able to handle it later.

@Ruckus This can be straightforward, but I was wondering how Sequential and ParallelTransition classes would affect the timeline.play flag before I tackled it myself. https://github.com/edvin/tornadofx/issues/373

@carlw If you operate on some object inside of the

sequentialTransition

builder, this object could define it's own timeline function perhaps, which calls the existing one with

play=false

.

You mean timeline would be overridden by a sequentialTransition extension function? That would be a cool way to disable autoplay without breaking anything

Let me try to implement this real quick. I see that the timeline builder is defined on EventTarget now, but that doesn't make any sense, does it? It isn't attached to the EventTarget anyways.

I propose to define timeline as a package level function, not an extension function, and then adding an extension function to SequentialTransition and friends.

@User uploaded a file: Transitions :)

Let's to a release this weekend, we've got some goodies in this one 🙂

@carlw Very grateful for your contribution once again, this was a nice addition to the animation capabilities!

@edvin No problem, if you look at the earlier game background example I posted from a JavaFX blog, you'll see that there's room to add some of the atomic Transition builders. Instead of using keyframe/keyvalue like the SO poster, you'd let the programmer use "fromX/toX" or "fromAngle/toAngle".

Nice, we should definitely add support for those, it's pretty verbose when you only have a single keyvalue for each frame/timeline.

@Ruckus What do you think of adding specific Transition classes like in this post? (Same article as posted before in case it scrolls off) http://bekwam.blogspot.com/2016/01/composable-javafx-paralleltransitions.html

@edvin I used these classes for a cancelled drag-and-drop operation in a business app

I think we already support those with move etc.

I see that we also support sequentialTransitions using

then

. Wow, so much stuff I didn't even know about!

You can chain then() s together?

@edvin i think there's still some value in having the dedicated classes, but i think my example where the sequence is known at compile time would be better off with then()

Yes, you can chain them.

it's nice...a lot better than what i did... sigh OOP baggage

t1.then(t2).then(t3).then(t4).play()

i threw that into my SO answer from this morning

Great! Not sure if I should remove the sequentialTransition builders or not.

what would the idiom be if you didn't know the sequence in advance? say you pulled a list of transformations from a file or other part of the program