You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.
first, thank you for your great work. Secondly, this might not be the right place for me to post, so please forgive me if not. I see that the people behind O.o maintain this library and I thought you might be interested.
I have been using observe-js for a few days and felt like something could be done to make O.o a little easier to use in daily life in terms of naming, atomicity and consistancy. That's why I released a jQuery plugin named Observe_evented:
While providing some help and details that could considered as superfluous (which can be disabled in options for performance though), I think it's a good way to encourage the adoption of O.o and improve the learning curve of newcomers.
As Observe_evented does not provide a shim, I am considering making another plugin to make it consume observe-js feeds in non-compatible browsers. I could have built the whole plugin on top of observe-js but there are some things I could not have done, and I did not want to make the library depend on a shim either.
Feedback on Observe_evented is of course welcome.
I also have two small remarks on the O.o spec, where should I post them ?
Thank you for your time.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
first, thank you for your great work. Secondly, this might not be the right place for me to post, so please forgive me if not. I see that the people behind O.o maintain this library and I thought you might be interested.
I have been using observe-js for a few days and felt like something could be done to make O.o a little easier to use in daily life in terms of naming, atomicity and consistancy. That's why I released a jQuery plugin named Observe_evented:
https://github.com/louisameline/observe_evented
While providing some help and details that could considered as superfluous (which can be disabled in options for performance though), I think it's a good way to encourage the adoption of O.o and improve the learning curve of newcomers.
As Observe_evented does not provide a shim, I am considering making another plugin to make it consume observe-js feeds in non-compatible browsers. I could have built the whole plugin on top of observe-js but there are some things I could not have done, and I did not want to make the library depend on a shim either.
Feedback on Observe_evented is of course welcome.
I also have two small remarks on the O.o spec, where should I post them ?
Thank you for your time.
The text was updated successfully, but these errors were encountered: