Public stable releases will be made available on the site and also exist in
Any push made to
master branch will have its unit tests passing, although maybe not
in all browsing environments (IE, etc) to ensure that it is stable, at least to a certain degree.
I will also include a minified version that will also have its unit tests run against it here:
Sugar now has a build available that has all methods on the
Date class as a
standalone module. The minified version can be found in
release/dates. Note that this build
still adds a number of methods to the
Array classes that Sugar requires
internally, including all the ES5 polyfill methods that are heavily used. This build will not follow
the standard release schedule, but will be updated when the Sugar Date module changes significantly.
Unit tests can be run through the shell script at
Sugar includes 11 localizations in the main package:
- English (en)
- French (fr)
- German (de)
- Spanish (es)
- Italian (it)
- Russian (ru)
- Korean (ko)
- Portuguese (pt)
- Japanese (ja)
- Simplified Chinese (zh-CN)
- Traditional Chinese (zh-TW)
In addition to these major locales, custom locales can be added using:
More documentation to come soon, but for now refer to
lib/locales for examples of what kind of data and formats are required in localization objects. All localizations, including those not found in the main package will be kept here.
If you do add a custom format for your locale, please consider forking and adding it to the repo! This especially includes the addition of new locales, but also new formats or tweaks to existing locales. Not everything can be added to the main package, but I would like to have as many languages/formats as possible available. When adding a locale contribution, the most important thing is to add unit tests that assert the correct format. These unit tests are found at
unit_tests/environments/sugar/date_LOCALE.js. Simply add or adjust the formats for the locale (the more tests, the better!) and issue me a pull request -- I will update the code to add these locales/formats. Have a look at other unit tests files for an example of the unit testing format.
Lib comparisons to various other libraries can be seen at http://sugarjs.com/libs. This is one of the areas where contributions are most welcome, as I don't have extensive knowledge of many different libraries, and there is so much to cover. To contribute simply find or create the appropriate lib name in
docs/libs, and follow the format provided. This will be an ongoing process, and I will push changes here out to the site every so often.
For other contributions, please add well formed unit tests in the sugar environment at
unit_tests/environments/sugar/MODULE.js. Unit tests can be run directly in the browser from
unit_tests/sugar.html, and should all be passing in all major browsers (Webkit,Mozilla,Opera, and IE6+). Node.js unit tests should also be passing and can be run in the console with
unit_tests/node.sh. Also of note is
unit_tests/prototype.html, however depending on various circumstances not all tests may be passing, so it's good to do a before/after. Mootools can be ignored for the time being.