Leo is your project, you provide free access to the fruits of your labor, if you're going to remote @root that's your decision, but it may cause me to ask questions I need answered if I am to preserve access to work that I've done.
I've written about my use of Leo 4.3: it served as an easily deployed tool for building utilities in the form of Windows Script Host files (WSF files), and that I came up with a scheme that made it easy for me to use a LEO file to hold the source code for the library of routines (in JScript or VBScript) used by the WSF files as well as the source code for the utilities I was building. Since each WSF file was independent and had to include every library routine used therein, the libraries ended up written to disk in multiple places in the various WSF files. These days, WSF files are frowned up on because script kiddies and other malefactors used VBScript and similar technologies, so perhaps I shouldn't care about preserving the ones I wrote, but I still use some of them in-house, and they need maintenance; I don't want to lose access to my Leo-based development environment if I can help it. The last thing I would want to do would be cut myself off from Leo's vibrant community; I am still a lone developer, working without help to write utilities for work when I'm short of time for work as it is. That said, if I must give up on using future versions of Leo, what do I do: pick a version of Leo that is closest to my needs and create a fork? Given that ease of deployment was essential, and that I was happy with the functions of Leo 4.3 and the Tkinter-based Leo GUI, my choice of version might go back quite a ways. I might have to revive the Tkinter-based GUI; I'd have to dig to find out how many releases of Leo ago I'd have to go. On Tuesday, February 16, 2021 at 4:26:24 PM UTC-5 Edward K. Ream wrote: > leoTangle.py supports @root files. Such files are deprecated and no longer > documented. This is on purpose. > > leoTangle.py contains some of Leo's oldest and least satisfactory code. > > @root is very slightly more flexible than @file, @clean etc. With @root > one can define sections (aka chunks) in several places. This ability is one > of the features of Knuth's original web and cweb projects. However, I have > never, ever, needed this capability. Imo, it is horrendous programming > style. > > Several (10?) years ago I proposed removing support for @root. Back then > at least one person objected. What do you think? Is anyone still using > @root? > > 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/bccaa651-4bac-4036-a192-785a49fde95dn%40googlegroups.com.
