-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add tweening support #204
Comments
Might be related to #120 |
We should also evaluate existing freely available solutions for this. Maybe there is a general data format for such animations that we can support or adapt. |
As a more abstract approach, we could consider implementing or referencing a tweening framework. I think that tweening would be a sufficient, streamlined, and generally reusable approach to modify numeric values over time. In fact, the aforementioned Tweening engine implements every single easing function defined by Robert Penner, which are available under BSD and MIT (this is the implementation in TweenEngine). In the end, we just need an interface that can be implemented by GUIComponents, Entities, Images, Sounds,... to modify their numeric attributes over time. Building node-based animations might be nice in terms of individualism - but let's be honest: Such a feature, including the corresponding UI in utiLITI and import / export capabilities, is probably out of scope for LITIENGINE. |
I've managed to come up with a working prototype for tweening support using the suggested Tweening Engine. It looks very promising and was super easy to implement. |
We should support some sort of xml-exportable animations for sprites to make more vivid games.
I imagine a node-based graph editor in utiLITI from where you can save newly created animations and import existing ones into your project.
To help you visualize the idea, this was inspired by this cool tweet I saw:
https://twitter.com/CodeManuPro/status/1075885060849582081?s=09
This should include the following features:
Since there is not really a need for this window to be pinned to the utiLITI main frame, we should just directly write it in JavaFX and include it as an "animations" tab once utiLITI is ported to JavaFX as well.
The text was updated successfully, but these errors were encountered: