Steven,
I think that you are on track by having a "mode" concept which is an
aggregation of tools.
A designer should easily be able to create a new mode and assign a new
set of tools to that mode.
Ie, in the EditMode, you attach:
scrollwheelZoom.js
dragPan.js
.left click -> addNode.js
.double click -> endLine.js
(or something similar)
My key point is that we should be able to attach multiple tools to a
Mode (or State if we talk about the State pattern)
And I agree that we should align ourselves with Pierre and the
Openlayers crowd.
Steven M. Ottens wrote:
> YO,
>
> I've been thinking some more;
>
> I believe that the PanZoomBar should be on always, at least if the
> user wants the panzoombar. So it's a configuration option of MapPaneOL.
> The panzoombar can work (and IMO should work) in both the drag mode
> and the editing mode. The things that change are the events coupled
> with mouse actions and keyboard events.
>
> So we end up with two difference approaches (:-();
>
> widgets for each action (classic way);
> -ZoomIn.js
> -ZoomOut.js
> -DragPan.js
> -GetFeatureInfo.js
> -EditLine.js
> -EditPolygon.js
> -EditPoint.js
> (although the last three might very well be much the same as the
> LineEditMode etc described below)
> Widgets for the type of interaction with configuration options what to
> include, since they influence the mouse and keyboard event handlers.
> As such a widget should modify those in OL. I'm thinking of something
> along the lines of:
> -DragMode
> .scrollwheel -> zoom
> .shift drag -> zoombox
> .left click -> getFeatureInfo
> .drag -> pan
> .double click -> zoom in
> -LineEditMode:
> .scrollwheel -> zoom
> .shift drag -> nothing (or actually select multiple
> nodes/lines but that's a different story)
> .drag -> pan
> .left click -> add Node
> .double click -> end line
> etc
>
> This means that we need to create widgets which can be configured to
> enable/disable control in the map. Pretty much like they ZoomIn for
> instance does now, with the only difference that it can en/disable
> multiple controls
>
> does this make sense?
>
> Steven
>
>
> On Aug 8, 2007, at 10:16 AM, Andreas Hocevar wrote:
>
>> Hi,
>>
>> On 8/7/07, Steven M. Ottens <[EMAIL PROTECTED]> wrote:
>>> This makes sense, do you have an idea how long it will be before the
>>> "editing mode" will be part of the OL-trunk and also in which sandbox
>>> it is currently hiding?
>>
>> Not sure, but here is some information about it:
>> http://trac.openlayers.org/wiki/Future/AdvancedEditing
>>
>>> The Measurement is a specific type of editing tool, as such it should
>>> use the new editing mdoe as well.
>>
>> If it is desired to change the measurement path while editing, yes.
>>
>> Regards,
>> Andreas.
>
>
>
--
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
