following up on the discussion about the strike-out vs.
I do use the strike out shortcut frequently to finish lines in my ToDo
workspace. I would be fine with the font size shortcuts, though, if
there were another easy way to apply the strike out emphasis.
We have a perceived dozen of ways that allow you to change something
about the look of text, accessible via different kinds of interactions
with the world:
- menu item "set font" in tools (allows to change font family and
size), has cmd-k as a shortcut
- menu item "set style" in tools (provides a choice of a subset of
families plus some generic styles like DefaultTextStyle, but I do not
really know how it works), cmd-K
- menu item "set alignment" in tools (choice between leftFlush,
centered, justified, rightFlush, which reads rather technical in the
camel case, doesn't it?), cmd-u
- Morph menu item "text properties..." currently signals a
MessageNotUnderstood: UndefinedObject>>bounds in Morph>>openNear:in:
(world is nil)
- a halo icon indicating "font size" that opens the "set font" dialog from above
- a halo icon indicating "font family" that opens the "set style"
dialog from above
- a halo icon indicating "text style/emphasis" that opens a textual
choice of text styles, including struckOut, and text justification
again (also again in technically looking camel case), have not found a
menu command for this.
- cmd-6 allows you to change the color, add Do Its and links in the
text. Have not found a way to do that from a menu.
- cmd-9 adjusts the kerning (makes the text narrower) and I can not
find the shortcut to make it wider. No menu that I know of does this.
- cmd-0 removes some kinds of text attributes. No menu item.
The third mentioned halo icon works for me to strike out text, but I
have to get the halo of the text morph inside the workspace. And first
I had to find out that the halo icon exists at all because it does not
appear for all kinds of morphs (which is reasonable). I would rather
like to access that from the context menu (or via a shortcut...).
Do we really need a set of different dialogs for all of this? Wouldn't
it be nicer to merge these into one dialog and make the choices read
less technical? Shouldn't all options be accessible in a consistent
way instead of some via menus, some via the halo, some only via the
Is this something we should rather improve instead of disagreeing
about the keyboard shortcuts? Maybe not in 5.2, but later...
I do not see a problem of rededicating shortcut keys per se. If there
is no agreement on whether this is a regression or progress, there is
still the more complex option of making the global shortcuts
configurable or introducing all kinds of preferences for deviations
from the traditional behavior, and adding built-in preference sets
that make your Squeak behave like a legacy version ("Squeak 3.2
compatibility mode"). I would not be a fan of this, though.
Am 02.07.2018 09:14 schrieb "Tobias Pape" <[hidden email]>:
>> On 02.07.2018, at 01:54, Chris Muller <[hidden email]> wrote:
>> Hi Tobias,
>> All I did was restore the original shortcut keys that had been in
>> Squeak since its earliest days. I suppose I'm curious why you didn't
>> pose this question to the one who killed underline and strikeout
>> formatting but, for whatever reason, you seem to only "object" to MY
>> improvements. But whatever, instead of questioning my friendliness,
>> how about talking about what's good for Squeak and the IDE?
>> Hot keys are for functions that are used *frequently*. In a web
>> browser, zoom-in and out makes sense when every web page uses
>> different font sizes. That's not the case for Squeak. Setting
>> themes, colors, preferences and fonts is all part of initial
>> _configuration_, something typically done only once in the lifespan of
>> an image. Most wares mature enough to worry about font sizes have
>> since developed their own configuration script which sets everything.
>> Nevertheless, it's now on the World menu, which can be activated by
>> mouse OR keyboard.
>> This provides desktop keys for the font size but do you really think
>> this is useful? I can't think of any case where I'd want to be
>> frequently flipping back and forth between global font sizes once
>> they're set up. We should spare hot keys for future USEFUL things, so
>> I vote we do NOT move it to trunk.
> Well I frequently change between laptop screen, 24" monitor and projectors of > different resolutions.
> Changing font sizes is much more frequent for me than that text change. I see how that can be useful sometimes but I so not see how this is so universally useful. IMHO, something like Emacs M-x in the vein of "apply this string method to the selection" would be more versatile and at the same time cater for thing that are useful but relatively infrequent.
> Best regards
>> On Sun, Jul 1, 2018 at 6:21 PM, Tobias Pape <[hidden email]> wrote:
>>> Do I parse that correctly that you just killed font size handling via shortcuts and introduced a new one?
>>> While this could all be justified, wouldn't it be friendlier to first talk about that?
>>> Eg, via inbox or so?
>>> Best regards
>>> On Sun, Jul 1, 2018 at 6:35 PM, <[hidden email]> wrote:
>>>> Chris Muller uploaded a new version of Tools to project The Inbox:
>>>> ==================== Summary ====================
>>>> Name: Tools-cmm.826
>>>> Author: cmm
>>>> Time: 1 July 2018, 6:35:14.376257 pm
>>>> UUID: e7b1e100-7da9-48e8-b544-7a5035c0693e
>>>> Ancestors: Tools-cmm.825
>>>> Command++ and Command+- hot keys for increasing/decreasing the sizes of all fonts.
|Free forum by Nabble||Edit this page|