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"

Line 1: Line 1:
 
[[Category:Mylar]]  
 
[[Category:Mylar]]  
  
[http://eclipse.org/mylar Mylar Home] [[Mylar Contributor Reference | Contributing]], [[Mylar Integrator Reference | Integrating]]
+
[http://eclipse.org/mylyn Mylyn Home] [[Mylyn Contributor Reference | Contributing]], [[Mylyn Integrator Reference | Integrating]]
  
 
[[Image:mylar-architecture.gif]]
 
[[Image:mylar-architecture.gif]]

Revision as of 18:46, 27 June 2007


Mylyn Home Contributing, Integrating

Mylar-architecture.gif

Note: Team framework is currently missing from the diagram

Frameworks

  • Tasks
    • org.eclipse.mylar.tasks.core: task and task repository abstractions. Runs headless. Entry point: TasksCorePlugin.
    • org.eclipse.mylar.tasks.ui: task list and other facilities such as offline and synchronization support that make tasks a first class part of Eclipse. Runs in RCP. Entry point: TasksUiPlugin.
  • Context
    • org.eclipse.mylar.context.core: context model and degree of interest abstractions. Runs headless. Entry point: ContextCorePlugin.
    • org.eclipse.mylar.context.ui: interest filters and other facilities for focusing workbench views and editors on context. Runs in RCP. Entry point: ContextUiPlugin.
  • Monitor
    • org.eclipse.mylar.monitor: UI framework for monitoring user interactions with the workbench. Can be used independently of Tasks and Context frameworks. Runs in RCP. Entry point: MylarUiPlugin.
    • org.eclipse.mylar.monitor.usage: user study framework, requires Eclipse Platform.

APIs

Back to the top