On Saturday, February 15, 2020 at 5:06:30 PM UTC-5, andyjim wrote: > > > 3. Simple Section Demarkations > For distraction-free creative/productive activity I'd like to be able to > optionally see only the text body, or, (and maybe the following belongs > under Display) in a collection/stack of zettels, or only the first lines, > or only the titles, or only the links, or only the citations or other > reference types. >
If one Leo node represents one zettel, the normal view in Leo would be just the text. We'd have to do something special to display anything else in the editing pane (usually called the "body" pane). The real question will be how to show some of the other metadata. Conceivably we could show it in a rendering pane. That might be the easiest thing to get going. Otherwise, we could add a new tab to the "Tabs" panel to show metadata. Bear in mind that we could start one way, and later if it seems worth the effort, develop something else. It wouldn't change the data that Leo stores. > Editor: > In my ideal world I might add a category to this list: Editor. My > idealized editor displays in rendered text, controlled more or less as a > word processor does, e.g. Ctl-I for italic (though I don't need and don't > want the accompanying bells and whistles of a word processor, 'just the > rendered text please'). > > This, I think, would significantly enhance creativity because with no > intervening (and distracting) step I get the immediate benefit of the > clarity that enhanced formatting gives, plus it eliminates from the display > all distracting markdown/coding, plus it eliminates me having to think in > markdown and type in markdown (distractions, distractions). > > YET, this wonderful interpretive, self-rendering editor stores the file in > text/markdown so it's transferable, or forward-compatible (as I have come > to like to put it). So when you read the file in a plain text editor (and > my ideal editor optionally displays and operates in plain text/markdown as > well), the markdown is there. But when rendered in the editor it's in > rendered mode and you edit directly in rendered mode with word-processor > style key commands. > All the markdown-type editors I've seen have you type in plain text, and they show the rendered view. After all, it's the main point of Markdown, etc., that you can just type plain text. If you want to type fully rendered text, well, you are getting into a word processor. You can easily set up Leo so that you can open a file (a Leo sub tree that's being saved in a file) or a specific node in an editor of your choice. If it's a file that's saved by Leo, then when you save it in the external editor, Leo knows that and can update it in the Leo outline. I don't know, however, if there are any markdown editors that work by typing directly into a rendered version and then save it in markdown form. We can look at that. > > Ok, here is a wild thought: Leo has a real time renderer, right? All we > gotta do then, in my ideal world, is rig key commands and allow the user to > work directly in the render pane, with the ability to toggle with the > regular body pane, either overlaid or side by side. > Easy for me to say from my vantage point as a non-programmer. My > imagination lives in joyous, unfettered freedom by the simple device of not > knowing what can't be done. > > Editing directly in the rendering pane is a whole other story. Normally the editing and rendering panes are laid out side by side, and you can only type into the editing pane. I'd suggest that anything more would be something to look at after we've got some experience on a basic system. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/63170eee-cd0b-4707-8fd8-e3ece2016c57%40googlegroups.com.
