Attachment 68854 Details for Bug 185836 – universal intro patch

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

[patch] universal intro patch

185836-intro.txt (text/plain), 42.31 KB, created by Balazs Brinkus

on 2007-05-26 08:36:46 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Balazs Brinkus

Created: 2007-05-26 08:36:46 EDT

Size: 42.31 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.mylar.doc
>Index: doc/toc.xml
>===================================================================
>RCS file: /cvsroot/technology/org.eclipse.mylar/org.eclipse.mylar.doc/doc/toc.xml,v
>retrieving revision 1.7
>diff -u -r1.7 toc.xml
>--- doc/toc.xml	17 Feb 2007 02:00:55 -0000	1.7
>+++ doc/toc.xml	26 May 2007 12:30:50 -0000
>@@ -1,20 +1,10 @@
> <?xml version="1.0" encoding="UTF-8"?>
> <?NLS TYPE="org.eclipse.help.toc"?>
> 
>-<toc label="Mylar"> 
>-	<topic label="Overview" href="doc/overview.html"/>
>-	
>+<toc label="Mylar">
>+	<topic label="Overview" href="doc/overview.html" />
>+	<topic label="What's new" href="doc/new.html" />
>+	
> </toc>
> 
>-	
>+
>Index: doc/overview.html
>===================================================================
>RCS file: /cvsroot/technology/org.eclipse.mylar/org.eclipse.mylar.doc/doc/overview.html,v
>retrieving revision 1.9
>diff -u -r1.9 overview.html
>--- doc/overview.html	16 Dec 2006 02:51:50 -0000	1.9
>+++ doc/overview.html	26 May 2007 12:30:50 -0000
>@@ -1,19 +1,59 @@
>-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
>- <head>
>-<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." >
>- <link rel="stylesheet" href="book.css" charset="ISO-8859-1" type="text/css">
>- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
>- <meta http-equiv="Content-Style-Type" content="text/css">
>- <title>
>- Mylar Overview
>- </title>
>- </head>
>-<body bgcolor="ffFFFF">
>- <h1 align="center">
>- Mylar</h1>
>-	Mylar documentation is wiki-based and available online from: <a href="http://eclipse.org/mylar/start.php">
>-	http://eclipse.org/mylar/start.php</a> 
>-	<img src="images/mylar-overview-small.gif">
>- </body>
>-</html>
>\ No newline at end of file
>+<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>
>+
>+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).
>+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.
>+
>+</body>
>+</html>
>Index: META-INF/MANIFEST.MF
>===================================================================
>RCS file: /cvsroot/technology/org.eclipse.mylar/org.eclipse.mylar.doc/META-INF/MANIFEST.MF,v
>retrieving revision 1.290
>diff -u -r1.290 MANIFEST.MF
>--- META-INF/MANIFEST.MF	24 May 2007 21:42:05 -0000	1.290
>+++ META-INF/MANIFEST.MF	26 May 2007 12:30:50 -0000
>@@ -10,7 +10,9 @@
> org.eclipse.mylar.tasks.core,
> org.eclipse.mylar.tasks.ui,
> org.eclipse.mylar,
>- org.eclipse.core.runtime
>+ org.eclipse.core.runtime,
>+ org.eclipse.ui.cheatsheets,
>+ org.eclipse.ui.intro
> Export-Package: org.eclipse.mylar.doc.internal.actions,
> org.eclipse.mylar.doc.internal.dialogs
> Bundle-RequiredExecutionEnvironment: J2SE-1.5
>Index: build.properties
>===================================================================
>RCS file: /cvsroot/technology/org.eclipse.mylar/org.eclipse.mylar.doc/build.properties,v
>retrieving revision 1.8
>diff -u -r1.8 build.properties
>--- build.properties	7 Sep 2006 17:40:18 -0000	1.8
>+++ build.properties	26 May 2007 12:30:50 -0000
>@@ -13,7 +13,10 @@
> doc/,\
> about.html,\
> .,\
>- icons/
>+ icons/,\
>+ intro/,\
>+ images/,\
>+ cheatsheets/
> src.includes = META-INF/,\
> plugin.xml,\
> about.html,\
>Index: plugin.xml
>===================================================================
>RCS file: /cvsroot/technology/org.eclipse.mylar/org.eclipse.mylar.doc/plugin.xml,v
>retrieving revision 1.10
>diff -u -r1.10 plugin.xml
>--- plugin.xml	21 Mar 2007 02:53:43 -0000	1.10
>+++ plugin.xml	26 May 2007 12:30:50 -0000
>@@ -51,6 +51,46 @@
> 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>
>Index: intro/css/tutorials.css
>===================================================================
>RCS file: intro/css/tutorials.css
>diff -N intro/css/tutorials.css
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ intro/css/tutorials.css	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,15 @@
>+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);
>+}
>Index: intro/css/whatsnew.css
>===================================================================
>RCS file: intro/css/whatsnew.css
>diff -N intro/css/whatsnew.css
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ intro/css/whatsnew.css	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,7 @@
>+a#mylar-noteworthy img {
>+	background-image: url(../../images/topiclabel/wn_mylar48.gif);
>+}
>+
>+a#mylar-noteworthy:hover img {
>+	background-image: url(../../images/topiclabel/wn_mylar48_hov.gif);
>+}
>Index: intro/css/overview.css
>===================================================================
>RCS file: intro/css/overview.css
>diff -N intro/css/overview.css
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ intro/css/overview.css	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,7 @@
>+a#mylar-overview img {
>+	background-image: url(../../images/topiclabel/ov_mylar48.gif);
>+}
>+
>+a#mylar-overview:hover img {
>+	background-image: url(../../images/topiclabel/ov_mylar48_hov.gif);
>+}
>Index: doc/new.html
>===================================================================
>RCS file: doc/new.html
>diff -N doc/new.html
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ doc/new.html	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,547 @@
>+<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>
>+Here are descriptions of some of the more interesting or
>+significant changes made to Mylar. They are grouped into:
>+<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>
>+ 
>+
>+<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">
>+			 New Task List layout 
>+			</td>
>+			<td valign="top">The Task List 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 Sort by 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 Help -&gt; Mylar
>+				UI Legend 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>
>+			Note that the incoming overlays can also be configured to use
>+			the Synchronize view style icons and left-facing placement via Preferences
>+			-&gt; Task List -&gt; Layout.&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.
>+			<img src="images/2.0M3/tasklist-tree.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			UI Legend for Connectors
>+			</td>
>+			<td valign="top">Help -&gt; Mylar UI Legend now displays
>+			connector-specific icon contributions.&nbsp;
>+			<img src="images/2.0M3/ui-legend-connectors.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Content Assist in Task Editor
>+			</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.
>+			<img src="images/2.0M3/tasks-content-assist.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Task tooltips show changes
>+			</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.
>+			<img src="images/2.0M3/task-tooltip-incoming.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Task Working Sets 
>+			(Experimental) 
>+			3.3 only
>+			</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 Edit...
>+			button visible below.
>+			<img src="images/2.0M3/tasks-working-sets.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Offline Improvements
>+			</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 Synchronize Automatically
>+			button in the Task List 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 Error
>+			Log view.&nbsp; Also note that the History button is now on
>+			the toolbar and a Submit buttons has been added as well.
>+			<img src="images/2.0M3/task-editor-error.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Task Editor Improvements
>+			</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 Synchronize button
>+			on the right of the header retrieves the latest contents.&nbsp; There
>+			have also been numerous layout and improvements.
>+			<img src="images/2.0M2/task-editor-warning.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Hyperlinks in Text Editors 
>+			(3.3 only)
>+			</td>
>+			<td valign="top">Hyperlinks are now supported in all text
>+			editors.&nbsp; Modify enablement or behavior via Preferences
>+			-&gt; General -&gt; Editors -&gt; Text Editors -&gt; Hyperlinking.
>+			<img src="images/2.0M2/hyperlinks-text.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Scheduled Task Presentation 
>+			(Experimental)
>+			</td>
>+			<td valign="top">The Task Activity view has been removed
>+			and replaced by the Scheduled presentation of the Task
>+			List.&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 Go Into 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;
>+			<img src="images/2.0M2/tasklist-schedule.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Task Editor lifecycle streamlined
>+			</td>
>+			<td valign="top">The Task Editor 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; Mark -&gt;
>+			 Clear Outgoing.&nbsp; If an editor is opened for a task not
>+			in the Task List the Add to Task List 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.
>+			<img src="images/2.0M1/task-editor-progress.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Hyperlinks in Java Editor 
>+			(3.3 only)
>+			</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 Project
>+			Properties -&gt; Task Repository). References to tasks must be
>+			moused over to turn into hyperlinks.
>+			<img src="images/2.0M1/java-editor-hyperlink.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Drag and Drop improvements
>+			</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">
>+			Platform Proxy Settings 
>+			(3.3 only)
>+			</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.
>+			<img src="images/2.0M2/repository-settings-proxy.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Max hits settings removed
>+			</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">
>+			Hyperlinks in Annotations and History 
>+			(3.3 only)
>+			</td>
>+			<td valign="top">Team annotations, enabled in the Java editor
>+			via popup menu -&gt; Team -&gt; Show Annotation 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 History view.
>+			<img src="images/2.0M3/team-hyperlinks-annotations.gif">
>+			<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">
>+			UI Usage Reports 
>+			(Experimental) 
>+			3.3 only
>+			</td>
>+			<td valign="top">File -&gt; New -&gt; Other -&gt; Mylar
>+			-&gt; UI Usage Report 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 Actions section).&nbsp; As before, we
>+			will be using these statistics as input to evolving and improving the
>+			Mylar UI.&nbsp;
>+			UI Usage Reporting 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 Submit to Eclipse.org 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 Preferences -&gt; Mylar -&gt; Usage Data 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>.
>+			<img src="images/2.0M3/ui-usage-report.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Context Activation Improvements
>+			</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">
>+			Quick Context View
>+			</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 Navigate
>+			-&gt; Quick Context view 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 Debug perspective) or when the
>+			navigator view is not in filtered mode.
>+			<img src="images/2.0M2/context-quick-view.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Retrieve from Attachments Table
>+			</td>
>+			<td valign="top">The Retrieve Context action on the
>+			attachments table can be used to bypass the Retrieve Context
>+			wizard.
>+			<img src="images/2.0M2/context-apply-attachments.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Add to Task Context from Synchronize View
>+			</td>
>+			<td valign="top">The Add to Task Context action can be
>+			invoked on change sets or resources that appear in the Synchronize
>+			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.
>+			<img src="images/2.0M2/synchronize-view-add.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Task Context editor
>+			</td>
>+			<td valign="top">The Context 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.
>+			<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">
>+			Dependencies show as subtasks 
>+			(Experimental)
>+			</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 Filter Subtasks in the Task List view menu.
>+			<img src="images/2.0M3/bugzilla-subtasks.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Shared Due Dates and Time Tracking
>+			</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;
>+			<img src="images/2.0M2/bugzilla-due-dates.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Local user names
>+			</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 Task Repository properties page.
>+			<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">
>+			Attachment support
>+			</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.
>+			<img src="images/2.0M3/jira-attachments.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Hyperlinks in Java Editor 
>+			(3.3 only)
>+			</td>
>+			<td valign="top">If a JIRA repository is set as the task
>+			repository on a project hyperlinking will work per task key.
>+			<img src="images/2.0M2/jira-java-hyperlinks.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Proxies and Http Auth
>+			</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">
>+			Hyperlinks in Task Editor
>+			</td>
>+			<td valign="top">References to JIRA issue keys are now
>+			hyperlinked.
>+			<img src="images/2.0M1/jira-editor-hyperlink.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			JIRA Core Services
>+			</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">
>+			Hyperlinks in Task Editor 
>+			(3.3 only)
>+			</td>
>+			<td valign="top">Trac hyperlinks are now supported in the task
>+			editor.
>+			<img src="images/2.0M2/trac-hyperlinks.gif">
>+			</td>
>+		</tr>
>+
>+		<tr>
>+			<td valign="top">
>+			Custom Fields
>+			</td>
>+			<td valign="top">
>+			Trac now supports the selection from a
>+			list of pre-defined values for custom fields.
>+			</td>
>+		</tr>
>+	</tbody>
>+</table>
>+
>+&nbsp;
>+
>+</body>
>+</html>
>Index: intro/tutorialsExtensionContent.xml
>===================================================================
>RCS file: intro/tutorialsExtensionContent.xml
>diff -N intro/tutorialsExtensionContent.xml
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ intro/tutorialsExtensionContent.xml	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,18 @@
>+<?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>
>Index: cheatsheets/Query.xml
>===================================================================
>RCS file: cheatsheets/Query.xml
>diff -N cheatsheets/Query.xml
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ cheatsheets/Query.xml	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,37 @@
>+<?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. 
>+ </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 Window &gt; Show View &gt; Other... &gt; Mylar &gt; Task List 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 New &gt; Query 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 Eclipse.org is on your repository list, you can skip this step.
>+ 
>+Click on the Add Repository Task button in the Query dialog. Select Bugzilla on the list then click on the Next button. Enter https://bugs.eclipse.org/bugs for the server&apos;s address, Eclipse.org for the label then click on the Finish button.
>+ </description>
>+ </item>
>+ <item title="Setup the query" dialog="true" skip="false">
>+ <description>
>+ Select Eclipse.org then click on the Next button. 
>+ Select Create a query using form then click on the Next button. 
>+ Enter Mylar bugs for the query&apos;s title.
>+ Select Mylar from the Product and P1, P2 from the Priority then click on the Finish button.
>+ </description>
>+ </item>
>+</cheatsheet>
>Index: intro/whatsnewExtensionContent.xml
>===================================================================
>RCS file: intro/whatsnewExtensionContent.xml
>diff -N intro/whatsnewExtensionContent.xml
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ intro/whatsnewExtensionContent.xml	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,15 @@
>+<?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>
>Index: intro/overviewExtensionContent.xml
>===================================================================
>RCS file: intro/overviewExtensionContent.xml
>diff -N intro/overviewExtensionContent.xml
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ intro/overviewExtensionContent.xml	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,13 @@
>+<?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>
>Index: cheatsheets/TaskFocus.xml
>===================================================================
>RCS file: cheatsheets/TaskFocus.xml
>diff -N cheatsheets/TaskFocus.xml
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ cheatsheets/TaskFocus.xml	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,93 @@
>+<?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. 
>+ </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 Window &gt; Open Perspective &gt; 	Other... &gt; Plug-in Development	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 Window &gt; Show View &gt; Other... &gt; Mylar &gt; Task List 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.
>+ 
>+In the main toolbar, click on the New button. Select the Plug-in Project from the list then click on the Next button. Enter SampleProject for the project&apos;s name then click on the Next button twice.
>+Select from the Templates part Hello, World then click on the Finish 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 New &gt; Category. Enter Tutorials for the category&apos;s name.
>+ 
>+Then right click on the Tutorials category and select New &gt; Task. Enter Learn task-focus for the task&apos;s title and change the priority to High. You can add some notes, too.
>+ 
>+Right click on the new task and select Activate to activate the task.
>+ 
>+Important: If it&apos;s not activated, click on the &quot;Focus on the Active Task&quot; toogle button in the Package Explorer and in the Outline view too.
>+ </description>
>+ </item>
>+ <item title="Open SampleAction file" dialog="true" skip="false">
>+ <description>
>+ Press down the Ctrl+Shift+T buttons or click on the &quot;Click to Perform&quot; link below. 
>+In the Open Type dialog enter SampleAction for the type&apos;s name then press the Enter button. 
>+After the file is opened you can see the SampleAction class both in the Package Explorer and in the Outline 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 void run(IAction action) method then you can see the run(IAction) method in the Outline view and in the Package Explorer under the SampleAction class.
>+ 
>+Next press the Alt button and click on the SampleAction class in the Outline view. 
>+Now you can see all methods. Methods which aren&apos;t in the focus are in grey color. Select window 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.
>+ 
>+Select the run(IAction) method in the Outline view or in the Package Explorer. Right click on the method and select Mark as Landmark. After then this method becomes a landmark.
>+ 
>+Also you can use key bindings. Ctrl+Shift+Alt+UpArrow to mark the element as landmark or Ctrl+Shift+Alt+DownArrow to mark less interesting for the element.
>+ </description>
>+ </item>
>+ <item title="Remove method from focus" dialog="true" skip="true">
>+ <description>
>+ Right click on the window field and select Remove from Focus. The window field will disappear on the list.
>+ </description>
>+ </item>
>+ <item title="Open Activator.java" dialog="true" skip="false">
>+ <description>
>+ Press down the Alt button and click on the src directory. Then you can see 3 packages. 
>+Alt+click on the sampleproject package and you can open the Activator.java file with a simple double-click on the file name.
>+ 
>+You can use Alt+RightArrow instead of Alt+click.
>+ </description>
>+ </item>
>+ <item title="Quick Context View" dialog="true" skip="false">
>+ <description>
>+ Press down Ctrl+Shift+Alt+RightArrow 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 Learn task-focus task and select deactivate.
>+ 
>+Click again on the task with the right mouse button and select Mark &gt; Complete. 
>+After then the task&apos;s name will be struck through.
>+ </description>
>+ </item>
>+</cheatsheet>

Actions: View | Diff

Attachments on bug 185836: 68854 | 68856 | 68862 | 68980 | 71562 | 71563