<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: 3.4 M5 New and Noteworthy: The Breadcrumb</title>
	<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/</link>
	<description>The JDT/UI and Text team presents new API and features</description>
	<pubDate>Mon, 07 Jul 2008 01:50:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.4</generator>

	<item>
		<title>By: mohbana</title>
		<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-57</link>
		<author>mohbana</author>
		<pubDate>Sat, 03 May 2008 23:50:07 +0000</pubDate>
		<guid>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-57</guid>
		<description>Unfortunately on linux (gtk) it doesn't look as good as on windows.  But it's a superb feature!</description>
		<content:encoded><![CDATA[<p>Unfortunately on linux (gtk) it doesn&#8217;t look as good as on windows.  But it&#8217;s a superb feature!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mohbana</title>
		<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-55</link>
		<author>mohbana</author>
		<pubDate>Fri, 02 May 2008 02:35:14 +0000</pubDate>
		<guid>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-55</guid>
		<description>very nice!</description>
		<content:encoded><![CDATA[<p>very nice!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ILOG BRMS Blogs &#187; Blog Archive &#187; What is new in the Eclipse 3.4 JDT</title>
		<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-50</link>
		<author>ILOG BRMS Blogs &#187; Blog Archive &#187; What is new in the Eclipse 3.4 JDT</author>
		<pubDate>Sat, 22 Mar 2008 03:39:12 +0000</pubDate>
		<guid>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-50</guid>
		<description>[...] and automatic addition of casts after &#8220;instanceof&#8221; tests were my favourites. The breadcrumb navigation bar also looked useful, allowing you to navigate to classes from within the Java source editor.   [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] and automatic addition of casts after &#8220;instanceof&#8221; tests were my favourites. The breadcrumb navigation bar also looked useful, allowing you to navigate to classes from within the Java source editor.   [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benno Baumgartner</title>
		<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-49</link>
		<author>Benno Baumgartner</author>
		<pubDate>Mon, 18 Feb 2008 08:35:44 +0000</pubDate>
		<guid>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-49</guid>
		<description>Hi Mik

As it looks for now: The Breadcrumb will stay in the Java Editor for 3.4. In 3.5 we will try to move it out to the trim, this might be a trim kind of thing in the editor area or the workbench trim, but this of course depends on the 3.5 planing and the priorities in 3.5 (think Java 7).

1: The thing I like most about the breadcrumb is that it needs much less space on the screen then the PE. Yes, Mylyn makes the mouse navigation much quicker in the PE. But it does not make the PE smaller. Regarding Alt+click: I don't know how this works, is this in the PE?

2: If we move it out in 3.5 we would of course be interested in working together with you to get the requirements right. That been said, I'm not 100% convinced that your task switching breadcrumb is really a breadcrumb. The breadcrumb shows the path to the current active element. The active element is the element at the cursor position (or maybe in the future the selected element in a view). Your breadcrumb shows the current active task, if I understand correct, and this is independent of any selection/cursor position. It's therefore more like an enhanced drop-down, and I'm not sure if we can/should bring this two concepts together. But maybe we can find a common abstraction.</description>
		<content:encoded><![CDATA[<p>Hi Mik</p>
<p>As it looks for now: The Breadcrumb will stay in the Java Editor for 3.4. In 3.5 we will try to move it out to the trim, this might be a trim kind of thing in the editor area or the workbench trim, but this of course depends on the 3.5 planing and the priorities in 3.5 (think Java 7).</p>
<p>1: The thing I like most about the breadcrumb is that it needs much less space on the screen then the PE. Yes, Mylyn makes the mouse navigation much quicker in the PE. But it does not make the PE smaller. Regarding Alt+click: I don&#8217;t know how this works, is this in the PE?</p>
<p>2: If we move it out in 3.5 we would of course be interested in working together with you to get the requirements right. That been said, I&#8217;m not 100% convinced that your task switching breadcrumb is really a breadcrumb. The breadcrumb shows the path to the current active element. The active element is the element at the cursor position (or maybe in the future the selected element in a view). Your breadcrumb shows the current active task, if I understand correct, and this is independent of any selection/cursor position. It&#8217;s therefore more like an enhanced drop-down, and I&#8217;m not sure if we can/should bring this two concepts together. But maybe we can find a common abstraction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mik Kersten</title>
		<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-48</link>
		<author>Mik Kersten</author>
		<pubDate>Fri, 15 Feb 2008 18:04:23 +0000</pubDate>
		<guid>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-48</guid>
		<description>As part of the design review, I think it would be good to keep a couple of points in mind that are not mentioned above:

1) For the significant number of developers using Mylyn, Eclipse doesn't look much like the screenshot above.  Instead we see a concise view of only the relevant paths within the containment hierarchy, making mouse navigation to these elements quick.  The breadcrumb UI overlaps with the Alt+click mechanism (and keyboard equivalent) that we have for showing all elements under a given project, folder, or type.  I haven't used it enough yet to know, but the editor breadcrumb could be a good alternate way of doing this in case its faster for some use cases.
http://www.eclipse.org/mylyn/images/mylyn-2.0.png  
http://live.eclipse.org/node/412

2) Since the Europa we already have an instance of a view that has a breadcrumb trail which is unrelated to editor navigation in the EPP packagings, i.e. Mylyn's Task List.  I think that both consistency and an interaction design that makes room for additional breadcrumb UIs is important.  For example, for developers using the Task List's working set and task switching, this bread-crumb drives which projects are visible and which editors and elements open, and as such feels more primary.  For those users moving this to trim could could cause a usability problem.  In addition, Mylyn has been trying to put the Task List breadcrumb switcher on the trim for the better part of a year now and we have had experimental support for it for quite some time.  It has turned out to be so tricky given the already overcrowded trim and toolbars that we might end up making this vertical trim for Mylyn 3.0 / Ganymede.
http://www.eclipse.org/mylyn/new/images/2.0/working-sets-switch.gif
144161: [patch] Use trim bar to show currently active task
https://bugs.eclipse.org/bugs/show_bug.cgi?id=144161</description>
		<content:encoded><![CDATA[<p>As part of the design review, I think it would be good to keep a couple of points in mind that are not mentioned above:</p>
<p>1) For the significant number of developers using Mylyn, Eclipse doesn&#8217;t look much like the screenshot above.  Instead we see a concise view of only the relevant paths within the containment hierarchy, making mouse navigation to these elements quick.  The breadcrumb UI overlaps with the Alt+click mechanism (and keyboard equivalent) that we have for showing all elements under a given project, folder, or type.  I haven&#8217;t used it enough yet to know, but the editor breadcrumb could be a good alternate way of doing this in case its faster for some use cases.<br />
<a href="http://www.eclipse.org/mylyn/images/mylyn-2.0.png" rel="nofollow">http://www.eclipse.org/mylyn/images/mylyn-2.0.png</a><br />
<a href="http://live.eclipse.org/node/412" rel="nofollow">http://live.eclipse.org/node/412</a></p>
<p>2) Since the Europa we already have an instance of a view that has a breadcrumb trail which is unrelated to editor navigation in the EPP packagings, i.e. Mylyn&#8217;s Task List.  I think that both consistency and an interaction design that makes room for additional breadcrumb UIs is important.  For example, for developers using the Task List&#8217;s working set and task switching, this bread-crumb drives which projects are visible and which editors and elements open, and as such feels more primary.  For those users moving this to trim could could cause a usability problem.  In addition, Mylyn has been trying to put the Task List breadcrumb switcher on the trim for the better part of a year now and we have had experimental support for it for quite some time.  It has turned out to be so tricky given the already overcrowded trim and toolbars that we might end up making this vertical trim for Mylyn 3.0 / Ganymede.<br />
<a href="http://www.eclipse.org/mylyn/new/images/2.0/working-sets-switch.gif" rel="nofollow">http://www.eclipse.org/mylyn/new/images/2.0/working-sets-switch.gif</a><br />
144161: [patch] Use trim bar to show currently active task<br />
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=144161" rel="nofollow">https://bugs.eclipse.org/bugs/show_bug.cgi?id=144161</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benno Baumgartner</title>
		<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-47</link>
		<author>Benno Baumgartner</author>
		<pubDate>Mon, 11 Feb 2008 13:11:12 +0000</pubDate>
		<guid>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-47</guid>
		<description>Please open separate bugs for each issue against JDT/Text. Thanks.</description>
		<content:encoded><![CDATA[<p>Please open separate bugs for each issue against JDT/Text. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrei Loskutov</title>
		<link>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-46</link>
		<author>Andrei Loskutov</author>
		<pubDate>Mon, 11 Feb 2008 12:14:26 +0000</pubDate>
		<guid>http://dev.eclipse.org/blogs/jdtui/2008/02/11/34-m5-new-and-noteworthy-the-breadcrumb/#comment-46</guid>
		<description>Do we have a "summary" bug for Breadcrumb's in Java editor, or we should create new bugs for all of the improvements/issues?
In particular, I found that the single click to open an package/editor on file would be better then double click right now.</description>
		<content:encoded><![CDATA[<p>Do we have a &#8220;summary&#8221; bug for Breadcrumb&#8217;s in Java editor, or we should create new bugs for all of the improvements/issues?<br />
In particular, I found that the single click to open an package/editor on file would be better then double click right now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
