Why? Well, a while back I tested a private server of theirs for Minecraft, and it didn’t work out so good (Lots of lag, don’t think their PS was meant for online games :p). Anyways, I asked them to cancel it, and they said they had to do it manually. Eventually it got taken offline, but I got charged for the time I used it (The email I got said I wasn’t going to). So, I forgot about it and yesterday the sites got taken down, which is no good. I paid off the what I owed them. Their a great hosting company anyways, I’m not letting ~$20 stop me from using them :p

So, that’s the story, and we should be fine until my bill comes up again (Next year) :p

Really how it works is simple. The compressor works like the asset class, sort of. An example of using the compressor is:

Fuel::add_package('compressor');

$files = array('script1.js', 'script2.js', 'scriptN.js');

// Echos <script src="http://.../scripts.pack.js" type="text/javascript"></script>
echo Compressor::js($files, 'scripts.pack');

Now, that’s a basic example of taking multiple scripts, compressing, and adding them to you assets folder. Note that it can cache to folders other than the assets folder (Set in ‘compressor/config/compressor.php’), but it will force the use of a js and css folder within the configured folder. This behavior is because the package was designed as a simple way of auto-magically compressing your scripts while you work on them locally, then not have to worry about it in the production environment.

It will return the code if the 2nd param is null:

$myscript = "Script goes here";
$myjs = Compressor::js($myscript);
echo $myjs; // Echos the compressed js

$myscripts = array('scripts.js');
$myjs = Compressor::js($myscripts);
echo $myjs; // Echos the compressed js files

That about covers the basic use. There is a HTML compressor, but it’s just a basic call to the html-compressor lib. Also, the documentation in the actually classes folder should cover anything not said here.

• Uses one flash element being repositioned around the page. Decreases load times and stress when multiple elements are copyable.
• Added the choice to choose which size method to use (Outer, inner, standard .width()/.height())
• Removed a couple of dependencies, and removed the resize event. This was due to the fact that if you resize an inactive
  element, it updates next time it is hovered over. Also if needed, the update can be called manually, which is a lot more
  resource friendly :p
• Added the events ‘mouseleave’, ‘mouseenter’, and ‘complete’ (Which is fired after a successful copy)
• Just about rewrote the thing, lots of code changes.

And a video of the script in action after the jump.

jQuery ZeroClipboard plugin from Kris K on Vimeo.

I’ll be updating this blog more often, hopefully!

Basic usage of the script goes along the lines of

$('selector').zeroclipboard({text: 'This is the text to copy!'});

Thats it! You use the same method to update text and any other options, or to destroy the flash object. Also, when the .remove() is called on element the clipboard is bound to, it removes the zeroclipboard automagically. Also, any mouse events on the element select are emulated when they are preformed on the flash object.

Read the entry on github for more information, but I am trying to make clipboards as easy and painless as possible. The only problem is the use of external libraries, which I would like to minimize, but right now they work good with the script.

Visit it over at Gfxtub.com

[dGallery]

• Add a tooltip, or comment, to any DOM object or just using coords
• Add it to one or multiple objects
• Have it removed after a certain amount of time, or when an event happens to the parent of the comment
• Choose how to position them

Tested Browsers: IE6+, Firefox 1.5+, Safari 4, and Google Chrome 1.0 (All on Windows).

For a full explaination, just go over to the [jQuery Tooltips Site]