capri

Capri Library :: Clasic object oriented JavaScript

npm install capri
1 downloads in the last month

© 2010-2012 Rotorz Limited. All rights reserved.
Rotorz Limited ( http://rotorz.com )

The Capri project (and all derivatives) are licensed under the terms of the BSD license or the GNU General Public License (GPL) Version 2.

The BSD license is recommended for most projects because it imposes fewer restrictions than the GPL license. You are free to select which license to use. Please ensure that any copyright information is retained in source files (even when in minified form).

Please refer to the relevant license text:

BSD-LICENSE.txt
https://github.com/rotorz/capri/blob/master/BSD-LICENSE.txt
GPL-LICENSE.txt
https://github.com/rotorz/capri/blob/master/GPL-LICENSE.txt

Overview

The fundamental purpose of Capri is to provide the ability to define and extend classes and namespaces in a way that is clean and easy to understand. The secondary purpose of Capri is to provide a reusable toolset that caters to common needs.

Capri can be used as a module for node.js applications or selected features can be built and minified for use in web applications. Capri also provides its own flavour of modules which can be used if desired. The intention of Capri-style modules is to allow developers to write modules that can be consumed by both server and client applications with minimal (if any) change.

It is useful to note that a cleaner syntax can be used when developing modules for ECMAScript 5 compliant platforms (like node.js or modern web browsers). Special property names must otherwise be placed within quotes for compatibility with all major browsers.

The project is largely experimental, it would be interesting to see if fellow developers find this of use!

IMPORTANT, CURRENT DOCUMENTATION IS INVALID FOR THIS RELEASE!

How to Contribute?

We have chosen to host our project using GitHub. Please read the contribution agreement before making any contributions. All bug reports and suggestions should be contributed by creating a new issue.

Please follow these steps if you would like to submit a bug fix or feature:

  1. Create new issue to discuss your ideas (optional)
  2. Fork the Capri repository.
  3. Take a look at how we format our code and read our formatting guide.
  4. Hack away!
  5. Create test cases to ensure that contributed source code works properly and is of a high standard.
  6. Create a pull request.

Contribution Agreement

Capri is licensed under the BSD and GPL licenses (find out more). To be in the best position to enforce these licenses the copyright status of Capri needs to be as simple as possible. To achieve this the following terms and conditions must be met:

  • All contributed content (including but not limited to source code, text, image, videos, bug reports, suggestions, ideas, etc.) must be the contributors own work.
  • The contributor disclaims all copyright and accepts that their contributed content will be released to the public domain.
  • The act of submitting a contribution indicates that the contributor agrees with this agreement. This includes (but is not limited to) pull requests, issues, tickets, e-mails, newsgroups, blogs, forums, etc.

Disclaimer

Linked content in the above text are for convienence purposes only and do not contribute to the agreement in any way. Linked content should be digested under the readers discretion.

npm loves you