Bram.us » Projects http://www.bram.us A rather geeky/technical weblog by Bram(us) Van Damme Sat, 04 Feb 2012 11:59:08 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Introducing Yummy! — A self hosted Delicious http://www.bram.us/2010/12/21/introducing-yummy-a-self-hosted-delicious/ http://www.bram.us/2010/12/21/introducing-yummy-a-self-hosted-delicious/#comments Tue, 21 Dec 2010 14:19:33 +0000 Bramus! http://www.bram.us/?p=2777 Continue reading →]]> After having quickly written DeliciousBackup I couldn’t resist myself into adding a wee bit more functionality to it. The result is a project called Yummy!. It’s goal: to become a self hosted Delicious.

New and improved

One of the new features in Yummy! which immediately stands out is that it’s been styled in a true Delicious-style, making it more attractive. Other visible features include the pagination and tags list.

With this version, private links are also hidden unless one is logged in. What’s also possible is something called tag plussing: you can filter out links having multiple tags (click on a related tag from the related tags list and you’re there).

In the back, most of the queries have been rewritten to support the mentioned tag plussing. Along with that I’ve also wiped out that one ugly (and slow) subquery which sported DeliciousBackup :)

Finally, Yummy! also sports nice urls and comes with a simple installer.

Plonk

Codewise, Yummy! is now OO driven and based upon a little PHP library called Plonk, which I developed to use in the PHP courses I’m teaching. Plonk itself partially inspired upon Spoon Library, which is the library of my choice (Since Yummy! isn’t that big I found Plonk to be more than sufficient).

I’m quite sure you’ll find some suggestions for Plonk, feel free to send them over. Please do note that I’ve deliberately kept some stuff in Plonk low-tech to not discourage my students when learning it — Spoon’s Template class for example is a few 100 times more powerful than Plonk’s ;)

Download and installing Yummy!

Yummy’s source code can be found over at GitHub. Installation instructions are provided in the attached readme.md file.

▼ Download Yummy! from GitHub

The Future, Feature Requests & Bugs

For now, Yummy! only lets you browse your imported links. Planned features of course are the ability add and edit links. Providing an RSS feed is also on the menu. If you’ve got some features or have found a bug, feel free to suggest/mention them via Yummy’s issues page on GitHub, or Fork off and do a pull request after you’ve implemented/fixed it ;-)

]]> http://www.bram.us/2010/12/21/introducing-yummy-a-self-hosted-delicious/feed/ 12 Introducing Gowalla Missing Items Location Finder (Gowalla MILF) http://www.bram.us/2010/08/12/introducing-gowalla-missing-items-location-finder-gowalla-milf/ http://www.bram.us/2010/08/12/introducing-gowalla-missing-items-location-finder-gowalla-milf/#comments Thu, 12 Aug 2010 15:51:46 +0000 Bramus! http://www.bram.us/?p=2536 Continue reading →]]> Today I released a tool named Gowalla Missing Items Location Finder (Gowalla MILF for short) which lets you locate Gowalla spots near you which contain items which are missing from your vault.

Gowalla Missing Items Location Finder — Welcome Screen
Gowalla Missing Items Location Finder — Welcome Screen

Development

The project was built in an afternoon, excluding the time fiddling with the (basic) Gowalla API and excluding the styling. Under the hood of Gowalla MILF one can find PHP, Spoon Library, Google-Geocoding-Class along with some extra custom classes such as one which communicates with the Gowalla API. Other technologies used are Google Maps (V2) and jQuery.

Gowalla Missing Items Location Finder — The Results
Gowalla Missing Items Location Finder — The Results

A vast amount of time was spent on minimizing the load on both my server and the Gowalla (API) server:

  • Templates are pre-compiled, which is done by Spoon itself.
  • All calls made to the API are cached into a database for two hours. This to prevent hitting a rate limit (is there any?)
  • The coordinates used for fetching of the locations/items near a lat-lng pair are rounded to three digits, resulting in the same API calls for two sets of coordinates which are very close to eachother (and resulting in more cache hits).
  • The transparent images used – which are fetched from Gowalla and then processed by PHP – are cached on disk, taking some load off my server when the same image is requested over and over.

For now the tool does not use Gowalla’s OAuth capabilities as I wanted to keep it simple to implement. However, OAuth might make into it as it would no long require one to have Gowalla Passport Security set to off whilst fechting his/her user info. Gowalla MILF now sports OAuth, read the announcement here.

Design

The design — if you can call that a design — is pretty straight forward and is built around the main map which one can see. Below are some extra screenshots of some special scenarios that might appear (no location, no items, no interesting spots or no spots at all)

Gowalla Missing Items Location Finder — No location (hometown not set)
Gowalla Missing Items Location Finder — No location (hometown not set)

Gowalla Missing Items Location Finder — Passport Privacy (No items)
Gowalla Missing Items Location Finder — Passport Privacy (No items)

Gowalla Missing Items Location Finder — No loot (no interesting spots around here)
Gowalla Missing Items Location Finder — No loot (no interesting spots around here)

Gowalla Missing Items Location Finder — No dice (no spots around here)
Gowalla Missing Items Location Finder — No dice (no spots around here)

The used icons in the sidebar were all found via iconfinder.net

Happy item hunting! Now, go check out Gowalla Missing Items Location Finder!

]]> http://www.bram.us/2010/08/12/introducing-gowalla-missing-items-location-finder-gowalla-milf/feed/ 6 Accessing data saved in the class property of DOM-elements with jQuery http://www.bram.us/2009/02/09/accessing-data-saved-in-the-class-property-of-dom-elements-with-jquery/ http://www.bram.us/2009/02/09/accessing-data-saved-in-the-class-property-of-dom-elements-with-jquery/#comments Mon, 09 Feb 2009 20:01:56 +0000 Bramus! http://www.bram.us/?p=1914 Continue reading →]]> A few weeks ago former colleague Jurriaan wrote a PrototypeJS extension to accessing data stored within classes of HTML elements. Basically it comes down to assigning extra classes (classes such as gender_male for example, which represent a property and a value) on an element, which you then read/write via Jurriaan’s extension. As this way of assigning data is a technique I’ve been using too, I took the liberty of writing a jQuery blend of his script.

Ow ow, what is this all about?

I suggest you read Jurriaan’s excellent post on the subject if you’re not acquainted with the subject. It situates the problem and explains the necessity of this plugin.

Cool, any demo?

Elementary my dear Watson, elementary:

Gimme gimme gimme (Download)!

Find the source on GitHub (click on the Download button)

Okay I downloaded it: How to I use this thing / Any differences between yours and Jurriaan’s version?

Usage is simple: include the script after you’ve included jQuery. From then on you can use the classData() function on a jQuery Object:

// Set data - this will set the class 'extradata_yes' on the elements that match the selector (note that the plugin does not break chaining)
$('.mySelector').classData('extradata','yes').css('backgroundColor','lime');
// Get data - alerts the extradata value of the elements that match the selector
alert($('.mySelector').classData('extradata'));

Please note that the setting of data does not break jQuery’s chaining.

As you might have noticed the getter and setter functions are non-existent: there’s one function to handle both the mutation and accessing of the data (this differs from Jurriaan’s approach: he has two functions)

Now, you might have noticed that there’s no way to set the glue (which defaults to an underscore) used in the call itself. Therefor an extra function comes in handy: classDataGlue(). Via that function you can set glue before getting and/or setting data.

// Set data with custom glue - this will set the class 'extradata-yes' on the elements that match the selector (note that the plugin does not break chaining)
$('.mySelector').classDataGlue('-').classData('extradata','yes').css('backgroundColor','lime');
// Alert current glue (note that we need to have a jQuery object for this)
alert($('').classDataGlue());
// Get data (note that the glue is still known to the plugin) - alerts the extradata value of the elements that match the selector
alert($('.mySelector').classData('extradata'));
// Get data that uses % as glue:
alert($('.mySelector').classDataGlue('%').classData('otherdata'));

Again note that the setting of the classDataGlue does not break jQuery’s chaining. Also note that when you set the glue, the calls that happen after it will still use that glue (viz: once the glue is set, it keeps using that glue. Make an extra call to classDataGlue() to set it to an other value).

You may always leave a comment below and/or – it certainly is no obligation but it would most certainly put a smile on my face – make a donation.


]]> http://www.bram.us/2009/02/09/accessing-data-saved-in-the-class-property-of-dom-elements-with-jquery/feed/ 9 PS_BRAMUS.TextConvert: PSD2TXT and TXT2PSD for the masses! http://www.bram.us/2008/10/30/ps_bramustextconvert-psd2txt-and-txt2psd-for-the-masses/ http://www.bram.us/2008/10/30/ps_bramustextconvert-psd2txt-and-txt2psd-for-the-masses/#comments Thu, 30 Oct 2008 17:40:47 +0000 Bramus! http://www.bram.us/?p=1821 Continue reading →]]> JSXWhat if you could extract all text strings from a PSD file into a TXT file? Sure, it’s possible, thanks to PS_BRAMUS.TextExport, the PSD2TXT script I wrote a few months ago. Now, what if you wanted to do that in the opposite direction and import strings from a TXT file into a PSD file (viz. TXT2PSD)? Look no further, PS_BRAMUS.TextConvert is here, and does both!

What is PS_BRAMUS.TextConvert

Don’t like reading? Member of the lazyweb? Savvy enough? You might as well just skip to the example then ;)

PS_BRAMUS.TextConvert is the successor of PS_BRAMUS.TextExport and consists out of two scripts:

  1. PS_BRAMUS.TextConvert.Export (PSD2TXT)
  2. PS_BRAMUS.TextConvert.Import (TXT2PSD)

The first script is a modded version of PS_BRAMUS.TextExport which scans your PSD file for text strings. After retrieving all text, the output is saved into a TXT file in your Documents folder.

The second script is the counterpart: it reads in TXT files (which you first exported via the first script) and replaces all text layers with the new content in your PSD file.

Is PS_BRAMUS.TextConvert something for me?

PS_BRAMUS.TextConvert is ideal for agencies/companies who need to translate Photoshop mockups: Export all text layers via PS_BRAMUS.TextConvert.Export to a text file, send that text file to the translation agency and let them do the translation, then import the translated file via PS_BRAMUS.TextConvert.Import into the PSD file.

PS_BRAMUS.TextConvert

Of course its usage is not limited to the example above. The Export part of PS_BRAMUS.TextConvert can be used for (speed)slicing for example

Requirements

  • Photoshop CS2 or newer is required
  • PS_BRAMUS.TextConvert has been tested and verified working with Photoshop CS2 and CS3 (CS4 untested but should work. Can anyone verify?)

Download / License

PS_BRAMUS.TextConvert released under a creative commons Attribution-ShareAlike 2.5 license. Should you use the script within a commercial context, or for any other reason you fancy, please consider clicking the PayPal donate button.

▼ Download PS_BRAMUS.TextConvert 1.0

Note: PS_BRAMUS.TextConvert was made possible by means of lexia:park, Barcelona, Spain.

Installation

  • Download PS_BRAMUS.TextConvert from the link above
  • Extract it to the Presets/Scripts folder of your Photoshop installation folder (defaults to C:\Program Files\Adobe\Adobe Photoshop CS3\Presets\Scripts on Windows)
  • Restart Photoshop if it was already running (important!)

How to use PS_BRAMUS.TextConvert

Once installed, usage is simple:

1. Exporting text (PSD2TXT)

PS_BRAMUS.TextConvert.Export

  • In Photoshop go to File > Scripts and select PS_BRAMUS.TextConvert.Export-1.0 from the list to export all text.
  • Per open PSD file, a TextConvert-[NAME_OF_YOUR_PSD_FILE].txt file will appear in your Documents folder
    (if multiple files are open, you can choose to only run PS_BRAMUS.TextConvert.Export on the currently active file or on all files)
  • After the export was done, you’ll get a little notification of this
    (if PS_BRAMUS.TextConvert.Export ran with a single file, the .txt file will open instead)

2. Reworking text

  • Locate the exported .txt file in your Documents folder and open it with your favorite text editor
  • Translate the strings you find in there, but make sure that you leave the [BEGIN /XXXX ] and [END /XXXX ] lines untouched! (If changed importing will fail)
  • Save the text file with the same name in the same location.

3. Importing text (TXT2PSD)

PS_BRAMUS.TextConvert.Import

  • In Photoshop go to File > Scripts and select PS_BRAMUS.TextConvert.Import-1.0 from the list to import all text.
  • Per open PSD file, the script will look if the TextConvert-[NAME_OF_YOUR_PSD_FILE].txt file exists in your Documents folder, read it in (if it exists) and update the text layers of your PSD file
    (if multiple files are open, you can choose to only run PS_BRAMUS.TextConvert.Import on the currently active file or on all files)
  • After the import was done, you’ll get a little notification of the number of files updated
    (if no txt files were found, then it will state that 0 files where changed)

Warning!

  • Please note that PS_BRAMUS.TextConvert.Import is not compatible with any version PS_BRAMUS.TextExport!
  • Please note that in between the running of the Export and Import NO CHANGES TO THE PSD FILE can be done!

Example

Given the fact that the image pictured on the left is a normal Photoshop file (viz. background layer, image elements on different layers, text layers, layer groups, etc) I’m quite sure the figure below explains it all:

PS_BRAMUS.TextConvert.Example

Now, did you download PS_BRAMUS.TextConvert already?

It certainly is no obligation but it would most certainly put a smile on my face ;)


]]> http://www.bram.us/2008/10/30/ps_bramustextconvert-psd2txt-and-txt2psd-for-the-masses/feed/ 12 flashLightBoxInjector 1.2 and Lightbox 2.0.4 http://www.bram.us/2008/04/15/flashlightboxinjector-12-and-lightbox-204/ http://www.bram.us/2008/04/15/flashlightboxinjector-12-and-lightbox-204/#comments Tue, 15 Apr 2008 19:51:57 +0000 Bramus! http://www.bram.us/2008/04/15/flashlightboxinjector-12-and-lightbox-204/ Continue reading →]]> bridgedGap2It has been brought to my attention that the release of Lightbox 2.0.4 broke some stuff in flashLightBoxInjector 1.2. After investigating the issue, it turns out that one (1) tiny change to the lightbox.js file is needed in order to get flashLightBoxInjector working with Lightbox 2.0.4.

In Lightbox 2.0.4 Lokesh (the author of Lightbox) decided to create the Lightbox instance without storing it into a variable. As flashLightBoxInjector relies on that variable, things broke. Now, to fix this follow this tiny procedure and it’ll work just fine, as it did with version 2.0.3:

  1. Open lightbox.js with your favorite texteditor
  2. Scroll down to the very last line where it reads 
    document.observe('dom:loaded', function () { new Lightbox(); });
  3. Replace that line with this 
    document.observe('dom:loaded', function () { myLightbox = new Lightbox(); });
  4. Save your file and … that’s it :)

I’ve changed the online example and flashLightBoxInjector 1.2 download and demos here on bram.us to include that change, so you can roll with it “out of the box”. Above that I’ve mailed Lokesh about this issue, hoping to see the variable reappear in a next release.

]]> http://www.bram.us/2008/04/15/flashlightboxinjector-12-and-lightbox-204/feed/ 3 PS_BRAMUS.TextExport 1.3 – Automatically export all Text layers from Photoshop PSD to a Text file (PSD2TXT) http://www.bram.us/2008/03/16/ps_bramustextexport-13-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/ http://www.bram.us/2008/03/16/ps_bramustextexport-13-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/#comments Sun, 16 Mar 2008 13:07:50 +0000 Bramus! http://www.bram.us/2008/03/16/ps_bramustextexport-13-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/ Continue reading →]]> JSXColleague Johan asked whether someone could knock up a script which exports all text layers from a Photoshop document to a text file (viz. a PSD2TXT tool/script), enabling one to slice even faster than he already can. Last week I released the first version of the script (v 1.2), now it’s time for an update.

What has changed?

  • UPD: Base rewrite, now gets all layers (sets & regular ones) in one variable.
  • UPD: Gives a nice warning, instead of a javascript error, when no file is open.
  • ADD: Layer Path & Layer Name in export.
  • ADD: Cycle Multiple Files when more than one file is open (user can still choose to only parse the current document though).

Download PS_BRAMUS.TextExport (PSD2TXT)

Update November 2008:
PS_BRAMUS.TextExport is outdated and has been replaced with PS_BRAMUS.TextConvert which does both import and export!

▼ Download PS_BRAMUS.TextExport 1.3

Installation / How to use

  • Download PS_BRAMUS.TextExport from the link above
  • Extract it to Presets/Scripts folder of your Photoshop installation folder (defaults to C:\Program Files\Adobe\Adobe Photoshop CS3\Presets\Scripts on Windows)
  • Restart Photoshop if it was already running
  • Open the PSD you wish to export text from
  • Now, when having a file opened, go to File > Scripts and select PS_BRAMUS.TextExport.1.3 from the list. textexport-small.jpg
  • Wait until the output file appears :)

Configuration

Three settings in PS_BRAMUS.TextExport can be configured, all to be found in the .jsx file itself.

  • Open up PS_Bramus.TextExport-1.3.jsx with your favorite texteditor
  • If you want to choose where to save the file to, set useDialog to true. If set to false (default), the output file will be saved into your documents folder
  • If you don’t want the exported file to be openend after the export has run, set openFile to false. If set to true (default), the output file will automatically be opened by your default text editor.
  • In the export file, each line is separated by a separator string. Change this one to use one you like (defaults to *************************************).

When running PS_BRAMUS.TextExport on multiple files, the useDialog & openFile parameters will be overriden. All files will be saved as nameofyourpsdfile.txt in your documents folder and only a notice that the files were saved will be shown.

Example

I’ve tested PS_BRAMUS.TextExport with a pretty complex PSD, which holds the design of 3RDS. Here are the results:

Input PSD

TextExport Input

Output TXT

TextExport Output

Make a donation

It certainly is no obligation but it would most certainly put a smile on my face ;)


]]> http://www.bram.us/2008/03/16/ps_bramustextexport-13-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/feed/ 30 PS_BRAMUS.TextExport 1.2 – Automatically export all Text layers from Photoshop PSD to a Text file http://www.bram.us/2008/03/12/ps_bramustextexport-12-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/ http://www.bram.us/2008/03/12/ps_bramustextexport-12-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/#comments Tue, 11 Mar 2008 23:12:50 +0000 Bramus! http://www.bram.us/2008/03/12/ps_bramustextexport-12-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/ Continue reading →]]> JSXColleague Johan asked whether someone could knock up a script which exports all text layers from a Photoshop document to a text file. Since I’ve scripted Photoshop before (heck, I even steered Photoshop from within C#) it was no biggie for me to knock up a simple script, which I dubbed TextExport

After Johan placed his request, I quickly knocked up a script which loops all layers (1.0), then (pretty important) expanded it to loop groups of layers too (1.1) and finally added some user friendly stuff like giving one the option to choose where to save the file holding all text elements (1.2).

Download

Update November 2008:
PS_BRAMUS.TextExport is outdated and has been replaced with PS_BRAMUS.TextConvert which does both import and export!

▼ Download PS_BRAMUS.TextExport 1.2

Installation / How to use

  • Download PS_BRAMUS.TextExport from the link above
  • Extract it to Presets/Scripts folder of your Photoshop installation folder (defaults to C:\Program Files\Adobe\Adobe Photoshop CS3\Presets\Scripts on Windows)
  • Restart Photoshop if it was already running
  • Open the PSD you wish to export text from
  • Now, when having a file opened, go to File > Scripts and select PS_BRAMUS.TextExport.1.2 from the list. textexport-small.jpg
  • Wait until the output file appears :)

Configuration

Three settings in PS_BRAMUS.TextExport can be configured, all to be found in the .jsx file itself.

  • Open up PS_Bramus.TextExport-1.2.jsx with your favorite texteditor
  • If you want to choose where to save the file to, set useDialog to true. If set to false (default), the output file will be saved into your documents folder
  • If you don’t want the exported file to be openend after the export has run, set openFile to false. If set to true (default), the output file will automatically be opened by your default text editor.
  • In the export file, each line is separated by a separator string. Change this one to use one you like (defaults to *************************************).

Example

I’ve tested PS_BRAMUS.TextExport with a pretty complex PSD, which holds the design of 3RDS. Here are the results:

Input PSD

TextExport Input

Output TXT

TextExport Output

Make a donation

It certainly is no obligation but it would most certainly put a smile on my face ;)


]]> http://www.bram.us/2008/03/12/ps_bramustextexport-12-automatically-export-all-text-layers-from-photoshop-psd-to-a-text-file/feed/ 9 JS_BRAMUS.lazierLoad 0.4 http://www.bram.us/2008/02/28/js_bramuslazierload-04/ http://www.bram.us/2008/02/28/js_bramuslazierload-04/#comments Thu, 28 Feb 2008 19:49:22 +0000 Bramus! http://www.bram.us/2008/02/28/js_bramuslazierload-04/ Continue reading →]]> JS_BRAMUS.lazierLoad, a Javascript Image Lazy Loader has been updated to version 0.4 thanks to some excellent suggestions by mo from pictor.us

What is lazierLoad?

lazierLoad is a little JavaScript wichh automatically hooks itself to the page, finds all images and only loads those appearing “above the fold” resulting in faster page loads as the images not located in the viewport, are not loaded until they appear within it (viz. when the user scrolls down).

The idea for lazierLoad was inspired upon Lazy Load (which is built for use with jQuery), yet the code differs quite a lot.

What is new in this version?

The most important (and only) change is that version 0.4 brings back the option to override the default settings from within the constructor. This behavior was available in 0.2 (but kinda undocumented), but dropped in 0.3 (in a lesser bright moment of me pondering). Upon request by mo from pictor.us, the option has been brought back.

To easily implement this, a lazierLoadAutoHook parameter got introduced. If set to true, JS_BRAMUS.lazierLoad will automagically start itself. When set to false one must manually invoke a new instantiation of JS_BRAMUS.lazierLoad.

Since version 0.3, the possible options to tweak are:

  • treshold: images which appear treshold pixels from the bottom will be loaded
    (defaults to “100”)
  • replaceImage: image to replace the non-loaded images with until they are loaded (most likely a transparent 1 by 1 pixel image)
    (defaults to “blank.gif”)
  • loadingImage: image to show while a non-loaded image is being loaded
    (defaults to “spinner.gif”)
  • extensions: array of extensions to lazyLoad
    (defaults to “['gif','jpg','png','jpg']”)
  • minWidth: minimum width an image must have in order to be lazyLoaded
    (defaults to “100”)
  • minHeight: minimum height an image must have in order to be lazyLoaded
    (defaults to “100”)

These default options can now be easily overriden from within the constructor.

Cool, is there a demo?

lazierload.gif

TIP: scroll down really really fast ;)

Where can I download it?

Right here:

http://www.bram.us/wordpress;/wp-content/uploads/2008/02/lazierload_04.zip;Download lazierLoad 0.4;

Wow, you’re going to fast: I have a question, I need help, I need more info, how do I configure this thing?

Don’t worry my friend, there’s a full page here on bram.us devoted to lazierLoad where you can find all info about it.

]]> http://www.bram.us/2008/02/28/js_bramuslazierload-04/feed/ 5 JS_BRAMUS.lazierLoad 0.3 http://www.bram.us/2008/02/27/js_bramuslazierload-03/ http://www.bram.us/2008/02/27/js_bramuslazierload-03/#comments Tue, 26 Feb 2008 23:38:34 +0000 Bramus! http://www.bram.us/2008/02/27/js_bramuslazierload-03/ Continue reading →]]> JS_BRAMUS.lazierLoad, a Javascript Image Lazy Loader has been updated to version 0.3. Changes are compatibility with the latest Prototype version (1.6.0.2), the introduction of a global options object to easily configure lazierLoad and some extra options such as minWidth, minHeight and extensions.

What is lazierLoad?

lazierLoad is a little JavaScript wichh automatically hooks itself to the page, finds all images and only loads those appearing “above the fold” resulting in faster page loads as the images not located in the viewport, are not loaded until they appear within it (viz. when the user scrolls down).

The idea for lazierLoad was inspired upon Lazy Load (which is built for use with jQuery), yet the code differs quite a lot.

What is new in this version?

The most important change is that version 0.3 introduces compatibility with Prototype 1.6 final or higher, something 0.2 was not capable of due to a rather huge change in how events are named between rc1 and the final.

Next to this compatibility issue, lazierLoad now holds a global config Object named lazyLoadOptions. This variable can easily be altered to reflect the options you want to use it with. In version 0.3 some new options were introduced: minWidth, minHeight and extensions.

In version 0.3, the possible options to tweak are:

  • treshold: images which appear treshold pixels from the bottom will be loaded
    (defaults to “100”)
  • replaceImage: image to replace the non-loaded images with until they are loaded (most likely a transparent 1 by 1 pixel image)
    (defaults to “blank.gif”)
  • loadingImage: image to show while a non-loaded image is being loaded
    (defaults to “spinner.gif”)
  • extensions: array of extensions to lazyLoad
    (defaults to “['gif','jpg','png','jpg']”)
  • minWidth: minimum width an image must have in order to be lazyLoaded
    (defaults to “100”)
  • minHeight: minimum height an image must have in order to be lazyLoaded
    (defaults to “100”)

Cool, is there a demo?

lazierload.gif

TIP: scroll down really really fast ;)

Where can I download it?

Right here:

http://www.bram.us/wordpress;/wp-content/uploads/2008/02/lazierload_03.zip;Download lazierLoad 0.3;

Wow, you’re going to fast: I have a question, I need help, I need more info, how do I configure this thing?

Don’t worry my friend, there’s a full page here on bram.us devoted to lazierLoad where you can find all info about it.

]]> http://www.bram.us/2008/02/27/js_bramuslazierload-03/feed/ 0 Commenting and Real Names http://www.bram.us/2008/02/24/commenting-and-real-names/ http://www.bram.us/2008/02/24/commenting-and-real-names/#comments Sun, 24 Feb 2008 21:43:05 +0000 Bramus! http://www.bram.us/2008/02/24/commenting-and-real-names/ iA states to Use Your Real Name When You Comment (or a name that identifies you).

]]> http://www.bram.us/2008/02/24/commenting-and-real-names/feed/ 0