I don't actually see the similarities here though. I am aware of NetBeans extensive use of "magic bags" (I believe Tim Boudreau refers to this as the capability pattern), this is part of what makes it really hard to get stuff done with the NetBeans RCP, you can never use the IDE to poke around and explore capabilities. Let me throw you an analogy here, would you rather deal with a bean which exposes it's members via properties or which is a Map?
/Casper On Nov 20, 8:57 pm, Fabrizio Giudici <[email protected]> wrote: > Casper Bang wrote: > > Nobody sees value in having a small and tight core, which can be > > decorated by importing features/aspects from a 3'rd part, 4'th part > > etc? It can work really well. > > It's very valuable and my preferred way of designing things. Generally > speaking, my preferred way to see that is: > > myObject.lookup(Extension.class).doSomething(); > > In context: > > list.lookup(Sorter.class).sort(); > list.lookup(MyGreatAndFastSorter.class).sort(); > > Just regular OOP constructs and no lies. > > -- > Fabrizio Giudici - Java Architect, Project Manager > Tidalwave s.a.s. - "We make Java work. Everywhere." > weblogs.java.net/blog/fabriziogiudici -www.tidalwave.it/people > [email protected] -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=.
