• When views initialize themselves with sub-components, e g the Timeline view's exhibit-timelineView-legend div, it would be nice if they used an already-present such div, when one exists (since not all CSS layouting tricks can be pulled off without placing elements in the appropriate location in the node tree), rather than creating a new one.
• In anticipation of eventual OPML or XOXO support, provide a means for nested filter attributes. These could take the attribute form of parent.child1 and parent.child2. The selection display boxes could then show the children as indented items (a la tree-like). Like most current OPML, an initial implementation limited to two levels should be sufficient.
• When loading a JSON file that contains no data, it would be nice to have a message to that effect instead of the "Browse Panel not configured" error message that pops up.
• In order to allow maximum theming flexibility, is it possible to have most images controlled via CSS rather than embedded in the html? For example, allowing the message bubble to be created via CSS divs allows a designer better control over placement, and allows images to be swapped with a simple change in the CSS rather than messing with the code. (from: mariagwyn).