On Wed, Jan 22, 2020 at 3:36 PM 'tfer' via leo-editor < [email protected]> wrote:
I've hung out with Leo since early days, discovered it when exploring > Literate Programming, always liked the focus management outline provides, > but I've yet to get the benefits I was looking for from it. > Thanks, Tom, for checking in. > Maybe that is due to what my envisioned use case is, I'm not looking to > write my own original code, (yet), I want to understand various existing > code, pick it apart, figure out what the author is doing, all with the eye > to modifying it, by changes or plugins. > That's usually a better plan than starting from scratch :-) Edward's recent posts show a lot of progress on flows for Python > development, but I find myself in the weird world of JavaScript these days, > which brings me to topic of the importer, I want to make a plugin for the > html presenter reveal.js I'm tentatively calling nthD, the intent of which > is break the slides out of their 2D "Flatland", and give you the ability to > use as many dimensions as you need to organize them, (think table of > contents, outlines...). > I have been impressed with your design work in "flatland". I look forward to nthD. > > To this end I tried import the main engine of reveal, the file reveal.js, > Leo creates an @auto node, and creates a subtree. I get the following in > the cmd shell I started Leo from: > > > ----------------------------------------------------------------------------------------------- > ===== PERFECT IMPORT FAILED ===== reveal.js > len(s1): 4810 len(s2): 4810 > first mismatched line: 3174 > [Snip] > It probably shouldn't be surprising that this file choked import, looking at it, it appears most of the code is a complex nesting of objects, variables, and functions in a top level anonymous function. I have just created #1481 <https://github.com/leo-editor/leo-editor/issues/1481> for this. Am I correct that the sources for reveal.js are here <https://github.com/hakimel/reveal.js/>? If not, please send the sources that failed for you. The JS importer should have a full set of proper/traditional unit tests. I have forgotten all the details of the JS importer. That's a good thing, because I'll be able to assess the existing code with new eyes. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0m8UrDJ%2Bh4ciSkqPVJ3WU3ViO4sh2%3DbLfG3CVxK9q0uw%40mail.gmail.com.
