Thanks, Martin
> Yes, that how it works. The cook tool puts together a list of .js
> files according to a recipe.
The only thing I don't understand is what this "recipe" looks like. I
mean, how this "putting together" is different from concatenating all
the .js files? Does it change the functions' definitions so that
nothing is undefined up to the time of usage?
> I can't make a good suggestion for a jQuery intro. I can answer about
> the odd looking constructions, such as:
>
> $(function() {
> // jquery goes here
>
> });
>
> These are because javascript is a function scoped, rather than a block
> scoped language, so to constrain the scope of variables you need to
> wrap them in a dummy function. In a block scoped language, you would
> just wrap the variables in a block (ie {...} or BEGIN...END).
Aha. So, for instance in [1] the onLoad function is defined so that it
can't be used outside the abego.loadFile, right? But what does the $()
mean here? Does this mean that the code in $() "sees" jQuery
functions?
[1]
http://tiddlywiki.abego-software.de/archive/IncludePlugin/Plugin-Include-src.1.0.1.js
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywikidev?hl=en.
