[Bf-docboard] Figure image inconsistency

[Glen Larsen]

This is a minor issue and I respect your decision but let me clarify a
point. It would require no JavaScript or other special CSS manipulation,
only that images that fill a page width are specified consistently. Either
way, browser zooming will work so I can consistently use that method.
Either way, mobile devices allow a pinch gesture to zoom the image.

On the page I referenced one image is the width of the paragraph, the other
is scaled to a 600px width (short by 40px or so). I can accept a little
ugliness if some purpose is served.

And a happy holidays to you as well! I've enjoyed the small bits that I
have contributed and hope to do more in the new year.

On Sun, Dec 24, 2017 at 3:51 PM, Tobias Heinke <heinke.tobias at t-online.de>
wrote:

> Hey Glen,
>
> In https://github.com/sphinx-doc/sphinx/issues/4229 one of the main devs
> says it's an intended behavior.
> I assume all (also mobile) browsers have a right click - context menu
> option like View Image or Open image in new tab - IMO that's sufficient.
>
> Deactivating the links would require a JS script to loop over all links to
> prevent the click event (slow) and CSS for the cursor.
> Adding links is only possible with an extension.
>
> It's a balance of: when you want to view the image it should be big, but
> if have to scroll over it can be annoying. page overview gets lost...
> So it's a case by case decision and the guide would become too lengthy.
>
> Happy holidays,
> Tobias
>
> Am 24.12.2017 um 22:42 schrieb Glen Larsen:
>
> Some figure:: directives specify a scaling option (with :width:, :height:,
> or :scale:), some do not. There is a distinct difference between this:
> without a scaling option sphinx will generate a simple IMG directive, with
> scaling a CLASS directive is used with an HREF to the image.
>
> Good examples of this are the first two large Example images in
> Compositing -> Node Types -> Converter Nodes -> Combine/Separate Nodes. The
> first has scale specified to 600px, the second no scale.
>
> Normally, I would advocate the second un-scaled figure --- it fills the
> page width which makes it look nicer. The problem is that, even on a large
> workstation screen, I cannot read the textual detail of the nodes. Because
> the first image contains an HREF to the image, I can simply click on it to
> get the full image. I cannot do that on the second (non-scaled image) and
> must resort to browser zooming.
>
> For usability we should do this one way or the other. The markup style
> guide gives good information regarding image creation but makes no
> recommendation on scaling.
>
> -glen
>
>
> _______________________________________________
> Bf-docboard mailing listBf-docboard at blender.orghttps://lists.blender.org/mailman/listinfo/bf-docboard
>
>
>
> _______________________________________________
> Bf-docboard mailing list
> Bf-docboard at blender.org
> https://lists.blender.org/mailman/listinfo/bf-docboard
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.blender.org/pipermail/bf-docboard/attachments/20171224/5336f341/attachment.html>