Re: [Mapbuilder-users] exchange tool mode with openlayers

Tue, 04 Sep 2007 14:45:44 -0700

Ha Andreas,

Allright, so, I'm not the only one who bumps his head against the different models.

If i may add a suggestion to this nabble discussion.

A developer like me wants to add his own extra's, and hopefully the platform is flat enough to allow for extensions within a reasonable time.

In openlayers the behavior of the panning and zooming is not influenced by extra event definitions.

Let's say that i want to keep track of the pixel values (and the bounding box) (maybe the realworldcoordinate)
I may register some events that can collect these values
map.events.register('mousedown', map, function (e) {storepixelXY(e)})
map.events.register('click', map, function (e) {if(pixelXYremainthesame(e) {issueGetFeatureInfo()}})

The 'normal' behavior is not broken.

I should say that i like the customizability of this. And is almost exactly an example in the OL trunk. (examples/getfeatureinfo.html)

MODES (or activeStates) are good. They allways were. Every application has them. But google does not, not in it's main maps-product.
Any extra thing made in googlemaps gets it's own application. This is possible thru the API.
In mapbuilder you can configure that normal behavior in config.xml. In Openlayers you can't.Can't it? But I think there is still a need for a simple API that works close on the DOM and can extend to 'normal' behavior.


Regards, Huub

Andreas Hocevar wrote: 
Huub,

On 9/4/07, huub fleuren <[EMAIL PROTECTED]> wrote:
  
 For instance: if i'm trying to bring my mappane-with-panzoombar in a
getFeatureInfo-state (it has a button and buttonbar ; it's invisible but can
be selected in the 'old' way) by using

     <GetFeatureInfo id="breinaald">
       <scriptFile>scripts/GetFeatureInfo.js</scriptFile>
       <buttonBar>breinaaldButtonBar</buttonBar>
       <targetContext>mainMap</targetContext>
       <class>Button</class>
       <enabledSrc>/images/BreinaaldEnable.png</enabledSrc>

<disabledSrc>/images/BreinaaldDisnable.png</disabledSrc>
       <infoFormat>text/plain</infoFormat>
       <featureCount>1</featureCount>
     </GetFeatureInfo>

 config.objects.breinaald.select()
    

The problem is that PanZoomBar and Mapbuilder button controls are
currently not compatible. You can either use PanZoomBar, or Mapbuilder
button controls.

The plan for the final 1.5 release is to introduce "modes" in
Mapbuilder, eg. a viewing mode, an editing mode, and a select/query
mode. There has been a discussion about it on the devel list [1], but
obviously there were no ressources available yet to implement it. The
implementation is not trivial, because PanZoomBar in OpenLayers is a
control which is not designed to be turned on and off during
application runtime.

Contributions are as always welcome, and I will be glad to help with
design and implementation questions.

Also note that the whole GetFeatureInfo / WebServiceRequest chain will
be cleaned up before the final 1.5 release, which might also involve
using OpenLayers for the request.

Regards,
Andreas.

[1] http://www.nabble.com/design-question-wrt-mouse-button-handling-t4228931.html



  

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Mapbuilder-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mapbuilder-users

Reply via email to