| Issue 26: | Use Google AJAX API Loader | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
We should switch the Maps and AJAX APIs to use the Google AJAX API Loader instead of the direct load versions. The options appear to be as follows: 1) Continue to use the direct loading scheme. The question then becomes when will this form of loading be deprecated? What do we loose in flexibility and elegance if we do this? 2) Use BobV's API loader wrapper classes. A user would need to request that the desired API be loaded and wait for the asynchronous load to complete before calling any of the GALGWT that depends on the API. 3) Allow the API key to be specified in a module property that does impact the number of permutations that the GWT compiler will generate. This will also require some mechanism to be able to deal with the asynchronous loading used the AJAX API loader and a way to provide notification of errors during loading. |
||||||||||||
,
Feb 19, 2008
Hello, I've played with Bob V.'s ajax feed api and Loader implementation yesterday looking to add some features and changes, Except of fact that implementation is dependant on library from Incubator I haven't managed to get Loader working correctly in hosted mode: GWT 1.60/WinXP PRO/IE7 Both ajax feed api sample and my own code cannot work with api in hosted mode if Ajax Loader implementation is used. It seems that iframe used to preload api is not updated in hosted mode (so assigned callbacks do not fire), I"m looking for some solution instead of using direct linking, mostly because current Google Ajax API docs discuss/show examples of using ajax Loader only, regards, Peter |
|||||||||||||
,
Feb 21, 2008
hi, I've to use classic inclusion via head script tags (jsapi+google loader) and modified Loader code which simply checks for google.feeds google.feeds.Feed being defined in document at intervals, That way I can play with Feed api samples in hosted mode. regards, Peter |
|||||||||||||
,
Feb 21, 2008
hi, sorry for another post, If Google Loader is used that is adviced to use new consistent naming convention: google.feeds.Feed google.search.NewsSearch etc, However in gwt apis direct naming is used. Exception is Bob's Ajax Feed api example implementatio which knowns about new namespace however it create local reference to it with custom namespace, so google.feeds becomes google_feeds.feeds in JSIO implementation, If I use existing api as is to bind into already loaded Feed api (via javascript loadedr from page header) I cannot use api because of that different naming (solved again as custom patches to use $wnd.google.feeds instead of $wnd.google_feeds.feeds), With Loader GWT implementation it could be probably better to make local reference only if it is not defined yet (e.g. with native javascript loader google.load(...)) and choose recommended namespace for variable: $wnd.google, That way I would be able to use GWT Google apis with pages where Google loader script is used natively, regards, Peter |
|||||||||||||
,
Jun 09, 2008
(No comment was entered for this change.)
Owner: mmendez
|
|||||||||||||
,
Jan 09, 2009
Alex volunteeered to look at migrating the AJAXLoader class created for the Visualization API into its own project.
Owner: a...@google.com
Cc: zun...@google.com daniel.libicki |
|||||||||||||
,
Jan 12, 2009
(No comment was entered for this change.)
Labels: API-AJAX_Loader
|
|||||||||||||
,
Feb 20, 2009
An AjaxLoader class has been added to trunk.
Status: Started
|
|||||||||||||
,
Dec 20 (5 days ago)
(No comment was entered for this change.)
Cc: -galgwt.reviews zun...@google.com
|
|||||||||||||
 Sign in to add a comment
|
|||||||||||||