I probably should have mentioned this. The comma-separated libs
works in iGoogle and the legacy apps form (using
'www.google.com/ig/f/' + lib_path). In the other containers (at least
in GMail), the list is a colon-separated list which I haven't
bothered with because the settings are less important to me.
Like in the iGoogle case, the list gives the path to the various
scripts. So "js/core:dynamic-height...." is mapped to
'http://www-gm-opensocial.googleusercontent.com/gadgets/js/'
lib_name +'.js' (i.e.
'http://www-gm-opensocial.googleusercontent.com/gadgets/js/core.js')
Like I said, I don't try to settings in the other containers, so
I can't vouch for its effectiveness.


On Mar 30, 6:57 am, Mariusz Nowak <[email protected]> wrote:
> I still can't get it working.
> On my side libs param have value 'js/core:dynamic-
> height:google.calendar-0.5:google.calendar-0.5.read:opensocial-0.8:security-
> token:views.js'
> When accordingly to legacy doc I try to load 'http://www.google.com/ig/
> f/js/core:dynamic-
> height:google.calendar-0.5:google.calendar-0.5.read:opensocial-0.8:security-
> token:views.js' it fails with 400 Not Found.
> Do you have any idea what am I doing wrong ?
> Thanks!
>
> On Mar 29, 7:25 pm, SerranoABQ <[email protected]> wrote:
>
> > Harm,
>
> > The URL parsing technique still works (for now). Just make sure
> > to require the "setprefs" library. I've had success with "setprefs"
> > and "dynamic-height" libraries and the legacy API calls
> > [_IG_Prefs()].
> > I simply parse the "libs" query parameter in the URL, split them
> > at the comma and inject each library into the DOM. Then I use the
> > legacy calls for the preferences (for some reason the gadgets.*
> > namespace is not available). This is how I have it set up
>
> >  var prefs;
> >  try{
> >   prefs=new _IG_Prefs();
> >  }catch(e){
> >   // Create dummy functions to mimic the original prefs object,
> >   // and complete gracefully. You could also add getInt, getArray,
> > etc.
> >   prefs={getString:function(s){return null},set:function(n,v){}};
> >  };
>
> > I use mootools as my framework for most of the code in the page
> > so it can function independently of the gadget functionality,
> > but I can still save settings when placed in iGoogle or
> > another gadget container.
>
> > Hope this helps,
> > Justin
> > On Mar 29, 10:05 am, Harm <[email protected]> wrote:
>
> > > Anyone?
>
> > > On Mar 14, 6:17 pm, Harm <[email protected]> wrote:
>
> > > > Hi all,
>
> > > > I'm trying to build a secure iGooglegadget. People need to sent
> > > > sensitive data to my server (typically username/pass).
> > > > I so far figured out that the way to do that is create agadgetwith
> > > > <Contenttype="url" href="https://bla.com/test.html";></Content> as
> > > > this is the only way to load SSL resources.
>
> > > > The initial page will show a login dialog. After the user is logged in
> > > > I want to set a hidden UserPref so I know that pariculargadgetis
> > > > authenticated.
> > > > I was going to do something like describe in this 
> > > > thread:http://groups.google.com/group/Google-Gadgets-API/browse_thread/threa...
>
> > > > The page loaded would use somejavascriptto set the user pref value.
> > > > Unfortunately I can't seem to find the correctjavascriptlibrary to
> > > > load. With the legancy API you needed to do some parsing and
> > > > dynamically load the libs, see under "Using theJavaScriptLibraries
> > > > with type="url" 
> > > > Gadgets":http://code.google.com/apis/gadgets/docs/legacy/fundamentals.html#Libs
>
> > > > This feature no longer seems available. Is there a way of loading the
> > > > correctjavascriptlibs on the remote site (test.html)? If so, how?
>
> > > > Thanks for your help.
>
> > > > With kind regards,
> > > > Harm
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" 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/Google-Gadgets-API?hl=en.

Reply via email to