Profile cover photo
Profile photo
David Griffin
70 followers
70 followers
About
David's posts

Post has attachment
Check out this video on YouTube:

I've entered a bit of "hangout hell"...  A seemingly innocuous change has had a ripple of bizarre errors.   Cause: I renamed my hangout app.  For whatever reason this changed my project id and seemed to drop a whole bunch of other settings.   I went through the pain of filling in all of the settings needed to get an app running (correctly I thought).  Now nothing runs!   If I launch the app through the API console it works OK, but if I try launching it "normally" it says it has trouble starting the hangout.   At one point it asked me to reinstall the Hangout plugin (which I did -- same result).  Sometimes it says "There was an error loading your app! This app couldn't open because it didn't provide required information." although I have no clue as to what information is missing (nothing in the console log to help).   Any suggestions or should I just start from scratch?

Since you suggested that we share more ideas/requests in the Hangout community, I thought I'd put a request out there.  Someone asked if the image buffer would be available and you indicated that under controlled circumstances that might be possible.   I would like to request that there be an API that lets the viewer do a "snapshot" of their video stream and make it available to the API.  By default it might replace the avatar.   This would let people change their avatar to something contextual for the hangout and allow that avatar to be used in the user experience of the apps (e.g., we have a game where we drag avatars around, but a lot of people haven't set their Google+ avatar yet or would prefer to use a different one for the hangout -- just like you dress up for different parties in real life...)   I hope this makes sense, and I think it still gives control to the user over the image that is handed to the API so privacy should be respected, etc.    For your consideration....  Thanks.

There seems to be changes afoot in the Hangouts interface.  There's been some restyling of the participants, simplified iframe hierarchy, etc.  All very cool.

One disturbing/annoying item is what appears to be a bit of a reliability issue in the API and I'm guessing I need to add some code to detect and recover from it.

What I'm seeing in the console log is "400 (Unknown SID)" errors popping up -- and as near as I can tell these seem to be associated with losses in shared data updates.   The URL is of the form:

https://plus.google.com/hangouts/_/channel/bind?VER=8&clid=9B21565809757F90…01_RC6%22%5D&SID=AFDA12EDAD175467&RID=16806&TYPE=terminate&zx=ilsggup0d7im

Any insight as to what is going on and, if this is to be expected, how I can "harden" my interaction with the shared data interface.  (I think, up to now, it's been so reliable that I never really thought about error cases there -- at least none where the hangout itself didn't eventually just up and die...)

Thanks!

I think there was a change in the video layout in 1.4 and I can't quite untangle what's going on.    It seems that getVideoFeed() will return either the defaultVideoFeed or a videoFeed.   However, when I call getDisplayedParticipant() on the default video feed I always generate an exception: "getDisplayedParticipant called before onApiReady was fired." 

Is there a new practice for determine the id of who is talking?

I asked this a few weeks back in the Hangouts community, which seems to not have much activity, so I'll take advantage of the great expertise here and ask again:

I'm working on a Hangout app and just figured out something that has been driving me a bit nuts -- and I haven't read anything about it so I'm checking to see if others see this too.

When I run the app in the API console (sandbox), all seems well.  But when I run the app from the "production" side everything is smaller.   

When I checked the window and viewport settings, it is reporting a 1360x920 viewport for a 1020x763 window (numbers approximate).   So it presenting everything 30% smaller!??

Is there a reason for this?   I checked a few of the iframes along the way and the min width and height don't seem to change.

I'm starting to wonder if I should be using the API Console for development as it doesn't represent what the user is going to see (even though it has some cool rapid turnaround features for debugging).

Does this bother anyone else? Can someone explain why this is done? Any guidance is welcome!

Thanks,

- dave

Did the Google API Console for hangouts change/break?  I can no longer use it (it fails to load with an syntax error in login.corp.google.com/request?s=oz-autopush-full.plus.corp.google.com:443/uberproxy).   Stopped working sometime last week.

I can access my app just fine without the console, but appreciate the reload facility in the API console testing access.

I'm working on a Hangout app and just figured out something that has been driving me a bit nuts -- and I haven't read anything about it so I'm checking to see if others see this too.

When I run the app in the API console (sandbox), all seems well.  But when I run the app from the "production" side everything is smaller.   

When I checked the window and viewport settings, it is reporting a 1360x920 viewport for a 1020x763 window (numbers approximate).   So it presenting everything 30% smaller!??

Is there a reason for this?   I checked a few of the iframes along the way and the min width and height don't seem to change.

I'm starting to wonder if I should be using the API Console for development as it doesn't represent what the user is going to see.

Any guidance is welcome!

Thanks,

- dave

Post has attachment
Fourth anniversary of my monthly nature wallpapers. Happy New Year!

Post has attachment
Framed 8 river and town prints for a new restaurant opening in Maynard. Hoping to hang them today. 
Photo
Wait while more posts are being loaded