Difference between revisions of "Metaclass"
| Line 3: | Line 3: | ||
In {{UBIK}}, a MetaClass is used to define the appearance and behavior of a certain set of future [[Contentclass|content objects]] or [[Instance|Instances]]. | In {{UBIK}}, a MetaClass is used to define the appearance and behavior of a certain set of future [[Contentclass|content objects]] or [[Instance|Instances]]. | ||
| − | A MetaClass can, and actually has to, inherit from another MetaClass, so it is usually also a [[Derivate|derivate]]. The inherit source can be a built in [[:Category: | + | A MetaClass can, and actually has to, inherit from another MetaClass, so it is usually also a [[Derivate|derivate]]. The inherit source can be a built in [[:Category:Metaclasses|Metaclass]], which is typically the case when customizing starts in an "empty" data model. Of course, and more likely, it will be another MetaClass that was already created during customizing. |
==See also== | ==See also== | ||
Revision as of 20:46, 2 February 2015
Basics
In UBIK®, a MetaClass is used to define the appearance and behavior of a certain set of future content objects or Instances.
A MetaClass can, and actually has to, inherit from another MetaClass, so it is usually also a Derivate. The inherit source can be a built in Metaclass, which is typically the case when customizing starts in an "empty" data model. Of course, and more likely, it will be another MetaClass that was already created during customizing.
