On Thu, Jan 6, 2011 at 5:02 PM, Matt Wilkie <[email protected]> wrote:
> I'm working on a big project which has a number of distinct steps or > tasks to it. Some of the tasks are manual, some of them are scripted. > Up to this point I've been using Freeplane (a freemind fork) to > outline the steps and Leo to edit the scripts and hold the detailed > notes in the context where they are most relevant. Inevitably though > the mindmap and code get out of synch with each other. So I migrated > the workflow tree to Leo. Clearly, this is the essential first step. > This brings an immediate advantage, I can > now put the various scripts directly in context on the branch of the > workflow tree where they get used. This is a great mental time saver, > I know longer need to keep a map in my head of where each script is > used, a map which was often hazy and confused. > > The gain of having everything in one place, and editable in one place, > is well worth it but I also find I miss the visual part of the mind > map. Yes. Leo can represent everything, but Leo *isn't* everything. > First thing in the morning, especially after a weekend, it's a > lot easier to look at the graphic and find my place than the Leo tree. > Something to do with more whitespace and leader lines. Is it possible > to have Leo generate a mindmap graphic from a tree? (see attached). Of course it is possible. The question is how, and what it will cost. The general solution is to do the work in a separate process, which then call any external programs you like. Presumably, the script would create the mindmap data, then pass the data to mindmap, and possibly then automatically import the imported graphic into Leo. This is the general strategy behind the screenshots plugin. I took a few false starts in that plugin: the early ideas were more complicated than they needed to be. Your project may be much simpler: you won't necessarily have to specify any options in your Leo outline. > I also have a new problem now: all my scripts are created with @file > nodes. When I clone the @file node Leo wants to write it twice. The > reason for cloning is that I need to have the scripts in their > appropriate branch of the workflow tree, but it's also very important > to be able to see at a glance all the scripts at once, without having > to navigate through and parse the tree. Surely I'm not the only one to > encounter this. How do you deal with this? You can live with the double writes, but there are other ways. If your script files start with @file myScript @others You can put the actual body of the script in a child, and clone that child. 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.
