Skip to end of metadata
Go to start of metadata

Purpose: To answer questions potential users of the product may have (not to answer questions developers may have). Don't assume a detailed knowledge of MapBuilder or its constituent technologies when adding Qs and As to this list.

Mapbuilder functionality

What browsers are supported?

Mozilla 1.* Firefox, Internet Explorer (IE) 6, IE 7
The following browsers are not supported: IE 5.5, Netscape 4
This table shows the browser support of the different releases. Unknown in this case means it probably works, but we haven't tested it fully.


Mapbuilder 1.0.1

Mapbuilder 1.5 RC2

Firefox 1.*



Firefox 2.*



Firefox 3.*



IE 6.*



IE 7.*



Safari 2.*



Safari 3.*



Opera 9.*



What features does mapbuilder provide?

A full list of features is included in our component register Component Register

Adding functionality


Debugging checklist

  • Javascript error: Check the javascript console as explained in Debugging.
  • no extra whitespace in config properties:
    Don't put in extra whitespace or comments for properties in config. Properties should look like <property>value</property> and not have any carriage returns within the element.
  • Empty HTML tags:
    Don't use the empty node form in the HTML page for mapbuilder elements (i.e. <div id="mbId"/>). This is because some browsers do not recognize the empty tag as being closed.
  • XML mime types: The XML documents you retrieve must have a mime type of "text/xml". File types that typically aren't served with that mime type include context documents (.cml), collections (.ccml) and often XSL files as well (.xsl). Check that the mime type mapping file for your server contains a line like:

text/xml xml xsl cml ccml

If you are using Apache, this file will be specified in the httpd.conf.

  • Browser caching of XSL stylesheets:
    Both IE and Mozilla based browsers cache stylesheets loaded by mapbuilder. If you are modifying widget stylesheets, be sure to clear the browser cache before reloading the page. Simply doing a Forced reload of a page is often not enough.
  • HTML DOCTYPE declarations.
    TBD: Is this still valid? We have made improvements in this area which may have fixed this.
    Some HTML doctype declarations cause problems using mapbuilder (including XHTML and those that refer to "loose.dtd"). The following doctype declarations are known to work correctly:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

What tools and techniques can I use to debug Mapbuilder?

Tools and techniques as explained at Debugging.


What licence does Mapbuilder Use?

The Lesser General Public Licence (LGPL)

Why was the LGPL license selected?

The LGPL is worded toward compiled languages and hence is probably not the best licence for a run-time language like Javascript.
However, the LGPL was selected because to be compatable with the libraries we use, and the projects which use us.
This article convinced us to change from the GPL to LGPL: .

Can I include Mapbuilder in a proprietary product?

Probably yes. TBD: More explaination needed here. Matthew?


  1.  how can i add a text near the point?


    in article

    i know how to add a point on map,

    how can i add a text near the point?


  2. I have been part of a team developing a system for a customer which uses Openlayers as its map interface. We use Proj4JS to perform the coordinate conversions.

    Because both Openlayers and Proj4JS are Open Source we have to get these approved for use. Openlayers is no problem but unfortunately the corporate lawyers have jumped on Proj4JS as it uses the L-GPL license. I don’t pretend to understand the reasons behind this but it means that we cannot use it.

     Does anyone know of an alternative Javascript library – either OS or commercial – that we could use to replace Proj4JS?

    (What is most annoying is that Proj4 and the Java conversion use MIT licences which would have been acceptable)