-
-
Notifications
You must be signed in to change notification settings - Fork 647
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
Listeners #72
Comments
Something like that? new D3NE.Component('mycomp', {
builder(node){ },
worker(node, inputs, outputs){ },
created(node){ }.
destroyed(node){ }
}); I think this can be represented as a node's lifecycle (as it is in Vue.js for components) |
Yes exactly like that! |
You're an Artist man, Keep up the good work |
Thanks! I'll do it in the near future |
I think it is important to have listeners in many components at some levels, for example a listener when a node is about to be deleted, so developers can free up some ressources associated with that node, or show some alerts, save some data etc.
The text was updated successfully, but these errors were encountered: