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

JSend 2.0 plans #2

Open
boye opened this issue Apr 4, 2014 · 2 comments
Open

JSend 2.0 plans #2

boye opened this issue Apr 4, 2014 · 2 comments
Assignees
@boye
Labels
enhancement
Milestone
JSend 2.0

Comments

@boye
Copy link
Contributor

boye commented Apr 4, 2014

We are considering a complete rewrite of JSend (2.0) and have the following plans in mind:

  • Modular structure, with the option to only include the features that one needs
  • Remove jQuery dependency
  • Support for Promises (with optionally a polyfill for browsers that doesn't offer support). Which polyfill this will be, isn't decided yet. Perhaps NPO?
  • AMD / CommonJS support
  • No more high-level aliases, just one consistent function call
  • IE7+ support (so no more ActiveXObject crap)
  • NPM / Bower support
@boye boye self-assigned this Apr 4, 2014
@humbroll
Copy link

humbroll commented Apr 7, 2014

Cool. +1

@boye boye added this to the JSend 2.0 milestone Aug 13, 2014
@iainvdw
Copy link
Contributor

iainvdw commented Jan 16, 2015

Plus, added support for JSONP, which is currently not available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@boye boye

Labels
enhancement
Projects
None yet
Milestone
JSend 2.0
Development

No branches or pull requests
3 participants
@boye @humbroll @iainvdw