On Wed, Nov 21, 2007 at 09:45:52AM +1100, Cameron Shorter wrote:
> Steven,
> Brainstorming on this topic, without having thought through all the details:
>
> * A baselayer by definition is not transparent. Right?
No. You can have a transparent baselayer. I've used this in the past for
creating o
Ok,
Commercial Support in now advertised on the Mapbuilder web site, and
referenced from the main contents. Thanks Steven for fixing permissions.
I suggest others interested in providing support list themselves as well.
http://docs.codehaus.org/display/MAP/Commercial+Support
Cameron Shorter wrot
Steven,
Brainstorming on this topic, without having thought through all the details:
* A baselayer by definition is not transparent. Right? In that case, in
MapPaneOL, we should be able to render all the layers until we get to
the baselayer, then we don't render the rest. (Will be slightly more
Andreas, you solution sounds good for the 1.5 release.
For 1.5 release candidate we want minimal impact changes and it sounds
like you have that covered.
Andreas Hocevar wrote:
> Hi,
>
> while all that was said by Steven should be considered for the trunk,
> we have to find a reliable solution fo
Hi again,
I have a refined proposal which might be more satisfying to those of
you that are in favour of a context-based solution:
IIRC, all map and layer control widgets only look for "Layer" and
"FeatureType" nodes in the context.
So why don't we add "BaseLayer" nodes? Since OWSContext is more
Hi list,
I often wonder what currently is the added value of Mapbuilder over
OpenLayers.
As I see it, the gap between Mapbuilder and OpenLayers is quickly
getting smaller and smaller. Soon OpenLayers will have WMC and OWS
Context read/write support, previous and next extent controls, a
distan
Hi,
while all that was said by Steven should be considered for the trunk,
we have to find a reliable solution for the upcoming release. I just
had a little chat with Steven, and we came up with the following
proposal:
- Base layers are strongly tied with resolutions. Resolutions are
currently in
Hi all,
While refactoring MapPaneOL to accomodate non-wms baselayers I
discovered that I missed an important problem during the last discussion:
If we have multiple baselayers we will need a solution similar to OL's
list of baselayers:
We need to parse all layers in the context doc and pick thos
