For anybody who been following the class, new, struct, and union discussion, will you help choose intuitive names for these new features? Description: http://wiki.cocoondev.org/attach?page=TimLarson Patch: http://wiki.cocoondev.org/attach?page=TimLarson%2Fwoody_union.diff
I am thinking of changing: "union"->"selector", "selection", "choose", "choice", etc. "struct"->"container" "class"->"define" or leave as "class" "new"->"use", "instance", or leave as "new"
Note that the concept currently called "class" may be reused in a global widget definition repository, and that the concept currently called "new" may be extended to allow it to provide customization parameters or elements to the definitions it creates instances of.
What names do you all suggest? The names will be used for the parallel concepts in the form definition, template, and binding. It would be nice to get the names settled for the next patch before this gets committed.
Tim, I would do it the opposite way: commit the patch so that people can play with it. Reading docs is good but we also need to get our hands on it to fully understand the underlying concepts and find good names for them.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
