In response to dclark's recent query about syncing leo and directory hierarchies, and the recent fixing of the @path infrastructure, I've done some more work on my "active_path" plugin.
An overview of what it does (i.e. the plugin menu about output) is here: http://www.greygreen.org/files/leo/About_Plugin_Activepath_Version_.html It's on the trunk (the regular trunk, not the Qt branch :-) I don't think it can cause damage easily, but of course it facilitates the creation of @auto or @shadow nodes which may map to existing files, so be careful. Please send ideas / bugs etc. There are some trick behaviors, eg. /foo/ /bar/ @auto some.txt is .../foo/bar/some.txt but /foo/ bar @auto some.txt is .../foo/some.txt where leo's view organizes some.txt in the bar organizer node (which doesn't exist on the file system). This is handy for organizing and documenting directories that contain things like ESRI GIS shapefiles, which are comprised of 4-6 sub files without the requirement of any containing directory. So instead of looking at: /foo/ counties.shp counties.dbf counties.shx counties.sht counties.xml you can look at /foo/ counties [body text "counties of Minnesota"] where 'counties' is a collapsed organizer node, and all the actual files are in 'foo'. Of course active_path can be used without messing with organizer nodes, so that it simply shadows the filesystem. Cheers -Terry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
