delusionworld blog

As I promised here is the script to use your MooTools Plugin Repository even more sufficient. It’s all about easy handling. I want to use all the Plugin I have without including a lot of script, css tags in my header. With this php code it’s really easy to do it.

First pls see the Screencast MPR Preparation Part 2.

Here you can see how I like to work – never write to much code. So by using autoload and the php file you don’t need to care about any javascript or css. Once you are done with your work – you can easily just save the content you get from the php script and upload it, so you don’t need to autocreate this on your server – just upload ONE javascript file and ONE css file and you it will contain all your plugins relevant code (except for the images :p).

My next plans:

• create a demo page where you can just write js/html/css code and don’t need to worry about file inclusion (a little playground)
• include a cache for the php script
• include a lot more plugins
• some other improvements for the script (find base tag, auto identify if the script is also used for css, …)

If you wanna try the things you have seen in the Screencast just download MPR.Preparation.Part2 extract it to a webserver (with php and curl) and look at the MPR.html.

daKmoR MooTools Plugin, Repository, Screencast

Some Time ago I had an idea on how to make using MooTools evan easier. Basically it’s about using a “convention” for Plugins (directory structur) and intraducing an function to autoload Code that’s mandatory.

This is about developing locally and not using it on the public server. For general use I will provide a Script that automatically generates ONE MooTools File to be included within you page.

To see how a local MooTools Plugin Repository could help you while developing you can see a short screencast.

For more Information you can see the original Post on MooForum.

daKmoR MooTools Plugin, Repository, Screencast