New Imagesystem: Question about geometry/scalepercent

Next topic

Author	Message
Marco Zinn	Tuesday 23 December 2003 8:34:38 am The new imagesystem has a filter called geometry/scalepercent. From the release docu: "geometry/scalepercent=widthpercent,heightpercent - Scale image to a percentage of what it was using widthpercent and heightpercent, the aspect ratio is maintained" My Question: If it will maintain the aspect ratio, why can I provide two paramters (widthpercent,heightpercent) and which is actually used? Will this scale up AND down? Does a paramter of "100" mean "100%" or should we use "1" or "1.00"? Marco http://www.hyperroad-design.com
Jan Borsodi	Friday 09 January 2004 6:22:40 am You're right the text is wrong, scaling in percent DOES NOT keep aspect ratio. Also a value of 100 means 100%. I've updated the page with this information. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Tuesday 23 December 2003 8:34:38 am

The new imagesystem has a filter called geometry/scalepercent.
From the release docu:
"geometry/scalepercent=widthpercent,heightpercent - Scale image to a percentage of what it was using widthpercent and heightpercent, the aspect ratio is maintained"
My Question: If it will maintain the aspect ratio, why can I provide two paramters (widthpercent,heightpercent) and which is actually used?
Will this scale up AND down? Does a paramter of "100" mean "100%" or should we use "1" or "1.00"?

Marco
http://www.hyperroad-design.com

Jan Borsodi

Friday 09 January 2004 6:22:40 am

You're right the text is wrong, scaling in percent DOES NOT keep aspect ratio. Also a value of 100 means 100%.

I've updated the page with this information.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 31 2025 06:16:46
Script start
Timing:	Jan 31 2025 06:16:46
Module start 'layout'
Timing:	Jan 31 2025 06:16:46
Module start 'content'
Timing:	Jan 31 2025 06:16:46
Module end 'content'
Timing:	Jan 31 2025 06:16:46
Script end

Main resources:

Total runtime	0.0151 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0045	588.3750	151.2422
Module start 'layout'	0.0045	0.0024	739.6172	36.7109
Module start 'content'	0.0070	0.0065	776.3281	90.1875
Module end 'content'	0.0135	0.0016	866.5156	29.9922
Script end	0.0151		896.5078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	15.1779	14	0.0002
Check MTime	0.0010	6.6180	14	0.0001
Mysql Total
Database connection	0.0006	4.0921	1	0.0006
Mysqli_queries	0.0019	12.5699	3	0.0006
Looping result	0.0000	0.0726	1	0.0000
Template Total	0.0012	7.8	1	0.0012
Template load	0.0009	5.9660	1	0.0009
Template processing	0.0003	1.8076	1	0.0003
Override
Cache load	0.0006	4.1584	1	0.0006
General
dbfile	0.0015	9.7139	8	0.0002
String conversion	0.0000	0.0600	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs