john lunzer wrote:
>
> From my short time testing out sr-speedbar (which keeps the speedbar in 
> the original window) speedbar works opposite of Leo. It builds up an 
> outline from parsing directory tree and source code of each file. This is 
> immensely useful for navigation but it lacks the ability to specify 
> arbitrary levels of code organization separate from the syntax of the 
> source code. To that same effect it lacks pretty much every other feature 
> of Leo where structure is created from the outline rather than the other 
> way around. 
>

Of course, traditional coding-environments are aiming to be non-intrusive. 
Tagbar and speedbar offer only a view on your data for the means of 
navigation. they are not meant at all to manipulate the data themself. 
Code-Manipulation is a problematic task, which can easily fail. Another 
thing is that a pure view is more robust for changes. A tool like Leo which 
enriches the structure with additional data can easily fail to fetch 
external changes to code, because it doesn't know on it's own what it 
should do with the data it has. A pure view on the other side just shows 
the data as they are, and dosn't inflict further problems.

BTW Besides the tag- and-project-view, there are also task-views (guided by 
hints in the code like "#FIXME dosomething here"), linter-views (which show 
failures, warnings and potential problems which tools like pylint or 
pyflask have found) and bookmarks for faster navigation. So for a 
professional coder there is not much demand for the abilitys Leo offer 
there. The advantage is not big enough to put up with the disadvantages and 
invest so much time to learn leo's ropes and corners.

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to