Oh. Artur, any content that gets copied to the ant-war directory fr'instance src/com/google/caja/demos/playground/examples/ would get served up by the same servlet.
For example, you could run the clock example locally by: 1. Running the servlet as below (note the first run builds a lot of stuff and takes a while) 2. <script src="http://localhost:8080/caja.js";> <script> caja.initialize({ server: "http://localhost:8080/"; }); caja.load(mydiv, uriPolicy, function(f) { f.code("http://localhost:8080/examples/clock.html";).run() }); </script> On Thu, May 3, 2012 at 8:29 AM, Mike Stay <[email protected]> wrote: > Jas, he wants the *guest* content as well as the cajoling server to be > on localhost. > > On Thu, May 3, 2012 at 8:27 AM, ๏̯͡๏ Jasvir Nagra <[email protected]> wrote: >> Hi Artur, >> >> It is. >> >> 1. svn checkout http://google-caja.googlecode.com/svn/trunk/ >> google-caja-read-only >> 2. cd google-caja-read-only >> 3. CLASSPATH=third_party/java/xerces/xercesImpl.jar: ant clean runserver >> >> That will start a cajoling servlet on localhost:8080 and you'll be >> able to follow the rest of the instructions from >> developers.google.com. >> >> On Thu, May 3, 2012 at 7:27 AM, Artur Ventura <[email protected]> >> wrote: >>> Hi there >>> >>> Is it possible to replicate these steps here: >>> >>> https://developers.google.com/caja/docs/gettingstarted/ >>> >>> But having the content to cajoled being present in localhost? I.E. >>> >>> frame.code('https://localhost:8080/guest.html', 'text/html') >>> >>> Or even: >>> >>> frame.code('file:///home/user/caja/guest.html', 'text/html') >>> >>> Using some kind of RPC system to provide the cajoling server with the >>> required content. The motivation behind this is being able to develop the >>> code on your own computer without using some public remote server. >>> >>> Thank you. > > > > -- > Mike Stay - [email protected] > http://www.cs.auckland.ac.nz/~mike > http://reperiendi.wordpress.com
