Minimize length of stream box during compose based on available space & maximum stream length

[neiljp]

Currently the stream box can be quite wide; we spread the boxes between the available width.

While topic length can vary, we should be able to find some way to determine a smaller length using urwid's features based on what we know about the maximum stream length at the time.

Good related features to consider

• if we can/should limit the width of the 'topic edit' box while editing (edit-one, edit-later, edit-all messages in a topic)
• fix the length of the stream box while editing, if the stream cannot be changed (pending message moving feature)

I've labelled this as a good first issue initially as this would be good to help someone new to this to get to know urwid and the core UI, but this may be challenging or trickier than I expect and involve digging a little to find the right combination of spacing, so that this works over a wide range of window widths.

[cyberShaw]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @cyberShaw! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

[zulipbot]

Hello @cyberShaw, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue?

If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 4 days.

If you've decided to work on something else, simply comment @zulipbot abandon so that someone else can claim it and continue from where you left off.

Thank you for your valuable contributions to Zulip!

[Sickaada]

@zulipbot claim

[zulipbot]

Hello @silentC1C4D4, it looks like someone has already claimed this issue! Since we believe multiple assignments to the same issue may cause some confusion, we encourage you to search for other unclaimed issues to work on. However, you can always reclaim this issue if no one is working on it.

We look forward to your valuable contributions!

[cyberShaw]

@zulipbot abandon

[zulipbot]

Hello @jalajcodes, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

[Sickaada]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @silentC1C4D4! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!