Function: Converts .png images to .jpg without renaming them — intended for iWeb.
Author: Ka
Notes: iWeb Optimizer is a workflow. Drag & Drop the folder published by iWeb on iWeb Optimizer Workflow. It will convert the .png images contained in the folder dropped on it into .jpg images but without renaming them (’image.png’ stays ‘image.png’ but is now a jpg image). It does the same with each subfolder found. The beauty is that the links are untouched and the website gets lighter very rapidly.
Notes:
-iWeb Optimizor does not make a backup copy of you png images.
-jpg does not deal with transparency.
Could be possible to have the option to filter by dimension (KB) the pngs to be converted in jpgs. It would leave alle the graphics of the theme untouched and would reduce the size only of the big pictures thanks!!
Comment by riccardo — September 11, 2008 @ 11:12 am
I think iweb optimizer works only with big images but not with small ones. I tried to convert my whole site and it was done from 5,5 MB to 8,9 MB. So, I’m manually applying iweb optimizer on my big images and it is quite a laborious task to do.
Comment by damoulianos — June 6, 2007 @ 3:57 am
I wrote a simple automator action for iWeb that will accept images or movie files as input, and create a blog entry for each file.
The unique feature about this action is that it will optionally keep a count of entries based on the title. So using this feature you could blog a couple of family photos, with entry names like ‘family photo 1′, ‘family photo 2′. Then blog some work photos with entry names like ‘work pic 1′, ‘work pic 2′. Then you could add some more family pics with names like ‘family photo 3′, ‘family photo 4′. The automator plugin will remember the counts for you!
You can get the action at iWeb Blogger Action
Comment by Rhett Maxwel — July 1, 2006 @ 1:24 pm
Hi,
I am the (evil) builder of iweb optimiz(e|o)r workflow
This workflow has not been really appreciated by most people and I understand :
Because of iweb optimiz(e|o)r workflow, sometimes (depends on the images) the website is heavyer than before and transparency is lost !
I am sorry if people have lost time with that tool, but let’s look forward now :
First point : I think iWeb Optimizor can be useful if the site is prepared for it. The images must be prepared to loose their transparency. For transparent images, i suggest to make a screen copy around them and to past this screen copy at the exact position where the transparent image were. That way the background will be included within the new image and no more need for transparency (if somebody understand, please translate into correct english.)
Second point : in my original submission to the present website, the description was a bit more complete than the one you can see above :
you will find below an extract of the original submission (no offense, just some more details) :
=========================================================
wish list :
iWeb is famous for producing heavy websites. Converting png images into jpg images is a good solution [04/25/2006 : hmmm, well, not always]. It is not the unique solution : iWeb generates multiple identical images in different folders. Regrouping those images in a unique folder could be done. It will be done maybe in a future release. I will appreciate help in this task.
known bugs :
-iWeb Optimizor does not make a backup copy of you png images -jpg does not deal with transparency
History: 21 apr 2006 : 0.1b1 first release
It is the first release of a beta release…things can been done to improve it, I am sure (gif usage, intelligent choice of the target image format, regrouping of multiple identical images, etc.)
What I think is that image optimization is the key to improve iWeb “slowness”
The download figures (577 at the present time) and some comments on Apple iWeb forums proves that the need exists for a turbo engine for iWeb. If somebody wants to work with me on this project, it would be cool. I have ideas but really very little time to code them (and we are not bound to use only automator actions)
Voilà ,
Ka (k@weedolucidea.com)
Comment by Ka — April 25, 2006 @ 6:06 pm
The standard theme I use cannot be transformed into jpg. There is a lot of transparency used and png is necessary. If you use this tool the website becomes bigger (48mb to 62mb in my case) and really is messed up. This is not a solution for me…
Comment by niels — April 23, 2006 @ 8:58 am