Le 16/10/2013 11:50, Sven Van Caekenberghe a écrit :
On 16 Oct 2013, at 10:20, Goubier Thierry <[email protected]> wrote:
Interesting display, Sven.
My take on that:
* Aesthetics: the system has two fonts, not one. -1 if I review a document with
more than one font.
In all documents, you have at least two fonts: body and headings, often quotes,
examples, listings, etc have an another font to make them stand out. In the new
approach, the idea is that monospaced fonts indicate code (in browsers,
debuggers, workspaces). It is a useful principle.
You're right. But nobody would dare write headings in a monospaced font
:) unless for an art project.
* Coherence / uniformity: A class name, a method selector has a different shape
in the GUI (proportional) than in the code (monospaced). Are they different
objects? Can I recognize my class name in the code without reading it?
Syntax highlighting should take care of that I guess.
I don't think so. This is no by making the selector green that it will
look more like the proportional version in the pane above.
Kind of disrupting the uniformity of the underlying model, when I'm
pushing for things like smart suggestions where the GUI understands the
objects written in the code.
I think that if the monospaced font is a point size smaller that the main sans
font (e.g. 12 and 11) the excessive width problem or visual shock is much more
manageable. In any case, I am giving it a try.
Probably. But then individual characters may become harder to read and
distinguish... sort of compromising character readability to make space
for the added whitespace inherent to the monospaced font.
I'd be more impressed if the argument was helping me distinguish between
| and l.
I'l let you try, then :)
Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
