As a proof of principle, I have already adapted VR3 to run in tab. It didn't take many changes.
On Tuesday, March 22, 2022 at 8:58:59 AM UTC-4 gates...@gmail.com wrote: > I wrote the nodetags.py plugin, and a few others that use new log-pane > tabs (nodewatch, the terribly broken interactive python terminal plugin, > etc.) :) > > Tabs are great. I've long wished that the body pane was tabbed -- > would've made one of my personal "Leo Apps" much easier to implement. > > On Tue, Mar 22, 2022 at 7:51 AM tbp1...@gmail.com <tbp1...@gmail.com> > wrote: > >> >> Let's start with the Log pane. Whoever came up with it had a brilliant >> idea. Most users are probably familiar with the Find and Nav tabs, and >> possibly the Completion and Spell tabs. You click on a tab and get a >> completely different view. What you may not realize is that a tab is just >> the display device for an entire mini-application, in the form of scripts >> and a set of one or more "widgets". To hook it into the log pane with its >> own tab is remarkably simple, programming-wise - this is the brilliant >> part. You just give the top-level widget and a tab name to the log pane >> and the pane sets up all the tab and switching machinery for you. So a tab >> could contain almost anything - a web browser, a dictionary, you name it. >> If it has a single top-level display widget and code behind that, it can >> get its own tab in the log pane. The scripts for the tab have access to >> all of Leo's code and data, so they can do just about whatever they like. >> Tabs can be installed by plugins, bit also by non-plugin scripts. >> >> -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/4d869fd3-11d0-4dca-9c93-f720d6e4844dn%40googlegroups.com.
