Hi David, if you look at the code for http://cgdh.ideacompany.ca/ at
around line 45 I've got the applet code, which I moved into the .js file
made sure all the double quotes were escaped and validated the syntax. 
Everything went okay.  Back in exhibit i created a div with a
ex:content=".key" inside assuming that this would take the value of .key
(which was that big line of applet code) and wrap place it between the
div opening and closing tags.  Unfortunately this didn't happen.  I'm
not sure if it's because I'm forcing it through the Thickbox.  Right now
the way the page is set up is that the param inside the applet tag has
it's value as ex:value-content=".key" (this is the correct way of
getting source inside the tag right?) for some reason the param reads
the code as ex:value-content instead of value.  Is this a limitation
with exhibit?  I suspect it's a limitation of the applet.

David Huynh wrote:
> Thank you for experimenting with that. Actually, I just tried embedding 
> HTML tags inside the JSON and it worked. There is no need to encode < as 
> &lt;, etc. Could you give it a try again?
>   
David Huynh and Johan Sundström wrote:

I have seen some rendering bugs like that but I'm not sure what causes 
them. In some cases a whole lens disappears. Maybe it's Firefox's own 
bugs? Could you try tweaking some CSS rules and see if there's a pattern?

The symptoms match image hosting on a server on a different domain
which does HTTP referrer (sic) enforcement, to avoid hot linking images
from other places.

I think Johan is correct, as these images are living off server and
various parts of the lens itself aren't disappearing.  But if I come
across any of the bugs that David mentioned I will see if I can do some
css tweaking and try and fix that issue.

Derek Kinsman
The Idea Company

New Media Designer

http://www.ideacompany.ca/
http://boring.ambitiouslemon.com/
1.416.371.5652

_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general

Reply via email to