This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm not sure if the race conditions I am encountering in Woodstock compomenents are derived from Woodstock components or the underlying Dojo functionality, and I'm hoping you can save me a lot of time by having the answer.
Turns out that the Woodstock Wizard component has some strange behavior, whereby, components do not get drawn, or are not visible, until components that have bindings get rendered. This is not isolated to the wizard component, but is repeatable more often using this component type. I am assuming that the bindings are using asynchronous calls, particularly valueChangeListenerExpression on the Woodstock listbox component.
Also, the most notable missing component in Woodstock, appears to be a onDocumentReady attribute or flag that takes asynch calls into account and doesn't fire until all components are rendered. Does Dojo have this?
Assuming that was directed at me, I have no knowledge of Woodstock at all and thus can't help any.
If you meant that as a more general question to all readers, then I step aside for someone else to answer