diff --git a/Documentation/Doxygen/DeveloperManual/Application/BlueBerry/BlueBerryIntro.dox b/Documentation/Doxygen/DeveloperManual/Application/BlueBerry/BlueBerryIntro.dox index a7045f61e1..06e657920c 100644 --- a/Documentation/Doxygen/DeveloperManual/Application/BlueBerry/BlueBerryIntro.dox +++ b/Documentation/Doxygen/DeveloperManual/Application/BlueBerry/BlueBerryIntro.dox @@ -1,73 +1,79 @@ /** \page BlueBerryIntro BlueBerry Application Framework BlueBerry is an application framework used in MITK for creating modular and extensible end-user applications. More high-level documentation can be found below: - \subpage BlueBerryWorkbench +- \ref BlueBerryExamples -Please see the \ref BlueBerryExamples for code examples demonstrating different features of the appication framework. +Please see the \ref BlueBerryExamples for code examples demonstrating different features of the application framework. + +The BlueBerry developer reference is available here: + +- \ref BlueBerryPlugins +- \subpage BlueBerryExtPointsIndex \page BlueBerryWorkbench The Workbench: What are Views, Editors, Perspectives? BlueBerry makes use of the Eclipse UI guidlines which state some concepts on how to build up a GUI. The different objects of the platform UI shall be described here: \section Workbench Workbench \li root object of the platform UI \li collection of \ref WorkbenchWindow "windows" \image html workbench.jpg "The Workbech" \section WorkbenchWindow WorkbenchWindow \li has one \ref Workbench-Page "page" \image html workbench-window.jpg "Worbench Windows" \section WorkbenchPage Workbench Page \li denotes to the inner part of the \ref WorkbenchWindow "window", that is: everything except the title bar \li may have one menu bar, one toolbar, one shortcut bar, and one statusbar \li has one or more \ref Perspective "perspectives" \image html workbench-page.jpg "Workbench Page" \section Perspective Perspective \image html workbench-window-perspective.png "A Perspective" \section Part Part \li every \ref Views "View" or \ref Editors "Editor" is called \b Part \subsection Editors Editors \li the StdMultiWidget is an example for an editor in our MainApp \li Contains the primary content, such as a document or image data, which users interact with \li content is the primary focus of attention and a reflection of the primary task \li primary position in the UI \li contributes commands to the workbench's main menu bar and toolbar \li shared in other perspectives \image html workbench-window-editor-area.png "Editor Area" \subsection Views Views \image html workbench-window-views.png "Views" \section ClassDiagram Summary as class diagram \image html workbench-class-diagram.jpg "class diagram" */ diff --git a/Documentation/Doxygen/DeveloperManual/Application/DevelopmentApplication.dox b/Documentation/Doxygen/DeveloperManual/Application/DevelopmentApplication.dox index 1bcb321658..4e00e090fc 100644 --- a/Documentation/Doxygen/DeveloperManual/Application/DevelopmentApplication.dox +++ b/Documentation/Doxygen/DeveloperManual/Application/DevelopmentApplication.dox @@ -1,16 +1,17 @@ /** \page DevelopmentApplication Developing with the MITK Application Framework MITK offers a powerful application featuring a plugin system and many predefined plugins. You can configure this application to offer a set of functionality to the user and easily create an installer. Working with the application, you will have to learn about extension points and the Blueberry framework itself. If you are new to the matter, please also consult \ref Architecture and \ref FirstSteps. +The MITK application extension-point reference is available here: + + - \subpage mitkExtPointsIndex */ diff --git a/Documentation/Doxygen/DeveloperManual/DeveloperManualPortal.dox b/Documentation/Doxygen/DeveloperManual/DeveloperManualPortal.dox index ec44916cba..aa9276cf30 100644 --- a/Documentation/Doxygen/DeveloperManual/DeveloperManualPortal.dox +++ b/Documentation/Doxygen/DeveloperManual/DeveloperManualPortal.dox @@ -1,33 +1,31 @@ /** \page DeveloperManualPortal MITK: Developer Manual Development with MITK can happen under several disctinct conditions. Depending on whether you are using the Toolkit or the entire application, different sections may apply to you. In case you are unsure about what you need, please refer to \link Architecture The Architecture of MITK text\endlink. An extensive Introduction to MITK is available under \link StartingDevelopment Starting your MITK Development\endlink. Depending on whether you are working with the \link DevelopmentToolkit Toolkit\endlink or the \link DevelopmentApplication Application\endlink, you can refer to their respective pages. Generated API-Documentation can be found \link DevelopmentAPI here\endlink. \section DeveloperManualStarting Starting your MITK Development */ diff --git a/Documentation/MITKDoxygenLayout.xml b/Documentation/MITKDoxygenLayout.xml index cdfdf03ebc..96f50c0087 100644 --- a/Documentation/MITKDoxygenLayout.xml +++ b/Documentation/MITKDoxygenLayout.xml @@ -1,196 +1,197 @@ +