After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617002 - Message composer should make a better use of space
Message composer should make a better use of space
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: Federico Mena Quintero
Evolution QA team
evolution[composer]
Depends on:
Blocks:
 
 
Reported: 2010-04-27 22:24 UTC by Federico Mena Quintero
Modified: 2021-05-19 11:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Federico Mena Quintero 2010-04-27 22:24:02 UTC
The message composer fits fine in 1024x600 (the resolution used by netbooks), but it makes very poor use of the space available.  The controls take up most of the screen and you get left with little space for your actual message.

* The menu bar is seldom used.

* The toolbar is too big.

* The "From" drop-down wastes a whole line of space if you only have a single mail account.

* Do you really need a "Signature" chooser?

* There is the "normal" amount of space between the From/To/CC/Subject lines, but this adds up to a significant amount of vertical space.  Can we make the spacing smaller?

* The biggest waste of space is in the HTML widget's toolbar, which is two tall lines full of icons and combo boxes.

Srini started a "lite" version of the composer, which needs to be turned on in the code.  Look for e_msg_composer_lite_new().  This removes the menu bar and toolbar, moves the "Send" and "Save Draft" buttons to the bottom bar, and generally makes the controls more compact.

However, this is not finished yet.  I'll work on this.
Comment 1 Matthew Barnes 2010-04-28 16:09:44 UTC
For the record, I'm not real thrilled with the way the "lite" stuff is hacked in at the moment.  I'd rather it be done through subclassing (Anjal should've had its own EMsgComposer subclass -- I was willing to make whatever accomodations were needed on the Evolution side), but it will likely require some in-depth class design rework, which may be out of scope here.
Comment 2 Federico Mena Quintero 2010-04-29 17:22:00 UTC
Sorry, I was away yesterday at a conference, so I haven't had a chance to actually see how the composer is coded.

I'll be glad to refactor things as needed.  Do you have any concrete ideas?  I'm sure you know that code better than I do :)
Comment 3 André Klapper 2012-06-27 10:38:57 UTC
Might make sense together with porting the composer to webkit in 3.7.
Comment 4 André Klapper 2021-05-19 11:37:12 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.