Right now, Microsoft plans to maintain WinJS’s existing features–this means responding to Issues and Pull Requests on a regular basis. We’re committed to making sure that WinJS continues to run well. At this time, we don’t have plans to invest in new features or feature requests; this also means that we’re not planning a new feature release.
- Provide developers with a distinctive set of UI controls with high polish and performance with fundamental support for touch, mouse, keyboard and accessibility
- Provide developers with a cohesive set of components and utilities to build the scaffolding and infrastructure of their applications
This is a first step for the WinJS project and there is still a lot of work that needs to be done. Feel free to participate by contributing along the way.
There are many ways to contribute to the project.
You can contribute by reviewing and sending feedback on code checkins, suggesting and trying out new features as they are implemented, submitting bugs and helping us verify fixes as they are checked in, as well as submitting code fixes or code contributions of your own.
Note that all code submissions will be rigorously reviewed and tested by the team, and only those that meet an extremely high bar for both quality and design appropriateness will be merged into the source.
Clone a copy of the master WinJS git repo:
git clone https://github.com/winjs/winjs.git
Change to the
Install the grunt command-line interface globally:
npm install -g grunt-cli
Grunt dependencies are installed separately in each cloned git repo. Install the dependencies with:
Note: You may need to use sudo (for OSX, *nix, BSD etc) or run your command shell as Administrator (for Windows) to install Grunt globally.
Refer to http://winjs.azurewebsites.net/#status for the current status of the unit tests and the list of known issues.
Check out our online playground at http://www.buildwinjs.com/playground/
The old playground is still available at http://winjs.azurewebsites.net/