Timothy Larson wrote:
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.
choice is my choice :-)
"struct"->"container"
ok, although 'composed' comes to mind too
in fact, I'm starting to think this has some overlap with the aggregate widget, no?
"class"->"define" or leave as "class" "new"->"use", "instance", or leave as "new"
I would stick to class and new, but that's showing a Java bias I'm ok for define and use if people find it more intuitive
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.
regards, -marc= -- Marc Portier http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/mpo/ [EMAIL PROTECTED] [EMAIL PROTECTED]
