[squeak-dev] Squeak's low-level gestures (was: Something in the update process..)

Chris Muller asqueaker at gmail.com
Tue Sep 17 15:36:03 UTC 2013

Add this method see if you like it better:

     ^ true

With this the text pane will remain the standard size and only expand
if more lines of text are entered.

The original philosophy of the horizontal-splitter algorithm is to 1)
only expose additional information but, 2) don't truncate any
information to accomplish that, e.g., only encroach on whitespace.

But, as we've discovered, we'd like for it to give precedence to the
Text pane, so it can encroach on a list even if it has no whitespace
available, because we want to be able to easily work with the text

FYI, (a) has nothing to do with smart-splitters; the scroll bar will
stick out below bottom edge whether a human or software drags the
splitter there..

On Tue, Sep 17, 2013 at 4:01 AM, Frank Shearar <frank.shearar at gmail.com> wrote:
> The only weird thing that I've seen is that if the code pane of an
> explorer is empty (as it will be if you've just opened it) the code
> pane will progressively shrink. But
> (a) it'll shrink just too far, making the code pane's scroll bar stick
> out below its bottom edge and
> (b) if I start typing in the code pane - adding expressions for
> evaluation, in other words - I have two lines with which to work. I
> _can_ resize the code pane, but that's a lot of work :)
> I suppose the problem with (b) is that even though I've typed some
> lines, the "character pressure" isn't quite enough to push the
> splitter up?
> frank
> On 17 September 2013 03:33, Chris Muller <asqueaker at gmail.com> wrote:
>> Thank you Frank!  I was curious whether anyone had tried it and what
>> they thought.  Once I got used to the movements, I've not been able to
>> go back.  I think debugging took the most getting used-to.  It seems
>> there's a case left where I still sometimes need to drag a splitter
>> manually (the one between debugger's code pane and variable lists).
>> Not because of a bug, because of the algorithm.
>> On Mon, Sep 16, 2013 at 4:55 PM, Frank Shearar <frank.shearar at gmail.com> wrote:
>>> So it might take me a while to get used to things
>>> adjusting/growing/shrinking, but actually I think I may learn to like
>>> the smart splitters a lot.
>>> So folks, got and try it out (look for "smart splitter" in
>>> Preferences) and give Chris some feedback!
>>> frank
>>> On 11 September 2013 19:39, Chris Muller <asqueaker at gmail.com> wrote:
>>>> Tim does your blue-button moving and resizing work?  It doesn't work
>>>> for me unless middle button is yellow and right button is blue (e.g.,
>>>> unswapped for Linux).
>>>> I ask because Bert's blue-drag and control-blue "pinch-zoom" is one of
>>>> a trio of improvements that has modernized Squeak's UI from the 1990's
>>>> scroll-bars to 2010's tablet-style UI's.  With
>>>>   1) Bert's blue-drag and control-blue-drag "pinch-zoom",
>>>>   2) the filterable lists feature, and
>>>>   3) the new smart-splitters,
>>>> Any need for scrolling has virtually evaporated.  Controlling Squeak
>>>> occurs in the cerebellum, so that more thinking about Squeak stays in
>>>> the cerebrum.  :)  It took a couple of days to get used to
>>>> middle-click yellow, but it is way worth it for having the blue
>>>> features work.
>>>> On Wed, Sep 11, 2013 at 12:55 PM, tim Rowledge <tim at rowledge.org> wrote:
>>>>> On 11-09-2013, at 10:35 AM, Frank Shearar <frank.shearar at gmail.com> wrote:
>>>>>> I just updated an image from 12641, and the blurry Ulam Spiral
>>>>>> background disappeared, replaced by the old brushed metal background.
>>>>>> What did that? Why?
>>>>> I noticed that too. Presumably an update made the change explicitly. What did mildly annoy me was that loading my preferences (mostly things like swapping back to proper mouse button use instead of the completely improper right-button-is-middle-button nonsense and getting scrollbars on the left as they should be) actually reset the background. It would be nice if only  deliberate change caused the new choice to be written out; no idea where the code is that does that right now.
>>>>> tim
>>>>> --
>>>>> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
>>>>> APATHY ERROR:  Don't bother striking any key.

More information about the Squeak-dev mailing list