View components provide views within editor kits. The user is able to configure view tabs using these views and the docking system that is present in the core system The label that will appear in the view menu etc. The class that should be instantiated to create the view. This should extend the ViewComponent class The colour of the view header Whether or not the view is user creatable. By default, the view is user createable. Setting this parameter value to "false" prevents the user creating a new view Gets the view categorisations, for example "class", "property", "visualisation". Developers should attempt to fit in with existing categorisations before inventing their own. The traditional values for this field are @org.protege.classcategory @org.protege.objectpropertycategory @org.protege.datapropertycategory @org.protege.annotationpropertycategory @org.protege.individualcategory @org.protege.datatypecategory @org.protege.ontologycategory Other values can be used but if you want them to display something needs to be put into the ProtegeProperties showing how they should be displayed in the Views menu. The categories of thing that this view can display. This is used by global selection to determine the suitability of a given view (on a given tab). The traditional values for this field are @org.protege.classcategory @org.protege.objectpropertycategory @org.protege.datapropertycategory @org.protege.annotationpropertycategory @org.protege.individualcategory @org.protege.datatypecategory