Re: Last call before deprecating the nested_splitter plugin

On Fri, May 24, 2024 at 5:03 PM Thomas Passin wrote: The plugin should be pretty easy to get working again, and it does not use > the nested splitter. One thing to know. It depends on an HTML template > file to load the CKEditor and the body content into the Qt widget. That > temp

Re: Last call before deprecating the nested_splitter plugin

. The plugin loads the Qt browser QWidget, loads the CKEditor code, and you can edit your node in full WYSIWYG glory. The plugin should be pretty easy to get working again, and it does not use the nested splitter. One thing to know. It depends on an HTML template file to load the CKEditor

Re: Last call before deprecating the nested_splitter plugin

On Friday, May 24, 2024 at 10:49:59 AM UTC-5 Edward K. Ream wrote: > I shall reinstate plugin, but I am not willing to fix it. Rev 0d2a7c4 <https://github.com/leo-editor/leo-editor/commit/0d2a7c4220da410ff413e83126a248c4ac6db7ef> in devel reinstates the plugin itself. #39

Re: Last call before deprecating the nested_splitter plugin

ile at rev cf89a85 on March 23 of this year. I probably deleted the file because it won't work with Qt6. The plugin uses QtWebKit. On March 25 the GitHub version of Leo started requiring PyQt6, so nobody has used this plugin with the GitHub version of Leo. #3930 <https://github.com/leo-edit

Re: Last call before deprecating the nested_splitter plugin

sent via email On Friday, May 24, 2024 at 12:29:43 PM UTC+1 Edward K. Ream wrote: > On Fri, May 24, 2024 at 5:59 AM jkn wrote: > >> jkn@tower:~/leo-editor$ find . -iname "*rich*" >> ./leo/plugins/richtext.py >> > > How strange. Please send me the file. > > Edward > -- You received this

Re: Last call before deprecating the nested_splitter plugin

On Fri, May 24, 2024 at 5:59 AM jkn wrote: > jkn@tower:~/leo-editor$ find . -iname "*rich*" > ./leo/plugins/richtext.py > How strange. Please send me the file. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Re: Last call before deprecating the nested_splitter plugin

:39 AM Thomas wrote: > > [The free_layout.get_top_splitter] method is used by the *richtext* > plugin as well as the flc itself. > > > Good catch. I'll convert the richtext plugin. > > > Where is this plugin? An external search for *text.py finds three files, > none of which looks

Re: Last call before deprecating the nested_splitter plugin

On Thursday, May 23, 2024 at 2:16:00 PM UTC-5 Edward K. Ream wrote: On Thu, May 23, 2024 at 10:39 AM Thomas wrote: [The free_layout.get_top_splitter] method is used by the *richtext* plugin as well as the flc itself. Good catch. I'll convert the richtext plugin. Where is this plugin

Re: Last call before deprecating the nested_splitter plugin

On Thu, May 23, 2024 at 10:39 AM Thomas Passin wrote: [The free_layout.get_top_splitter] method is used by the *richtext* plugin > as well as the flc itself. > Good catch. I'll convert the richtext plugin. Edward -- You received this message because you are subscribed to the Google

Re: Last call before deprecating the nested_splitter plugin

= f.top.findChild(*NestedSplitter*) *<* return child and child.top() return None This method is used by the *richtext* plugin as well as the flc itself. *qt_gui* also has a method by this name but it has been updated to return the 'main_splitter'. On Thursday, May 23, 2024 at 10:52:37 AM U

Re: Last call before deprecating the nested_splitter plugin

On Thu, May 23, 2024 at 7:00 AM Thomas Passin wrote: Is it correct that the "main" splitter is the one whose splitter bar runs > all the way either from top to bottom or from side to side, depending on > orientation? > Yes, kinda. But you shouldn't take my word for it. Consult the code! Search

Re: Last call before deprecating the nested_splitter plugin

Is it correct that the "main" splitter is the one whose splitter bar runs all the way either from top to bottom or from side to side, depending on orientation? On Thursday, May 23, 2024 at 5:10:32 AM UTC-4 Edward K. Ream wrote: > On Wed, May 22, 2024 at 5:50 PM Thomas Passin wrote: > > I'd

Re: Last call before deprecating the nested_splitter plugin

On Wed, May 22, 2024 at 5:50 PM Thomas Passin wrote: I'd like to have a command to place the log frame into its own panel next > to the body editor's. > ... > So there should be three built-in layouts instead of two, and there should > be a command or commands similar to

Re: Last call before deprecating the nested_splitter plugin

I think one thing is missing. I'd like to have a command to place the log frame into its own panel next to the body editor's. This layout has the tree pane vertically on the left, the body in the middle, and the log frame on the right. I'm sure I could come up with a script to do this, but I

Last call before deprecating the nested_splitter plugin

Imo, PR #3911 is ready to be merged into devel. Please let me know if you disagree. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: ENB: VR panes and the NestedSplitter plugin

shenanigans with the body/outline ratio are resolved to my satisfaction. Thomas, if the VR3 plugin rearranges panes, then VR3 must manage the new layout. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this grou

Re: ENB: VR panes and the NestedSplitter plugin

On Friday, May 10, 2024 at 1:13:54 PM UTC-4 Edward K. Ream wrote: On Friday, May 10, 2024 at 8:47:46 AM UTC-5 Thomas wrote: Going by last night's devel rev, VR was close to working as expected when I used the toggle command, at least with the particular layout I was using when I tried it.

Re: ENB: VR panes and the NestedSplitter plugin

On Friday, May 10, 2024 at 8:47:46 AM UTC-5 Thomas wrote: Going by last night's devel rev, VR was close to working as expected when I used the toggle command, at least with the particular layout I was using when I tried it. That's good to know. The branch for this PR, though, was a mess so

Re: ENB: VR panes and the NestedSplitter plugin

it to VR3 too, since this part of the code started out the same. On Friday, May 10, 2024 at 5:58:50 AM UTC-4 Edward K. Ream wrote: > This Engineering Notebook post discusses issues with the nested_splitter > (NS) plugin uncovered two days ago while working on #3892 > <https://github.co

ENB: VR panes and the NestedSplitter plugin

This Engineering Notebook post discusses issues with the nested_splitter (NS) plugin uncovered two days ago while working on #3892 <https://github.com/leo-editor/leo-editor/issues/3892>: Add VR commands to cover/uncover the body pane. I've been considering what to do ever since.

Re: mod_http plugin issue

On Tue, Nov 28, 2023 at 1:56 PM lewis wrote: > I have the mod_http.py plugin enabled in myLeoSettings.leo however when > Leo starts the log pane does not show the message 'http serving enabled at > 127.0.0.1:8130' > See #3682. <https://github.com/leo-editor/leo-editor/issue

Re: mod_http plugin issue

revise the code. On Tuesday, November 28, 2023 at 2:56:27 PM UTC-5 lewis wrote: > I have the mod_http.py plugin enabled in myLeoSettings.leo however when > Leo starts the log pane does not show the message 'http serving enabled at > 127.0.0.1:8130' > > http://localhost:8130/ in a browser

mod_http plugin issue

I have the mod_http.py plugin enabled in myLeoSettings.leo however when Leo starts the log pane does not show the message 'http serving enabled at 127.0.0.1:8130' http://localhost:8130/ in a browser is unable to connect and can’t establish a connection to the server at localhost:8130

ENB: About the indented_languages plugin

This Engineering Notebook post discusses an impractical project, the indented_languages plugin. Please feel free to ignore the plugin and this post :-) *tl;dr:* See the summary. *The indented_languages plugin* The indented_languages plugin (See #3574 <https://github.com/leo-editor/

Re: Mint/XFCE Update May Cause Viewrendered3 Plugin to Crash Leo

On Tue, Jun 13, 2023 at 9:55 AM Thomas Passin wrote: > It may even crash the whole system. This is not a bug in VR3, but some > disconnect between a XFCE change in the OpenGL graphics version and its > support. Other projects have had the same problem. The error message is > strange,

Mint/XFCE Update May Cause Viewrendered3 Plugin to Crash Leo

It may even crash the whole system. This is not a bug in VR3, but some disconnect between a XFCE change in the OpenGL graphics version and its support. Other projects have had the same problem. The error message is strange, supposedly from vmware: "vmw_ioctl_command error Cannot allocate

Re: Plugin xsltWithNodes.py Can no longer work

On Fri, Apr 21, 2023 at 10:42 PM Thomas Passin wrote: > The plugin requires a library that no longer exists (4Suite). Really? What about https://pypi.org/project/4Suite-XML/ > Is there a standard way to handle plugins that are too obsolete? Do they > move to the attic? I see

Plugin xsltWithNodes.py Can no longer work

The plugin requires a library that no longer exists (4Suite). Is there a standard way to handle plugins that are too obsolete? Do they move to the attic? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this grou

Re: Viewrendered3 plugin may not render nodes for some linux distros

On Thursday, January 12, 2023 at 10:36:51 PM UTC-6 tbp1...@gmail.com wrote: To be more specific, here's what I've installed that work - Thanks for these two detailed reports. I'm not overly surprised that Qt5 is flaky. Edward -- You received this message because you are subscribed to the

Re: Viewrendered3 plugin may not render nodes for some linux distros

To be more specific, here's what I've installed that work - PyQt6 6.4.0 PyQt6-Qt6 6.4.2 PyQt6-sip 13.4.0 PyQt6-WebEngine 6.4.0 PyQt6-WebEngine-Qt6 6.4.2 The packages you need to install are PyQt6

Viewrendered3 plugin may not render nodes for some linux distros

I have been spinning up several new Linux virtual machines, and I discovered that VR3 isn't rendering visibly. It's still working, since you can export the rendering to the browser, but nothing is painted on the VR3 panel. All these VMs use a recent version of Python3 with PyQt5. The PyQt5

Re: Viewrendered3 Plugin In A Tab?

On Sun, Apr 10, 2022 at 11:05 PM tbp1...@gmail.com wrote: > I have adapted the VR3 plugin to run in a tab in the log pane instead of > in its own pane. The way I did it, it's not strictly a plugin, but it has > all the same functionality. There is a script to toggle the tab

Viewrendered3 Plugin In A Tab?

I have adapted the VR3 plugin to run in a tab in the log pane instead of in its own pane. The way I did it, it's not strictly a plugin, but it has all the same functionality. There is a script to toggle the tab on or off, and a button to run the script. It was easy to make the change. I'm

Re: To Plugin or Not?

On Thu, Feb 24, 2022 at 12:22 PM tbp1...@gmail.com wrote: > I'd like to know what people think about the question of whether to turn this app into a plugin. The choice is yours. @button scripts, especially those that apply to a single outline need not ever become plugins. If, later, you

Re: To Plugin or Not?

Thanks for your thoughts. @jake. This app too will only make sense within the specific outline it's for. I thought it might be interesting to some other folks, otherwise I wouldn't even have considered turning it into a plugin. On Thursday, February 24, 2022 at 1:28:23 PM UTC-5 gates

Re: To Plugin or Not?

only make sense inside the one outline they live and work in. A plugin for those seems like overkill, especially if it would pollute the rest of my Leo session. But that's a tradeoff you'll have to think about for yourself. Jake On Thu, Feb 24, 2022 at 1:22 PM tbp1...@gmail.com wrote: > I

To Plugin or Not?

I am developing an Leo application that displays in a tab in the Log frame. Eventually it will probably use two tabs. The code lives in a new subdirectory in Leo's plugins directory. Currently this code is not a real Leo plugin, because it does not use the plugin machinery. Instead

Freewin Plugin Now Works With PyQt6

With the latest version of the devel branch, build c6baa0090b, the Freewin plugin has its full rendering capability under PyQt6. The PyQT6 version must be at least 6.23. You may also need to install PyQt6-WebEngine, which is available via pip from PyPI. The new version of FW is 1.8

Re: New picture_viewer.py plugin in devel

On Sat, Oct 23, 2021 at 12:38 PM tbp1...@gmail.com wrote: I now noticed that an initial path is already one of the *run(*) > arguments. Great! > :-) It's remarkable how simple all the methods are. Edward -- You received this message because you are subscribed to the Google Groups

Re: New picture_viewer.py plugin in devel

On Saturday, October 23, 2021 at 11:14:24 AM UTC-4 tbp1...@gmail.com wrote: > I'm also thinking it might be useful to be able to optionally specify the > target directory. > I now noticed that an initial path is already one of the *run(*) arguments. Great! -- You received this message

Re: New picture_viewer.py plugin in devel

Turns out you can set the initial zoom factor like this: from leo.plugins.picture_viewer import Slides Slides.scale = .5 Slides().run(c, reset_zoom = False) So no need to change any code. You must use reset_zoom = False for this to work. The one minor negative is that the window itself doesn't

Re: New picture_viewer.py plugin in devel

I tried the *width* argument, and I had expected that the aspect ratio would be the original. Instead, the width was set to my value but the original size was not changed. So the image was clipped in width. This is not very helpful. I'd rather see the zoom factor set so that the specified

Re: New picture_viewer.py plugin in devel

Oh, I see, those args are for *run()*, not the constructor. On Saturday, October 23, 2021 at 9:39:14 AM UTC-4 tbp1...@gmail.com wrote: > Those args in the docstring are not set in the *Slides* constructor: > > exception executing script > TypeError: 'reset_zoom' is an unknown keyword argument >

Re: New picture_viewer.py plugin in devel

Those args in the docstring are not set in the *Slides* constructor: exception executing script TypeError: 'reset_zoom' is an unknown keyword argument line 4: from leo.plugins.picture_viewer import Slides * line 5: Slides(reset_zoom = False, width = 900, sort_kind =

Re: New picture_viewer.py plugin in devel

On Fri, Oct 22, 2021 at 8:34 PM tbp1...@gmail.com wrote: > Here's my stab at it. Replace all the current text in the docstring ahead > of the binding and API information with the following: Done at rev 2f65d83

Re: New picture_viewer.py plugin in devel

On Fri, Oct 22, 2021 at 8:47 PM tbp1...@gmail.com wrote: > This is very nice, and one of the nice things about it is how it > automatically ignores non-image files without the user having to do > anything. > > A suggestion for better usability - after you zoom or shrink a slide, the > new zoom

Re: New picture_viewer.py plugin in devel

On Fri, Oct 22, 2021 at 10:52 PM tbp1...@gmail.com wrote: > In get_files(), there is > > os.path.splitext(str(z))[1].lower() in self.extensions > > I'm just wondering why it isn't g.os_path_splitext() instead. Are these > *g.os_path_** commands being phased out? (Actually, I never understood >

Re: New picture_viewer.py plugin in devel

ober 22, 2021 at 9:34:19 PM UTC-4 tbp1...@gmail.com wrote: > >> Here's my stab at it. Replace all the current text in the docstring >> ahead of the binding and API information with the following: >> >> Display image files in a directory tree as a slide show. >> &

Re: New picture_viewer.py plugin in devel

ext in the docstring ahead > of the binding and API information with the following: > > Display image files in a directory tree as a slide show. > > This plugin will display all files in a directory tree that have > image extensions. By default the recognized extensions are > '.jpeg', '.

Re: New picture_viewer.py plugin in devel

Here's my stab at it. Replace all the current text in the docstring ahead of the binding and API information with the following: Display image files in a directory tree as a slide show. This plugin will display all files in a directory tree that have image extensions. By default

Re: New picture_viewer.py plugin in devel

On Fri, Oct 22, 2021 at 10:59 AM tbp1...@gmail.com wrote: And I see from the PixMap docs that it can actually support some other > formats. > > You may think it's the same thing, but I suggest spelling out just what > the viewer can do would be helpful. > Ah, the curse of knowledge. Please

Re: New picture_viewer.py plugin in devel

On Fri, Oct 22, 2021 at 10:45 AM tbp1...@gmail.com wrote: > picture_viewer.py is in the plugins directory but not in LeoPyRef. > Thanks for this report. Rev 2693456 in devel adds the missing @file node. Edward -- You received this message because you are subscribed to the Google Groups

Re: New picture_viewer.py plugin in devel

Maybe the docstring said that at one time but it doesn't now : ). It says this: A plugin for displaying slides from a folder and its subfolders. And this: The following keyword arguments may be supplied to the run method: ... extensions = ['.jpeg', '.jpg', '.png'], # List of file extensions

Re: New picture_viewer.py plugin in devel

picture_viewer.py is in the plugins directory but not in LeoPyRef. On Friday, October 22, 2021 at 10:50:49 AM UTC-4 Edward K. Ream wrote: > On Fri, Oct 22, 2021 at 8:13 AM tbp1...@gmail.com > wrote: > >> What are the slides? Image files? HTML bullet files? >> > > Good question. As the

Re: New picture_viewer.py plugin in devel

On Fri, Oct 22, 2021 at 8:13 AM tbp1...@gmail.com wrote: > What are the slides? Image files? HTML bullet files? > Good question. As the docstrings says, by default the viewer will display all .jpeg, .jpg, and .png files in the root directory and all subdirectory. The *show_slide *method

Re: New picture_viewer.py plugin in devel

which >> contains the docstring. >> > > *Note*: there is no need to enable this plugin. The plugin exists only to > support scripts. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscri

Re: New picture_viewer.py plugin in devel

On Thursday, October 21, 2021 at 9:42:16 PM UTC-5 Edward K. Ream wrote: > See PR #2280 <https://github.com/leo-editor/leo-editor/pull/2280>, which > contains the docstring. > *Note*: there is no need to enable this plugin. The plugin exists only to support scripts. Edward -

New picture_viewer.py plugin in devel

See PR #2280 , which contains the docstring. My copy of myLeoSettings.leo contains @command nodes for slide shows. For example: *@command slides* from leo.plugins.picture_viewer import Slides Slides().run(full_screen = True, sort_kind =

Re: Discuss: remove VR2 plugin?

On Sat, Aug 21, 2021 at 1:17 PM tbp1...@gmail.com wrote: > Definitely remove it. Will do. Thanks for your comments. 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

Re: Discuss: remove VR2 plugin?

VR2 and VR3 plugins. > > At present, the VR2 plugin is marked as experimental. The plugin isn't > causing any problems, but having redundant code might be confusing. > > Thomas, are you good with retiring VR2? Any other comments? > > Edward > -- You received this message

Discuss: remove VR2 plugin?

If I am not mistaken Thomas has contributed both the VR2 and VR3 plugins. At present, the VR2 plugin is marked as experimental. The plugin isn't causing any problems, but having redundant code might be confusing. Thomas, are you good with retiring VR2? Any other comments? Edward -- You

Freewin V 1.3 Plugin Now In the Devel Branch

The user-noticeable changes in V 1.3 are: Add CNTL-F7 ability to copy our gnx to clipboard; CNTL-F9 now recognizes a gnx when preceded by '(' or '['; Use internal RsT stylesheet if @settings path does not exist. Just to recap recent improvements, the plugin chooses a light or dark

Re: Freewin - A Plugin That Provides Free Floating Edit/Render Windows

It is an excellent extension! Thanks! On Thursday, June 17, 2021 at 8:05:48 PM UTC+7 Edward K. Ream wrote: > On Wednesday, June 16, 2021 at 4:21:43 PM UTC-5 tbp1...@gmail.com wrote: > >> My new Freewin plugin has just been merged into the devel branch. This >> plugin will o

Re: Freewin - A Plugin That Provides Free Floating Edit/Render Windows

On Wednesday, June 16, 2021 at 4:21:43 PM UTC-5 tbp1...@gmail.com wrote: > My new Freewin plugin has just been merged into the devel branch. This > plugin will open a smaller-than-Leo window that is dedicated to showing the > node that was selected when the Freewin window was opene

Re: Freewin - A Plugin That Provides Free Floating Edit/Render Windows - Rational and Use

This plugin came from a long thread we had on Google Groups more than a year ago. The thread was about the possibility of using Leo as a "Zettelkasten", which translates as "Card Case". The thread is at Zettelkasten Thread <https://groups.google.com/g/leo-editor/c

Re: Freewin - A Plugin That Provides Free Floating Edit/Render Windows - Styling

be fixed when the Qt6 WebEngineView component is released, if not before. My next post will cover the rationale for the plugin design, how I expected to use it, and and some other uses I have already found to be convenient. On Wednesday, June 16, 2021 at 5:21:43 PM UTC-4 tbp1...@gmail.com wrote

Freewin - A Plugin That Provides Free Floating Edit/Render Windows

My new Freewin plugin has just been merged into the devel branch. This plugin will open a smaller-than-Leo window that is dedicated to showing the node that was selected when the Freewin window was opened. This window is provides a plain editing view, and can be switched to provide a view

Re: The ekr-1591 branch works around icons problems in the todo plugin

On Wednesday, November 11, 2020 at 5:57:25 AM UTC-6 Edward K. Ream wrote: > The ekr-1591 branch > is ready for > testing. This branch fixes #1591 > : Todo icons are > not shown for

The ekr-1591 branch works around icons problems in the todo plugin

The ekr-1591 branch is ready for testing. This branch fixes #1591 : Todo icons are not shown for pyqt 5.14. For full details, see PR #1728.

Re: view-rendered plugin and mermaid.js

Ok, so this helped, thank you - but I still wasn't able to undock it from an existing window, but in other docs I was able to move it around.I was able to reset the local cache (db folder) and IT'S WORKING!! :-D Thanks so much for your help guys. - Kevin On Thu, 2020-08-13 at 18:13 -0700,

Re: view-rendered plugin and mermaid.js

On Thu, Aug 13, 2020 at 1:31 PM Thomas Passin wrote: > Now that I've looked at mermaid a little more, I think that you could > write the mermaid diagram syntax in a Leo node - since it's just text - > ,and then run Mermaid on it using the command line version of mermaid. > That sounds like the

Re: view-rendered plugin and mermaid.js

There is a setting in LeoSettings : *@bool use-vr-dock = False* * True: The VR dock is (can be) moved.* * False: (Recommended) The VR dock splits the body dock.* * *Warning*: You may have to clear caches if you change this setting.* Add that setting to your myLeoSettings file, set to True.

Re: view-rendered plugin and mermaid.js

On Thursday, August 13, 2020 at 7:01:56 PM UTC-4, k-hen wrote: > > This worked! I was able to get it for a new test file BUT the > original file has VR3 docked *inside* the body and I can't seem to detach > it. > It seems these settings are on a per-file basis, but there's nothing I can

Re: view-rendered plugin and mermaid.js

This worked! I was able to get it for a new test file BUT the original file has VR3 docked *inside* the body and I can't seem to detach it.It seems these settings are on a per-file basis, but there's nothing I can see saved within the document on positioning. Is there a way I can reset the

Re: view-rendered plugin and mermaid.js

You need to have Docutils installed to have VR3 render Restructured text, and you need Markdown installed to render (no surprise here) markdown. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: view-rendered plugin and mermaid.js

On Thursday, August 13, 2020 at 6:22:54 PM UTC-4, k-hen wrote: > > Ok, thanks! I've got this going, the docks feature is interesting. > Strangely I can move the body and the tabs, but not the VR3 panel... > I've tried restarting & redragging it a few times but still no luck :-/ > Add a node

Re: view-rendered plugin and mermaid.js

ut > viewrendered.py and add or uncomment viewrendered3.py. Then restart > Leo. Actually, you could run both plugins, but it's less confusing > and a better use of screen real estate not to. > > I don't recall if the version of the plugin in Leo 6.2.x final is the > same as its

Re: view-rendered plugin and mermaid.js

ke it might be something that I'd like using myself. > > > On Thursday, August 13, 2020 at 1:32:49 PM UTC-4, Thomas Passin wrote: >> >> The VR3 plugin can display the diagram outputs. It wouldn't update >> automatically when you made a change - you would have to ref

Re: view-rendered plugin and mermaid.js

to viewrendered3 if you decide that Leo is promising enough for your project. It looks like it might be something that I'd like using myself. On Thursday, August 13, 2020 at 1:32:49 PM UTC-4, Thomas Passin wrote: > > The VR3 plugin can display the diagram outputs. It wouldn't

Re: view-rendered plugin and mermaid.js

e to get mermaid.js [ >>> https://mermaid-js.github.io/] working via the view-rendered plugin. >>> >> >> Thanks for the link to mermaid! >> >> Leo doesn't do js directly, so I don't think the vr plugin is likely ever >> going to support merm

Re: view-rendered plugin and mermaid.js

bled plugins. Comment out viewrendered.py and add or uncomment viewrendered3.py. Then restart Leo. Actually, you could run both plugins, but it's less confusing and a better use of screen real estate not to. I don't recall if the version of the plugin in Leo 6.2.x final is the same as its cur

Re: view-rendered plugin and mermaid.js

I don't mind refreshing at all. Pardon the naive question, but how would I go about trying VR3? On Thursday, August 13, 2020 at 1:32:49 PM UTC-4 tbp1...@gmail.com wrote: > The VR3 plugin can display the diagram outputs. It wouldn't update > automatically when you made a change - you

Re: view-rendered plugin and mermaid.js

The VR3 plugin can display the diagram outputs. It wouldn't update automatically when you made a change - you would have to refresh the plugin view to see that changed image. It *may* be possible to get mermaid to run in a panel inside Leo. It could be launched using graal, and Leo can

Re: view-rendered plugin and mermaid.js

, Edward K. Ream wrote: > > On Thu, Aug 13, 2020 at 8:21 AM k-hen > > wrote: > > I was wondering if it's possible to get mermaid.js [ >> https://mermaid-js.github.io/] working via the view-rendered plugin. >> > > Thanks for the link to mermaid! > > Leo doesn

Re: view-rendered plugin and mermaid.js

On Thu, Aug 13, 2020 at 8:21 AM k-hen wrote: I was wondering if it's possible to get mermaid.js [ > https://mermaid-js.github.io/] working via the view-rendered plugin. > Thanks for the link to mermaid! Leo doesn't do js directly, so I don't think the vr plugin is likely ever going to s

view-rendered plugin and mermaid.js

Hi All, I was wondering if it's possible to get mermaid.js [https://mermaid-js.github.io/] working via the view-rendered plugin. It's also possible that I'm just missing something. I'm aware that it works through LeoVue (which is awesome) but I'd really like to see it in the native editor

Re: vs code plugin: git graph

On Wed, Jul 29, 2020 at 10:24 PM Félix wrote: > It's suggested to (and easy once you're familiar with the api,) add buttons into other extension's (or default) views and panels, I didn't know that was possible. That's a way cool feature. > I'm going to try it out and correct myself if needed!

Re: vs code plugin: git graph

> various features and extensions. > > With one or more git extensions enabled, there is an icon that looks like > an upside-down tree. It also contains a number showing how many changed > files there are. > > What I meant was that I was expecting to see some visual indicat

Re: vs code plugin: git graph

ows us to show/hide icons for the various features and extensions. With one or more git extensions enabled, there is an icon that looks like an upside-down tree. It also contains a number showing how many changed files there are. What I meant was that I was expecting to see some visual indication of the git

Re: vs code plugin: git graph

graph > <https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph> > plugin. It's *much* better than gitk or anything else I have seen. > Mission accomplished! > > The only glitch: By default it looks like you have to execute the "View > Git Graph" command

vs code plugin: git graph

At last, an easy way to visualize git branch structure: the git graph <https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph> plugin. It's *much* better than gitk or anything else I have seen. Mission accomplished! The only glitch: By default it looks like you have to e

Heh: how to find the source code for any vs code plugin

You can see the source code for any vs code plugin without having to install it: - In vs code, click the plugins (building blocks) icon on the left. - Search for the plugin. - Selecting the plugin opens a corresponding extension's tab. - All plugins have a "Repository" button in the e

Re: warning viewrender3.py plugin has been commited with unresolved conflicts.

Right, and Edward has already asked me to clear this up. On Wednesday, April 1, 2020 at 11:38:11 AM UTC-4, vitalije wrote: > > Title tells everything. While executing unit tests, two are failing: check > syntax of all files and pluginTestCase for viewrender3. > > Vitalije > -- You received

warning viewrender3.py plugin has been commited with unresolved conflicts.

Title tells everything. While executing unit tests, two are failing: check syntax of all files and pluginTestCase for viewrender3. Vitalije -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails

Re: history tracer plugin

Thanks for the confirmation. Vitalije On Monday, March 9, 2020 at 6:35:22 AM UTC+1, Matt Wilkie wrote: > > I've just published the new version of leo-ver-serv on crates.io. The >> version 1.8 includes both the fix for the Windows and also has automatic >> refresh after more than 10s of

Re: history tracer plugin

> > I've just published the new version of leo-ver-serv on crates.io. The > version 1.8 includes both the fix for the Windows and also has automatic > refresh after more than 10s of inactivity. > v1.8 confirmed working on my Win10 machine. Thanks! -matt -- You received this message because

Re: history tracer plugin

On Sat, Feb 29, 2020 at 3:15 AM vitalije wrote: > I've just published the new version of leo-ver-serv on crates.io. The > version 1.8 includes both the fix for the Windows and also has automatic > refresh after more than 10s of inactivity. > Thanks, Vitalije. Edward -- You received this

Re: history tracer plugin

I've just published the new version of leo-ver-serv on crates.io. The version 1.8 includes both the fix for the Windows and also has automatic refresh after more than 10s of inactivity. If the page looses focus for more than 10s, it will refresh automatically once it regains focus. Vitalije

Re: history tracer plugin

There used to be a bug on Windows where sending the list of Leo files to the front end included '\n\r' but the front end was expecting just '\n'. I know that I have fixed this bug, but perhaps I didn't push the changes to the crates.io and cargo install command uses the old version without this

Re: history tracer plugin

Can you tell me more about your problem on Windows? Am I correct to assume that leo-ver-serv is running and accepting snapshots on both Windows and Linux? You wrote that there is no activity in the browser. Have you tried reloading page? Does the input for selecting Leo file has expected

  1   2   3   4   5   6   7   8   9   10   >