Super important.
Super important... call fixHtml at instance creation time and only once This method must be run in the context of the thing creating the XHTML to capture the bound functions
Calls fixHtmlAndJs and if there's embedded script tags, append the JsCmds to the String returned from applying the function to the enclosed HTML.
Calls fixHtmlAndJs and if there's embedded script tags, append the JsCmds to the String returned from applying the function to the enclosed HTML. For use when converting a JsCmd that contains HTML.
Calls fixHtmlAndJs and if there's embedded script tags, construct a function that executes the contents of the scripts then evaluations to Expression.
Calls fixHtmlAndJs and if there's embedded script tags, construct a function that executes the contents of the scripts then evaluations to Expression. For use when converting a JsExp that contains HTML.
~> accesses a property in the current JsExp
~> accesses a property in the current JsExp
This exists for backward compatibility reasons for JQueryLeft and JQueryRight which are now deprecated.
This exists for backward compatibility reasons for JQueryLeft and JQueryRight which are now deprecated. Use ~> whenever possible as this will be removed soon.
(Since version 2.3) Use ~>
instead
Super important.
Super important... call fixHtml at instance creation time and only once This method must be run in the context of the thing creating the XHTML to capture the bound functions
(Since version 2.4) Use fixHtmlAndJs or fixHtmlFunc
A long time ago, Lift was going to track every function/GUID combination vended to a web page with extreme granularity. This meant that for every function/GUID vended, Lift would put that GUID in an attribute associated with the element on the page. In order to capture the GUIDs, some methods like SHtml.ajaxCall() returned a Tuple containing the GUID and the JsExp. This caused confusion and ugly code. So, the GUIDJsExp came into being. Basically, it's backward compatible with the Tuple (String, JsExp), but it functions like a JsExp (although you don't even have to call .toJsCmd because the toString method returns the expresion itself). It should make the ajaxCall()._2.toJsCmd thing into ajaxCall().