A few notes regarding object access and windowing…

I’m not familiar with using jsOrb as a library, but I do know that you can pass dynamic objects such as Datasets from the parent window to the child and vice versa using simple object reference.

Additionally, you also use that methodology to notify child/parent asynchronously when processing large objects, script requests via XMLHttpRequest and dynamic script src execution requests. That is very useful when building web applications and is fundamental to AJAX.

As a language, Javascript is very robust but only to the extent of thought put into its application.

For a new user of JavaScript what would be a good start to grok the core concepts? A book/tutorial will be helpful.

var business\u0032business=”bar”;

…is perfectly legal, even though you’ll probably want to use “2″.

x = y.gimme; x();

You’ll get NaN because it doesn’t know to setup the correct scope.

Good points, and clearly made.

Sorry about missing the closing blockquote in my earlier response, I’ve gotten used to comment previews, I guess.

–Dethe

My statement about objects (variables whose .constructor property in some way descends from Object) was correct. Primitive string *values* are immutable in JS, but an object of type String may have new properties added to it at any time. Same with object of type Number. Their primitive values, however, are (as you point out) immutable.

Also, the hash deference is exactly equivalent. That there’s no way to have a JS lexer handle an variable name with spaces in it in no way detracts from the equivalence, it just means that the dot operator has to follow the rules of thing that aren’t string literals. Also, note that the way it was phrased, I said that anything you can do with the dot operator you can do with hash dereferences. I didn’t say it worked the other way around.

Regards

Every object is always mutable

Except numbers and strings and functions and perhaps a few other things.

The dot operator is equivalent to de-referencing by hash (e.g., foo.bar === foo["bar"])

Not quite equivalent. You can say foo['string with spaces'] and foo['keyword'] (where keyword is a Javascript keyword, like “for.” Neither of these cases work using dot notation.

I don’t think either of these points detract from what you’re trying to say, but I’ll make them in the interest of accuracy.

Anyhow, I like “grok” … “understand” seems insufficient. I guess my analogy would be that you can read all the automotive magazines you wand, but until you get behind the wheel of a car, you don’t “grok” driving.

I needed to write polling “threads” (interval functions) to handle the request/response nature of this type of activity. But it works fine. You call JsOrb.importGraph(context, obj, callback) and your callback is executed when the import is complete, and gets passed a reference to the imported graph.

Yet another reason to hate IE: why not let me instantiate objects in another JS context?

*sigh*

grok grok grok.

grok grok.

grok.

(I love anonymous commenting)