> > > > > 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*. > Does this imply that every outline opened has its own Python console? If you put the console in the Log pane, IMHO, you might create a 'hierarchy clash'. As I understand the Leo UI, the three panes (Outline, Log, Editor) always *belong to one and the same* outline. A Python console that serves all outlines opened would break this design. Again, PyCharm has a solution for this problem: In PyCharm, if you hover above the left-most button in the status bar, a list of tools is presented (among them a Python console). If chosen, the Python console is opened below the other panes, with its *own vertical toolbar* to the left. Reinhard > -- 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.
