This module extends the basic Image LazyLoader functionality (see Image Lazyloader).
Project page URI: https://drupal.org/sandbox/basvanderheijden/2030603
Git clone URI: git clone --branch master basvanderheijden@git.drupal.org:sandbox/basvanderheijden/2030603.git paas_lazycolor
Instead of presenting the user with a throbber on a white background, the average color of the image will be used as a placeholder.
So if you're image is predominantly red colored, you will see a red rectangle while the image is loaded. The red rectangle will be replaced by the original image source once the image has been downloaded (or is positioned within the browsers viewport).
FYI: Inspiration to create this extension module, stems from Pinterest (see Pinterest amazing attention to detail and why design should lead code) which uses the same technique for preloading images.
Because calculating the average colors for each image is quite a heavy task on the backend, and the main purpose of lazy loading is to decrease load on the server, the average colors will be only be generated once, and cached in a seperate cache bin. It will also be cached statically for multiple requests to the same image within a single page request.
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://ventral.org/pareview/httpgitdrupalorgsandboxbasvanderheijden20306...
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2
bertboerland commentedREADME.txt is missing
Comment #3
cravecode commentedWhat an interesting idea for a module! Other than the automated testing results, this module looks pretty good. Congrats and good luck!
My suggestions:
Comment #4
bertboerland commented@cravecode, thanks! yes, the effect on pinterest is almost to fast to be seen, but subconscious one "feels" the color :-)
Comment #5
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #6
bertboerland commentedstill would love to see this as a module instead of a sandbox. so please, what else do we need to do?
Comment #7
klausiLooks like this needs review? See https://drupal.org/node/532400
Comment #8
kscheirer$Id$strings at the top of files.Otherwise seems pretty short and sweet, nice work.
----
Top Shelf Modules - Crafted, Curated, Contributed.
Comment #9
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #10
basvanderheijden commentedIssues fixed (branch, readme files etc).
Comment #11
basvanderheijden commentedComment #12
PA robot commentedProject 1: https://drupal.org/node/2235863
Project 2: https://drupal.org/node/2030715
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 secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
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.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #13
avpaderno