Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Mylyn Demonstration"
(→Story: Use bugzilla bug 105288) |
|||
(9 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | ''Please note that the demo script has not yet been updated for Mylyn 2.0.'' | ||
+ | |||
==Usefull Resources== | ==Usefull Resources== | ||
− | [http://www.eclipse.org/ | + | [http://www.eclipse.org/mylyn/start.php getting started]<br> |
− | [http://www.eclipse.org/ | + | [http://www.eclipse.org/mylyn/presentations/ presentations]<br> |
− | [http://www.eclipse.org/ | + | [http://www.eclipse.org/mylyn/publications.php publications]<br> |
− | [http://www.eclipse.org/ | + | [http://www.eclipse.org/mylyn/tips.php tips]<br> |
− | + | [http://www.eclipse.org/mylyn/faq.php faq]<br> | |
==Demo 1: Tasks == | ==Demo 1: Tasks == | ||
+ | ===Problem=== | ||
+ | * discuss problem of information overload and overhead of context switching | ||
+ | * discuss lack of integration of tasks with IDE workflow | ||
+ | |||
+ | * Repository connectors | ||
+ | ** Mylyn can link to all repositories | ||
+ | ** Mylyn does not have its own store | ||
+ | |||
+ | ===Story=== | ||
* Open Workspace | * Open Workspace | ||
* Show Repositories | * Show Repositories | ||
Line 39: | Line 50: | ||
* Task Context | * Task Context | ||
− | ** | + | ** Mylyn monitors all your activity |
** Creates a degree of interest model | ** Creates a degree of interest model | ||
*** highly used items are marked more important | *** highly used items are marked more important | ||
Line 82: | Line 93: | ||
==Demo 3: Collaboration== | ==Demo 3: Collaboration== | ||
− | === | + | ===Problem=== |
* Tell what the problem of change sets are | * Tell what the problem of change sets are | ||
* Tell why you don;t want to collaborate via e-mail | * Tell why you don;t want to collaborate via e-mail | ||
Line 97: | Line 108: | ||
** Expertise is focused on one task | ** Expertise is focused on one task | ||
** Context can be shared | ** Context can be shared | ||
+ | |||
+ | ===Story=== | ||
+ | * Find a problem by entering stat into the Find | ||
+ | * Open the task to check it out (look for context Icon) | ||
+ | * Find the context within the Attachements | ||
+ | * Activate the task context by clicking on the attachement | ||
+ | * The task context is now active in the workspace | ||
+ | * Jump into the Task tab context (bottom) to show the context | ||
+ | * Switch back to another task to show how easy it is to go back to a previous task |
Latest revision as of 15:05, 13 September 2007
Please note that the demo script has not yet been updated for Mylyn 2.0.
Contents
Usefull Resources
getting started
presentations
publications
tips
faq
Demo 1: Tasks
Problem
- discuss problem of information overload and overhead of context switching
- discuss lack of integration of tasks with IDE workflow
- Repository connectors
- Mylyn can link to all repositories
- Mylyn does not have its own store
Story
- Open Workspace
- Show Repositories
- Task List
- Create a Bugzilla Query
- Show how the tasklists is organised
- Show how you can quickly recognize tasks
- Difference between open and closed task
- Open a Bug
- Make a change to a task and show
- it has outgoing changes
- it is a-synchronous
- Open a task not in any of your lists by using navigate/open repository task
- show linking from a stack trace to a java source
- show linking from a java source back to a bug
- show linking from a bug to a bug
- Make a search
- Point out the difference between an search and a query
- Show shortcut CTRL-H from task to show openening of corre
- Show personal planning and
- tell why you would use this personal stuff
- show how you can you pick out the tasks that have personal notes (have stripes on the board)
- Show tasklist filter menu
- Show priority filtering (don't do it)
- Click filter completed tasks
Demo 2: Task Focussed UI
- What is information overload
- How does this relate to the eclipse workspace
- How are programmers working usually (multi-tasking)
- Scrolling, searching, tagging, filtering is not programming
- Task Context
- Mylyn monitors all your activity
- Creates a degree of interest model
- highly used items are marked more important
- Unused items decay and are moved out ouf your context
- What you touch is in your context
- It is managed for you as you work
- Task-focused UI
- You only see what you need in the context of your task
- View filtering, Element decoration
- Automatic folding, contents assist ranking
- Indicate what contest assist is
- Consistently integrated all through Eclipse
- Editor an perspective management
- Opens and closed editors when tasks are switched
- Automatically closes editors when they are decayed
- Opens the perspective you wherein last (when activated in preferences)
- One click task switching
- Opens editors and perspecitves
- Re-arranges all views
Story: Use bugzilla bug 179144
- there should a project
- A important bug comes in:
- You have to work on it, right click and open the bug
- Activate the bug
- package explorer: toggle focus ui
- (link with editor button should be on)
- open some class
- hold control and navigate around
- Now press the focus button
- press content assist and show that the interesting methods show first
- Press the editor Fold uninteresting methods
- tell that the task context is saved with the task
- deactivate the task and show eclipse returns to normal
- re-activate the task to go back where you left off(ONE CLICK)
- tell that the focus is applied to other views like the problem view
- show how ALT CLICK works
- open a new source from the class
- tell about the degree of intereset
- show how stuff can be removed from the task list mark as less interesting
Demo 3: Collaboration
Problem
- Tell what the problem of change sets are
- Tell why you don;t want to collaborate via e-mail
- overload, interruption, no sharing
- What is Change Set Managamement
- Changes are autmatically grouped by task
- commit messages are automatic
- are used to linked to tasks
- add below the commit message
- everything is linked
- Why is Task context sharing such a good thing
- Expertise is focused on one task
- Context can be shared
Story
- Find a problem by entering stat into the Find
- Open the task to check it out (look for context Icon)
- Find the context within the Attachements
- Activate the task context by clicking on the attachement
- The task context is now active in the workspace
- Jump into the Task tab context (bottom) to show the context
- Switch back to another task to show how easy it is to go back to a previous task