Re: why not merge that eclipse-perspective-lookalike and NB3.6-explorer tree ?

For navigating *inside* a class, you might find my "navigator" module 
useful.  http://workspaceswitcher.netbeans.org/servlets/ProjectDownloadList

-Tim

Peter Buckenleib wrote:
> Am Donnerstag, 2. September 2004 15:22 schrieb Tor Norbye:
> 
>>(b) each dir component would cause the files to scroll further to the
>>right thus increasing the likelihood of horizontal scrollbars and
>>either clipping the left or the right side of the display. E.g. rather
>>than
>>    abc.foo.bar.baz
>>        MyJavaSourceFile1
>>        MyJavaSourceFile2
>>  I had
>>     abc
>>         foo
>>              bar
>>                   baz
>>                         MyJavaSourceFile1
>>                         MyJavaSourceFile2
> 
> That doesn't realy count. You have to scroll a too small window in tree-mode 
> and in flat mode, cause in both cases the interessting part is on the 
> rightmost place, and as far as i know there is no implementation that aligns 
> and scrolls a panel from right to left (except hebrew,arabian, or so).
> A flat list of 30 identical items "abc.daf.gh....." is not that beautiful site 
> to look at. If you scroll the window to the rightmost place and longer names 
> show up as you scroll down, you have to scroll to the right again, and if you 
> have sourcefiles with identical names in different packages, your lost when 
> your flat list clips away the package name.
> 
> 
>>   (Notice also how the old behavior takes up a lot more vertical space!)
> 
> just if you expand ALL nodes, but why would you do that? 
> Why do you want nodes under abc.foo.bar.baz to be epanded when you are working 
> in abc.foo.def.ghi?
> Also if you have to work at abc.foo.abc.def.MyJavaSourceFile1 and 
> abc.foo.ghi.jkl.MyJavaSourceFile2 simultanously, you can collapse all the 
> nodes between, and have the interesting parts of your project as close 
> together as possible. In flat mode you have to scroll for miles in all 4 
> directions or use another kind of navigation to go from a to b. But that is 
> another story.
> 
> 
> 
>>typically I more often jump between methods in my files and that
> 
> Why not use "goto source", goto implementation", or the new 
> "usage"-navigation?
> regards
> 
> Peter