Marcelo de Moraes Serpa wrote:
> Less manegeable becouse I would have to keep copies of the pictures on
> the disk. If I ever want to change these watermarks, I would have to
> somehow recreate them. It is more work to do than if I used the
> per-request runtime applying of watermark approach, sin
@Per Jessen
Disk-space is cheap, especially if you don't need to be worried about
backup etc. I'm not sure why you think applying watermarks in an
off-line process would any less manageable than doing it on-line.
Well, the processing will be "online" in the sense that it will be triggered
via an
Bernhard Kohl wrote:
> I think it also depends on the size of your images. If they are huge
> megapixel files processing them on the fly might cause severe lag.
> Still adding a watermark to an image with 100-200 thousand pixels is
> done within milliseconds on a modern machine.
>
(You probably
On Wed, Aug 6, 2008 at 3:04 PM, Marcelo de Moraes Serpa <[EMAIL PROTECTED]
> wrote:
> Hello,
>
> My next project will be a kind of online photo viewer. All of these photos
> will need to have watermark applied to them. The problem is that, depending
> on the picture, different watermarks need to b
Marcelo de Moraes Serpa wrote:
> My next project will be a kind of online photo viewer. All of these
> photos will need to have watermark applied to them. The problem is
> that, depending on the picture, different watermarks need to be
> applied. The easiest solution would be to process these pict
Hello,
My next project will be a kind of online photo viewer. All of these photos
will need to have watermark applied to them. The problem is that, depending
on the picture, different watermarks need to be applied. The easiest
solution would be to process these picture at runtime using GD, apply t
6 matches
Mail list logo