Pierre van Rooden wrote:
Nico Klasens schreef:
Considering these differences it might be wise to drop the usage of
"mixin type" as name.
I agree. When I read this scetion my intial idea was not that this was
a "mixin' type, but a "mimic' type:
You map an objecttype (or functionset, or whatever) to make it appear
as something else (namely a pre-defined objecttype, funtionset, etc)
I disagree :-) It is not that I want to drop the name, because it is
conceptually wrong. It might be wise not to use it because jsr-170 is a
hot topic lately. jsr-170 uses the same name, but applies it
differently. (mixin types are assigned to nodes not types). It could be
confusing for people who know jsr-170 and MMBase.
You still have to know what 'else' is. iow you still need another node
type which defines what is required for the component. this node type
can mingle with the primary node types.The only difference is that you
can't create a node based on that node type. Usage of mixin in this
description is correct? These types could also be used to add extra
fields to a primary node type which are not mapped to a field. A primary
node type only defines the minimal set of fields which are
allowed/required for node creation.
Nico
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
