Quick Release

[Updownquark]

Here's everything I can think of that I need to do before Quick is ready for release.

• [x] Break up files. Need to be able to break large UIs into multiple files with one root file that references the others.
  • [ ] Expose element values (e.g. active value) to both internal and external content
  • [ ] Allow "with-extension" specification on promises where the add-on requires the promised type
  • [ ] Test multiple-levels, with external content using external content, specifying child placeholders as promised children, etc.
• [ ] Styles. Quick needs the ability to modify styles like color and border based on other properties of the element. E.g. a style for tree nodes that are selected.
  • [x] Make styles more flexible, e.g. (box with class x)'s child label on press
  • [x] Figure out if style-set should be in there. Implement or delete it.
  • [x] Specify and implement style attributes for all relevant widgets in base and x
  • [x] Cursor
  • [x] Implement model values
  • [x] Pressed
  • [x] editable-text-widget.error
  • [ ] Do we need a variable-depth wildcard or something so e.g. all labels which have a box for an ancestor have a particular style?
• [x] Auto-inheritance. This for sure goes down deep in Qonfig. Qonfig Toolkits should be able to specify add-ons that are automatically applied to elements of a specified type from other toolkits just by loading the modifier toolkit.
• [x] Local variables in widgets--visible to children as well
• [x] Versioning. Need to formalize versions of toolkits and implementations and how to connect the two.
• [ ] Complete Quick Swing
  • [x] Expression types
  • [x] Binary operators
  • [x] Unary operators
  • [x] Assignments
  • [x] Array access
  • [x] Constructor invocation
  • [x] Cast
  • [x] Increment/Decrement
  • [ ] Widgets
  • [x] Combo boxes
  • [x] Spinners
  • [x] Sliders
  • [x] Radio buttons
  • [x] Offloaded actions
  • [x] Menu button
  • [x] Scroll pane
  • [x] Toggle buttons
  • [x] Progress bar
  • [x] TiledPane
  • [x] Collapse pane
  • [x] Tabs
  • [ ] ObservableValueSelector
  • [ ] Composite cell renderer/editor
  • [ ] Settings Menu
  • [ ] Forms
  • [ ] Draggability
  • [ ] Splash screen manipulation
  • [x] Dialogs
    • [x] Message
    • [x] Confirmation
    • [x] Input
    • [x] General
  • [ ] Windows
  • [ ] App features (e.g. Help->About)
  • [ ] Complete existing with warnings
  • [ ] Complete and test model types
  • [x] Event:
    • [x] take-until
    • [x] map-to
    • [x] filter
    • [x] filter-by-type
  • [x] Value
    • [x] flatten
  • [ ] Collection
    • [x] filter
    • [x] filter-by-type
    • [x] refresh-each
    • [ ] filter-mod
    • [ ] map-equivalent
    • [x] flatten
    • [ ] equivalence
    • [ ] reverse
    • [x] cross
    • [ ] equivalence
    • [ ] reverse
    • [x] where-contained
    • [ ] group-by
    • [ ] Unit tests on everything
    • [ ] Traceability on everything
  • [ ] Maps and multi-maps
    • [ ] Transformation (design and implement)
  • [ ] Inspect every element and attribute in the toolkits and verify that they are used correctly
  • [x] Clean Up
  • [x] Make clean, formal API for specifying new Observable Model values and types
  • [x] Make clean, formal API for specifying new widgets
  • [x] Rearrange toolkit implementation code to make cleaner (make QuickX)
  • [x] Merge to dev and master
  • [x] DB and Remote APIs should not be in master, only dev
• [ ] QWYSIWYG
  • [x] Render XML with coloring, context hovers, links within document
  • [x] Watch values
  • [x] Style debugger
  • [ ] Report handling (error/warn/info)
  • [ ] Visualize on the affected content
  • [ ] Console view with all (filtered) reports
  • [ ] Support usage of external content, with value hovers, watch values, etc.
  • [ ] Editor
  • [ ] Text editing with content assist
  • [ ] WYSIWYG
  • [ ] Reqorder (record and re-play action sequences)
• [ ] Testing (compute test coverage and fill in as many gaps as possible)
• [ ] Documentation
  • [ ] Javadoc
  • [ ] ObServe (see #15)
  • [ ] ObservableConfig
  • [ ] Quick (docs and training)

[Updownquark]

Riffing on styles:

Widget types (and widget add-ons) can specify model values (like states from legacy Quick, e.g. focused, selected) available to style values and style attributes applicable to them.

Style classes will be achieved using add-ons. Style sheets and toolkits can specify add-ons with a widget required type, and then style sheets with that add-on in scope can specify styles that only apply to elements that inherit that add-on.

Style values can be specified directly on widgets, or via style sheets in the head section or in external style sheets.

Style attributes are declared on a new