Comments on: WebExport 1.0b311 Posted

By: Daniel Staudigel

Daniel Staudigel — Wed, 20 Sep 2006 23:01:43 +0000

This is no longer an active comment area. Please direct any queries to the current one, linked from the WebExport page.

In response to your question, I looked into it, exporting some images at 300×300, but could not get any blockiness at all… if you could give some examples web pages/files that exhibit this behavior, that would be great. I may need to do a multi-step reduction process for the really small images. Also, please make sure you are using 1.0r112 not the one for this thread.

By: Mike

Mike — Wed, 20 Sep 2006 21:35:29 +0000

Very nice, but for whatever reason some of the pictures become extremely blocky when exported at reduced resolution (I am using the default of 480 pixels). Incidentally, I noticed that the developer of iPhoto Export seemed to have a similar problem in previous versions:

http://www.hagus.net/node/122

By: Randy Harris

Randy Harris — Fri, 25 Aug 2006 06:48:50 +0000

Hi Dan,

wow, WebExport is great and much improved from CustomHTMLExport (and easier to say too. :)

By chance do you think you'll do a sample template for AirTight's AutoViewer?

Thanks much,

Randy at http://www.MacSeven.com

By: Daniel Staudigel

Daniel Staudigel — Tue, 08 Aug 2006 15:48:33 +0000

The difference, in terms of functionality, is slight. WebExport is the new CustomHTMLExport because I got tired of trying to pronounce the latter when explaining what I was doing with my free time. WebExport is much easier to say, easier to type, etc. It is CHTML 2.0, so to speak. As such, it has a vastly improved template engine, a much better user interface, and some new capabilities over CHTML, like metadata saving. The template formats are NOT COMPATIBLE. They are, however, easily convertable. In WebExport tags are delimited by greater-than/less-than signs, as opposed to square brackets. This makes it more compatible with PHP, and makes it look more like real HTML. I have also added things like more intelligent loops, if/then/else conditionals, and a very deep connection with python, which allows for a tremendous amount of flexibility. An example of this difference is with CHTML, you could only specify next/prev photos and gallery buttons to loop continuously. In WebExport it is a simple job of putting them in a conditional box, and they disappear at the end and beginning of the lists. I leave CHTML up only so you can continue to use it if you have templates for it. I will be dropping it soon.

For future reference, I am going to add the above section to the WebExport page.

By: Dave

Dave — Tue, 08 Aug 2006 06:49:31 +0000

Hey Daniel,

What's the difference between CustomHTMLExport and WebExport?

I could download and find out, but don't have the time today, so I'll just ask.