[opencms-dev] RE: opencms-dev Digest, Vol 63, Issue 6

Arash Kaffamanesh arash.kaffamanesh at pomegranate.de
Thu Oct 20 17:14:28 CEST 2005


Stephan Hartman has developed a module for image operations:


> Could this be easily developed as a "module" for OpenCMS? 

Why not? OpenCms is great and better than FatWire (I heared FatWire is
dead, like the predecessors, Divine, Futuretense, OpenMarket :-) )

> Maybe we can do the job...

Would be fine.

By the way few days ago somebody asked me to integrate Pixory as Image
Server into OpenCms, does anybody have any experience with Pixory?


-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Riveira Faraldo,
Sent: Donnerstag, 20. Oktober 2005 16:53
To: opencms-dev at opencms.org
Subject: [opencms-dev] RE: opencms-dev Digest, Vol 63, Issue 6

We are currently using FatWire ContentServer and although OpenCMS still
has some raw things, like the way to create new structured, XML content
(not serious if you have to do so many things to have a new object type,
including restart), it looks quite promising. We are giving it a try.

Right now we're using Imagemagick with FatWire for image processing (as
it also gives nice features like converting to JPG or GIF, rescaling,
vignetting, whatever you could dream of...)

The promised 6.2 image scaler is a step in the right direction, but it
is still far away from what is really needed for an image function

I know that I'm not (yet :-) paying for support, so I am nobody to ask
for features, but I would be happy to see:

	- auto image scaling functions : obtaining the URL adress of an
image, you should be able to specify the size (like
/scaledimages/100x100/image.gif); then the system, when asked for the
image, it would look into a temp folder for the scaled image; if not
there, it should scale it, save it and serve it; then, next time it is
asked for the same image, same size, it is already there; also, if you
need another size you can have it

	- of course, that should take care of HTTP headers for caching
in proxies and the user navigator

	- and last, whenever the image is "touched" or changed, every
scaled version of it must be deleted so they're regenerated when the
user asks for the images

We have already implemented all this with servlets for Tomcat/JSP
websites; with FatWire we have almost all of that. 

Could this be easily developed as a "module" for OpenCMS? Maybe we can
do the job...

> > String propValue = // obtain "image.size" String value from
> > somehow CmsImageScaler scaler = new CmsImageScaler(propValue);
> > int height = scaler.getHeight();
> > int width = scaler.getWidth();

Bernardo Riveira
Este mensaje se dirige exclusivamente a su destinatario. Puede contener
información privilegiada, confidencial o legalmente protegida. Si ha
recibido este mensaje por error le rogamos que lo borre inmediatamente,
así como todas sus copias, y lo comunique al remitente. En virtud de la
legislación vigente está prohibida la utilización, divulgación, copia o
impresión sin autorización. No existe renuncia a la confidencialidad o
privilegio por causa de una transmisión errónea.

This mail is send to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please
visit http://mail.opencms.org/mailman/listinfo/opencms-dev

More information about the opencms-dev mailing list