Attached: two-column OmniOutliner Pro OPML file.
Chris
On Wednesday, August 31, 2022 at 5:06:53 PM UTC+2 tbp1...@gmail.com wrote:
> Here is Dave (Winer)'s spec <http://opml.org/spec2.opml>. I would think
> that there would be an XML schema (or maybe a DTD would be able to the the
> joib) somewhere that could be used for validating an OPML file, but I
> didn't find one in a very hasty search.
>
> Since OPML only includes what Leo calls headline text, I'm wondering if
> there would ever be any use for text in (Leo) node bodies. An OPML outline
> node can contain other information besides the headline text, so maybe
> that's why the plugin may deal with Leo's user attributes - the info has to
> go somewhere.
>
> Is it the case, @chr, that you want to round-trip OPML files with other
> applications with full fidelity (except maybe data about an editor's
> state)? Or do you only need to include a subset of information?
>
>
>
> On Wednesday, August 31, 2022 at 10:13:37 AM UTC-4 chr...@gmail.com wrote:
>
>> I found only one public one at http://validator.opml.org/ (website and
>> validator by Dave Winer, the original OPML guy, still at the wheel), but it
>> doesn't seem to work so well.
>> I submitted an issue at
>> https://github.com/scripting/opml.org/issues/6#issue-1357384900
>>
>>
>> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com wrote:
>>
>>> Shouldn't be hard to adjust the output format, I would think (not
>>> knowing anything about the actual plugin). Do you know of an OPML
>>> validator so potential fixes could be tested?
>>>
>>> On Tuesday, August 30, 2022 at 12:11:37 PM UTC-4 chr...@gmail.com wrote:
>>>
>>>> That's what I did, and the resulting file was not OPML. Check my
>>>> previous message:
>>>> https://groups.google.com/g/leo-editor/c/bV98DK9QtPI/m/m7bLQioQCgAJ
>>>>
>>>> On Tuesday, August 30, 2022 at 5:07:08 AM UTC+2 tbp1...@gmail.com
>>>> wrote:
>>>>
>>>>> Without knowing anything about the plugin, it looks like the signature
>>>>> of fc.write_leo_file() is currently not the signature the plugin
>>>>> thinks it is. I'd try commenting out the extra params in the plugin, and
>>>>> see what what you get:
>>>>>
>>>>> ok = self.c.fileCommands.write_Leo_file(
>>>>> fileName#,
>>>>> #outlineOnlyFlag=not self.opml_write_derived_files,
>>>>> #toString=False, toOPML=True
>>>>> )
>>>>>
>>>>> You would have to restart Leo, or run a new Leo session, to try the
>>>>> changes out.
>>>>> On Monday, August 29, 2022 at 6:15:29 PM UTC-4 chr...@gmail.com wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> If you want you can skip to "*Problem*" below.
>>>>>>
>>>>>> I'm new to Leo but not to Python, and not to the world. For 30
>>>>>> years, I've been trying to recapture the magic of MORE (and
>>>>>> ThinkTank...) ,
>>>>>> but on Windows (had to switch in 1989, never used a Mac since). No way.
>>>>>> Recently got fed up, got a Mac Mini M1, an iPhone and iPad, bought
>>>>>> OmniOutliner, but I now only use it on IOS to exchange OPML files with
>>>>>> Windows because _BREVITYALERT_. Even though I got to a decent level in
>>>>>> Python, I never tried LEO because _BREVITYALERT_
>>>>>>
>>>>>> But THIS IS THE ONE. Wow!
>>>>>>
>>>>>> *Problem*
>>>>>> Of course, my first message is also about a problem. I'm pretty sure
>>>>>> I got the leoOPML.py plugin configuration right (file, tree, directives,
>>>>>> body panel), but when I type *write-opml-file* in the mini-buffer
>>>>>> (and by the way this procedure seems to be nowhere on leoeditor.com
>>>>>> or davy39.github.io/leo-editor/apidoc/leo.plugins.html. Thanks,
>>>>>> Google),
>>>>>> I get this:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Traceback (most recent call last): File
>>>>>> "C:\Python310\lib\site-packages\leo\core\leoKeys.py", line 2521, in
>>>>>> callAltXFunction func(event) File
>>>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in
>>>>>> writeOpmlCommand c.opmlCommands.writeFile(fileName) File
>>>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in
>>>>>> writeFile ok = self.c.fileCommands.write_Leo_file(TypeError:
>>>>>> FileCommands.write_Leo_file() got an unexpected keyword argument
>>>>>> 'outlineOnlyFlag'*
>>>>>> everytime, either with my own narrow set of parameter plugins or
>>>>>> with the one in leosettings.leo.
>>>>>>
>>>>>> I went through the plugin code, tried to remove line 321, but then
>>>>>> *Tostring=False* became unexpected too. Then I tried to learn about
>>>>>> *c.filecommands*, but I thought it better to join the group and
>>>>>> write this.
>>>>>> ???
>>>>>>
>>>>>> Thanks in advance for help,
>>>>>>
>>>>>> Chris
>>>>>>
>>>>>
--
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/f82f415f-8e60-4fbf-ba5f-9d203cf11628n%40googlegroups.com.
<?xml version="1.0" encoding="UTF-8"?>
<opml version="2.0">
<head><!-- <editor>
<sidebar width="203"/>
<column name="text" width="242"/>
<column name="Col2-Bodypane" width="150"/>
</editor> -->
<title>Document (1)</title>
<expansionState>0,3,4,7,8,9,12,13,14</expansionState>
<vertScrollState></vertScrollState>
<windowTop>0</windowTop>
<windowLeft>0</windowLeft>
<windowRight>682</windowRight>
<windowBottom>684</windowBottom>
</head>
<body>
<outline text="headline 1" Col2-Bodypane="Body text 1">
<outline text="headline 1.1" Col2-Bodypane="Body text 1.1"/>
<outline text="headline 1.2" Col2-Bodypane="Body text 1.2"/>
</outline>
<outline text="headline 2" Col2-Bodypane="Body text 2">
<outline text="headline 2.1" Col2-Bodypane="Body text 2.1">
<outline text="headline 2.1.1" Col2-Bodypane="Body text 2.1.1"/>
</outline>
<outline text="headline 2.2" Col2-Bodypane="etc."/>
</outline>
<outline text="headline 3" Col2-Bodypane="etc.">
<outline text="headline 3.1" Col2-Bodypane="etc."/>
<outline text="headline 3.2" Col2-Bodypane="etc.">
<outline text="headline 3.2.1" Col2-Bodypane="etc."/>
<outline text="headline 3.2.2" Col2-Bodypane="etc."/>
<outline text="headline 3.2.3" Col2-Bodypane="etc.">
<outline text="headline 3.2.3.1" Col2-Bodypane="etc.">
<outline text="headline 3.2.3.1.1" Col2-Bodypane="etc.">
<outline text="headline 3.2.3.1.1.1" Col2-Bodypane="etc."/>
</outline>
</outline>
</outline>
</outline>
<outline text="headline 3.4" Col2-Bodypane="etc."/>
</outline>
<outline text="headline 4" Col2-Bodypane="etc."/>
</body>
</opml>
