On Fri, Jan 18, 2013 at 11:38 PM, Steve Eynon <
steve.ey...@alienfactory.co.uk> wrote:
> > If possible, change your module to not care about order.
>
> Hmm... that reminds me of:
>
> Patient: "Doctor, doctor! It hurts when I do this"
> Doctor: "Well don't do it then!"
>
> After realising this has
> If possible, change your module to not care about order.
Hmm... that reminds me of:
Patient: "Doctor, doctor! It hurts when I do this"
Doctor: "Well don't do it then!"
After realising this has to be a common issue with RequireJS, I
figured it must have been already solved. And in some way it i
Yes, lots of async going on, so the dependencies of the modules may cause
the module's exporting function (the thing you pass to define() as the
second parameter) to occur in an unpredictable order.
If possible, change your module to not care about order.
However, I'm thinking about scanning the
The priority ordering is lost when the call is handed over to
RequireJS from pageinit:invokeInitializer().
There's a shed load of code on the server side to ensure the priority
ordering is kept.
The generated page init JSON is in the correct order.
The initialisation code is called in the correct
Hiya,
I have the following in a component:
void setupRender() {
jsSupport.require("af/highcharts/theme/darkGreen").priority(InitializationPriority.EARLY);
jsSupport.require("af/highcharts/lineChart").with(params);
}
and yet the theme module is still called *after* the lineChart. From
Fi
