Difference between revisions of "Protege4Preferences"

From Protege Wiki
Jump to: navigation, search
(Initial page)
 
(Added plugins)
Line 33: Line 33:
  
 
Control over the default behaviour when creating ontologies from scratch.
 
Control over the default behaviour when creating ontologies from scratch.
 +
 +
== Plugins ==
 +
 +
Download or update plugins using the [[EnablePluginAutoUpdate#Plugin_preferences|plugin preferences]].
  
 
== Renderer ==
 
== Renderer ==

Revision as of 07:52, November 7, 2008

Protege 4.x Preferences

This page contains a guide to customising Protege 4.x through its preferences menu.


Back to Protege4UserDocs


Many Protege 4.x features can be configured using the inbuilt preferences. Preferences are stored in a system-specific way and are persistent across new installations of the tool.

Find them under File | Preferences.

Installed plugins may add further panels to this dialog. Below is a list of the default preferences:

Annotations

Control over the visibility of given annotations.

Find / Search

Control over how the find / search functionality behaves. eg searching using full regular expressions can be slow for large ontologies.

New Entities

Control how URIs and labels get generated when creating new classes/properties and individuals (including automatic ID formulation).

Also see New Entity Preferences for a more detailed description of these preferences.

New Ontologies

Control over the default behaviour when creating ontologies from scratch.

Plugins

Download or update plugins using the plugin preferences.

Renderer

Control over how entities are displayed in Protege 4.x.

Firstly, how to generate the short human readable version of an entity - whether to use part of its URI or perhaps a label stored in an annotation value (also see Protege4NamingAndRendering).

Secondly, control over highlighting of certain syntactic or structural information.

Thirdly, fonts used to display entities in views.

Tree Preferences

How deep to open up hierarchies when they are first shown.

Usage

Control over what axioms are shown in the usage views. Hiding some axioms can make the view more concise.

Simple subclass axioms subclass axioms that have a named superclass or for which the current class is the superclass

XML Writer

Control over the form of XML serialisations (eg whether or not to use XML entities to shorten file length).