Add buttons? #3122
Replies: 3 comments 4 replies
-
|
I'd call that a clickable menu bar as the first row, but I like the idea. Or at the bottom (more like editors like Update: Nano calls this their "Shortcut list", https://www.nano-editor.org/dist/v2.0/nano.html#Shortcut-Lists "The Shortcut Lists are the two lines at the bottom of the screen which show some of the more commonly used functions in the editor." -- this is incredibly helpful for novices and is one of the reasons nano is often used on training courses introducing the terminal. For example, in Software Carpentry workshops - see e.g. https://swcarpentry.github.io/shell-novice/03-create.html#create-a-text-file |
Beta Was this translation helpful? Give feedback.
-
|
I am not sure if you are suggesting to display key bindings at the bottom of the screen, but they can be displaed or hidden when pressing Alt+G. However, nothing happens when clicked. |
Beta Was this translation helpful? Give feedback.
-
|
I didn't know about |
Beta Was this translation helpful? Give feedback.
-
|
There is this comment suggesting ways micro could provide new overlays to plugins. I do not currently have enough time and interest to read and think about new UI features, but I was thinking someone could use the suggested feature to make a plugin where context menus (different with menu bars) could be opened and used with mouse. It does not seem like overlays have been discussed and approved much, so no one may have implemented it yet. I think it may take a while to properly make and review implementations. There have also been other discussion threads and issues about adding menus or buttons, so I think they should be linked to one thread sometime. |
Beta Was this translation helpful? Give feedback.
-
|
I believe that those types of menus do not fit terminal text editors; perhaps they do in GUI applications. |
Beta Was this translation helpful? Give feedback.
-
|
I think so too, because there may not be much people that would use menus in micro. There will have to be a lot more code maintained too if GUI elements like menus are added, so I think it is better if adding at least context menus is left to a plugin like mentioned in my comment. Overlays could be used to implement GUI elements in plugins without including them in micro, so it may be more likely that overlays would be added when there is an implementation. |
Beta Was this translation helpful? Give feedback.
-
|
The home page boasts "Micro has full support for the mouse." which to some people (e.g. me) would suggest any menus and lists would be clickable and scrollable with the mouse-wheel. Micro with the alt-g bindings display on resembles the older nano and pico editors (which also use mainly ctrl-options), but as far as I know, they lack any real mouse support. If it helps, I am picturing the key-binding list as akin to a top-of-window menu (traditionally fully keyboard accessible with Alt keybindings in DOS/Windows), and the more recent ribbon UI (both typically at the top of the screen). Early word processors like WordStar and Word for DOS are perhaps closer to today's terminal editors than their GUI descendants. (If it makes more sense to keep this kind of thing in plugins, that's fine - I don't know about the micro internals) |
Beta Was this translation helpful? Give feedback.
-
Since the mouse can be used to move your typing position in micro, why not add button? It could look like this...
You can click on File and then have the option to save the file, open the file, etc. The buttons will just be word, nothing fancy.
Beta Was this translation helpful? Give feedback.
All reactions