Attachment #68854 for bug #185836

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.




<?xml version="1.0" encoding="UTF-8"?>
<?NLS TYPE="org.eclipse.help.toc"?>

<toc label="Mylar">
	<topic label="Overview" href="doc/overview.html" />
	<topic label="What's new" href="doc/new.html" />
	<!--<topic label="Tips and tricks" href="doc/tips.html"/>-->
	<anchor id="concepts"/>
	<anchor id="tasklist"/>
	<anchor id="java"/>
	<anchor id="xml"/>
	<anchor id="bugzilla"/>
	<anchor id="monitor"/>
	<topic label="For Developers" href="doc/developer/index.html">
		<topic label="Release Notes" href="doc/developer/changes.html"/>
	</topic>
	-->
</toc>






<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="copyright"
	content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="STYLESHEET" href="book.css" charset="ISO-8859-1"
	type="text/css">
<style>
td {
	border-top: solid thin black;
}

img[alt] {
	background-color: #ffdddd;
}

tr {
	vertical-align: top;
}
</style>
<title>Mylar Overview</title>
<script language="JavaScript"
	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
</head>

<body>

<h2>Mylar Overview</h2>

<p>Mylar is a task-focused UI for Eclipse that makes working with
very large workspaces as easy as working with small ones. Mylar extends
Eclipse with mechanisms for keeping track of the tasks that you work on.
A task is defined as any unit of work that you want to recall or share
with others, such as a bug reported by a user or a note to yourself
about improving a feature. You can store tasks locally in your
workspace, or they can come from one or more task repositories. To
connect to a task repository, you must have a connector that supports
that repository. (A task repository is a bug/ticket/issue tracker such
as Bugzilla, Trac, or JIRA).</p>
<p>Once your tasks are integrated, Mylar monitors your work activity
on those tasks to identify information relevant to the task-at-hand.
Mylar monitors Eclipse and captures your interaction in a task context.
System artifacts such as files, types, methods, and fields get assigned
a degree-of-interest based on how recently and frequently you interact
with them. This results in uninteresting elements being filtered from
view within Eclipse, allowing you to focus on on what is important. From
this, Mylar creates a task context, which is the set of all artifacts
related to your task. These can include methods you have edited, APIs
you have referred to, and documents you have browsed. Mylar uses this
task context to focus the Eclipse UI on interesting information, hide
what's uninteresting, and automatically find what's related. Having the
information you need to get your work done at your fingertips improves
your productivity by reducing the time you spend searching, scrolling,
and navigating. By making task context explicit, Mylar also facilitates
multitasking, planning, reusing past efforts, and sharing expertise.</p>

</body>
</html>

Lines 10-16 Link Here

(-)META-INF/MANIFEST.MF (-1 / +3 lines)
10	org.eclipse.mylar.tasks.core,	10	org.eclipse.mylar.tasks.core,
11	org.eclipse.mylar.tasks.ui,	11	org.eclipse.mylar.tasks.ui,
12	org.eclipse.mylar,	12	org.eclipse.mylar,
13	org.eclipse.core.runtime	13	org.eclipse.core.runtime,
		14	org.eclipse.ui.cheatsheets,
		15	org.eclipse.ui.intro
14	Export-Package: org.eclipse.mylar.doc.internal.actions,	16	Export-Package: org.eclipse.mylar.doc.internal.actions,
15	org.eclipse.mylar.doc.internal.dialogs	17	org.eclipse.mylar.doc.internal.dialogs
16	Bundle-RequiredExecutionEnvironment: J2SE-1.5	18	Bundle-RequiredExecutionEnvironment: J2SE-1.5

Lines 13-19 Link Here

(-)build.properties (-1 / +4 lines)
13	doc/,\	13	doc/,\
14	about.html,\	14	about.html,\
15	.,\	15	.,\
16	icons/	16	icons/,\
		17	intro/,\
		18	images/,\
		19	cheatsheets/
17	src.includes = META-INF/,\	20	src.includes = META-INF/,\
18	plugin.xml,\	21	plugin.xml,\
19	about.html,\	22	about.html,\




            commandId="org.eclipse.mylar.doc.legend.show"
            schemeId ="org.eclipse.ui.defaultAcceleratorConfiguration">
      </key>
   </extension>
   <extension
         point="org.eclipse.ui.intro.configExtension">
      <configExtension
            configId="org.eclipse.ui.intro.universalConfig"
            content="intro/overviewExtensionContent.xml">
      </configExtension>
      <configExtension
            configId="org.eclipse.ui.intro.universalConfig"
            content="intro/whatsnewExtensionContent.xml">
      </configExtension>
      <configExtension
            configId="org.eclipse.ui.intro.universalConfig"
            content="intro/tutorialsExtensionContent.xml">
      </configExtension>
   </extension>
   <extension
         point="org.eclipse.ui.cheatsheets.cheatSheetContent">
      <category
            id="org.eclipse.mylar.cheatsheet"
            name="Mylar">
      </category>
      <cheatsheet
            category="org.eclipse.mylar.cheatsheet"
            contentFile="cheatsheets/Query.xml"
            id="org.eclipse.mylar.cheatsheet.query"
            name="Create a query from bugs.eclipse.org">
         <description>
            Learn how to create a query from bugs.eclipse.org
         </description>
      </cheatsheet>
      <cheatsheet
            category="org.eclipse.mylar.cheatsheet"
            contentFile="cheatsheets/TaskFocus.xml"
            id="org.eclipse.mylar.cheatsheet.taskfocus"
            name="Use Task-Focused UI">
         <description>
            Learn how to use Task-Focused UI
         </description>
      </cheatsheet>
   </extension> 
  
</plugin>




a#mylar-query img {
	background-image: url(../../images/topiclabel/tu_query48.gif);
}

a#mylar-query:hover img {
	background-image: url(../../images/topiclabel/tu_query48_hov.gif);
}

a#mylar-task img {
	background-image: url(../../images/topiclabel/tu_task48.gif);
}

a#mylar-task:hover img {
	background-image: url(../../images/topiclabel/tu_task48_hov.gif);
}

Added Link Here

(-)intro/css/whatsnew.css (+7 lines)
1	a#mylar-noteworthy img {
2	background-image: url(../../images/topiclabel/wn_mylar48.gif);
3	}
4
5	a#mylar-noteworthy:hover img {
6	background-image: url(../../images/topiclabel/wn_mylar48_hov.gif);
7	}

Added Link Here

(-)intro/css/overview.css (+7 lines)
1	a#mylar-overview img {
2	background-image: url(../../images/topiclabel/ov_mylar48.gif);
3	}
4
5	a#mylar-overview:hover img {
6	background-image: url(../../images/topiclabel/ov_mylar48_hov.gif);
7	}




<html>
<head>
<meta name="copyright"
	content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="STYLESHEET" href="book.css" charset="ISO-8859-1"
	type="text/css">
<style>
td {
	border-top: solid thin black;
}

img[alt] {
	background-color: #ffdddd;
}

tr {
	vertical-align: top;
}
</style>
<title>What's New in Mylar 2.0</title>
<script language="JavaScript"
	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
</head>

<body>
<h2>What's New in Mylar 2.0</h2>
<p>Here are descriptions of some of the more interesting or
significant changes made to Mylar. They are grouped into:</p>
<ul>
	<li><a href="#Tasks">Tasks</a></li>
	<li><a href="#TaskRepositories">Task Repositories</a></li>
	<li><a href="#Team">Team</a></li>
	<li><a href="#TaskContext">Task Context</a></li>
	<li><a href="#BugzillaConnector">Bugzilla Connector</a></li>
	<li><a href="#JIRAConnector">JIRA Connector</a></li>
	<li><a href="#TracConnector">Trac Connector</a></li>
</ul>
<br>

<table cellpadding="10" cellspacing="0" width="600">
	<colgroup>
		<col width="20%">
		<col width="80%">
	</colgroup>
	<tbody>

		<tr>
			<td colspan="2"><a name="Tasks"></a>
			<div style="font-size: 20px; font-weight: bold;">Tasks</div>
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b> New Task List layout </b></p>
			</td>
			<td valign="top">The <i>Task List</i> layout has been updated to
			use a custom drawn tree instead of relying on multiple columns in
			order to provide the following improvements:
			<ul>
				<li>Support for subtasks (for an example see the Bugzilla
				section)</li>
				<li>The icon columns no longer take up a large amount of
				horizontal space, making more of the Summary visible.&nbsp; Sort
				using <i>Sort by</i> in the view menu.</li>
				<li>The table header and horizontal scrollbar are gone, making
				2-3 more tasks visible.</li>
				<li>The icon scheme has been updated to make incoming
				indicators easier to pick out, hits more consistent with tasks, and
				the kind of task appear on the icon (see the <i>Help -&gt; Mylar
				UI Legend</i> for the updated scheme).&nbsp; Note in particular that new
				tasks now have the task icon background and are distinguished by a
				special incoming indicator.</li>
			</ul>
			<p>Note that the incoming overlays can also be configured to use
			the Synchronize view style icons and left-facing placement via <i>Preferences
			-&gt; Task List -&gt; Layout</i>.&nbsp; Please use <a
				href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=182772">bug
			182772</a> for feedback or reporting any OS-specific rendering problems.</p>
			<p><img src="images/2.0M3/tasklist-tree.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>UI Legend for Connectors</b></p>
			</td>
			<td valign="top"><i>Help -&gt; Mylar UI Legend</i> now displays
			connector-specific icon contributions.&nbsp;
			<p><img src="images/2.0M3/ui-legend-connectors.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Content Assist in Task Editor</b></p>
			</td>
			<td valign="top">The Task Editor now supports content
			assist.&nbsp; The proposals include all usernames/emails associated
			with an &quot;Assigned to&quot; for all bugs in the repository.&nbsp;
			The username in the repository credentials is used to highlight your
			username.
			<p><img src="images/2.0M3/tasks-content-assist.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Task tooltips show changes</b></p>
			</td>
			<td valign="top">Task List tooltips now summarize incoming
			changes, making it easier to scan for changes without opening the
			task editor.&nbsp; Note that the popup menu can be used to mark tasks
			read without opening.
			<p><img src="images/2.0M3/task-tooltip-incoming.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Task Working Sets<br>
			(Experimental)<br>
			3.3 only</b></p>
			</td>
			<td valign="top">Categories and Queries can be added to a Task
			Working Set.&nbsp; Switching Task Working Sets makes only the tasks
			for that working set appear.&nbsp; This can be useful for those with
			a large Task List, several non-overlapping projects, different sets
			of tasks for different venues (e.g. home vs. work).&nbsp; For 2.0M3
			switching working sets is only supported via the working set switcher
			on the main toolbar.&nbsp; To switch to see only one working set you
			need to Ctrl+click that working set, otherwise multiple will be
			visible.&nbsp; The create a new Task Working Set use the <i>Edit...</i>
			button visible below.
			<p><img src="images/2.0M3/tasks-working-sets.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Offline Improvements</b></p>
			</td>
			<td valign="top">The offline support has been improved to be
			more transparent.&nbsp; Offline data for all tasks, even unread ones,
			is downloaded in the background, so before going offline all you need
			to do is run one successful synchronization.&nbsp; If switching
			frequently between being connected note that you can toggle
			background synchronizations via the <i> Synchronize Automatically</i>
			button in the <i>Task List</i> view menu.&nbsp; Opening repository
			tasks is now much faster due to synchronization and offline
			concurrency improvements.&nbsp; Any submission errors are now shown
			on the task editor header (Eclipse 3.3) instead of the <i>Error
			Log</i> view.&nbsp; Also note that the <i>History</i> button is now on
			the toolbar and a <i>Submit </i>buttons has been added as well.
			<p><img src="images/2.0M3/task-editor-error.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Task Editor Improvements</b></p>
			</td>
			<td valign="top">The performance of repository task opening has
			improved dramatically because there are no more synchronous trips to
			the server and all editor pages load lazily.&nbsp; If editor contents
			become stale, the header will be updated as below (Eclipse 3.3) or a
			dialog will show (Eclipse 3.2).&nbsp; The <i>Synchronize</i> button
			on the right of the header retrieves the latest contents.&nbsp; There
			have also been numerous layout and improvements.
			<p><img src="images/2.0M2/task-editor-warning.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Hyperlinks in Text Editors<br>
			(3.3 only)</b></p>
			</td>
			<td valign="top">Hyperlinks are now supported in all text
			editors.&nbsp; Modify enablement or behavior via <i>Preferences
			-&gt; General -&gt; Editors -&gt; Text Editors -&gt; Hyperlinking.</i>
			<p><img src="images/2.0M2/hyperlinks-text.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Scheduled Task Presentation<br>
			(Experimental)</b></p>
			</td>
			<td valign="top">The <i>Task Activity</i> view has been removed
			and replaced by the <i>Scheduled</i> presentation of the <i>Task
			List</i>.&nbsp; When in focused mode this presentation shows only the
			tasks scheduled for the current workweek.&nbsp; Since unscheduled
			query hits will not show, this makes it easier to work without
			getting distracted by incoming items.&nbsp; To focus on the workday,
			use the <i>Go Into</i> action on the day container.&nbsp; When the
			focused mode is off, this presentation both past task activity and
			tasks scheduled for the future.&nbsp;&nbsp;
			<p><img src="images/2.0M2/tasklist-schedule.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Task Editor lifecycle streamlined</b></p>
			</td>
			<td valign="top">The <i>Task Editor</i> no longer closes on
			submission, and instead shows progress while it synchronizes with the
			repository. If incoming changes occur while editor is open the
			refresh will preserve and mark any outgoing changes.&nbsp; In order
			to clear outgoing changes use the context menu -&gt; <i>Mark </i>-&gt;
			<i> Clear Outgoing</i>.&nbsp; If an editor is opened for a task not
			in the <i> Task List </i>the <i>Add to Task List</i> action can be
			used on the editor's context menu. Formatting of the editor has been
			improved and uses the new form look on Eclipse 3.3.
			<p><img src="images/2.0M1/task-editor-progress.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Hyperlinks in Java Editor<br>
			(3.3 only)</b></p>
			</td>
			<td valign="top">References to tasks and bugs in the Java Editor
			and now hyperlinked consistently with the Task Editor.&nbsp; The Task
			Repository must be defined on the corresponding project (set via <i>Project
			Properties </i>-&gt; <i>Task Repository</i>). References to tasks must be
			moused over to turn into hyperlinks.
			<p><img src="images/2.0M1/java-editor-hyperlink.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Drag and Drop improvements</b></p>
			</td>
			<td valign="top">To attach files to a repository task them onto
			the Task Editor from a navigator view or operating system
			window.&nbsp; Dragging a URL that corresponds to a task onto the Task
			List will cause the corresponding task to be created and added to the
			Task List, if the corresponding repository exists.</td>
		</tr>

		<tr>
			<td colspan="2"><a name="TaskRepositories"></a>
			<div style="font-size: 20px; font-weight: bold;">Task
			Repositories</div>
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Platform Proxy Settings<br>
			(3.3 only)</b></p>
			</td>
			<td valign="top">By default task repositories now use the global
			platform proxy settings instead of the Platform Update
			settings.&nbsp; These can be overridden per-repository.
			<p><img src="images/2.0M2/repository-settings-proxy.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Max hits settings removed</b></p>
			</td>
			<td valign="top">The &quot;Max hits&quot; setting on task
			repository queries has been removed since it was too easy to not
			notice when the max was reached.</td>
		</tr>

		<tr>
			<td colspan="2"><a name="Team"></a>
			<div style="font-size: 20px; font-weight: bold;">Team</div>
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Hyperlinks in Annotations and History<br>
			(3.3 only)</b></p>
			</td>
			<td valign="top">Team annotations, enabled in the Java editor
			via popup menu -&gt; <i> Team -&gt; Show Annotation</i> now show
			hyperlinked references to tasks.&nbsp; Note that you must press F2
			for focus and Ctrl to activate the hyperlink.&nbsp; Task Hyperlinks
			are also available in the <i>History</i> view.
			<p><img src="images/2.0M3/team-hyperlinks-annotations.gif">
			<p><img src="images/2.0M3/team-hyperlinks-history.gif">
			</td>
		</tr>

		<tr>
			<td colspan="2"><a name="TaskContext"></a>
			<div style="font-size: 20px; font-weight: bold;">Task Context</div>
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>UI Usage Reports<br>
			(Experimental)<br>
			3.3 only</b></p>
			</td>
			<td valign="top"><i>File -&gt; New -&gt; Other -&gt; Mylar
			-&gt; UI Usage Report</i> will generate a report of your perspective,
			view, preference, command and editor usage in Eclipse.&nbsp; This
			reporting facility builds on the Mylar Monitor used to study early
			releases of Mylar and has been extended to upload statistics to the
			mylar.eclipse.org server where they can be accessed by all interested
			(via the button in the <i> Actions</i> section).&nbsp; As before, we
			will be using these statistics as input to evolving and improving the
			Mylar UI.&nbsp;
			<p><i>UI Usage Reporting</i> is installable as a separate feature
			that can be used independently of the rest of Mylar.&nbsp; Currently
			it is only available to Eclipse 3.3 users but will be made available
			to 3.2 users for the next release.&nbsp; If installed it will ask to
			run once every three weeks, at which point you will see statistics
			displayed as below.&nbsp; We then ask that you share your usage data
			with the community, via the <i>Submit to Eclipse.org</i> button, so
			that it can help inform Eclipse developers how the UI is being
			used.&nbsp; Note that only interaction events that have IDs starting
			with &quot;org.eclipse&quot; will be uploaded in order to avoid
			having private ID names made public.&nbsp; Note that the information
			gathered also includes interaction information about elements, so to
			avoid sharing the IDs of private elements make sure to leave on
			&quot;Obfuscate elements using SHA message digest one-way hash&quot;
			via the <i>Preferences -&gt; Mylar -&gt; Usage Data</i> page.&nbsp;
			More information on how the monitor works can be found in <a
				href="http://wiki.eclipse.org/index.php/Mylar_Integrator_Reference#Monitor_API">
			Eclipsepedia</a>.</p>
			<p><img src="images/2.0M3/ui-usage-report.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Context Activation Improvements</b></p>
			</td>
			<td valign="top">Task contexts are now dramatically quicker to
			activate and provide a perfect restore of the editors that were
			available when the task was deactivated.&nbsp; This includes
			restoring the line numbers and selections of editors closed.&nbsp; As
			a result there should be no more need to use the &quot;Pause
			Capturing Context&quot; action and we are considering removing it
			(comment on <a
				href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=186874">bug
			186874</a> if you still have a use case for it).</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Quick Context View</b></p>
			</td>
			<td valign="top">There is now quick view of the task context
			that&nbsp; similar to the Ctrl+O quick outline.&nbsp; Invoke it via <i>Navigate
			-&gt; Quick Context view</i> or Ctrl+Alt+Shift+RightArrow.&nbsp; This
			quick view can be used to show the task context when a navigator view
			is not visible (e.g. in the <i>Debug</i> perspective) or when the
			navigator view is not in filtered mode.
			<p><img src="images/2.0M2/context-quick-view.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Retrieve from Attachments Table</b></p>
			</td>
			<td valign="top">The <i>Retrieve Context</i> action on the
			attachments table can be used to bypass the <i>Retrieve Context</i>
			wizard.
			<p><img src="images/2.0M2/context-apply-attachments.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Add to Task Context from Synchronize View</b></p>
			</td>
			<td valign="top">The <i>Add to Task Context</i> action can be
			invoked on change sets or resources that appear in the <i>Synchronize
			</i>view.&nbsp; This can be useful when an incoming change set should be
			reviewed but has no corresponding task context or when outgoing
			changes have no task context, e.g. if applied from a patch with no
			context attached.
			<p><img src="images/2.0M2/synchronize-view-add.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Task Context editor</b></p>
			</td>
			<td valign="top">The <i>Context</i> tab on the Task Editor
			provides a preview of the task context contents.&nbsp; This facility
			can be used to remove elements and edit their interest, for example,
			before sharing the context with others. When first opened this view
			will show all of the elements in the task context that have a
			corresponding content provider (e.g. Java elements and files). For
			long-running tasks this can cause a large number of elements that
			have decayed in interest to show.&nbsp; The filter slider bar can be
			used to adjust degree-of-interest threshold to show only the most
			interesting elements.
			<p><img src="images/2.0M1/task-context-editor.gif">
			</td>
		</tr>

		<tr>
			<td colspan="2"><a name="BugzillaConnector"></a>
			<div style="font-size: 20px; font-weight: bold;">Bugzilla
			Connector</div>
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Dependencies show as subtasks<br>
			(Experimental)</b></p>
			</td>
			<td valign="top">If a bug A is set to &quot;depend on&quot; B,
			bug B will be shown as a subtask of A.&nbsp; This supports creating
			dependent bugs to indicate that the work is not completed until all
			dependent bugs are done.&nbsp; Enable this functionality by toggling
			off <i>Filter Subtasks</i> in the <i>Task List</i> view menu.
			<p><img src="images/2.0M3/bugzilla-subtasks.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Shared Due Dates and Time Tracking</b></p>
			</td>
			<td valign="top">If Time Tracking is enabled on the repository,
			shared due dates can be scheduled.&nbsp; When the due date arrives
			the task will get a small red bell overlay in its upper-right
			corner.&nbsp; Personal scheduled for dates can be used independently
			of due dates.&nbsp; Tasks with due dates that are not past will have
			a blue bell overlay instead.&nbsp; If the time tracking is not
			enabled, or not supported by the repository, due dates can be used
			locally as with personal tasks.&nbsp;
			<p><img src="images/2.0M2/bugzilla-due-dates.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Local user names</b></p>
			</td>
			<td valign="top">If your Bugzilla repository is configured to
			use local user IDs rather than full email IDs enable the
			corresponding option on the <i> Task Repository </i>properties page.
			<p><img src="images/2.0M1/bugzilla-local-users.gif">
			</td>
		</tr>

		<tr>
			<td colspan="2"><a name="JIRAConnector"></a>
			<div style="font-size: 20px; font-weight: bold;">JIRA Connector</div>
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Attachment support</b></p>
			</td>
			<td valign="top">The JIRA task editor now supports attachments,
			both for files and for task contexts.&nbsp; Submission errors are now
			displayed instead of failing silently.
			<p><img src="images/2.0M3/jira-attachments.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Hyperlinks in Java Editor<br>
			(3.3 only)</b></p>
			</td>
			<td valign="top">If a JIRA repository is set as the task
			repository on a project hyperlinking will work per task key.
			<p><img src="images/2.0M2/jira-java-hyperlinks.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Proxies and Http Auth</b></p>
			</td>
			<td valign="top">The JIRA Connector now supports proxy settings
			and http auth.&nbsp; In addition, there have been numerous bug fixes
			of connectivity and rich editor support.</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Hyperlinks in Task Editor</b></p>
			</td>
			<td valign="top">References to JIRA issue keys are now
			hyperlinked.
			<p><img src="images/2.0M1/jira-editor-hyperlink.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>JIRA Core Services</b></p>
			</td>
			<td valign="top">The JIRA feature will now install without
			requiring additional downloads from Tigris.org.</td>
		</tr>

		<tr>
			<td colspan="2"><a name="TracConnector"></a>
			<div style="font-size: 20px; font-weight: bold;">Trac Connector</div>
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Hyperlinks in Task Editor<br>
			(3.3 only)</b></p>
			</td>
			<td valign="top">Trac hyperlinks are now supported in the task
			editor.
			<p><img src="images/2.0M2/trac-hyperlinks.gif">
			</td>
		</tr>

		<tr>
			<td valign="top">
			<p align="right"><b>Custom Fields</b></p>
			</td>
			<td valign="top">
			<p class="MsoPlainText">Trac now supports the selection from a
			list of pre-defined values for custom fields.</p>
			</td>
		</tr>
	</tbody>
</table>

<p>&nbsp;</p>

</body>
</html>




<?xml version="1.0" encoding="UTF-8" ?>
<introContent>
	<extensionContent id="org.eclipse.mylar" name="Mylar"
		style="css/tutorials.css" path="tutorials/@">
		<group label="Mylar" id="mylar" style-id="content-group">
			<link 
				url="http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.platform.cheatsheet&amp;input=org.eclipse.mylar.cheatsheet.query" 
				label="Create a query" id="mylar-query"	style-id="content-link">
				<text>Learn how to create a query from bugs.eclipse.org.</text>
			</link>
			<link
				url="http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.platform.cheatsheet&amp;input=org.eclipse.mylar.cheatsheet.taskfocus"
				label="Use Task-Focused UI" id="mylar-task" style-id="content-link">
				<text>Learn how to use Task-Focused UI.</text>
			</link>
		</group>
	</extensionContent>
</introContent>




<?xml version="1.0" encoding="UTF-8"?>
<cheatsheet title="Create a query from bugs.eclipse.org">
   <intro>
      <description>
         This cheat sheet shows you how to create a query from bugs.eclipse.org.<br/>
      </description>
   </intro>
   <item title="Open the Task List view" dialog="true" skip="false">
      <description>
         If the Task List view is not opened, select in the main menu  <b>Window</b> &gt; <b>Show View</b> &gt; <b>Other...</b> &gt; <b>Mylar</b> &gt; <b>Task List</b> or click on the &quot;Click to Perform&quot; link below.
      </description>
      <command serialization="org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.mylar.tasks.ui.views.TaskListView)" confirm="true">
      </command>
   </item>
   <item title="Create a new Query" dialog="true" skip="false">
      <description>
         In the Task List view, click on the right mouse button then select <b>New &gt; Query</b> or click on the &quot;Click to Perform&quot; link below.
      </description>
      <command serialization="org.eclipse.ui.newWizard(newWizardId=org.eclipse.mylar.tasks.ui.wizard.new.query)" confirm="true">
      </command>
   </item>
   <item title="Add Task Repository" dialog="true" skip="true">
      <description>
         If <b>Eclipse.org</b> is on your repository list, you can <b>skip</b> this step.
<br/><br/>
Click on the <b>Add Repository Task</b> button in the Query dialog. Select Bugzilla on the list then click on the Next button. Enter <b>https://bugs.eclipse.org/bugs</b> for the server&apos;s address, <b>Eclipse.org</b> for the label then click on the <b>Finish</b> button.
      </description>
   </item>
   <item title="Setup the query" dialog="true" skip="false">
      <description>
         Select <b>Eclipse.org</b> then click on the <b>Next</b> button.<br/>
 Select <b>Create a query using form</b> then click on the <b>Next</b> button.<br/>
 Enter <b>Mylar bugs</b> for the query&apos;s title.
 Select <b>Mylar</b> from the Product and <b>P1, P2</b> from the Priority then click on the <b>Finish</b> button.
      </description>
   </item>
</cheatsheet>




<?xml version="1.0" encoding="UTF-8" ?>
<introContent>
	<extensionContent id="org.eclipse.mylar" name="Mylar"
		style="css/whatsnew.css" path="whatsnew/@">
		<group id="content-group" style-id="content-group">
			<link label="Mylar"
				url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.mylar.doc/doc/new.html"
				id="mylar-noteworthy" style-id="content-link">
				<text>
					Find out the significant changes made to Mylar
				</text>
			</link>
		</group>
	</extensionContent>
</introContent>




<?xml version="1.0" encoding="utf-8" ?>
<introContent>
	<extensionContent id="org.eclipse.mylar" name="Mylar"
		style="css/overview.css" path="overview/@">
		<group id="content-group" style-id="content-group">
			<link label="Mylar"
				url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.mylar.doc/doc/overview.html"
				id="mylar-overview" style-id="content-link">
				<text>Learn more about Mylar task-focused ui</text>
			</link>
		</group>
	</extensionContent>
</introContent>




<?xml version="1.0" encoding="UTF-8"?>
<cheatsheet title="Use Task-Focused UI">
   <intro>
      <description>
         This cheat sheet shows you how to handle a task lifecycle and how to use task-focused ui.<br/>
      </description>
   </intro>
   <item title="Open the Plug-in perspective" dialog="true" skip="false">
      <description>
         If you&apos;re not already in Plug-in Development perspective in the main menu select <b>Window</b> &gt; <b>Open Perspective</b> &gt; 	<b>Other...</b> &gt; <b>Plug-in Development</b>	or click on the &quot;Click to Perform&quot; link below.
      </description>
      <command serialization="org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.pde.ui.PDEPerspective)" confirm="true">
      </command>
   </item>
   <item title="Open the Task List view" dialog="true" skip="false">
      <description>
         If the Task List view is not opened, select in the main menu  <b>Window</b> &gt; <b>Show View</b> &gt; <b>Other...</b> &gt; <b>Mylar</b> &gt; <b>Task List</b> or click on the &quot;Click to Perform&quot; link below.
      </description>
      <command serialization="org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.mylar.tasks.ui.views.TaskListView)" confirm="true">
      </command>
   </item>
   <item title="Create a sample project" dialog="true" skip="false">
      <description>
         Before we start this cheat sheet, we need a project to practice.
<br/><br/>
In the main toolbar, click on the <b>New</b> button. Select the <b>Plug-in Project</b>  from the list then click on the <b>Next</b> button. Enter <b>SampleProject</b> for the project&apos;s name then click on the <b>Next</b> button twice.
Select from the Templates part <b>Hello, World</b> then click on the <b>Finish</b> button.
      </description>
   </item>
   <item title="Create and activate a task" dialog="true" skip="false">
      <description>
         In the Task List view, click on the right mouse button, then select <b>New &gt; Category</b>. Enter <b>Tutorials</b> for the category&apos;s name.
<br/><br/>
Then right click on the <b>Tutorials</b> category and select <b>New &gt; Task</b>. Enter <b>Learn task-focus</b>  for the task&apos;s title and change the priority to <b>High</b>. You can add some notes,  too.
<br/><br/>
Right click on the new task and select <b>Activate</b> to activate the task.
<br/><br/>
<b>Important:</b> If it&apos;s not activated, click on the <b>&quot;Focus on the Active Task&quot;</b> toogle button in the <b>Package Explorer</b> and in the <b>Outline</b> view too.
      </description>
   </item>
   <item title="Open SampleAction file" dialog="true" skip="false">
      <description>
         Press down the <b>Ctrl+Shift+T</b> buttons or click on the &quot;Click to Perform&quot; link below. <br/> 
In the <b>Open Type</b> dialog  enter <b>SampleAction</b> for the type&apos;s name then press the <b>Enter</b> button.<br/> 
After the file is opened you can see the SampleAction class both  in the <b>Package Explorer</b> and in the <b>Outline</b> view.
      </description>
      <command serialization="org.eclipse.jdt.ui.navigate.open.type" confirm="true">
      </command>
   </item>
   <item title="Add method to focus" dialog="true" skip="false">
      <description>
         Select in the Editor the <b>void run(IAction action)</b> method then you can see the <b>run(IAction)</b> method in the <b>Outline</b> view and in the <b>Package Explorer</b> under the SampleAction class.
<br/><br/>
Next press the Alt button and click on the SampleAction class in the <b>Outline</b> view.<br/> 
Now you can see all methods. Methods which aren&apos;t in the focus are in <b>grey</b> color. Select <b>window</b> field from the list. After that all methods will disappear which aren&apos;t in the focus.
      </description>
   </item>
   <item title="Landmark" dialog="true" skip="false">
      <description>
         If an element&apos;s interest ranks high enough, it becomes a landmark, which is an implicitly created bookmark. Landmarks are showed in bold font.
<br/><br/>
Select the <b>run(IAction)</b> method in the <b>Outline</b> view or in the <b>Package Explorer</b>. Right click on the method and select <b>Mark as Landmark</b>. After then  this method becomes a landmark.
<br/><br/>
Also you can use key bindings. <b>Ctrl+Shift+Alt+UpArrow</b> to mark the element as landmark or <b>Ctrl+Shift+Alt+DownArrow</b> to mark less interesting for the element.
      </description>
   </item>
   <item title="Remove method from focus" dialog="true" skip="true">
      <description>
         Right click on the <b>window</b> field and select <b>Remove from Focus</b>. The window field will disappear on the list.
      </description>
   </item>
   <item title="Open Activator.java" dialog="true" skip="false">
      <description>
         Press down the <b>Alt</b> button and <b>click</b> on the <b>src</b> directory. Then you can see 3 packages. <br/>
<b>Alt+click</b> on the  <b>sampleproject</b> package and you can open the Activator.java file with a simple double-click on the file name.
<br/><br/>
You can use <b>Alt+RightArrow</b> instead of <b>Alt+click</b>.
      </description>
   </item>
   <item title="Quick Context View" dialog="true" skip="false">
      <description>
         Press down <b>Ctrl+Shift+Alt+RightArrow</b> buttons, then you can see all elements which are in the focus.
      </description>
   </item>
   <item title="Complete task" dialog="true" skip="false">
      <description>
         In the Task List view, click on the right mouse button on the <b>Learn task-focus</b> task and select deactivate.
<br/>
Click again on the task with the right mouse button and select <b>Mark &gt; Complete</b>. <br/>
After then the task&apos;s name will be struck through.
      </description>
   </item>
</cheatsheet>

Return to bug 185836

Lines 1-20 Link Here

(-)doc/toc.xml (-15 / +5 lines)
1	<?xml version="1.0" encoding="UTF-8"?>	1	<?xml version="1.0" encoding="UTF-8"?>
2	<?NLS TYPE="org.eclipse.help.toc"?>	2	<?NLS TYPE="org.eclipse.help.toc"?>
3		3
4	<toc label="Mylar">	4	<toc label="Mylar">
5	<topic label="Overview" href="doc/overview.html"/>	5	<topic label="Overview" href="doc/overview.html" />
6	<!--	6	<topic label="What's new" href="doc/new.html" />
7	<topic label="New & Noteworthy" href="doc/new.html"/>	7	<!--<topic label="Tips and tricks" href="doc/tips.html"/>-->
8	<anchor id="concepts"/>
9	<anchor id="tasklist"/>
10	<anchor id="java"/>
11	<anchor id="xml"/>
12	<anchor id="bugzilla"/>
13	<anchor id="monitor"/>
14	<topic label="For Developers" href="doc/developer/index.html">
15	<topic label="Release Notes" href="doc/developer/changes.html"/>
16	</topic>
17	-->
18	</toc>	8	</toc>
19		9
20		10

Lines 1-19 Link Here

(-)doc/overview.html (-18 / +58 lines)
1	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2	<html>	1	<html>
3	<head>	2	<head>
4	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >	3	<meta name="copyright"
5	<link rel="stylesheet" href="book.css" charset="ISO-8859-1" type="text/css">	4	content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
6	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">	5	<meta http-equiv="Content-Language" content="en-us">
7	<meta http-equiv="Content-Style-Type" content="text/css">	6	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
8	<title>	7	<link rel="STYLESHEET" href="book.css" charset="ISO-8859-1"
9	Mylar Overview	8	type="text/css">
10	</title>	9	<style>
11	</head>	10	td {
12	<body bgcolor="ffFFFF">	11	border-top: solid thin black;
13	<h1 align="center">	12	}
14	Mylar</h1>	13
15	<p>Mylar documentation is wiki-based and available online from:<b> <a href="http://eclipse.org/mylar/start.php">	14	img[alt] {
16	http://eclipse.org/mylar/start.php</a> </b></p>	15	background-color: #ffdddd;
17	<img src="images/mylar-overview-small.gif">	16	}
18	</body>	17
19	</html>	18	tr {
		19	vertical-align: top;
		20	}
		21	</style>
		22	<title>Mylar Overview</title>
		23	<script language="JavaScript"
		24	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
		25	</head>
		26
		27	<body>
		28
		29	<h2>Mylar Overview</h2>
		30
		31	<p>Mylar is a task-focused UI for Eclipse that makes working with
		32	very large workspaces as easy as working with small ones. Mylar extends
		33	Eclipse with mechanisms for keeping track of the tasks that you work on.
		34	A task is defined as any unit of work that you want to recall or share
		35	with others, such as a bug reported by a user or a note to yourself
		36	about improving a feature. You can store tasks locally in your
		37	workspace, or they can come from one or more task repositories. To
		38	connect to a task repository, you must have a connector that supports
		39	that repository. (A task repository is a bug/ticket/issue tracker such
		40	as Bugzilla, Trac, or JIRA).</p>
		41	<p>Once your tasks are integrated, Mylar monitors your work activity
		42	on those tasks to identify information relevant to the task-at-hand.
		43	Mylar monitors Eclipse and captures your interaction in a task context.
		44	System artifacts such as files, types, methods, and fields get assigned
		45	a degree-of-interest based on how recently and frequently you interact
		46	with them. This results in uninteresting elements being filtered from
		47	view within Eclipse, allowing you to focus on on what is important. From
		48	this, Mylar creates a task context, which is the set of all artifacts
		49	related to your task. These can include methods you have edited, APIs
		50	you have referred to, and documents you have browsed. Mylar uses this
		51	task context to focus the Eclipse UI on interesting information, hide
		52	what's uninteresting, and automatically find what's related. Having the
		53	information you need to get your work done at your fingertips improves
		54	your productivity by reducing the time you spend searching, scrolling,
		55	and navigating. By making task context explicit, Mylar also facilitates
		56	multitasking, planning, reusing past efforts, and sharing expertise.</p>
		57
		58	</body>
		59	</html>

Lines 51-56 Link Here

(-)plugin.xml (+40 lines)
51	commandId="org.eclipse.mylar.doc.legend.show"	51	commandId="org.eclipse.mylar.doc.legend.show"
52	schemeId ="org.eclipse.ui.defaultAcceleratorConfiguration">	52	schemeId ="org.eclipse.ui.defaultAcceleratorConfiguration">
53	</key>	53	</key>
		54	</extension>
		55	<extension
		56	point="org.eclipse.ui.intro.configExtension">
		57	<configExtension
		58	configId="org.eclipse.ui.intro.universalConfig"
		59	content="intro/overviewExtensionContent.xml">
		60	</configExtension>
		61	<configExtension
		62	configId="org.eclipse.ui.intro.universalConfig"
		63	content="intro/whatsnewExtensionContent.xml">
		64	</configExtension>
		65	<configExtension
		66	configId="org.eclipse.ui.intro.universalConfig"
		67	content="intro/tutorialsExtensionContent.xml">
		68	</configExtension>
		69	</extension>
		70	<extension
		71	point="org.eclipse.ui.cheatsheets.cheatSheetContent">
		72	<category
		73	id="org.eclipse.mylar.cheatsheet"
		74	name="Mylar">
		75	</category>
		76	<cheatsheet
		77	category="org.eclipse.mylar.cheatsheet"
		78	contentFile="cheatsheets/Query.xml"
		79	id="org.eclipse.mylar.cheatsheet.query"
		80	name="Create a query from bugs.eclipse.org">
		81	<description>
		82	Learn how to create a query from bugs.eclipse.org
		83	</description>
		84	</cheatsheet>
		85	<cheatsheet
		86	category="org.eclipse.mylar.cheatsheet"
		87	contentFile="cheatsheets/TaskFocus.xml"
		88	id="org.eclipse.mylar.cheatsheet.taskfocus"
		89	name="Use Task-Focused UI">
		90	<description>
		91	Learn how to use Task-Focused UI
		92	</description>
		93	</cheatsheet>
54	</extension>	94	</extension>
55		95
56	</plugin>	96	</plugin>

Added Link Here

(-)intro/css/tutorials.css (+15 lines)
1	a#mylar-query img {
2	background-image: url(../../images/topiclabel/tu_query48.gif);
3	}
4
5	a#mylar-query:hover img {
6	background-image: url(../../images/topiclabel/tu_query48_hov.gif);
7	}
8
9	a#mylar-task img {
10	background-image: url(../../images/topiclabel/tu_task48.gif);
11	}
12
13	a#mylar-task:hover img {
14	background-image: url(../../images/topiclabel/tu_task48_hov.gif);
15	}

Added Link Here

(-)doc/new.html (+547 lines)
1	<html>
2	<head>
3	<meta name="copyright"
4	content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
5	<meta http-equiv="Content-Language" content="en-us">
6	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
7	<link rel="STYLESHEET" href="book.css" charset="ISO-8859-1"
8	type="text/css">
9	<style>
10	td {
11	border-top: solid thin black;
12	}
13
14	img[alt] {
15	background-color: #ffdddd;
16	}
17
18	tr {
19	vertical-align: top;
20	}
21	</style>
22	<title>What's New in Mylar 2.0</title>
23	<script language="JavaScript"
24	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
25	</head>
26
27	<body>
28	<h2>What's New in Mylar 2.0</h2>
29	<p>Here are descriptions of some of the more interesting or
30	significant changes made to Mylar. They are grouped into:</p>
31	<ul>
32	<li><a href="#Tasks">Tasks</a></li>
33	<li><a href="#TaskRepositories">Task Repositories</a></li>
34	<li><a href="#Team">Team</a></li>
35	<li><a href="#TaskContext">Task Context</a></li>
36	<li><a href="#BugzillaConnector">Bugzilla Connector</a></li>
37	<li><a href="#JIRAConnector">JIRA Connector</a></li>
38	<li><a href="#TracConnector">Trac Connector</a></li>
39	</ul>
40	<br>
41
42	<table cellpadding="10" cellspacing="0" width="600">
43	<colgroup>
44	<col width="20%">
45	<col width="80%">
46	</colgroup>
47	<tbody>
48
49	<tr>
50	<td colspan="2"><a name="Tasks"></a>
51	<div style="font-size: 20px; font-weight: bold;">Tasks</div>
52	</td>
53	</tr>
54
55	<tr>
56	<td valign="top">
57	<p align="right"><b> New Task List layout </b></p>
58	</td>
59	<td valign="top">The <i>Task List</i> layout has been updated to
60	use a custom drawn tree instead of relying on multiple columns in
61	order to provide the following improvements:
62	<ul>
63	<li>Support for subtasks (for an example see the Bugzilla
64	section)</li>
65	<li>The icon columns no longer take up a large amount of
66	horizontal space, making more of the Summary visible.  Sort
67	using <i>Sort by</i> in the view menu.</li>
68	<li>The table header and horizontal scrollbar are gone, making
69	2-3 more tasks visible.</li>
70	<li>The icon scheme has been updated to make incoming
71	indicators easier to pick out, hits more consistent with tasks, and
72	the kind of task appear on the icon (see the <i>Help -> Mylar
73	UI Legend</i> for the updated scheme).  Note in particular that new
74	tasks now have the task icon background and are distinguished by a
75	special incoming indicator.</li>
76	</ul>
77	<p>Note that the incoming overlays can also be configured to use
78	the Synchronize view style icons and left-facing placement via <i>Preferences
79	-> Task List -> Layout</i>.  Please use <a
80	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=182772">bug
81	182772</a> for feedback or reporting any OS-specific rendering problems.</p>
82	<p><img src="images/2.0M3/tasklist-tree.gif">
83	</td>
84	</tr>
85
86	<tr>
87	<td valign="top">
88	<p align="right"><b>UI Legend for Connectors</b></p>
89	</td>
90	<td valign="top"><i>Help -> Mylar UI Legend</i> now displays
91	connector-specific icon contributions.
92	<p><img src="images/2.0M3/ui-legend-connectors.gif">
93	</td>
94	</tr>
95
96	<tr>
97	<td valign="top">
98	<p align="right"><b>Content Assist in Task Editor</b></p>
99	</td>
100	<td valign="top">The Task Editor now supports content
101	assist.  The proposals include all usernames/emails associated
102	with an "Assigned to" for all bugs in the repository.
103	The username in the repository credentials is used to highlight your
104	username.
105	<p><img src="images/2.0M3/tasks-content-assist.gif">
106	</td>
107	</tr>
108
109	<tr>
110	<td valign="top">
111	<p align="right"><b>Task tooltips show changes</b></p>
112	</td>
113	<td valign="top">Task List tooltips now summarize incoming
114	changes, making it easier to scan for changes without opening the
115	task editor.  Note that the popup menu can be used to mark tasks
116	read without opening.
117	<p><img src="images/2.0M3/task-tooltip-incoming.gif">
118	</td>
119	</tr>
120
121	<tr>
122	<td valign="top">
123	<p align="right"><b>Task Working Sets<br>
124	(Experimental)<br>
125	3.3 only</b></p>
126	</td>
127	<td valign="top">Categories and Queries can be added to a Task
128	Working Set.  Switching Task Working Sets makes only the tasks
129	for that working set appear.  This can be useful for those with
130	a large Task List, several non-overlapping projects, different sets
131	of tasks for different venues (e.g. home vs. work).  For 2.0M3
132	switching working sets is only supported via the working set switcher
133	on the main toolbar.  To switch to see only one working set you
134	need to Ctrl+click that working set, otherwise multiple will be
135	visible.  The create a new Task Working Set use the <i>Edit...</i>
136	button visible below.
137	<p><img src="images/2.0M3/tasks-working-sets.gif">
138	</td>
139	</tr>
140
141	<tr>
142	<td valign="top">
143	<p align="right"><b>Offline Improvements</b></p>
144	</td>
145	<td valign="top">The offline support has been improved to be
146	more transparent.  Offline data for all tasks, even unread ones,
147	is downloaded in the background, so before going offline all you need
148	to do is run one successful synchronization.  If switching
149	frequently between being connected note that you can toggle
150	background synchronizations via the <i> Synchronize Automatically</i>
151	button in the <i>Task List</i> view menu.  Opening repository
152	tasks is now much faster due to synchronization and offline
153	concurrency improvements.  Any submission errors are now shown
154	on the task editor header (Eclipse 3.3) instead of the <i>Error
155	Log</i> view.  Also note that the <i>History</i> button is now on
156	the toolbar and a <i>Submit </i>buttons has been added as well.
157	<p><img src="images/2.0M3/task-editor-error.gif">
158	</td>
159	</tr>
160
161	<tr>
162	<td valign="top">
163	<p align="right"><b>Task Editor Improvements</b></p>
164	</td>
165	<td valign="top">The performance of repository task opening has
166	improved dramatically because there are no more synchronous trips to
167	the server and all editor pages load lazily.  If editor contents
168	become stale, the header will be updated as below (Eclipse 3.3) or a
169	dialog will show (Eclipse 3.2).  The <i>Synchronize</i> button
170	on the right of the header retrieves the latest contents.  There
171	have also been numerous layout and improvements.
172	<p><img src="images/2.0M2/task-editor-warning.gif">
173	</td>
174	</tr>
175
176	<tr>
177	<td valign="top">
178	<p align="right"><b>Hyperlinks in Text Editors<br>
179	(3.3 only)</b></p>
180	</td>
181	<td valign="top">Hyperlinks are now supported in all text
182	editors.  Modify enablement or behavior via <i>Preferences
183	-> General -> Editors -> Text Editors -> Hyperlinking.</i>
184	<p><img src="images/2.0M2/hyperlinks-text.gif">
185	</td>
186	</tr>
187
188	<tr>
189	<td valign="top">
190	<p align="right"><b>Scheduled Task Presentation<br>
191	(Experimental)</b></p>
192	</td>
193	<td valign="top">The <i>Task Activity</i> view has been removed
194	and replaced by the <i>Scheduled</i> presentation of the <i>Task
195	List</i>.  When in focused mode this presentation shows only the
196	tasks scheduled for the current workweek.  Since unscheduled
197	query hits will not show, this makes it easier to work without
198	getting distracted by incoming items.  To focus on the workday,
199	use the <i>Go Into</i> action on the day container.  When the
200	focused mode is off, this presentation both past task activity and
201	tasks scheduled for the future.
202	<p><img src="images/2.0M2/tasklist-schedule.gif">
203	</td>
204	</tr>
205
206	<tr>
207	<td valign="top">
208	<p align="right"><b>Task Editor lifecycle streamlined</b></p>
209	</td>
210	<td valign="top">The <i>Task Editor</i> no longer closes on
211	submission, and instead shows progress while it synchronizes with the
212	repository. If incoming changes occur while editor is open the
213	refresh will preserve and mark any outgoing changes.  In order
214	to clear outgoing changes use the context menu -> <i>Mark </i>->
215	<i> Clear Outgoing</i>.  If an editor is opened for a task not
216	in the <i> Task List </i>the <i>Add to Task List</i> action can be
217	used on the editor's context menu. Formatting of the editor has been
218	improved and uses the new form look on Eclipse 3.3.
219	<p><img src="images/2.0M1/task-editor-progress.gif">
220	</td>
221	</tr>
222
223	<tr>
224	<td valign="top">
225	<p align="right"><b>Hyperlinks in Java Editor<br>
226	(3.3 only)</b></p>
227	</td>
228	<td valign="top">References to tasks and bugs in the Java Editor
229	and now hyperlinked consistently with the Task Editor.  The Task
230	Repository must be defined on the corresponding project (set via <i>Project
231	Properties </i>-> <i>Task Repository</i>). References to tasks must be
232	moused over to turn into hyperlinks.
233	<p><img src="images/2.0M1/java-editor-hyperlink.gif">
234	</td>
235	</tr>
236
237	<tr>
238	<td valign="top">
239	<p align="right"><b>Drag and Drop improvements</b></p>
240	</td>
241	<td valign="top">To attach files to a repository task them onto
242	the Task Editor from a navigator view or operating system
243	window.  Dragging a URL that corresponds to a task onto the Task
244	List will cause the corresponding task to be created and added to the
245	Task List, if the corresponding repository exists.</td>
246	</tr>
247
248	<tr>
249	<td colspan="2"><a name="TaskRepositories"></a>
250	<div style="font-size: 20px; font-weight: bold;">Task
251	Repositories</div>
252	</td>
253	</tr>
254
255	<tr>
256	<td valign="top">
257	<p align="right"><b>Platform Proxy Settings<br>
258	(3.3 only)</b></p>
259	</td>
260	<td valign="top">By default task repositories now use the global
261	platform proxy settings instead of the Platform Update
262	settings.  These can be overridden per-repository.
263	<p><img src="images/2.0M2/repository-settings-proxy.gif">
264	</td>
265	</tr>
266
267	<tr>
268	<td valign="top">
269	<p align="right"><b>Max hits settings removed</b></p>
270	</td>
271	<td valign="top">The "Max hits" setting on task
272	repository queries has been removed since it was too easy to not
273	notice when the max was reached.</td>
274	</tr>
275
276	<tr>
277	<td colspan="2"><a name="Team"></a>
278	<div style="font-size: 20px; font-weight: bold;">Team</div>
279	</td>
280	</tr>
281
282	<tr>
283	<td valign="top">
284	<p align="right"><b>Hyperlinks in Annotations and History<br>
285	(3.3 only)</b></p>
286	</td>
287	<td valign="top">Team annotations, enabled in the Java editor
288	via popup menu -> <i> Team -> Show Annotation</i> now show
289	hyperlinked references to tasks.  Note that you must press F2
290	for focus and Ctrl to activate the hyperlink.  Task Hyperlinks
291	are also available in the <i>History</i> view.
292	<p><img src="images/2.0M3/team-hyperlinks-annotations.gif">
293	<p><img src="images/2.0M3/team-hyperlinks-history.gif">
294	</td>
295	</tr>
296
297	<tr>
298	<td colspan="2"><a name="TaskContext"></a>
299	<div style="font-size: 20px; font-weight: bold;">Task Context</div>
300	</td>
301	</tr>
302
303	<tr>
304	<td valign="top">
305	<p align="right"><b>UI Usage Reports<br>
306	(Experimental)<br>
307	3.3 only</b></p>
308	</td>
309	<td valign="top"><i>File -> New -> Other -> Mylar
310	-> UI Usage Report</i> will generate a report of your perspective,
311	view, preference, command and editor usage in Eclipse.  This
312	reporting facility builds on the Mylar Monitor used to study early
313	releases of Mylar and has been extended to upload statistics to the
314	mylar.eclipse.org server where they can be accessed by all interested
315	(via the button in the <i> Actions</i> section).  As before, we
316	will be using these statistics as input to evolving and improving the
317	Mylar UI.
318	<p><i>UI Usage Reporting</i> is installable as a separate feature
319	that can be used independently of the rest of Mylar.  Currently
320	it is only available to Eclipse 3.3 users but will be made available
321	to 3.2 users for the next release.  If installed it will ask to
322	run once every three weeks, at which point you will see statistics
323	displayed as below.  We then ask that you share your usage data
324	with the community, via the <i>Submit to Eclipse.org</i> button, so
325	that it can help inform Eclipse developers how the UI is being
326	used.  Note that only interaction events that have IDs starting
327	with "org.eclipse" will be uploaded in order to avoid
328	having private ID names made public.  Note that the information
329	gathered also includes interaction information about elements, so to
330	avoid sharing the IDs of private elements make sure to leave on
331	"Obfuscate elements using SHA message digest one-way hash"
332	via the <i>Preferences -> Mylar -> Usage Data</i> page.
333	More information on how the monitor works can be found in <a
334	href="http://wiki.eclipse.org/index.php/Mylar_Integrator_Reference#Monitor_API">
335	Eclipsepedia</a>.</p>
336	<p><img src="images/2.0M3/ui-usage-report.gif">
337	</td>
338	</tr>
339
340	<tr>
341	<td valign="top">
342	<p align="right"><b>Context Activation Improvements</b></p>
343	</td>
344	<td valign="top">Task contexts are now dramatically quicker to
345	activate and provide a perfect restore of the editors that were
346	available when the task was deactivated.  This includes
347	restoring the line numbers and selections of editors closed.  As
348	a result there should be no more need to use the "Pause
349	Capturing Context" action and we are considering removing it
350	(comment on <a
351	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=186874">bug
352	186874</a> if you still have a use case for it).</td>
353	</tr>
354
355	<tr>
356	<td valign="top">
357	<p align="right"><b>Quick Context View</b></p>
358	</td>
359	<td valign="top">There is now quick view of the task context
360	that  similar to the Ctrl+O quick outline.  Invoke it via <i>Navigate
361	-> Quick Context view</i> or Ctrl+Alt+Shift+RightArrow.  This
362	quick view can be used to show the task context when a navigator view
363	is not visible (e.g. in the <i>Debug</i> perspective) or when the
364	navigator view is not in filtered mode.
365	<p><img src="images/2.0M2/context-quick-view.gif">
366	</td>
367	</tr>
368
369	<tr>
370	<td valign="top">
371	<p align="right"><b>Retrieve from Attachments Table</b></p>
372	</td>
373	<td valign="top">The <i>Retrieve Context</i> action on the
374	attachments table can be used to bypass the <i>Retrieve Context</i>
375	wizard.
376	<p><img src="images/2.0M2/context-apply-attachments.gif">
377	</td>
378	</tr>
379
380	<tr>
381	<td valign="top">
382	<p align="right"><b>Add to Task Context from Synchronize View</b></p>
383	</td>
384	<td valign="top">The <i>Add to Task Context</i> action can be
385	invoked on change sets or resources that appear in the <i>Synchronize
386	</i>view.  This can be useful when an incoming change set should be
387	reviewed but has no corresponding task context or when outgoing
388	changes have no task context, e.g. if applied from a patch with no
389	context attached.
390	<p><img src="images/2.0M2/synchronize-view-add.gif">
391	</td>
392	</tr>
393
394	<tr>
395	<td valign="top">
396	<p align="right"><b>Task Context editor</b></p>
397	</td>
398	<td valign="top">The <i>Context</i> tab on the Task Editor
399	provides a preview of the task context contents.  This facility
400	can be used to remove elements and edit their interest, for example,
401	before sharing the context with others. When first opened this view
402	will show all of the elements in the task context that have a
403	corresponding content provider (e.g. Java elements and files). For
404	long-running tasks this can cause a large number of elements that
405	have decayed in interest to show.  The filter slider bar can be
406	used to adjust degree-of-interest threshold to show only the most
407	interesting elements.
408	<p><img src="images/2.0M1/task-context-editor.gif">
409	</td>
410	</tr>
411
412	<tr>
413	<td colspan="2"><a name="BugzillaConnector"></a>
414	<div style="font-size: 20px; font-weight: bold;">Bugzilla
415	Connector</div>
416	</td>
417	</tr>
418
419	<tr>
420	<td valign="top">
421	<p align="right"><b>Dependencies show as subtasks<br>
422	(Experimental)</b></p>
423	</td>
424	<td valign="top">If a bug A is set to "depend on" B,
425	bug B will be shown as a subtask of A.  This supports creating
426	dependent bugs to indicate that the work is not completed until all
427	dependent bugs are done.  Enable this functionality by toggling
428	off <i>Filter Subtasks</i> in the <i>Task List</i> view menu.
429	<p><img src="images/2.0M3/bugzilla-subtasks.gif">
430	</td>
431	</tr>
432
433	<tr>
434	<td valign="top">
435	<p align="right"><b>Shared Due Dates and Time Tracking</b></p>
436	</td>
437	<td valign="top">If Time Tracking is enabled on the repository,
438	shared due dates can be scheduled.  When the due date arrives
439	the task will get a small red bell overlay in its upper-right
440	corner.  Personal scheduled for dates can be used independently
441	of due dates.  Tasks with due dates that are not past will have
442	a blue bell overlay instead.  If the time tracking is not
443	enabled, or not supported by the repository, due dates can be used
444	locally as with personal tasks.
445	<p><img src="images/2.0M2/bugzilla-due-dates.gif">
446	</td>
447	</tr>
448
449	<tr>
450	<td valign="top">
451	<p align="right"><b>Local user names</b></p>
452	</td>
453	<td valign="top">If your Bugzilla repository is configured to
454	use local user IDs rather than full email IDs enable the
455	corresponding option on the <i> Task Repository </i>properties page.
456	<p><img src="images/2.0M1/bugzilla-local-users.gif">
457	</td>
458	</tr>
459
460	<tr>
461	<td colspan="2"><a name="JIRAConnector"></a>
462	<div style="font-size: 20px; font-weight: bold;">JIRA Connector</div>
463	</td>
464	</tr>
465
466	<tr>
467	<td valign="top">
468	<p align="right"><b>Attachment support</b></p>
469	</td>
470	<td valign="top">The JIRA task editor now supports attachments,
471	both for files and for task contexts.  Submission errors are now
472	displayed instead of failing silently.
473	<p><img src="images/2.0M3/jira-attachments.gif">
474	</td>
475	</tr>
476
477	<tr>
478	<td valign="top">
479	<p align="right"><b>Hyperlinks in Java Editor<br>
480	(3.3 only)</b></p>
481	</td>
482	<td valign="top">If a JIRA repository is set as the task
483	repository on a project hyperlinking will work per task key.
484	<p><img src="images/2.0M2/jira-java-hyperlinks.gif">
485	</td>
486	</tr>
487
488	<tr>
489	<td valign="top">
490	<p align="right"><b>Proxies and Http Auth</b></p>
491	</td>
492	<td valign="top">The JIRA Connector now supports proxy settings
493	and http auth.  In addition, there have been numerous bug fixes
494	of connectivity and rich editor support.</td>
495	</tr>
496
497	<tr>
498	<td valign="top">
499	<p align="right"><b>Hyperlinks in Task Editor</b></p>
500	</td>
501	<td valign="top">References to JIRA issue keys are now
502	hyperlinked.
503	<p><img src="images/2.0M1/jira-editor-hyperlink.gif">
504	</td>
505	</tr>
506
507	<tr>
508	<td valign="top">
509	<p align="right"><b>JIRA Core Services</b></p>
510	</td>
511	<td valign="top">The JIRA feature will now install without
512	requiring additional downloads from Tigris.org.</td>
513	</tr>
514
515	<tr>
516	<td colspan="2"><a name="TracConnector"></a>
517	<div style="font-size: 20px; font-weight: bold;">Trac Connector</div>
518	</td>
519	</tr>
520
521	<tr>
522	<td valign="top">
523	<p align="right"><b>Hyperlinks in Task Editor<br>
524	(3.3 only)</b></p>
525	</td>
526	<td valign="top">Trac hyperlinks are now supported in the task
527	editor.
528	<p><img src="images/2.0M2/trac-hyperlinks.gif">
529	</td>
530	</tr>
531
532	<tr>
533	<td valign="top">
534	<p align="right"><b>Custom Fields</b></p>
535	</td>
536	<td valign="top">
537	<p class="MsoPlainText">Trac now supports the selection from a
538	list of pre-defined values for custom fields.</p>
539	</td>
540	</tr>
541	</tbody>
542	</table>
543
544	<p> </p>
545
546	</body>
547	</html>

Added Link Here

(-)intro/tutorialsExtensionContent.xml (+18 lines)
1	<?xml version="1.0" encoding="UTF-8" ?>
2	<introContent>
3	<extensionContent id="org.eclipse.mylar" name="Mylar"
4	style="css/tutorials.css" path="tutorials/@">
5	<group label="Mylar" id="mylar" style-id="content-group">
6	<link
7	url="http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.platform.cheatsheet&input=org.eclipse.mylar.cheatsheet.query"
8	label="Create a query" id="mylar-query" style-id="content-link">
9	<text>Learn how to create a query from bugs.eclipse.org.</text>
10	</link>
11	<link
12	url="http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.platform.cheatsheet&input=org.eclipse.mylar.cheatsheet.taskfocus"
13	label="Use Task-Focused UI" id="mylar-task" style-id="content-link">
14	<text>Learn how to use Task-Focused UI.</text>
15	</link>
16	</group>
17	</extensionContent>
18	</introContent>

Added Link Here

(-)cheatsheets/Query.xml (+37 lines)
1	<?xml version="1.0" encoding="UTF-8"?>
2	<cheatsheet title="Create a query from bugs.eclipse.org">
3	<intro>
4	<description>
5	This cheat sheet shows you how to create a query from bugs.eclipse.org.<br/>
6	</description>
7	</intro>
8	<item title="Open the Task List view" dialog="true" skip="false">
9	<description>
10	If the Task List view is not opened, select in the main menu <b>Window</b> > <b>Show View</b> > <b>Other...</b> > <b>Mylar</b> > <b>Task List</b> or click on the "Click to Perform" link below.
11	</description>
12	<command serialization="org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.mylar.tasks.ui.views.TaskListView)" confirm="true">
13	</command>
14	</item>
15	<item title="Create a new Query" dialog="true" skip="false">
16	<description>
17	In the Task List view, click on the right mouse button then select <b>New > Query</b> or click on the "Click to Perform" link below.
18	</description>
19	<command serialization="org.eclipse.ui.newWizard(newWizardId=org.eclipse.mylar.tasks.ui.wizard.new.query)" confirm="true">
20	</command>
21	</item>
22	<item title="Add Task Repository" dialog="true" skip="true">
23	<description>
24	If <b>Eclipse.org</b> is on your repository list, you can <b>skip</b> this step.
25	<br/><br/>
26	Click on the <b>Add Repository Task</b> button in the Query dialog. Select Bugzilla on the list then click on the Next button. Enter <b>https://bugs.eclipse.org/bugs</b> for the server's address, <b>Eclipse.org</b> for the label then click on the <b>Finish</b> button.
27	</description>
28	</item>
29	<item title="Setup the query" dialog="true" skip="false">
30	<description>
31	Select <b>Eclipse.org</b> then click on the <b>Next</b> button.<br/>
32	Select <b>Create a query using form</b> then click on the <b>Next</b> button.<br/>
33	Enter <b>Mylar bugs</b> for the query's title.
34	Select <b>Mylar</b> from the Product and <b>P1, P2</b> from the Priority then click on the <b>Finish</b> button.
35	</description>
36	</item>
37	</cheatsheet>

Added Link Here

(-)intro/whatsnewExtensionContent.xml (+15 lines)
1	<?xml version="1.0" encoding="UTF-8" ?>
2	<introContent>
3	<extensionContent id="org.eclipse.mylar" name="Mylar"
4	style="css/whatsnew.css" path="whatsnew/@">
5	<group id="content-group" style-id="content-group">
6	<link label="Mylar"
7	url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.mylar.doc/doc/new.html"
8	id="mylar-noteworthy" style-id="content-link">
9	<text>
10	Find out the significant changes made to Mylar
11	</text>
12	</link>
13	</group>
14	</extensionContent>
15	</introContent>

Added Link Here

(-)intro/overviewExtensionContent.xml (+13 lines)
1	<?xml version="1.0" encoding="utf-8" ?>
2	<introContent>
3	<extensionContent id="org.eclipse.mylar" name="Mylar"
4	style="css/overview.css" path="overview/@">
5	<group id="content-group" style-id="content-group">
6	<link label="Mylar"
7	url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.mylar.doc/doc/overview.html"
8	id="mylar-overview" style-id="content-link">
9	<text>Learn more about Mylar task-focused ui</text>
10	</link>
11	</group>
12	</extensionContent>
13	</introContent>

Added Link Here

(-)cheatsheets/TaskFocus.xml (+93 lines)
1	<?xml version="1.0" encoding="UTF-8"?>
2	<cheatsheet title="Use Task-Focused UI">
3	<intro>
4	<description>
5	This cheat sheet shows you how to handle a task lifecycle and how to use task-focused ui.<br/>
6	</description>
7	</intro>
8	<item title="Open the Plug-in perspective" dialog="true" skip="false">
9	<description>
10	If you're not already in Plug-in Development perspective in the main menu select <b>Window</b> > <b>Open Perspective</b> > <b>Other...</b> > <b>Plug-in Development</b> or click on the "Click to Perform" link below.
11	</description>
12	<command serialization="org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.pde.ui.PDEPerspective)" confirm="true">
13	</command>
14	</item>
15	<item title="Open the Task List view" dialog="true" skip="false">
16	<description>
17	If the Task List view is not opened, select in the main menu <b>Window</b> > <b>Show View</b> > <b>Other...</b> > <b>Mylar</b> > <b>Task List</b> or click on the "Click to Perform" link below.
18	</description>
19	<command serialization="org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.mylar.tasks.ui.views.TaskListView)" confirm="true">
20	</command>
21	</item>
22	<item title="Create a sample project" dialog="true" skip="false">
23	<description>
24	Before we start this cheat sheet, we need a project to practice.
25	<br/><br/>
26	In the main toolbar, click on the <b>New</b> button. Select the <b>Plug-in Project</b> from the list then click on the <b>Next</b> button. Enter <b>SampleProject</b> for the project's name then click on the <b>Next</b> button twice.
27	Select from the Templates part <b>Hello, World</b> then click on the <b>Finish</b> button.
28	</description>
29	</item>
30	<item title="Create and activate a task" dialog="true" skip="false">
31	<description>
32	In the Task List view, click on the right mouse button, then select <b>New > Category</b>. Enter <b>Tutorials</b> for the category's name.
33	<br/><br/>
34	Then right click on the <b>Tutorials</b> category and select <b>New > Task</b>. Enter <b>Learn task-focus</b> for the task's title and change the priority to <b>High</b>. You can add some notes, too.
35	<br/><br/>
36	Right click on the new task and select <b>Activate</b> to activate the task.
37	<br/><br/>
38	<b>Important:</b> If it's not activated, click on the <b>"Focus on the Active Task"</b> toogle button in the <b>Package Explorer</b> and in the <b>Outline</b> view too.
39	</description>
40	</item>
41	<item title="Open SampleAction file" dialog="true" skip="false">
42	<description>
43	Press down the <b>Ctrl+Shift+T</b> buttons or click on the "Click to Perform" link below. <br/>
44	In the <b>Open Type</b> dialog enter <b>SampleAction</b> for the type's name then press the <b>Enter</b> button.<br/>
45	After the file is opened you can see the SampleAction class both in the <b>Package Explorer</b> and in the <b>Outline</b> view.
46	</description>
47	<command serialization="org.eclipse.jdt.ui.navigate.open.type" confirm="true">
48	</command>
49	</item>
50	<item title="Add method to focus" dialog="true" skip="false">
51	<description>
52	Select in the Editor the <b>void run(IAction action)</b> method then you can see the <b>run(IAction)</b> method in the <b>Outline</b> view and in the <b>Package Explorer</b> under the SampleAction class.
53	<br/><br/>
54	Next press the Alt button and click on the SampleAction class in the <b>Outline</b> view.<br/>
55	Now you can see all methods. Methods which aren't in the focus are in <b>grey</b> color. Select <b>window</b> field from the list. After that all methods will disappear which aren't in the focus.
56	</description>
57	</item>
58	<item title="Landmark" dialog="true" skip="false">
59	<description>
60	If an element's interest ranks high enough, it becomes a landmark, which is an implicitly created bookmark. Landmarks are showed in bold font.
61	<br/><br/>
62	Select the <b>run(IAction)</b> method in the <b>Outline</b> view or in the <b>Package Explorer</b>. Right click on the method and select <b>Mark as Landmark</b>. After then this method becomes a landmark.
63	<br/><br/>
64	Also you can use key bindings. <b>Ctrl+Shift+Alt+UpArrow</b> to mark the element as landmark or <b>Ctrl+Shift+Alt+DownArrow</b> to mark less interesting for the element.
65	</description>
66	</item>
67	<item title="Remove method from focus" dialog="true" skip="true">
68	<description>
69	Right click on the <b>window</b> field and select <b>Remove from Focus</b>. The window field will disappear on the list.
70	</description>
71	</item>
72	<item title="Open Activator.java" dialog="true" skip="false">
73	<description>
74	Press down the <b>Alt</b> button and <b>click</b> on the <b>src</b> directory. Then you can see 3 packages. <br/>
75	<b>Alt+click</b> on the <b>sampleproject</b> package and you can open the Activator.java file with a simple double-click on the file name.
76	<br/><br/>
77	You can use <b>Alt+RightArrow</b> instead of <b>Alt+click</b>.
78	</description>
79	</item>
80	<item title="Quick Context View" dialog="true" skip="false">
81	<description>
82	Press down <b>Ctrl+Shift+Alt+RightArrow</b> buttons, then you can see all elements which are in the focus.
83	</description>
84	</item>
85	<item title="Complete task" dialog="true" skip="false">
86	<description>
87	In the Task List view, click on the right mouse button on the <b>Learn task-focus</b> task and select deactivate.
88	<br/>
89	Click again on the task with the right mouse button and select <b>Mark > Complete</b>. <br/>
90	After then the task's name will be struck through.
91	</description>
92	</item>
93	</cheatsheet>