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

Listeners #72

Closed
Hamdiovish opened this issue Apr 9, 2018 · 6 comments
Closed

Listeners #72

Hamdiovish opened this issue Apr 9, 2018 · 6 comments

Comments

@Hamdiovish
Copy link

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.

@Ni55aN
Copy link
Member

Ni55aN commented Apr 9, 2018

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)

@Hamdiovish
Copy link
Author

Yes exactly like that!
Component's lifecycle feature will give the ability to the library to be used in complex and heavy usages such websocket or whatever.

@Ni55aN
Copy link
Member

Ni55aN commented Apr 9, 2018

4085c9e

@Ni55aN Ni55aN closed this as completed Apr 9, 2018
@Hamdiovish
Copy link
Author

You're an Artist man,
Perfect job,
I'm interested in contributing in this project, please consider to comment its code, its main components and build instructions for easier contribution.

Keep up the good work

@Ni55aN
Copy link
Member

Ni55aN commented Apr 9, 2018

Thanks! I'll do it in the near future

@Ni55aN
Copy link
Member

Ni55aN commented Dec 19, 2018

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

No branches or pull requests

2 participants