[OpenLayers-Users] Custom Build: browserNotSupported?
Andreas Hocevar
ahocevar at opengeo.org
Thu Jul 14 10:33:03 EDT 2011
Hi,
by adding the Canvas renderer only you will still get the same error
message in IE<9.
The issue you ran into is one of the few (if not the only one) where
the debugging console won't give you any hint, and the message you get
is not useful either. One thing that could be done easily would be to
replace the "browserNotSupported" lang key with something like
"noRenderersForThisBrowser"
If you create a ticket and add a patch, I'll happily review it.
http://trac.osgeo.org/openlayers/changeset/12127 may serve as an
example to see where needs to be changed.
Andreas.
On Thu, Jul 14, 2011 at 2:33 PM, Michael <mdm at yachtpc.com> wrote:
> Thank you, that did the trick.
>
> Actually, just adding "OpenLayers/Renderer/Canvas.js" made the error go
> away.
>
> I had looked in the OL code to see what error would throw that particular
> message.
>
> So, how do we modify the codebase or build tool to make that requirement
> more evident?
>
> Michael
>
> On 7/14/2011 3:16 AM, Andreas Hocevar wrote:
>>
>> Hi,
>>
>> in addition to Layer.Vector, you need to add vector renderers to your
>> build profile, e.g.
>>
>> OpenLayers/Renderer/SVG.js
>> OpenLayers/Renderer/VML.js
>> OpenLayers/Renderer/Canvas.js
>>
>> Andreas.
>>
>> On Thu, Jul 14, 2011 at 4:42 AM, Michael<mdm at yachtpc.com> wrote:
>>>
>>> Okay, I am delving deeper into OL awesomeness. I am just starting with
>>> the
>>> "build" process. I am using OL 2.11-RC
>>>
>>> My page, and the example pages, hosted on my site work fine with the
>>> distributed build, and also with the "full" build.
>>>
>>> However, when I do my custom (adding on the lite.cfg with all the
>>> OpenLayers
>>> modules that throw an error added back in), I end up with a popup saying
>>> "browserNotSupported"
>>>
>>> This happens whether I use FF or IE, and Safari too.
>>>
>>> Clearly, I need to add in another module... or more... but which? Since
>>> it
>>> works with a full build, this seems to be a configuration issue, not a
>>> code
>>> bug, but a suggestion would be nice
>>>
>>> Michael
>>>
>>>
>>>
>>> ps:
>>> My page is the attribution.html example.
>>>
>>> My includes are as follows:
>>>
>>>
>>> [include]
>>> OpenLayers/Map.js
>>> OpenLayers/Layer/WMS.js
>>> OpenLayers/Layer/Vector.js
>>> OpenLayers/Control/LayerSwitcher.js
>>> OpenLayers/Control/Attribution.js
>>> OpenLayers/Control/Navigation.js
>>> OpenLayers/Control/PanZoom.js
>>> OpenLayers/Control/ArgParser.js
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/openlayers-users
>>>
>>
>>
> _______________________________________________
> Users mailing list
> Users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-users
>
--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
More information about the Users
mailing list