[
https://issues.apache.org/jira/browse/WAVE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041344#comment-13041344
]
David Hearnden commented on WAVE-281:
-------------------------------------
The wave panel's width should be sized for maximum readability (print is
~66chars per line, screens is ~80 chars per line), independent of padding, so
the extra padding shouldn't affect horizontal space or readability at all.
GWave's layout does fit more content in a smaller space, but it has other more
significant layout problems that the new layout avoids (e.g., consistent
left-alignment within a blip). All the layout properties of WIAB's wave panel
are intentional, and were put together by a UI designer. I'm not a UI
designer, so I'm less qualified to describe the intent for the extra padding.
FYI you can play around with the layout in the blip mock page
(src/org/waveprotocol/wave/client/wavepanel/view/dom/full/mock/blip.html) to
see what reducing the padding would look like.
> Unnecessary padding in WIAB web client
> --------------------------------------
>
> Key: WAVE-281
> URL: https://issues.apache.org/jira/browse/WAVE-281
> Project: Wave
> Issue Type: Improvement
> Components: Web Client
> Reporter: Zachary “Gamer_Z.” Yaro
> Priority: Minor
> Attachments: gwave_padding.png, wiab_padding.png
>
>
> Blips in the WIAB web client have unnecessary padding. This means more
> vertical scrolling to read threads and less horizontal space for each line,
> which can be annoying on lower-resoultion screens. Attached are two images
> showing the difference between padding in the Google Wave client versus the
> WIAB client.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
