- Integrate jQuery lazy load with Drupal image field
- Fast and dynamic identifier for image selector
- Custom lazy load event and effect

Primary differs from http://drupal.org/project/lazy_image_loader:
image_lazy creates custom image formatter to produces this correspondent html img tag:

<img class="lazy" src="img/grey.gif" data-original="img/example.jpg"  width="640" heigh="480">
<noscript><img src="img/example.jpg" width="640" heigh="480"></noscript>

So user choose image field display type: "Image lazy load", image_lazy takes care the rest.
This provides consistency in the system, while you still have the ability to select custom lazy load effect and event for specific collection of images.

In contrary with "lazy_image_loader", you manually create custom html img tag, then invoke the effect by javascript. One group of settings applies sitewide.

Project page: http://drupal.org/sandbox/dk129/1498508
Git: git.drupal.org:sandbox/dk129/1498508.git
Version: Drupal 7

Comments

patrickd’s picture

Status: Needs review » Postponed (maintainer needs more info)

Welcome!

Can you explain how your module differs from Lazy Image Loader module?

If the differences aren't that big and your module is actually duplicating/improving the goals of lazy image loader module, I'd love to see you both joining forces and making the existing module awesome :)

regards

patrickd’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)

Also, it appears that there have been multiple project applications opened under your username:

Webform userkey: https://drupal.org/node/1367796

As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your newer application (this one) has been marked as 'closed(duplicate)', so only one application is left open.

If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.

dk129’s picture

Hi,

Actually, I've closed Webform userkey, (https://drupal.org/node/1367796).
I have changed Webform userkey maintenance status: Unsupported and development status: Obsolete
That module is not granted yet, so I think I need to reapply this project, right?

Khoa

dk129’s picture

Hi,

Well this is total different from https://drupal.org/project/lazy_image_loader
for lazy_image_loader, you have to embed your custom html image tag (eg: node body) to make lazy loader works, and there's only one single effect and event applied sitewide.

Meanwhile, my module do more from underlying field architecture, provide better consistency approach, works with some other contributed modules (eg: views). and people could have as many group of effects and events as they want.

regards

patrickd’s picture

Status: Closed (duplicate) » Needs review

Okay then let's reopen this one.

dk129’s picture

Cheers :)

luxpaparazzi’s picture

Status: Needs review » Needs work

You should remove " from .info file:

name = "Image lazy"
description = "Image lazy load"
core = "7.x"

=>

name = Image lazy
description = Image lazy load
core = 7.x
/**
 * @file
 * module file
 */

Doc-comments should be more explicit.

It's best practice to put Javascript into .js files:

  $script = <<<EOT
(function($){
  Drupal.behaviors.image_lazy = {
    attach: function(context, settings) {
      var image_lazy = settings.image_lazy || {};
      $.each(image_lazy, function(index, config){
        $("." + index, context).show().lazyload({
          event : config.lazy_event || "scroll",
          effect : config.lazy_effect || "show"
        });
      });
    }
  }
})(jQuery);
Code too short
This project is too short to approve you as git vetted user. We are currently discussing how much code we need, but everything with less than 120 lines of code or less than 5 functions cannot be seriously reviewed. However, we can promote this single project manually to a full project.
luxpaparazzi’s picture

The response time for a review is now approaching 4 weeks.
Get a review bonus and we will come back to your application sooner.
See: http://drupal.org/node/1410826

You could for example start by evaluating my own project:
http://drupal.org/node/1302786

klausi’s picture

Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application.

klausi’s picture

Issue summary: View changes

Update project and git links

avpaderno’s picture

Title: Image lazy » [D7] Image lazy
Issue summary: View changes