If we want to provide a data structure, we need to create

1. a meta model using the EMF
2. an extension point schema.

Data Structure

After taking a closer look at the data structure, you may want to classify them as follows:

1. Core data (PDF files)
2. Core meta data (meta data describing a PDF file)
3. Data generated by users

Then there is the data needed internally for configuration purposes, such as available update sites, locally installed data vs. data to be accessed online etc.

Thus, the model generated with the EMF is divided up into three logical parts:

1. Application-specific data model
2. Data model for handling content structures
3. Meta data model

After generating the corresponding classes, you can go on to define the extension points which describe a specific data unit.. This data will be not be editable later and will be distributed via an update server.Note that even at this early stage you are able to generate content units based on PDE tooling. The advantage is that very early on in the process you can generate productive data, and this does not necessarily require the expert knowledge of a programmer.Furthermore, you can flexibly respond to changing data structures.

EMF Edit

In addition, the EMF Edit framework offers adapters that enable developers to represent the generated data model in an Eclipse application. This saves having to implement Jface Viewers, which means enormous time savings compared with the traditional approach to Viewer generation.

Application status

At this point we have an application which allows us to browse the information units registered as extension points.

Outlook

In the next sequel we will focus on how to use functionalities which is shipped with the IDE plugins of Eclipse, and how to use several functionalities under the hood; so the next articles become more code orientated.

Download

Download the CVS Team Project-Set