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 > template file

Re: Last call before deprecating the nested_splitter plugin

I looked at this a bit. It swaps in an instance of the CKEditor for the Leo body editor. CKEditor is a commercial product whose most basic level is under the GPL2 license, and so can be used at no charge. It's written in javascript and runs in a browser. It's a WYSIWYG )(rich text) editor.

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 in devel reinstates the plugin itself. #3931

Re: Last call before deprecating the nested_splitter plugin

On Friday, May 24, 2024 at 6:29:43 AM UTC-5 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. Mystery partly solved. gitk reports that I deleted that file at rev

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

jkn@tower:~/leo-editor$ find . -iname "*rich*" ./leo/plugins/richtext.py on my system... On Friday, May 24, 2024 at 11:42:49 AM UTC+1 Edward K. Ream wrote: > 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

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? An

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 Groups

Re: Last call before deprecating the nested_splitter plugin

Speaking of which, the free layout controller still has this method: def get_top_splitter(self) -> Optional[Wrapper]: """Return the top splitter of c.frame.top.""" f = self.c.frame if hasattr(f, 'top') and f.top: child = f.top.findChild(*NestedSplitter*) *<*

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