2015-07-05 11:46 GMT+02:00 Peter Uhnák <i.uhnak@gmail.com>:
I was looking at https://pharo.fogbugz.com/f/cases/edit/15237/Spec-TextModel-for-plain-text and it seems that we have (at least ) three different menus.
TextEditor class>>yellowButtonMenu (TextModel for editing text)
â âSmalltalkEditor class>>yellowButtonMenu (default TextModel, for code)
â RubSmalltalkCodeMode class>>menuOn: (Playground)
â Since we have already disabled code completion in TextModel some time ago I would propose to set TextEditor's menu by default, and have the Code one only explicitly (through #beForCode which would also enable the default codeCompletion).
Shortcuts interestingly work even without the menu, so it shouldn't break people's workflow (e.g. you could still inspect things and so forth).
The cleaner way would be to use TextEditor as default EditorClass in TextModel "beForText" and SmalltalkEditor for "beForCode". With that, the menublock coude ask the editor class for the default menu (now it uses SmalltalkEditors menu as default)
Anyone has any objections?
Peter
