<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">&gt; &gt; We don't have something like a pyramid representation of layers (yet)<br>
&gt;<br>
&gt; Emm.. Can i read about that pyramid anywhere?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Some notes taken a while back:<br>
http://wiki.koffice.org/index.php?title=Krita/Akademy_2007_Meeting#tile_backend<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>&gt; &gt; where we could filter at the zoom level nearest to the actual zoom level.<br>
&gt; &gt; That would be<br>
&gt; &gt; one solution, sort of.<br>
&gt;<br>
&gt; Why do we need many thumbs? And why filtering the nearest one? Why not have<br>
&gt; only two layer representations: original and current zoom level? Zoomed<br>
&gt; copy could (?) be used by projection (keeping in mind interpolation).<br>
Because scaling is also an expensive process. The pyramid would be updated continuously, in a background thread.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Cyrille Berger</p></body></html>