That xml bread-crumbs thing ...

Can we please please pretty please have the option to disable things like this? For me these bread-crumbs are completely useless and only use screen space.

S.

7 comments

+1
So far I haven't seen any use for it, but then I am only editing
Ant build.xml files and an occasional XML configuration file.

Feedback
- I don't want to bother looking up at the xml breadcrumbs
because I am focused on looking at the XML itself. You have to
do a little mental translation to tie the breadcrumbs to the
position the caret is at. Most of the time most of the code
blocks are already visually apparant becaues of the indentation
levels in the editor.

- I don't like the xml breadcrumbs right under the tabs. Looks
bad.

- I try to use keyboard as much as possible, so I'm not that
interested in clicking on the breadcrumbs.

I use "Move Caret to Code Block Start" CTRL+[ and "Move Caret to
Code Block End" CTRL+] alot when I do want to the top of the
outer block. One thing enhancement which would help with those
command is that if you hit CTRL+[ to goto the code block start,
then if you hit CTRL+[ again it should take you to the start of
the next higher code block. Currently, pressing CTRL+[
repeatedly does nothing.

For example, if you put your caret on the word "fork" below and
press CTRL+[, the caret will move here to the start of the javac
code block "<|javac". I would like to press CTRL+[ again to
immediately move the caret up to the target code block start,
but currently pressing CTRL+[ here does nothing. What I have to
do know is hit LEFT_ARROW to move the caret to the left one
space, e.g. "|<javac", and then I can hit CTRL+[.

        
        
            
            
                
            
        

]]>

0

Hello Alex,

I use "Move Caret to Code Block Start" CTRL+[ and "Move Caret to Code
Block End" CTRL+] alot when I do want to the top of the outer block.
One thing enhancement which would help with those command is that if
you hit CTRL[ to goto the code block start, then if you hit CTRL[
again it should take you to the start of the next higher code block.
Currently, pressing CTRL+[ repeatedly does nothing.


I guess this could work in more places that just xml...


0

Stefan Arentz wrote:

Can we please please pretty please have the option to disable things
like this? For me these bread-crumbs are completely useless and only
use screen space.


If it were somewhere down the bottom, and displayed as a copyable XPath
expression, it might be a different story.

Daniel

0

+1.

Nice idea about the copyable XPath expression.

As the feature is now, it's cute, but I don't think I will use it for anything. And it is distracting when moving between tabs, because the editor pane moves up and down. I don't like that.

John Hurst

0

I think the breadcrumbs have some value when editing HTML, which has a more
free-form structure and greater average element depth that 'typical' xml-based
formats (hbm,spring,...).

However, -1 on the 'Copyable XPath' idea. Something that it only used once
a week or less does not deverve such an prominent place on the screen.


0

If it were somewhere down the bottom, and displayed
as a copyable XPath
expression, it might be a different story.


Sure, but that would give you the problem of deciding which XPath expression to pick as it is nowhere near unique.

By the way, I have just been facing this problem in an Open Source project I am currently working on. I have implemented a heuristic for offering a choice of XPath expressions for HTML nodes, but it is extremely basic. Is anyone aware of a solution to this in an existing Open Source project?

Thanks a lot,
Jens

0

While I support the option to disable, I must say that I've come to like
the feature actually :)
When reading deeply-nested structures, it's nice to be able to quickly navigate
to an ancestor element of a given type.


0

Please sign in to leave a comment.