Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Mylyn/Architecture"

(Frameworks)
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
 
[http://eclipse.org/mylyn Mylyn Home] [[Mylyn Contributor Reference | Contributing]], [[Mylyn  Integrator Reference | Integrating]]
 
[http://eclipse.org/mylyn Mylyn Home] [[Mylyn Contributor Reference | Contributing]], [[Mylyn  Integrator Reference | Integrating]]
  
[[Image:mylar-architecture.gif]]
+
[[Image:Mylyn-components.png|800px]]
  
''Note: Team framework is currently missing from the diagram''
 
 
== Frameworks ==
 
== Frameworks ==
  

Latest revision as of 08:13, 20 June 2011


Mylyn Home Contributing, Integrating

Mylyn-components.png

Frameworks

Tasks

  • org.eclipse.mylyn.tasks.core: Task, task list and task repository abstractions. Facilities for synchronizing the task list and managing offline data. Runs headless and standalone.
  • org.eclipse.mylyn.tasks.ui: Tasks view and editor framework. Runs in RCP. Entry point: TasksUi.
  • org.eclipse.mylyn.web.core: Web and networking API.

Context

  • org.eclipse.mylyn.context.core: Context model and degree of interest abstractions. Runs headless and standalone. Entry point: ContextCore.
  • org.eclipse.mylyn.context.ui: Interest filters and other facilities for focusing workbench views and editors on context. Runs in RCP. Entry point: ContextUi.

Monitor

  • org.eclipse.mylyn.monitor.ui: UI framework for monitoring user interactions with the workbench. Can be used independently of Tasks and Context frameworks. Runs in RCP.
  • org.eclipse.mylyn.monitor.usage: User study framework, requires Eclipse Platform.

APIs

Back to the top