On Wed, Dec 3, 2008 at 5:03 PM, Giancarlo F. Berner <[EMAIL PROTECTED] > wrote:
> > So I am curious about your graphics converter/resizer. If it is something > you can share with us that would be awesome. I gladly will pickup work in > "image processing". > We will strongly consider opensourcing it once we have PoC-ed it properly into a Magnolia-module. At the time this task is not prioritized, so it might not be until january some time. oc > > Thanks! > Giancarlo > > > On Dec 3, 2008, at 3:13 AM, Ole Christian Rynning wrote: > > Thanks all! > > I'm amazed by all the great (and quick!) feedback! Seems like the Magnolia > community has come a long way, (another great reason to go for it)! > > About Graphics/ImageMagick, I have experience with it leaking memory like a > sieve. We already have a working implementation of a graphics > converter/resizer in Java in our current CMS. > > Best regards, > > Ole Christian > > On Wed, Dec 3, 2008 at 12:01 AM, Giancarlo F. Berner < > [EMAIL PROTECTED]> wrote: > >> Hi Tom >> Thanks a lot! Yeah, one approach is to upload images and use the >> ImageMagick batch process. >> >> I have spent quite some time on an algorithm for scaling images in Java. >> There are many interesting approaches, but none is complete. The problem is >> that you need several different "filters" to complete the scaling and my >> imaging knowledge is rather limited. However, I did a lot of experimental >> work and have a working solution, but the quality could be better. My >> "vision" is to have a class which instantiates the image data and does >> different renderings (e.g. rotation, scaling, etc.). >> >> So if there is anyone out there who is wasting brain juice on the same >> topic, maybe we could scratch our heads and come up with a neat Java API. >> >> Thanks for your hint, Tom! >> Giancarlo >> >> >> On Dec 2, 2008, at 2:47 PM, Thomas Duffey wrote: >> >> >> On Dec 2, 2008, at 4:27 PM, Giancarlo F. Berner wrote: >> >> The real challenge here is to write a image scaling servlet which renders >> photoshop quality images! >> >> >> My suggestion for this part of the problem is to use ImageMagick (Or >> GraphicsMagick, if you like) along with Runtime.exec(). I tried to find >> something as awesome as ImageMagick but for Java and came up mostly empty >> handed. Yes, there is JMagick, but there are several reasons why you might >> not want to use it. Some of those reasons are described here: >> >> http://www.darcynorman.net/2005/03/15/jai-vs-imagemagick-image-resizing/ >> >> Good luck! >> >> Tom >> >> On Dec 2, 2008, at 1:21 PM, David Smith wrote: >> >> >> Speaking from the peanut gallery, I would prefer the images be >> >> pre-scaled and stored multiple ways in the DMS myself as it speeds up >> >> rendering to the public. Scaling on the fly from a single copy to each >> >> client is expensive on system resources. >> >> >> --David >> >> >> Jackson Nicolas wrote: >> >> Hi Ole, >> >> >> You seem to be receiving a lot of responses but there's one I would >> >> hope to read but isn't here. I was expecting that the "Magnolia-way" >> >> would be not store multiple instances of the same image, but instead >> >> one instance and be able to deliver multiple instances on request. In >> >> this case, you would not have to make any changes to the DMS but >> >> instead create a simple servlet that can deliver varying instances. >> >> >> Unless you REALLY do have a valid reason to store multiple instances >> >> of the same image, I don't see why you should. Since you want to do >> >> the resize on automatically on the upload anyway, why not do it on the >> >> download. Magnolia is great with caching so you will only have to >> >> resize once just as you would with the upload. >> >> >> I hope this helps. >> >> >> >> Best, >> >> Jackson >> >> >> On Tue, Dec 2, 2008 at 11:35 AM, Ole Christian Rynning <[EMAIL PROTECTED] >> >> <mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>>> wrote: >> >> >> I am currently in a very early stage evaluating Magnolia. >> >> >> I need to import and manage several thousands of product images >> >> with the WCMS/DMS. Typically the images are large jpgs, pngs, gifs >> >> and pdfs. When importing I wish to automatically resize the image >> >> into three sizes: thumbnail, product and large (+ full). >> >> >> For this I wish to to develop a module/template that: >> >> A) Automatically resizes the images and stores them into the DMS >> >> i.e. under images/products/name-{thumb,small,large,full} upon >> >> upload/import. >> >> B) A template that allows the editor to navigate the DMS by >> >> thumbnails, and insert images with selected size. >> >> >> Can anybody give me some general pointers for how to do this (the >> >> magnolia-way!)? >> >> >> Best regards, >> >> >> Ole Christian >> >> >> >> ------------------------------ >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[EMAIL PROTECTED]> >> ---------------------------------------------------------------- >> >> >> >> >> ------------------------------ >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[EMAIL PROTECTED]> >> ---------------------------------------------------------------- >> > > > > > ------------------------------ > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[EMAIL PROTECTED]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[EMAIL PROTECTED]> ----------------------------------------------------------------
