We currently have a problem with the chameleon architecture that requires that
the mapfile be loaded before parsing the HTML template.  This forces chameleon
developers to hardcode the mapfile path in the main script that calls chameleon
and makes it impossible to implement multi-template applications in which the
mapfile may change depending on the template in which we are.  Unless you keep
passing the mapfile path in the URL which isn't really the nicest solution.

It seems that what would make the most sense would be to have a global mapfile
by default, but also have the ability to change the mapfile either in a global
setting of a template, or even better directly inthe Map widget.

This would probably be hard to change, but that's definitely an issue for
applications that aren't mapfile-centric or that use multiple mapfiles.