On Wed, Aug 26, 2009 at 9:28 PM, Greg Brown<[email protected]> wrote: > My vote (in case some of you are not aware of it) is to leave the names > as-is. As Todd says, Sun didn't invent these terms - they have been around > for a long time. Calling these classes anything other than what they are > seems artificial (and confusing).
<delurk> In Eclipse, when i do ctrl-shift-t and then type List i get List - antlr.collections List - com.sun.xml.bind.v2.schemagen.xmlschema List - groovyjarjar.antlr.collections List - java.awt List - java.util When I type Map i get Map - java.util Map - javax.swing.text.html Map - org.hibernate.mapping Now if this would really bother me (which it doesn't) i would go to settings-java-appearance-type filters and exlude the packages i don't want to see in autocompletion. I'm sure intellij has a similar option. Looking at koders.com, there are *many* other projects that use these terms as well Map.java -> http://www.koders.com/?s=file%3aMap.java&la=Java&li=* ArrayList.java -> http://www.koders.com/default.aspx?s=file%3AArrayList.java&btn=&la=Java&li=* LinkedList.java -> http://www.koders.com/default.aspx?s=file%3ALinkedList.java&btn=&la=Java&li=* So what is the big deal here ? If this were commons-collections then i would understand the energy being spent on the discussion, but Pivot is a state of the art RIA framework for god's sake :-) Most developers don't even care about these collection classes, they just want to deliver a kick-ass RIA app to their customers, something which Pivot claims to do very well. The collection classes are neither Pivot's main drawback nor its biggest feature, so focus energy on the part that your users will really care about. </delurk> Jorg
