Difference between revisions of "Metaclass"
Line 6: | Line 6: | ||
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. | 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. | ||
− | + | ==See also== | |
− | UBIK MetaClass Model | + | * [[UBIK MetaClass Model]] |
− | + | ||
[[Category:UBIK Object]] | [[Category:UBIK Object]] |
Revision as of 12:41, 7 August 2012
Basics
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 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.