On Apr 12, 5:06 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> 2. There is a better way than toggle-fixed-file: the file-write logic > will scan for an @bool fixedWindow node. Changing that node will > immediately affect whether future saves are as fixed or unfixed > files. I shall certainly do this. This is now on the trunk. It was straightforward to do. > What if *all* files could be made "fixed" and yet retain the > advantages of unfixed files? Indeed, it is easy to do: simply create / > home/.leoDB.py, containing all **inessential** info in all known .leo > files: marks, expansion states, window positions, presently selected > node, recently opened files. After using fixed .leo files awhile, I am already fed up with a single window position. Not having Leo remember expansion state, selected node and marks will also be bad. I'll be working on home/.leoDB very soon. As I think about it, though, a variety of problems appear. Specifically, marks, etc are presently associated with <v> elements, so gnx's won't do: they are associated with <t> elements. Drat. The same old problems with anonymous vnodes...It looks like more invention is needed...There are also issues with saving info in .leoDB. *Getting* info is easy if the data are Python dicts in .leoDB.py, but writing info might be more difficult. It's not a one-hour project. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
