Great! Thanks for verifying with Camino!

David

Bruce Robertson wrote:
> All load OK in Camino   1.6.7, OSX 10.5.7
>
> On May 17, 4:06 pm, David Huynh <[email protected]> wrote:
>   
>> Hi all,
>>
>> It's been one of the long-standing, advanced issues discussed here: how
>> to dynamically load various Simile Widget APIs on-the-fly, especially
>> because there's no way to change the <head> of the page within your web
>> publishing platform. The challenge is to ensure that the many js files
>> to be loaded asynchronously are loaded in the right order.
>>
>> I'm starting to experiment with a solution--here's 2 examples in which
>> all APIs are loaded only when a button is clicked:
>>
>> http://trunk.simile-widgets.org/timeline/examples/test_dynamic_loadin...
>>
>> http://trunk.simile-widgets.org/exhibit/examples/test_dynamic_loading...
>>     (ignore the Google Maps "wrong key" alert)
>>
>> Here's a simpler example in which the APIs are loaded from <script>
>> inside <body> rather than inside <head>:
>>
>> http://trunk.simile-widgets.org/timeline/examples/test_dynamic_loadin...
>>
>> I've tested these on
>> - Firefox 3, Mac OS X and Windows
>> - Safari 4, Mac OS X
>> - IE8
>> - Chrome
>>
>> Please let me know if they don't work for you on some particular
>> browser. (This new dynamic loading support has not been released yet.
>> What you're seeing are the development versions of the APIs.)
>>
>> The solution involves generating "compilations", basically a single js
>> file for each locale that includes all the js code. All compilations
>> support the same way for specifying a callback.
>>
>> Thanks,
>>
>> David
>>     
> >
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to