documentation

Guides

Examples

Get Lazy!

Lazy is important with limited resources. How is it possible to not create the event handler you need in your application before your application component is used?

The answer is to be lazy. jquery.claypool.js provides routers to stand in between the framework and the application, so events can be registered up front, and the actual component can be created only when it's required by the actualization of a relevant event. It's like TiVo for jquery.

Plugins

Extension Points

Cool X-Ray Glasses

Using a couple simple conventions to create routers, tune logging levels, toggle development or production setting, scan for application components, your applications wiring becomes transparent to other developers.

jquery.claypool also provides a full featured, highly efficient category logging implementation so you can quickly debug very specific areas of your application in any browser or even running in Rhino. And when you turn it off you will see nearly zero impact on performance. Claypool itself is fully instrumented with category logging so you can always peer under the runtime hood.

Write Less, Do More

Lazy also mean we don't want to have to configure any more than required unless our application really, really, really needs it.

jquery.claypool provides highly railable patterns to avoid configuration, while giving your application tons of space to grow. We didnt try to think of every thing, only what 90% of you will need anyway.

Project