On Sat, Mar 3, 2018 at 12:47 AM, rengel <[email protected]> wrote:
> you might want to study the user interface of PyCharm ( https://www.jetbrains.com/pycharm/), especially their wording of menu entries and their 'Tools' menu. Good idea. It's on my list of things to do immediately. > If the Python console should be used, make it visible in the menu; don't bury it in the documentation. Actually, my intention is to make key features visible *directly*, not just in menus. I am going to enable the python_terminal plugin today, in both master and devel. Once that is done, the plugin will be visible in the plugins menu *and in the Log pane*. Terry and I are debating whether this should be moved to Leo's core, or remain a plugin. The issue, I think, is whether any related commands could be "baked in" to Leo's menus, or created dynamically by the plugin. I'm investigating, but there is so much going on right now that it may take a few days. Terry and I are also debating whether the valuespace plugin suffices. Imo, it does not, precisely because its way-cool features are hidden. I am investigating embedding an ipython terminal into Leo. That would make all of ipython's cool features *visible* as well as available. There's a big difference. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
