On Mon, 18 Nov 2013 14:16:01 -0600 "Edward K. Ream" <[email protected]> wrote:
> > Second: I wanted to import a Django project structure into Leo. Leo has a > > File|Import command that works well - but only with files. Now, a project > > folders/files structure is a perfect example for hierarchically arranged > > things, and thus it should be easy to import such a structure into Leo. I > > would expect the Import command to do this. But I had do research just to > > find out, that there are some obscure plugins or scripts that do the job. > > This is a harder problem to solve with documentation. I've just put > recursive import on the list of topics for screencasts. Note that the active_path.py plugin is a fairly friendly (by Leo standards ;-) solution for this - create a node "@path /path/to/my/project" and then just double click to expand directories / @auto import files. It has some mass recursive import menu options too. One thing that it seems shouldn't be that hard for us to get done, although I know Edward's already working on things up to 24 hours a day (don't do that too often! :-) and I'm not finding a ton of time at the moment, would be some kind of inventory of the status of various plugins. For example for this project import thing I think there's a couple of old probably broken plugins that sound like they do similar things, unpleasant decoys for new users. There's been various metadata fields for plugins proposed before, author, maintenance status, maturity status. Cheers -Terry -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
