non member submissions are not automatically posted. if people expect tobe
taking part in discussions more than occasionally, it is probably better to
join the list.
--
Chris
Forwarded message 1
In message <001a01c07e67$c53fadf0$0100a8c0@aries>
"Charles F. Munat" <chas@munat.com> wrote:
> FWIW, lest Andrew appear to be alone in his concerns about "scroll-free
> scrolling," I agree that implementations of SVG on the Windows platform (and
> others) should include scrollbars and that the recommendation should make
> this clear. Panning is a nice added functionality, but it should not be the
> sole means of accommodating images larger than the view screen.
>
> People expect scrollbars. It's that simple. A shift to a panning paradigm
I don't think they expect them on GIFs or JPEGs, do they ?
> will require retraining millions of users, and will increase the slope of
> the learning curve, and for what? Where is the benefit? I am especially
> concerned by the ramifications for users with cognitive disabilities of
> further complicating the user interface. So I think this is an accessibility
> issue.
Sorry, I've not really been following this too much, but I fail to see what
the fuss is about... Nor what the difference is between scrolling and
panning. Scrolling is moving around the image. Panning is moving around the
image. You have to do that if you incorporate any form of zoom. The default
workarea specified by the SVG should be the main area and shouldn't have
scroll bars if there are sections outside of this area. If I've
misunderstood then please just tell me to refer to the document, and I'll
re-check what I've read...
--
Justin Fletcher, SVG developer for RISC OS
URL: http://www.movspclr.co.uk/