<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="+1">Comment in text.</font><br>
</p>
<div class="moz-cite-prefix">Le 26/04/2020 à 23:46, ken.dickey---
via Cuis-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:f2fba78f95a18c38b6615bc4f075107f@whidbey.com">I think we
have a user interface problem with
LayoutSpec>>minorDirectionPadding:
<br>
<br>
One is easily confused, so perhaps our descriptions are wrong --
we are talking badly.
<br>
<br>
In particular, I would like to use "attraction" rather than
"padding", but see below.
<br>
<br>
===============================================
<br>
<br>
I also propose a brief discussion in the Terse Guide.
<br>
<br>
Perhaps something like:
<br>
=========================
<br>
<br>
LayoutMorph's arrange subMorphs as either a horizontal Row or a
vertical Column.
<br>
<br>
Along this Major or Layout Axis, subMorphs may be attracted toward
one side (0.0) or the other (1.0) or anywhere in between.
<br>
</blockquote>
<br>
<blockquote type="cite"
cite="mid:f2fba78f95a18c38b6615bc4f075107f@whidbey.com">
<br>
If a Row, one can specify the placement attraction symbolically as
<br>
{ #rowLeft (0.0), #center (0.5), #rowRight (1.0) }
<br>
<br>
If a Column, one can specify the placement attraction symbolically
as:
<br>
{ #colTop (0.0), #center (0.5), #colBottom (1.0) }
<br>
<br>
A LayoutMorph may also have a Morph Separation specified as x@y
<br>
<br>
======
<br>
<br>
Each subMorph of a LayoutMorph may have an optional LayoutSpec
which the subMorph uses to indicate how that Morph wants to be
arranged by its containing LayoutMorph.
<br>
<br>
Options include treating the Morph's width and height as fixed or
proportional to the LayoutMorph's extent.
<br>
</blockquote>
<p><br>
</p>
What about "Minor or Perpendicular axis/direction" ?<br>
<blockquote type="cite"
cite="mid:f2fba78f95a18c38b6615bc4f075107f@whidbey.com">
<br>
A LayoutSpec may also indicate an attraction along the <b>Minor
or Contrary Axis.
</b><br>
<br>
Again, symbols may be used.
<br>
<br>
If in a LayoutMorph Row: { #rowTop (0.0), #center (0.5),
#rowBottom (1.0)}
<br>
<br>
If in a LayoutMorph Column: { #colLeft (0.0), #center (0.5),
#colRight (1.0) }
<br>
<br>
=============================================================
<br>
<br>
I propose we change the access methods
<br>
LayoutMorph>>padding: -->
LayoutMorph>>attraction:
<br>
LayoutSpec>>minorDirectionPadding: -->
LayoutSpec>>attraction:
<br>
<br>
And use the symbols as above in place of {#right, #top, #left,
#bottom}.
<br>
</blockquote>
<p>Symbol is nice I guess.<br>
</p>
<p>Is it wise to propose to the user understanding two messages with
the same name but a bit different behavior? <br>
</p>
<p>May be the second one could be make more explicit as
minorAttraction: perpendicualAttraction:, alternateAttraction:.
... <br>
</p>
<p>Which of padding or attraction is the most well known term in GUI
construction? It could help to decide.<br>
</p>
Hilaire<br>
<pre class="moz-signature" cols="72">--
GNU Dr. Geo
<a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a></pre>
</body>
</html>