On Thu, Oct 11, 2018 at 1:19 PM Offray Vladimir Luna Cárdenas < [email protected]> wrote:
> I think that converting Leo to other languages makes little sense from a > practical point, but exploring Leo ideas in other environments makes a lot > of sense (and viceversa). > I agree. > What I would like to see is more decoupling between the different parts of > Leo, and Leo offering "outlining" services to data and documents coming > from different places (including Jupyter notebooks, the file system, > internet, data bases and so on). > Yes. I think this is on the main line of the big dreams discussion. > This is difficult, because there is a tension between providing an > integrated experience easy for beginners and decoupling Leo so it can offer > its advantages to other communities and users. So my approach would be to > select specific communities and enhance Leo for them, starting with the Leo > community itself and the proposal for outlines exemplifying particular > workflows for users. I will try to expand a little bit on this: > > - Maria is a writer. She will like to use Leo to write prose and > organize her writings. So she creates a Leo outline and starts to write > several places of her work: characters, plot and publishing. For each of > those she creates a Leo node and puts more children nodes, showing all > characters, the plot parts and subplots and the publishing artifacts: a > book in PDF and EPUB formats. Maria uses Leo clones when she needs to > showcase how different parts of her work are connected and combines light > formats for describing what she is doing: YAML for characters and their > attributes and Markdown for prose in plot and publishing. Because Leo > support all this formats and also directives, buttons and scripts, Maria is > able to create the publishing she wants and automatize the process to focus > in what she cares about: good storytelling. She can share a .leo document > template so other writers can benefit from her workflow. The more technical > part of the template (directives, buttons and scripts) was created with the > help of the Leo community, where Maria started to share their early > templates without any automatic behavior. > > This should be doable, with relatively minimal effort. We would want buttons to export/save to pdf, epub and yaml. > > - Gonzalo is a developer. He needs to read and understand code wrote > by others and to adapt some pieces for his own needs and create new scripts > that can be used with other code to suits his needs... > > c.recursiveImport is the main tool for this. It's the foundation of recursive import scripts. Just yesterday I found some more bugs in c.recursiveImport, while I was studying the neovim code. > > - Rosana is a data scientist. She needs to load data from several > sources and experiment with it interactively by making queries and > visualizations... > > This is likely the most challenging for Leo at present. Imo, we want better tools for dealing connecting with other environments in separate processes. Once we have the different user stories, we try to see how Leo in its > actual form can help to this people or how need to be changed. The > important part of the stories is to think that all different Leo users are > creating outlines and hope to see a particular behavior to make their life > easier. We could try to track the original outlines and how they were > changed with the help of the community and also how some functionality was > incorporated in Leo to make it more usable for them. > Well, this is the endless documentation problem. > For example live Markdown rendering could be enabled by writing something > in the Leo command line or from a graphical preview, without going into > complex @settings files. > Live Markdown rendering already exists. Put this in any body node: @language md # My Headline My body Open the view-rendered pane with vr-show, and start typing in the body pane. 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 an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
