[meta] Programatic widget test cases

[Brian Lucas]

It would be helpful to have two different forms of instantiation in the widget test cases: 1. script-based 2. HTML markup-based

Only non-deprecated widgets need apply.

[ktiedt]

(In [5866]) references #287 includes createWidget() examples for Clock, ColorPalette?, ComboBox?, DatePicker?, and DebugConsole?. Would have Dialog, but it is buggy... still trying to figure out whats going on with it.

[dylan]

we've made progress on this, but this is a lot of effort, so we'll move some of this effort to 0.4.1 (and maybe even 0.5). We also need to come up with a list of widgets that fail to work with programmatic instantiation.

[bill]

oops, meant to set this for 0.5

[tk]

Going to recommend this be closed, with the new requirements for each package, this should be resolved on its own as things are ported to 0.9.

[bill]

Well, it would still be nice to have examples of programatic creation in each test, since we do (in theory) support that. Sometimes the differences are interesting, like for Buttons, specifying the label as a label attribute rather than innerHTML.

[tk]

I thought that was part of the new test case/documentation requirements for Dijits/DojoX?

[bill]

See #4843: Menu/MenuItem and ComboBox are the major ones not done.

[rcoup]

(In [11173]) references #287 Add a programmatic creation example for Menu.

[dante]

(In [11658]) refs #287 - programatic splitcontainer example

[bill]

(In [11801]) Programmatic editor creation test (refs #287)

[bill]

(In [12879]) Programmatic tree example. Refs #287.

[dante]

time to punt him.

[toonetown]

(In [14143]) Refs #287 - remove extra character

[dante]

(In [14841]) refs #287 - add programatic filteringselect example.

[dante]

(In [14842]) refs #287 - whoops .. broken function.

[bill]

(In [15322]) Better StackContainer? programmatic test. Refs #287.