Mapsicle - ability to pass GStreetviewPanoramaOptions into Mapsicle.prototype.upStreetView

[GoogleCodeExporter]

The GStreetviewPanorama object is created in
Mapsicle.prototype.upStreetView with a fixed set of
GStreetviewPanoramaOptions.  This prevents the developer using Mapsicle
from being able to set some useful options, namely enableFullScreen,
features and userPhotosOptions.

These options must be set in the constructor and cannot be changed later. 
Mapsicle should have some mechanism to pass these options into the Mapsicle
constructor.  It could either wrap all the options, or (preferably since
Google sometimes adds new options) lets you pass in the full
GStreetviewPanoramaOptions object.

Original issue reported on code.google.com by chimpath...@gmail.com on 23 Dec 2009 at 4:55

[GoogleCodeExporter]

Ideally it should allow GStreetviewPanorama as well. In our case the panorama 
options 
is not as important as the panorama itself

Original comment by jose.noh...@gmail.com on 23 Dec 2009 at 7:35

[GoogleCodeExporter]

Original comment by pamela.fox on 23 Dec 2009 at 8:06

• Added labels: Class-Mapsicle, Type-Enhancement

[GoogleCodeExporter]

r1185 in trunk already allows you to construct Mapsicle with enableFullScreen,
features and userPhotosOptions. Hopefully I'll get around to accepting a
GStreetviewPanoramaOptions instead, so I'll leave this ticket open.

Original comment by stephend@gmail.com on 4 Jan 2010 at 8:57

• Changed state: Started

[GoogleCodeExporter]

@jose.noheda: that's a separate and rather more difficult problem, which 
deserves its
own ticket. Why do you need to construct your own panorama?

Original comment by stephend@gmail.com on 4 Jan 2010 at 9:24

[GoogleCodeExporter]

I need it to port Mapsicle to Gmaps4JSf which already has a panorama tag and 
only needs 
to be enhanced. Otherwise it means duplicating lots of code

Original comment by jose.noh...@gmail.com on 5 Jan 2010 at 10:47