Forum Posts Feed
Visual Outliner (new from the developer of Goal Enforcer)
< Next Topic | Back to topic list | Previous Topic >
Posted by washere
Nov 15, 2018 at 03:11 PM
Thanks tightbeam, if John Lennon was alive & into outlining his songs & ideas with apps, he may say regarding a dream global interchangeable tree data-format across apps:
Imagine…
Posted by Rochus
Nov 15, 2018 at 08:27 PM
washere wrote:
+ PRICE:
>+ OPML
>
> - It’s the best Tree Outliner Structure file format there is. I’ve
>tested nearly a thousand software in the last three years.
>
> - My recommendation for devs is to:
> - Use OPML Version 1, NOT Version 2
> - Only use the two minimum tags, for node title/name and node text data.
> - Tree Structure (nodes, sub node levels)? OPML is basically a
>simple cut down version of html. Levels are basically nested node tags
>inside each other. Nothing to do, no tags, just nesting.
>
Thanks for your detailed submissions. I consider implementing OPML 1 in CrossLine as an import/export file format. There only seem to be small OPML example files available. Do you have a decently large file having the features you recommend and which you could give away?
Posted by washere
Nov 15, 2018 at 10:35 PM
Rochus wrote:
washere wrote:
......................
>Thanks for your detailed submissions. I consider implementing OPML 1 in
>CrossLine as an import/export file format. There only seem to be small
>OPML example files available. Do you have a decently large file having
>the features you recommend and which you could give away?
Hi Rochus,
Thanks. I find your works intriguing and innovative.
OPML V1, with only the main 2 tags and nested structure is very simple and anyone here can learn it in 2 minutes, never mind expert coders like you.
The file size does not matter as long as the nesting does not break scope like other html nesting tags (li, url etc etd).
For example a simple 2 node tree code is below here, 1st node has a sub-node and a sub-sub-node, the 2nd node in the tree has only root node but is mulit-line. The Code would be:
##################################################################
##################################################################
That’s it. I have given info on this to several devs publicly or by email. One I can remember is linked below.
I showed how one can stick to a few rules (of course also less work too fortunately), plus use some apps to generate or check sample OPML code.
The main things to remember:
1) Just use the 2 OMPL tags
2) Nest node levels properly, don’t break nesting
3) Avoid temptation to add further OMPL v1 & v2 tag options
These few rules not only make the work a lot easier and a lot less in volume, but they will also ensure this mini-me version of OPML v1 will be read by almost any app that pretends to import OPML.
In my experience because so many OPML versions/varieties are out there, in reality just under half OPML import/exports across apps are successful as a result.
https://github.com/zadam/trilium/issues/78
Posted by washere
Nov 15, 2018 at 10:46 PM
As I suspected, the forum software attempted to embed the OPML code in my last post, probably as Markdown or similar. So:
############################################
https://ibb.co/mcDP70
or
https://pastebin.com/Vm1sntKi
############################################
Posted by Rochus
Nov 15, 2018 at 11:27 PM
> washere wrote:
Thank you very much for your explications.
>The file size does not matter as long as the nesting does not break
>scope like other html nesting tags (li, url etc etd).
It’s not about the file size; but if I have externally validated data of reasonable size I can use it to develop and test my parser/importer and can be sure that I have seen and corrected most of the issues.
>
If the outline item is either a title or a text, I can create an outline tag with either a title or a text attribute, right?
>3) Avoid temptation to add further OMPL v1 & v2 tag options
Ok; of course text formatting and embedded images get lost, only plain text is exported.
>be read by almost any app that pretends to import OPML.
By the way: have you noticed that CrossLine can import HTML files and translates the title structure to outline levels? Here is an example: http://software.rochus-keller.info/WarAndPeace.cldb.zip. I downloaded and imported the HTML version of War and Peace from http://www.gutenberg.org/files/2600/2600-h/2600-h.htm as recommended in http://www.organizingcreativity.com/2018/02/what-makes-a-good-outliner .