I have nothing to add or correct in your understanding prototype. Today I have worked on some improvements first of all in making prototype outline not dependent on LeoPyRef.leo. I have created list of all filenames in the installation leo/ folder and its subfolders for which c.looksLikeDerivedFile returns True. Then I wrote simple script to check every of those files and see what version it is in @+leo sentinel and eliminated some false_positives (files that have this string in their content, but which are not really derived files). Then I've created script which made dictionary of filenames as a keys and values are paths that should be in effect when importing derived file so that its headline need not to change. And finally I wrote script that for any given filename from the catalog imports derived file and put it as child of EXTERNALS node. This allows playing with read and write code while having imported file as a vnode.
Later I worked on the line numbering but it is not finished yet. I will report later. And for the record, I have learned from Edwards ENBs on this forum quite a lot for the last ten or more years. Many things that I can do today in computing I can mostly because of using Leo. Vitalije -- 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.
