Return-Path: 
 <user-return-592-apmail-forrest-user-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-user-archive@www.apache.org
Received: (qmail 20299 invoked from network); 10 Sep 2004 18:58:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 10 Sep 2004 18:58:08 -0000
Received: (qmail 27789 invoked by uid 500); 10 Sep 2004 18:58:08 -0000
Delivered-To: apmail-forrest-user-archive@forrest.apache.org
Received: (qmail 27758 invoked by uid 500); 10 Sep 2004 18:58:07 -0000
Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:user-help@forrest.apache.org>
list-unsubscribe: <mailto:user-unsubscribe@forrest.apache.org>
list-post: <mailto:user@forrest.apache.org>
Reply-To: user@forrest.apache.org
Delivered-To: mailing list user@forrest.apache.org
Received: (qmail 27747 invoked by uid 99); 10 Sep 2004 18:58:07 -0000
X-ASF-Spam-Status: No, hits=0.1 required=10.0
	tests=DNS_FROM_RFC_ABUSE,LOTS_OF_STUFF
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from [216.109.118.113] (HELO web60302.mail.yahoo.com)
 (216.109.118.113)
  by apache.org (qpsmtpd/0.28) with SMTP; Fri, 10 Sep 2004 11:58:06 -0700
Message-ID: <20040910185804.36758.qmail@web60302.mail.yahoo.com>
Received: from [62.174.255.28] by web60302.mail.yahoo.com via HTTP;
 Fri, 10 Sep 2004 11:58:04 PDT
Date: Fri, 10 Sep 2004 11:58:04 -0700 (PDT)
From: Jason End <bensnephew@yahoo.com>
Subject: Re: screenshot scaling
To: user@forrest.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N


If this is implemented, documentation should recommend
that images be scaled proportionally, so the
thumbnails look the best possible. Non-proportional
scales are usually what messes images up. That could
be done using % in the width/height setting, or
finding the porportional pixel lengths. 
So thumbnail sizes for 1024x768 images would be
128x96, 256x192,  512x384...

If you want, contact me when it's documentation time,
and I'll write it up.

Jay


Charles Palmer wrote:
>+1
>
>This is an issue that I am also going to have to deal
>with as I try to
>migrate my OOo manuals to Forrest. I can link to an
>image file, which OOo
>can scale to suit me, but the chances are that the
>image size will be wrong
>if the same image file is referenced in a Forrest
>document. You might want a
>smaller image in the HTML, but still want to be able
>to view the image at
>the full resoution (think: screen shots).
>
>Now, if images could be referenced using the site:
>mechanism as hrefs  (<img
>src="site:images/screenshot">), then you could
control >how images were
>rendered with something like this (in site.xml):
>
><images href="full-size-images/">
>    <screenshot href="ss1.bmp" width="100"
height="60" >expand="Click to view
>this screen shot full-size"/>
></images>
>
>The height and width attributes limit the size when
>viewed in the main page
>(simply pass the attributes through to the HTML <img>
>tag which will allow
>the browser to do the scaling), and if the expand
>attribute is present then
>render the image something like this:
>
><a href="full-size-images/screenshot.html">
>   <img src="full-size-images/ss1.bmp" width="100"
>height="60"
>   alt="Click to view this screen shot full-size" />
></a>
>
>No doubt a few details missing but you get the idea.
>What do you think?

>Charles Palmer


		
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo