321 |
} |
} |
322 |
\end{figure*} |
\end{figure*} |
323 |
|
|
|
\section{Hardware-accelerated implementation} |
|
|
|
|
324 |
It is important that the background can be zoomed to different resolutions. |
It is important that the background can be zoomed to different resolutions. |
325 |
However, we are currently |
However, we are currently |
326 |
not trying to attain infinite zoomability\cite{furnas00infinity}, |
not trying to attain infinite zoomability\cite{furnas00infinity}, |
327 |
only the range of zooming that would be reasonable for a single PDF document. |
but only the more modest goal of zooming within a range |
328 |
|
that would be reasonable for a single PDF document, i.e. approximately 100-fold |
329 |
|
difference between mininum and maximum zoom. |
330 |
|
This is in line with our |
331 |
|
intended use, since it would be unreasonable to expect a texture to be recognizable |
332 |
|
if a sub-pixel area were zoomed to the full screen. |
333 |
|
Of course, methods such as the ones presented in \cite{furnas00infinity} could be used |
334 |
|
to allow the unique background to look similar at different scales; however, |
335 |
|
this would remove the use of the texture as a cue of scale. |
336 |
|
|
337 |
For zooming, it would be possible to use a solution such as the ones in \cite{furnas00infinity}, |
\section{Hardware-accelerated implementation} |
|
but... |
|
338 |
|
|
339 |
In hardware rendering, the use of resources is critical |
In hardware rendering, the use of resources is critical |
340 |
The two relevant types of resources here are texture memory |
The two relevant types of resources here are texture memory |
341 |
and |
and rendering time. |
342 |
|
|
343 |
|
|
344 |
|
|
345 |
|
|