rhodges / oregon-marinemap

Automatically exported from code.google.com/p/oregon-marinemap
0 stars 0 forks source link

Support for optional geo-manipulators #58

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Oregon MarineMap users desire to be able to optionally clip their AOI's to one 
or more boundaries.  The options would either be no clipping at all, clip to 
the oregon shoreline and/or clip to the territorial sea.  Since AOI's could 
represent wave energy site proposals or any number of other things and these 
proposals might occur on land or outside the territorial sea, they should be 
able to define them there.  

Tim: I seem to remember the client, in one of the early manipulators 
implementations requesting the available manipulators and being able to specify 
which manipulators get applied to the drawn shape.

The UI implementation might for example be a set of checkboxes.  These might 
show up next to the 'draw shape' button or maybe a popup before or after the 
drawing.  Chad probably has some thoughts.

Original issue reported on code.google.com by tim.j.welch@gmail.com on 4 Oct 2010 at 8:48

GoogleCodeExporter commented 9 years ago
Well have to save this info on the model somehow so that if we need to reclip 
on the server we have the necessary info.  Also important for editing 
attributes without affecting the clipping.

I think manipulators should support this as is, except that there is no 
facility for the server to tell the client that the manipulator should be 
selected from a list. 

Original comment by underbluewaters on 5 Oct 2010 at 12:58

GoogleCodeExporter commented 9 years ago
A first cut at optional manipulators is in the "feature_optional_manipulators" 
branch.

Details are here:
http://code.google.com/p/marinemap/wiki/OptionalManipulators

Feedback welcome.

Original comment by perrygeo...@gmail.com on 7 Oct 2010 at 3:31

GoogleCodeExporter commented 9 years ago
as of changeset 6c83430f66c1, there is support for display names and 
descriptions (both optional) which will make for a nicer UI

157     class Options:
158         name = 'YourManipulatorClass'
159         display_name = 'Your Manipulator Class'
160         description = 'Check it out. This is my brand new manipulator.'

Original comment by perrygeo...@gmail.com on 11 Oct 2010 at 6:35

GoogleCodeExporter commented 9 years ago
The optional manipulator seems to be working fine with OMM.
Nice work Matt Perry!

Issue 50 now addresses the need for additional manipulators to be created.

Original comment by sfletche@gmail.com on 2 Nov 2010 at 6:30