Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
A powerful! collection of low-level plugins for MooTools
Shell
Branch: master
Failed to load latest commit information.
class-extras @ fac6ebf Update class-extras, custom-event and tree.
custom-event @ 211b959 Update class-extras, custom-event and tree.
dynamic-matcher @ 6b1c8ca Updating all to 1.0.5 (no code changes, MooTools forge support, minor…
event-stack @ a42acac Updating all to 1.0.5 (no code changes, MooTools forge support, minor…
form-autogrow @ de5de0d Updating all to 1.0.5 (no code changes, MooTools forge support, minor…
form-placeholder @ 32ebfce Updating all to 1.0.5 (no code changes, MooTools forge support, minor…
history @ ac653be Add Router and updates to history/tree
interface @ c90cf8e Updating all to 1.0.5 (no code changes, MooTools forge support, minor…
mobile @ faa6e06 Updating mobile
mootilities @ 593dff0 Update Mootilities again :)
router @ 0260713 Add Router and updates to history/tree
scroll-loader @ 8f128fc Updating mobile, tree and scroll-loader to their latest versions.
tree @ 9c49339 Add Router and updates to history/tree
.gitmodules Add Router and updates to history/tree
README.md Add Router and updates to history/tree
build Add Router and updates to history/tree
register Update, Register, Build. It's like Veni, Vidi, Vici, but with Power.
update Update, Register, Build. It's like Veni, Vidi, Vici, but with Power.

README.md

MooTools PowerTools!

PowerTools! for MooTools brings powerful low-level Plugins to speed up the development of JavaScript-heavy web applications.

Download, Build and Demos

Download

git clone git://github.com/cpojer/PowerTools.git
cd PowerTools
./update

Included Components

Build

Build via Packager.

./register
./build <path/to/packager> > powertools.js

This builds all of PowerTools! and puts the contents into 'powertools.js'. Alternatively you can also ./register all parts of PowerTools! and then build them manually. For more information on this see the repository of each component you want to build. If your packager executable is in your PATH you do not have to specify it manually.

Update all repositories

./update <remote>

Where is the name of the git remote, defaults to 'origin'.

Credits

Thanks to @timwienk for helping me with the bash scripts.

Something went wrong with that request. Please try again.