Difference between revisions of "Mylyn/Architecture"

From Eclipsepedia

Jump to: navigation, search
(APIs)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Image:mylar-architecture.gif]]
+
[[Category:Mylyn]]
 +
 
 +
[http://eclipse.org/mylyn Mylyn Home] [[Mylyn Contributor Reference | Contributing]], [[Mylyn  Integrator Reference | Integrating]]
 +
 
 +
[[Image:Mylyn-components.png|800px]]
  
 
== Frameworks ==
 
== 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'''
+
'''Tasks'''
** org.eclipse.mylar.context.core: context model and degree of interest abstractions. Runs headless. Entry point: ContextCorePlugin.
+
* <code>org.eclipse.mylyn.tasks.core</code>: Task, task list and task repository abstractions. Facilities for synchronizing the task list and managing offline data. Runs headless and standalone.
** org.eclipse.mylar.context.ui: interest filters and other facilities for focusing workbench views and editors on context.  Runs in RCP. Entry point: ContextUiPlugin.
+
* <code>org.eclipse.mylyn.tasks.ui</code>: Tasks view and editor framework. Runs in RCP. Entry point: <code>TasksUi</code>.
 +
** [[Mylyn/Architecture/Task_Editor|Task Editor API]]
 +
* <code>org.eclipse.mylyn.web.core</code>: [[Mylyn/Architecture/Web|Web and networking API]].
 +
 
 +
'''Context'''
 +
* <code>org.eclipse.mylyn.context.core</code>: Context model and degree of interest abstractions. Runs headless and standalone. Entry point: <code>ContextCore</code>.
 +
* <code>org.eclipse.mylyn.context.ui</code>: Interest filters and other facilities for focusing workbench views and editors on context.  Runs in RCP. Entry point: <code>ContextUi</code>.
  
* '''Monitor'''
+
'''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.
+
* <code>org.eclipse.mylyn.monitor.ui</code>: UI framework for monitoring user interactions with the workbench.  Can be used independently of Tasks and Context frameworks. Runs in RCP.
** org.eclipse.mylar.monitor.usage: user study framework, requires Eclipse Platform.
+
* <code>org.eclipse.mylyn.monitor.usage</code>: User study framework, requires Eclipse Platform.
  
 
== APIs ==
 
== APIs ==
  
* org.eclipse.mylar.bugzilla.core: Java API used for accessing Bugzilla reports on a server.  Runs headless, see [[Mylar Integrator Reference#Headless APIs]].
+
* org.eclipse.mylyn.bugzilla.core: Java API used for accessing Bugzilla reports on a server.  Runs headless, see [[Mylyn Integrator Reference#Headless APIs]].

Latest revision as of 08:13, 20 June 2011


Mylyn Home Contributing, Integrating

Mylyn-components.png

[edit] 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.

[edit] APIs