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

Documenting wrappers and other interfaces #36

Closed
willsoto opened this issue Sep 12, 2014 · 6 comments
Closed

Documenting wrappers and other interfaces #36

willsoto opened this issue Sep 12, 2014 · 6 comments
Labels

Comments

@willsoto
Copy link
Contributor

In the README, number 4 states you would like better interfaces, like an Angular wrapper. Did you have any thoughts in mind on where these would go / where they would be listed? (I actually just wrote one, so this is partly a shameless plug lol)

But I do think it would be a good idea to have a list of wrappers that are available so people can find them easily.

@gionkunz
Copy link
Collaborator

Cool man 😄 I've started my own one but never invested a lot of time. It was more a PoC. Nice to see that you've implemented something! I'll give it a go this weekend and maybe report some issues. I'm fine if the ng-chartist module is living in your house. I'll definitely contribute to the module when there is work and I find time.

One thought I had, what would actually be nice, is if the series data can be done with nested directives. This way the core configuration could be done declaratively in HTML.

Once I've tested your module and it's ready to be used, I'll list it in the documentation and the readme of Chartist of course.

Awesome move to start this module!
Cheers
Gion

@gionkunz
Copy link
Collaborator

gionkunz commented Oct 6, 2014

@Paradox41 if we update the ng-chartist.js to 0.2.0 I'll add it to the next release of the documentation. I will include a new section on the chartist landing page that shows wrapper libraries and projects where it has been used so far.

@willsoto
Copy link
Contributor Author

willsoto commented Oct 6, 2014

That sounds easy enough 😄

@willsoto
Copy link
Contributor Author

@gionkunz I've done some work on this already, but I wanted to know if you had any plans for other events or a way to programmatically access available events.

At the moment, my code will accept whatever event and handler get passed and obviously only ones that are emitted will get called. Which might lead to some confusing behavior (maybe?). Then again, my directive is intended to be a dumb wrapper, I don't really want to have too much knowledge about what the underlying library is doing.

Thoughts?

@gionkunz
Copy link
Collaborator

Finally got to this 🎉 Although the library evolved a lot now and we need to update the angular directive :-) There is now also a asterisks subscription for the event emitter that allows you to subscribe for all events and also there are animations with SMIL.

@willsoto
Copy link
Contributor Author

Cool. When I get a chance I'll read through the docs and see what needs to change.

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

No branches or pull requests

2 participants