Foolish me

...I'll start using a javascript syntax checker (will include a feed back for this as well as it would be a great addition for WebControlWrapper), although now I'm having the following error
Could not execute returned javascript: $ is not defined
Source: var langdir = document.getElementsByTagName('body')[0]; if(langdir) { langdir.removeAttribute('dir'); }
var langdir = document.getElementsByTagName('body')[0]; if(langdir) { langdir.setAttribute('lang','en-US,en;q=0.8'); }
THE FIX (for those who may encounter this error):
In the computed property I forgot to check that the Libraries have been loaded first....upon creation of the control, the set event of the property is invoked...the libraries MUST be loaded before set can be invoked my property should look like the following:
mValue = value
if LibrariesLoaded = true then
ExecuteJavaScript("$('#" + Me.ControlID + "').progressbar({ value: " + str(value) + "});")
end if
Greg:
Would it be possible to invoke computed properties after the generation of controls?...still invoking non-computed properties before libraries have been loaded within the WebControlWrapper class? I realize this would mean a change within the WebSDK...but before I make a feedback I just want to make sure that I myself, am not doing something incorrectly. Yet it would be understood that within the WebControlWrapper that computed properties would always (in probably 90% of the time) involve some sort of javascript...which would need to be invoked after control creation rather than before?...I realize this should probably be within the beta list, although may be valuable to another community member since the WebSDK has already been released and I'd like to prevent the cascade of similar questions since someone else may search for a similar question. (Thus, why my posts are generally 'long' to ensure I include as many keywords which may be searched related to similar questions

)