... | ... | @@ -2,4 +2,19 @@ This page tries to give information about which concepts one should respect when |
|
|
|
|
|
# Writing your own view for ATHEN on the example of the CorefView
|
|
|
|
|
|
We go through the details of creating your own view, using the CoreferenceView. At first one needs to be able to get your own view displayed by ATHEN, this is covered in a different tutorial. If you want to archive this, please refer to - [ATHEN - Integrating your own view](ATHEN - how to integrate your own view) |
|
|
\ No newline at end of file |
|
|
We go through the details of creating your own view, using the CoreferenceView. At first one needs to be able to get your own view displayed by ATHEN, this is covered in a different tutorial. If you want to archive this, please refer to - [ATHEN - Integrating your own view](ATHEN - how to integrate your own view)
|
|
|
|
|
|
So this page assumes you are able to display your own view already, and have it listening and reacting to the main editor. The following section describes how to properly (as of my **current** opinion) structure your view.
|
|
|
|
|
|
|
|
|
## General ideas behind the structuring
|
|
|
|
|
|
Your view (which is the class that is displayed) should always have its own project!
|
|
|
Furthermore, you need to understand my intention of a view like this:
|
|
|
|
|
|
The class of the view serves as the glue between the layout of the view and the editor. The view class itself should therefore only contain a single UI reference (the actual view). The class now server the purpose of a **controller** between the view (the UI Element) and the model (which is the CAS object, accessible using the editor) This process id depicted as follows:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<img src="/uploads/fc1264bd0d522f662f053e1a2c0ec76e/MVC-ATHEN_Views.PNG" alt="MVC of the editor and the views" style="width: 640px;" style="height: 480px;"/> |
|
|
\ No newline at end of file |