Method "startupAt" for widgets

[lazaridis_com]

The "startupAt" function would work similar to the existent "placeAt". It would do nothing more than:

• call placeAt(node)
• call startup
• return this

The usage would be simple:

tree1 = new Tree().startupAt('TreeDiv');

Related discussion:

​http://dojo-toolkit.33424.n3.nabble.com/Instantiation-of-a-Widget-simplest-way-tp2867781p2894507.html

[Karl Tiedt]

What advantage does this beyond obfuscating placeAt() over the previous developers suggestion of making startup() return "this" so:

widg = new widget().placeAt(node).startup();

works as expected?

[lazaridis_com]

Making startup() chainable was my initial thought, but I refrained, as this can break existent behavior.

Additionally, if I would see code where "placeAt(node).startup();" is used repeatedly, I would immediately ask: why not in one function, e.g. "startupAt"?

(please use the mailing-list topic for further discussion, I've understood that this is the process within the project)

[dylan]

Bill, thoughts on this one? This is a suggestion for a syntactic sugar clean-up for placeAt + startup.

[bill]

placeAt() does return "this", so placeAt(node).startup() is possible.

Also, since [28251] placeAt() sometimes calls startup() implicitly, but not in all cases. Maybe that should be changed for 2.0. I'll add a note to the code for that.

But I don't want to add a separate startupAt() method.

[bill]

In [30830]:

add todo for 2.0, refs #12846 !strict