Hi Andreas et al,
On Thu, 2007-11-22 at 02:09 +0100, Andreas Hocevar wrote:
> It was agreed to not add it to the branch. And thus the last merge
> from trunk to 1_5 did not contain this change.
OK. Steven confirmed the same thing, so that is clear for us now.
> But if you want us to vote on tha
Hi Roald --
On Nov 22, 2007 1:12 AM, Roald de Wit <[EMAIL PROTECTED]> wrote:
> It's not quite sure to me and Cameron whether or not it was agreed in
> the last meeting to put my layerId changes into the 1.5 branch. Can you
> please explicitly vote for or against it asap?
First of all, thanks for
Steven, I think this is a good solution for 1.5, but think we can do a
better job with OWS Context for future versions.
I think that we should aim to make OWS Context simple and for that I
think that , and should all be merged. Ie:
...
Our applications then decide whether we treat a servi
Hi List,
It's not quite sure to me and Cameron whether or not it was agreed in
the last meeting to put my layerId changes into the 1.5 branch. Can you
please explicitly vote for or against it asap?
Some cons and pros:
- new and not tested enough
- might break existing apps (if there are bugs)
+
I'll throw in my 2 cents here too, since this is a question I've asked
myself many times.
The strength of MapBuilder is the MVC design pattern for building
applications, and handling the model on the client side. (Most MVC
frameworks hold the model on the server side) This means that
MapBuil
In addition to Andrea's comments.
In Mapbuilder, we can use XSL while in Openlayers all XML parsing is
done by JS converting XML into JS objects.
For building a widget like a Legend from an XML service (like GML), XSL
is still the easier technology to work with.
There are moves to support JSON
Hi all,
After discussing this with Andreas we decided for the following approach
for the 1.5 release:
GMAPS, VE, YMAPS and non WMS-baselayers are only supported in OWSContext
So if we have a standard WMC, we will add a hidden baseLayer, just as
Andreas did already, nothing changes there. It will
Hi Bart,
On Nov 21, 2007 10:31 AM, Bart van den Eijnden (OSGIS) <[EMAIL PROTECTED]>
wrote:
> I agree with 2 (I come from a server-side framework, i.e. Chameleon), but
> ofcourse since OL already provides most of the building blocks (GML parser
> etc.) it will require a few lines of code to intera
Hi Andreas,
thanks for your insight.
I agree with 2 (I come from a server-side framework, i.e. Chameleon), but
ofcourse since OL already provides most of the building blocks (GML parser
etc.) it will require a few lines of code to interact with the OGC Web
Services. Only things like printing (PDF
Hi Bart,
I can only speak for myself here, but I see the added value in the following:
* The MVC pattern allows us to build applications in a modular manner.
OpenLayers gives us the map, Mapbilder the application around the map.
* Of course there are also server-side frameworks giving us this
fu
10 matches
Mail list logo
