Show multi-tabs for infowindow

[GoogleCodeExporter]

"well I would like for the info window to show the user contributed content, 
which is GFC members on a tab, text messages on another tab, and their 
picasa/flickr pics on the third tab - if no one has added any content to any 
one of the tabs, maybe we should just have a message that says something 
along the lines of "be the first to contribute""

Original issue reported on code.google.com by pamela.fox on 27 Sep 2009 at 10:27

[GoogleCodeExporter]

So for the tab names, in left to right order:

Supporters | Messages | Photos

"Supporters" will show the GFC members and will be the first to show in the
info-window - I believe that from a GFC standpoint this was going to show the 
most
recent supporters to have voted

"Messages" tab shows the contributed text messages - this is a list of messages
contributed, a scrolling list of messages, you can choose an appropriate number 
of
messages to display based on latency, etc.  It should pull the most recently
contributed messages

"Photos" tab shows contributed photos, pulled from the contributed links to 
Picasa
and Flickr as thumbnails, and if a user clicks on a pic then they get taken to 
a new
browser window/tab to show that pic on picasa or flickr

Original comment by justin%s...@gtempaccount.com on 27 Sep 2009 at 10:42

[GoogleCodeExporter]

oh yeah, and let's definitely use the same look and feel for the tabs as the 
tabs
we're using at the top, per Pamela's demo at:

http://gmaps-samples-v3.googlecode.com/svn/trunk/infowindow/tabs.html

Original comment by justin%s...@gtempaccount.com on 27 Sep 2009 at 10:43

[GoogleCodeExporter]

What about the situation where no GFC members have signed in that area? They 
should be 
listed as a number in supporters, right?

I kind of think the GFC members icons should be shown next to their mssage - it 
feels 
weird to separate the user data that way.

Original comment by pamela.fox on 27 Sep 2009 at 10:48

[GoogleCodeExporter]

This feels to me like something that ought to be in its own branch for the sake 
of
having something stable to launch.  IE, we need a code branch that we're calling
frozen feature-wise.  This might be a little tricky, because it looks like 
Pamela's
source repository isn't quite set up for normal branching.  Also, I'm not sure I
agree that we should have the exact same UI for tabs inside info windows.  I 
used
that theme simply because it was quick and dirty, not because I thought it was 
a good
fit for the content, and I think info windows are a bit more sensitive to 
ill-fitting
design.  Probably needs to be more like a solid fill color rather than gradients
everywhere for that.

Original comment by api.boba...@gmail.com on 29 Sep 2009 at 1:04

[GoogleCodeExporter]

Obsoleting Earth Petition issues as that project is over.

Original comment by pamela.fox on 20 Sep 2010 at 2:06

• Changed state: WontFix