Difference between revisions of "Metaclass"
| Line 1: | Line 1: | ||
In UBIK, a MetaClass is used to define the appearance and behavior of a certain set of future [[Contentclass|content objects]]. | In UBIK, a MetaClass is used to define the appearance and behavior of a certain set of future [[Contentclass|content objects]]. | ||
| − | A MetaClass can, and actually has to, inherit from another MetaClass. This can be a built in [[UBIK System Object|UBIK System-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. | + | A MetaClass can, and actually has to, inherit from another MetaClass. This can be a built in [[Category:UBIK System Object|UBIK System-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. |
[[Category:UBIK Object]] | [[Category:UBIK Object]] | ||
Revision as of 11:47, 4 June 2012
In UBIK, a MetaClass is used to define the appearance and behavior of a certain set of future content objects.
A MetaClass can, and actually has to, inherit from another MetaClass. This can be a built in, 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.
