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 202638 - hide the formatting toolbar in composer
hide the formatting toolbar in composer
Status: RESOLVED DUPLICATE of bug 408707
Product: GtkHtml
Classification: Other
Component: html-editor-control
3.8.x
Other All
: Normal enhancement
: Future
Assigned To: gtkhtml-maintainers
Evolution QA team
evolution[composer]
: 231520 304792 495459 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-05-07 00:14 UTC by Miles Lane
Modified: 2008-06-22 23:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
small patch (619 bytes, patch)
2005-05-19 18:58 UTC, Vincent Noel
needs-work Details | Review

Description Miles Lane 2001-05-07 00:14:38 UTC
When I am composing messages with only plain text, there should
be an option to hide the formatting toolbar in the composition 
windows.  In fact, I think it should be the default state.
The only buttons that work on the toolbar are the indent/exdent 
and text-type list (which, frankly is a complete mystery in the 
plaintext context, anyhow).
Comment 1 Larry Ewing 2001-07-05 18:40:23 UTC
The list items work in plain text, because they render in the plain
text output.  The same is true for the indent functions.
Comment 2 Miles Lane 2001-07-06 04:10:35 UTC
Hi Larry,

Okay, I understand that this is by design.
However, I would still like the option to hide
the formatting toolbar.  I don't use it and am
perfectly happy to format my document by typing
in what I want.  For one thing, if I format it,
I know exactly what I'm getting and I don't have
to fool around learning a formatting tool's quirks.
Since I won't use it and, likely, many others will
not use it either, why should our valuable screen
real estate be consumed by unused GUI controls?

I would like to see this bug report reduced in
priority rather than marked as "NOT A BUG".

Thanks,
       Miles
Comment 3 Larry Ewing 2001-07-10 19:53:28 UTC
That is reasonable.  Reducing to cosmetic.
Comment 4 Vincent Noel 2005-05-19 18:29:36 UTC
*** Bug 304792 has been marked as a duplicate of this bug. ***
Comment 5 Vincent Noel 2005-05-19 18:29:57 UTC
*** Bug 231520 has been marked as a duplicate of this bug. ***
Comment 6 Vincent Noel 2005-05-19 18:58:51 UTC
Created attachment 46651 [details] [review]
small patch

For my own enjoyment I have created the attached patch.
It just hides the formatting toolbar when not in HTML mode. I realize that you
then loose the paragraph alignment items then, but I fail to see the use of
those in plain text anyway...
Comment 7 André Klapper 2005-05-20 14:35:20 UTC
adding patch keyword
Comment 8 Vincent Noel 2005-06-03 17:22:00 UTC
See how the message window looks without the formatting toolbar :
http://www.gnome.org/~vnoel/screenshots/evo-new-message.png

The patch gives you cute window messages :-)
Comment 9 André Klapper 2005-09-27 21:46:35 UTC
if the patch could be extended to also include a menu item in the "view" menu,
it would be rather cool...
Comment 10 Kaushal Kumar 2005-10-28 10:59:47 UTC
Vincent: An option to hide/unhide the toolbar would be nice.
Comment 11 Karsten Bräckelmann 2006-01-14 03:32:31 UTC
FWIW, the Paragryph Style dropdown is *highly* useful even when composing text/plain messages. Think of lines (maybe commands) that should not wrap. I use to need them all the time...
Comment 12 Matthew Barnes 2008-04-09 11:33:22 UTC
*** Bug 495459 has been marked as a duplicate of this bug. ***
Comment 13 Matthew Barnes 2008-04-09 12:08:13 UTC
You know, I didn't think I liked this idea at first.  But looking at the screenshot in comment #8, I have to say it's growing on me.  The window in the screenshot looks clean and simple.

We could easily make paragraph style (and alignment) available through the context menu in plain-text mode.  In fact, it should be anyway.

I would also add a separator followed by a "Style Toolbar" toggle to the View menu.  The question then becomes, how should it behave in HTML mode?  Should we force it to be visible in HTML mode and desensitize the menu item?  Or should we keep it orthogonal to HTML/text mode, potentially forcing the user to toggle /two/ things everytime he switches modes?

A third option is to remember the visiblity for each mode.  So we'd have two GConf keys -- "visible-in-html" and "visible-in-text" -- and toggling the View menu item would change the setting for the current mode.  Or would that be too confusing?

I'm leaning toward the third option myself.  It sounds good on paper (er, Bugzilla) but I think I'd have to actually play with it to know whether it's intuitive enough.
Comment 14 Matthew Barnes 2008-06-22 23:17:34 UTC
Merging this discussion into bug #408707.  There's a proposal there for improving the toolbars.

*** This bug has been marked as a duplicate of 408707 ***