Skip to content
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

Figure out what to do about Animation.types() #64

Open
doughsay opened this issue Jul 11, 2020 · 1 comment
Open

Figure out what to do about Animation.types() #64

doughsay opened this issue Jul 11, 2020 · 1 comment
Labels
discussion Needs discussion

Comments

@doughsay
Copy link
Member

Need to have a discussion about this, a lot of us feel like something's wrong here...

@doughsay doughsay added the discussion Needs discussion label Jul 11, 2020
@doughsay doughsay mentioned this issue Jul 11, 2020
4 tasks
@vanvoljg
Copy link
Member

Maybe an ETS table that holds onto this part of application state? Meaning the animations which are available to the application.

I'm still puzzling out how to do discovery of available modules and how to turn that into a type. I really want to figure out how to do it at runtime, but it may end up being compile-time. Runtime would make it so we evenually can allow users to add their own animations to a running Xebow application, which would be fantastic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Needs discussion
Projects
None yet
Development

No branches or pull requests

2 participants