Hi David, Yui has done a lot of work so it can be loaded at the same time as other frameworks with no conflicts. -- they put everything through the global yui or y object to ensure that the global window namespace is not polluted.
-- I use yiu 2.x lib with timeline (and jquery) and it works fine. The new 3.x yui additionally includes further work on making the lib more modular so that you do not load more of the lib then you're actually using. -- lowers the initial and final page weights. I suggest yui due to their specific work in loading js as needed (w/ dependency trees) and your interest in the subject. If you feel that as-needed loading would be a good feature addition then I suggest that you leverage the yui work rather than re-inventing it. They continue to put time and $$ into the toolkit. Since they use it for powering the main yahoo properties, it is robust, well tested and documented. And they have an excellent community mailing list, including the developers. Larry Sent via BlackBerry from T-Mobile -----Original Message----- From: David Huynh <[email protected]> Date: Fri, 05 Jun 2009 09:25:11 To: <[email protected]> Subject: Re: dynamic loading of widget APIs Thanks, Larry. One reason I have been hesitating to use any of these n frameworks is that our users might actually use one of the other n -1 frameworks, which conflicts with the one we choose. Do you have a sense of how well YUI plays with other frameworks? David [email protected] wrote: > Hi David, > > Fyi, Yahoo has done a lot of work in this area of dynamic loading of js. See > the loader section of the yuo site. They've extended the work in their 3.0 > ver. > > Larry > Sent via BlackBerry from T-Mobile > > -----Original Message----- > From: David Huynh <[email protected]> > > Date: Sun, 17 May 2009 16:06:10 > To: <[email protected]> > Subject: dynamic loading of widget APIs > > > > 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_loading/fully_dynamic.html > > http://trunk.simile-widgets.org/exhibit/examples/test_dynamic_loading/fully_dynamic.html > (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_loading/body_scripts.html > > 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 -~----------~----~----~----~------~----~------~--~---
