Sounding fairly good. For the Query with the left click, I'm wondering whether we should be making this configurable. Ie, There are lots of different ways to set up a query: 1. WMS Query 2. WFS Query 3. Query the top layer 4. Query the top layer that is selected 5. Query all layers 6. Return one feature 7. Return many features ...
Which makes me think that there should be a Query controller which can be attached to your PanZoomButton. (I use the word "controller" in the classic MVC sense. Ie, code that just controls an action and doesn't contain an associated button). I realise I'm talking about extra work here, and possibly a restructuring of how we handle our tools, so you are welcome to take or leave these thoughts as you see fit. Steven M. Ottens wrote: > I've been looking to the google interface. I noticed that they use the > right mouse button for custom menus. But I think you are right that > there's no need (yet) for a right mouse click. Also I believe > OpenLayers should handle the right click/left click, not mapbuilder. > > Andreas has a good point that currently the left click is available > for getFeatureInfo. So the new setup will be: > PanZoomButton: > - left click: getFeatureInfo (WMS) > - left drag: pan > - left double click: zoom > - shift left drag: zoombox > - scroll: zoom > MeasurementButton: > - left click: new point (first click erases previous measurement line) > - left drag: pan > - left drag on line-node: drag the node (I don't think there are > nodes yet though) > - left double click: end line (go back to panzoom mode) > - shift left drag: zoombox > - scroll wheel: zoom > > For point/line/polygon editing tools it would become slightly more > complex, there you might want to introduce the right click menu as > google does. > > Since this is rather complex, I'm going to develop this in a sandbox > so it won't stop the release. > > Steven > > > On Aug 7, 2007, at 11:28 AM, Cameron Shorter wrote: > >> It sounds like you might be running the risk of making an application >> which has lots of gee-wiz features, but is too fancy to be useful for >> the average punter. >> >> I suspect that it would be worth introducing a buttonBar and using >> the "State Pattern" to determine how a mouse click is processed, >> depending on what StateButton is selected. >> >> Ie, if the "PointEditing" button is selected on the button bar, then >> Left clicks are processed as adding a Point, Click Drags are >> processed as Pan, ... (or whatever). >> >> Note that we have associated One button with one tool. Eg: Pan button >> triggers Pan Tool. But you could have Editing Button sets up Pan Tool >> for click/drag, EditingPoint Tool click, etc. >> >> For default uses of buttons, I suggest you look at the Google Maps >> interface, as this will become the defacto UI that most users will be >> familiar with. >> >> Steven M. Ottens wrote: >>> Hi all, >>> >>> I'm working on an application which uses MapPaneOL and has the >>> following functionality: >>> double click: zoom >>> (left) drag: pan >>> scrollwheel: zoom >>> shift-drag: zoombox >>> right click: getfeatureinfo >>> >>> But I also want to add measurement and possibly editing tools. This >>> means that I've basically run out of mouse buttons ;) >>> What I need is this: >>> (left) drag: drag >>> left click: new point >>> double click: end line (and back to panzoom mode) >>> scroll: zoom >>> And possibly: right click on line/nodes a menu with more functionality >>> >>> Right now we have the following buttons: >>> - ZoomIn >>> - ZoomOut >>> - GetFeatureInfo >>> - DragPan >>> - Measurement >>> And the widget: >>> - PanZoomBar >>> >>> To be able to do what I want I need to adapt: >>> - GetFeatureInfo to support right click >>> - Measurement to support drag and scroll >>> - PanZoomBar to become a button >>> >>> So my questions is: >>> Should I create three new widgets to do what I want, or is it >>> better to modify the existing widgets in a way that makes it >>> configurable to do either the normal way or my way? Are other >>> people interested in this behavior? >>> >>> Steven >>> >>> >>> ------------------------------------------------------------------------- >>> >>> 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-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel >>> >>> >> >> >> --Cameron Shorter >> Systems Architect, http://lisasoft.com.au >> Tel: +61 (0)2 8570 5050 >> Mob: +61 (0)419 142 254 >> > > > -- Cameron Shorter Systems Architect, http://lisasoft.com.au Tel: +61 (0)2 8570 5050 Mob: +61 (0)419 142 254 ------------------------------------------------------------------------- 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
