[Dojo-interest] Upgrade from 0.2 to 0.4.1

[James Burke]

Unlike the .* syntax, "common" works like any other module resource
names. Basically, whatever you specify as the dojo.require()
statement, translate the dots to slashes, and add a ".js" to the end:

dojo.require("foo.bar.common");
maps to a file foo/bar/common.js. Inside that file, there should be a
dojo.provide("foo.bar.common");

James

On 1/8/07, Corey Samuels <Corey.Samuels at kaplan.com> wrote:
> Thanks for the info James.
>
> Can you also elaborate on how the "common" module resource works, as per
> one of your previous suggestions?
>
> Corey wrote:
> > - __package__.js file (is this deprecated?)
>
> James responded:
> > Not deprecated, but discouraged. It maps to the ".*" part of a
> dojo.require call. For instance,
> dojo.require("application.airline.utility.*) maps to
> application/airline/utility/__package__.js. Internally, we're going with
> a "common" module resource instead of __package__.js For instance,
> dojo.require("application.airline.utility.common) maps to
> application/airline/utility/common.js
>
> Corey asks:
> In this example, what might be contained in the
> application/airline/utility/common.js file?
>
> Also, what purpose would the statement
>         dojo.require("application.airline.utility");
> serve, if any?
>
> Thanks,
> Corey
>
> _______________________________________________
> Dojo FAQ: http://dojo.jot.com/FAQ
> Dojo Book: http://manual.dojotoolkit.org/DojoDotBook
> Dojo-interest at dojotoolkit.org
> http://dojotoolkit.org/mailman/listinfo/dojo-interest
>