Why does Pivot include its own collection classes?
The short answer is that they make the API easier to use, and provide a consistent API across all classes that require indexed or keyed access. The longer answer: • Pivot’s collection classes fire events that notify listeners when collections are modified. This makes it very easy to wire an application data structure directly into a UI. • Pivot’s collection interfaces enable construction of arbitrary object hierarchies using XML. Any class that implements the Sequence or Dictionary interface can be instantiated and configured completely in markup. Note, however, that developers aren’t required to use these collection classes. Pivot includes various wrapper classes that allow existing model and collection data to be incorporated directly into a Pivot user interface.
Related Questions
- OK, so I know I am supposed to use proxy when manipulating the Collection classes once they are managed by the cache. But what happens to POJOs that share the Collection objects, e.g., a List instance that is shared by two objects??
- Are the J2SE reflection and collection classes supported in J2ME?
- Why does Pivot include its own collection classes?
