jvimedia/alpha

Suggestion: Reduce white space between messages.

bazbt3 opened this issue · 8 comments

Could you please consider reducing the amount of white space, initially between messages, maybe elsewhere later?

Why? On a 1900 x 1200 (24"/61cm) display with default browser zoom there are:

  • Only 6 rows visible when arriving at the page (i.e. with the post dialogue visible.)
  • A maximum of around 8.5 rows scrolled down the list.

(FYI my 14" laptop at home though has half the totals.)

This may have 2 positive benefits:

  1. More posts onscreen.
  2. It may be better to visually indicate a difference between JVI Alpha and ADN Alpha - e.g. to ensure that editing account info is seen to be done in a separate site.

Suggestions:

  • Compress the space between window title and post dialogue.
  • Compress the space both sides of the lines dividing posts.
  • The post status line is currently always below the avatar, even for a single-line post (may require lots work to achieve minimal benefits.)

Thanks for reading!

Hey @bazbt3. Can you explain "The post status line is currently always below the avatar, even for a single-line post (may require lots work to achieve minimal benefits.)"? The post status line is the "2w - Reply via AlphaRevive_Local" thing (as shown below)?

aikawa_grabs 2014-05-31 at 20 03 15

Hiya!

You're exactly right - and I consider it a massive waste. It's 'clean' alright but trying to achieve a uniform row height is a bit daft when you consider most people have to scroll ridiculous numbers of messages daily.

The minimal benefits/work tradeoff refers to my relative lack of experience with CSS/modern screen layout tools. ;)

Now, was I right to raise the issue at GitHub or would you have preferred email?

On 31 May 2014, at 20:04, "Charlotte W." notifications@github.com wrote:

Hey @bazbt3. Can you explain "The post status line is currently always below the avatar, even for a single-line post (may require lots work to achieve minimal benefits.)"? The post status line is the "2w - Reply via AlphaRevive_Local" thing (as shown below)?


Reply to this email directly or view it on GitHub.

Barrie,

I get what you mean now and will have a look to see what I can do.

Cheers.

On 31 May 2014, at 21:23, bazbt3 notifications@github.com wrote:

Hiya!

You're exactly right - and I consider it a massive waste. It's 'clean' alright but trying to achieve a uniform row height is a bit daft when you consider most people have to scroll ridiculous numbers of messages daily.

The minimal benefits/work tradeoff refers to my relative lack of experience with CSS/modern screen layout tools. ;)

Now, was I right to raise the issue at GitHub or would you have preferred email?

On 31 May 2014, at 20:04, "Charlotte W." notifications@github.com wrote:

Hey @bazbt3. Can you explain "The post status line is currently always below the avatar, even for a single-line post (may require lots work to achieve minimal benefits.)"? The post status line is the "2w - Reply via AlphaRevive_Local" thing (as shown below)?


Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

Hmmm… my replying via email seems to have cluttered up the comments, sorry. Trying CodeHub on iPhone now.

Thanks for taking this seriously. :)

Worked well for me ;P

I'm just very good at pretending to take you seriously! ;)

On 31 May 2014, at 21:52, bazbt3 notifications@github.com wrote:

Hmmm… my replying via email seems to have cluttered up the comments, sorry. Trying CodeHub on iPhone now.

Thanks for taking this seriously. :)


Reply to this email directly or view it on GitHub.

If it breaks or others complain, don't come running to me or point fingers. If it's universally approved then yeah, you can have more things to do. :)
e.g. landing page screenshot

could you make that a new issue please? cheers Baz

On 31 May 2014, at 21:59, bazbt3 notifications@github.com wrote:

If it breaks or others complain, don't come running to me or point fingers. If it's universally approved then yeah, you can have more things to do. :)


Reply to this email directly or view it on GitHub.