forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From philippe perez <Philippe.Pe...@Sun.COM>
Subject Re: photogallery plugin thoughts
Date Fri, 06 Jan 2006 13:22:10 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Hi Tim,<br>
I read you proposal with a real interest because I have the same
feeling a couple of weeks ago.<br>
(I don't have any skills in Java programming ... ;-) )<br>
I'm using Forrest Photogallery plugin feature into a personnal
genealogical site and I'm<br>
manipuling a lot a family pictures and/or census scans....<br>
I spent a lot of time to migrate my previous Forrest v0.6 into
Photogallery directories<br>
and it was a mess to have to generate images three times each.... Apart
of that is the<br>
disk space required according to the resolution used.<br>
So in my point of view, I would be a great mechanism to only have one
original picture<br>
and Forrest take care of everything for the others 2. So point 2 is my
If somebody decides to implement that please let me know where I have
to sign up ;-)<br>
Tim Williams wrote:
  <pre wrap="">I've looked at the Photogallery plugin and have some changes I'd like
to discuss.

1) Move from directory to file convention.  I don't particularly care
for the whole directory-based convention for the image variations
(preview | small | big).  I'd like to just be able to dump a bunch of
existing image directories into the gallery and not have to do much
work.  (Yeah, I know there's scripting that can do some grunt work
here).  I'd like to move the plugin to a filename based approach.  The
short version is that each image variation would live in the same
directory as the main image file but with an added identifier in the
name.  Something like:

2) Let cocoon generate these images for us.  I don't like having to
pregenerate all of the image variations so I would like cocoon to do
it for us. This is pretty simple with the ImageReader but we very
quickly run into memory issues.  The only solution to this (besides
the obvious boosting maxmem) I can think of is to implement a
PersistentImageReader that, once it generates the requested image
variation, writes it to disk.  Then, the next time though it only
needs to be read from disk.  This means that cocoon needs write
permission but it's about the best way I can think to do it.

I've actually got #1 working with the plain ImageReader (although it
could be static disk-based as well).  I've got #2 mostly working as
well but the image writing needs some cleanup.  Anyway, I like where
this is going but didn't want to drastically change the current plugin
without some discussion.

<div class="moz-signature">-- <br>
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
<meta content="Philippe PEREZ" name="author">
<table style="width: 718px; height: 176px;" border="1" cellpadding="2"
 style="vertical-align: top; width: 180px; background-color: rgb(88, 121, 147);"><font
 style="color: rgb(255, 255, 255);" color="#000099"><small><b><br>
      <span style="color: rgb(255, 255, 255);">Philippe PEREZ</span></b></small></font><font
 style="color: rgb(255, 255, 255);" color="#3333ff"><font
 style="color: rgb(255, 255, 255);"><br>
      <small>Partner Support Engineer</small><br>
      <small> T&eacute;l. : +33 1 34 03 17 08</small><br>
      <small> Fax&nbsp;: +33 1 34 03 17 20</small><br>
      <small> Port. : +33 6 08 52 82 38</small></font><br>
      <small>AIM : pperezfr</small><br>
      </font> <b style="color: rgb(255, 255, 255);"><a
 style="color: rgb(0, 0, 0);" href=""><small></small></a></b><br>
 style="vertical-align: top; background-color: rgb(255, 199, 38); width: 190px;">
      <div align="center"><small><br>
      <big style="color: rgb(0, 0, 0);"><b>Sun Microsystems France S.A</b></big></small><big
 style="color: rgb(0, 0, 0);"><br>
      <small> 13 avenue Morane Saulnier</small><br>
      <small> 78140 Velizy Villacoublay<br>
      </small></big><br style="color: rgb(0, 0, 0);">
      <span style="color: rgb(0, 0, 0);">Le site d&eacute;di&eacute;
&agrave; la formation :</span><br>
      <a style="font-weight: bold;" href=""></a><br>
 style="width: 160px; vertical-align: top; color: rgb(0, 0, 0); background-color: rgb(231,
111, 0);">
      <div align="center"> <span><!-- END SOLARIS 10 MOVES AHEAD -->
<!-- END L1 COMPONENT V.0 --></span><br>
      <div class="e8img"><a
      <img src="cid:part1.04040003.08060004@Sun.COM" alt="" border="0"></a></div>
      <p>Augmentez vos b&eacute;n&eacute;fices.<br>
Toutes les formations Solaris 10.<br>
      <a style="font-weight: bold;"
 class="morelink">&raquo;&nbsp;Enregistrez-vous d&egrave;s &agrave; pr&eacute;sent</a></p>
<!-- END E8 COMPONENT V.1 --></span> </div>
      <td rowspan="1" colspan="3"
 style="background-color: rgb(88, 121, 147); vertical-align: top;">
      <pre wrap="">"Legal Notice
The information contained in this communication is confidential, is intended only for the
use of the recipient named above, and might be legally privileged.
If the reader of this message is not the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please resend this communication to the
sender and delete the original transmission or any copy of it."</pre>

View raw message