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.

Sign up for GitHub

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

Jump to bottom

JSEvents issues #36

Open
paraboul opened this issue Nov 29, 2016 · 0 comments
Open

JSEvents issues #36

paraboul opened this issue Nov 29, 2016 · 0 comments
Assignees
@paraboul

Comments

@paraboul
Copy link
Member

paraboul commented Nov 29, 2016 •
edited

We should rework the JSEvents class :

  • It should be exposed to the userland through ClassMapper as EventEmitter base class (NodeJS compat).
  • ClassMapperWithEvents<T> that currently implements JSEvents should somehow inherit the prototype.
  • JSEvents::CreateEventObject() should also uses a prototyped object rather than implementing JSEvents_funcs everytime.

png
@paraboul paraboul self-assigned this Nov 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paraboul paraboul

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paraboul