Performance

[Updownquark]

Performance sucks. My simple tests take 5 or more seconds to finish setup and then another 2 to finish layout and rendering.

Here are the hot spots JProfiler gives me:

• Observable stack: This is the big one. StyleChangeObservable.start is creating and subscribing to an observable that listens to several attributes at once. The flattened observable's elements each use several sorted collections, filtered for uniqueness, type, style condition matching, etc. and the bottom line is that the stack for just creating the observable is several hundred frames deep. There may be ways to optimize around this, but if at all possible, this call chain must be shortened.
• ObservableSortedSet.CollectionWrappingSortedSet.iterator(): The only way I could think of to do this was to dump the entire collection into a tree set and then return that set's iterator. Not sure there is a better way to do this dynamically, but maybe some caching could help.
• Text layout: QuickTextElement is using up some cycles determining its preferred width. This seems to me like a complex operation that may not really be optimizable, but I didn't dive too deep.

Quick needs to be quick or it will never be useful.

[Updownquark]

I created some cache collection types in ObServe and used these to front the DocumentStyle with caches. So now the style sheets can just be invoked once per document per attribute. This sped up both loading and update times significantly.

I'd love it if one day Quick just popped up and started going for moderately complex documents, but for now it's fine.