Looks like Pharo 7 will be the most impressive release in all aspects of system:).
About pragmas: I believe we should move to Commander with first class commands. It requires to create command classes for all menu items. For example "Save image": SaveImageCommand>>execute Smalltalk snapshot: true andQuit: false. SaveImageCommand class>>worldMenuActivation <classAnnotation> ^CmdContextMenuCommandActivation byRootGroupItemFor: *CmdWorldMenuContext * SaveImageCommand class>>globalShortcutActivation <classAnnotation> ^CmdShortcutCommandActivation by: $s meta shift for: *CmdWorldMenuContext * It will bring reusable commands which activation can be extended 2018-06-01 20:23 GMT+03:00 Peter Uhnák <i.uh...@gmail.com>: > On Fri, Jun 1, 2018 at 6:46 PM, Sean P. DeNigris <s...@clipperadams.com> > wrote: > >> Peter Uhnák wrote >> > Pharo adds 25px margin on all sides of a full-screen window. >> >> Good point. I wonder why that's the case! > > > According to the github issue discussion, this is the case. > > >> Peter Uhnák wrote >> > it provides the most important/common options that user needs >> >> Ah! Good to know and interesting, but presumably very subjective. > > > For sure. But for an end-user application it is my responsibility to > figure out the UI/UX. > > >> Although it is currently flexible, I don't think we have that now. >> > > The pragma collection can be filtered, but it is not used by the code, so > it is all-or-nothing, not very flexible. I think this is for future > iterations. > > Peter Uhnák wrote >> > very often I find myself having to move windows, just so I can expose a >> > piece of desktop to click on. >> >> Why don't you use the 25px margin?! ha ha j/k >> > > This applies to fullscreen only. It doesn't apply when you manually move a > window to this space. > And for fullscreen, I often have the margin disabled. So that's why. :) > > Peter >
