Sorry to be late to this conversation. Just closed the ticket for layer tools working. I will avoid the good conversation you all are having on services and such and simply state... <div><br></div><div>1. I like the suggesting to make a tab for layer tools. </div>
<div>2. When using a layer tool to add a sketch feature the tab would display the basic sketch attributes (if it is a feature in a database it could display those attributes) </div><div>3. This would be good because it would allow users to change sketch attributes when adding the feature up front. </div>
<div>4. It would also make the behavior similar to how measure works. </div><div><br></div><div>As usual this is probably not very clear but to get an idea. </div><div><br></div><div>1. Identify a feature </div><div>2. Select the measure line tool and measure a line </div>
<div>(both identify and measure remain at tabs) </div><div>3. Identify is still functioning and you can see those results if you toggle the identify tab on or can go back and continue to measure. </div><div><br></div><div>
<br></div><div><br></div><div>Hope this helps </div><div><br></div><div><br></div><div><div><br><div class="gmail_quote">On Tue, Dec 4, 2012 at 9:54 AM, Eli Adam <span dir="ltr"><<a href="mailto:eadam@co.lincoln.or.us" target="_blank">eadam@co.lincoln.or.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div class="im">On Tue, Dec 4, 2012 at 8:05 AM, Jim Klassen <span dir="ltr"><<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div>More oddly, how do you tell users which tabs are service tabs and which aren't?<br> </div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div><br></div><div>I would think correct behavior would be for the map to do what is selected in the toolbar.</div></div></blockquote></div><div><br>I agree with this. We may also have to differentiate between 'service' and service 'results' and switching between the two. Also how you are able to switch between the two. <br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF"><div><br></div><div>Identify</div><div>Draw</div><div>Switch to Identify tab</div>
<div><br>
</div><div>Should show the previous identify results but not update them on click since you are still in draw mode.</div></div></blockquote></div><div><br>Agree, they are 'results'. To active the identify 'service' again, click the identify button in the toolbar and now map clicks update the 'results'. <br>
<br>Some 'results' would perhaps have to be changed so the tab is not a 'service' too. For instance look at the identify results and then hit 'back to settings' and the choose 'Draw box' then continue on. Should that action deactivate your currently engaged tool and reactivated the identify tool? Or should the identify 'results' not let you click 'back to settings'?<br>
<br>We also have to keep active tool icons propagating through all this so that the user knows which tool is active. <br><br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div><div><br></div></div><div>I'm not saying this is (or isn't) the most useful behavior, just what I'd expect given the model of tools are the verbs.</div></div></blockquote></div><div>
<br>
Right, but we need some approach to differentiate what is what and this is the most specific approach articulated so far (and closely matches the existing behavior?). <br>
<br>Are there cases where we want to allow multiple tools at once? Like pan or scroll wheel during layer tools-->add polygon? What would be the impacts of that?<br><br></div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div><div><div></div><div>On Dec 4, 2012, at 9:25, Brent Fraser <<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>> wrote:<br></div><div></div>
<blockquote type="cite"><div>
<div>Dan,<br>
<br>
Can't GeoMoose just stop the Add Polygon operation if another
command is selected? </div></div></blockquote></div></div></div></blockquote></div><div><br>I also like the idea of cancelling half completed actions. <br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div><div><blockquote type="cite"><div><div> I don't like having to create a tool (or
tools?) for each editable layer. What am I missing?<br>
<pre cols="72">Best Regards,
Brent Fraser</pre>
On 12/4/2012 6:29 AM, Dan Little wrote:<br>
</div>
<blockquote type="cite">
<div style="font-size:10pt;font-family:arial,helvetica,sans-serif">
<div>
<div style="font-size:10pt">GeoMOOSE has a problem. It
tries to let users do a lot of things that, ultimately, will
cause them harm.</div>
<div style="font-size:10pt"><br>
</div>
<div style="background-color:transparent">The Scenario</div>
<div style="background-color:transparent">---------------------</div>
<div style="background-color:transparent">A user is going
along identifying things. Then they decide to add a <span style="color:rgb(54,99,136);border-bottom-width:2px;border-bottom-style:dotted;border-bottom-color:rgb(54,99,136)">Polygon</span> to
the map. Then they want to identify things again, so they
simply return to the identify tab.</div>
<div style="background-color:transparent"><br>
</div>
<div style="background-color:transparent">The application
fundamentally breaks here. It will try to draw polygons and
identify things at the same time. This isn't a problem if
the user were to, once again, click the "Identify" tool from
the toolbar.</div>
<div style="background-color:transparent"><br>
</div>
<div style="background-color:transparent"><br>
</div>
<div style="background-color:transparent">There are
variations on this tune but the underlaying question to it
all is, how should we be defining the users verb focus? And
how do we do it in a consistent predictable manner?</div></div></div></blockquote></div></blockquote></div></div></div></blockquote></div><div><br>Yes consistent predictable is important. <br> </div><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div><div><blockquote type="cite"><div><blockquote type="cite"><div style="font-size:10pt;font-family:arial,helvetica,sans-serif"><div>
<div style="background-color:transparent"><br>
</div>
<div style="background-color:transparent">Some thoughts:</div>
<div style="background-color:transparent">1. When switching
to any tool, any "service tabs" close. That means, the
users' ability to add a polygon would close the "identify"
tab. Removing the users ability to go after the tab. This
has the negative consequence of not being able to refer to
your results for as long or allow the results to interact
with other tools.</div></div></div></blockquote></div></blockquote></div></div></div></blockquote></div><div><br>Instead of closing tabs, what about making the tab no longer a 'service' but 'results' when this happens? Like Jim brought up above?<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF"><div><div><blockquote type="cite"><div><blockquote type="cite"><div style="font-size:10pt;font-family:arial,helvetica,sans-serif">
<div>
<div style="background-color:transparent"><br>
</div>
<div style="background-color:transparent"><font face="arial, helvetica, sans-serif">2. The root
of these problems seem connected with some lack of
consistency with drawing. The vector layers are
handled separately from the layers that are used as "temp
drawing layers" for the services. We could move the
drawing and editing tools into a "tab" so that instead of
doing things like "Add Polygon", the user would click a
button like "Edit Vector Layer" or "Add Sketches" and it
would open a service-like tab that would give all of the
layer editing options. The may mean creating a tool for
each vector layer the user wants to have editable.</font></div></div></div></blockquote></div></blockquote></div></div></div></blockquote></div><div>If we go the route where the user can reactivate a 'service' by clicking on the tab, then we would probably need a tab for everything. Perhaps in the case of vector layers, it would just be a tab with a button that says 'reactive vector tools'?<span class="HOEnZb"><font color="#888888"><br>
<br>Eli<br> </font></span></div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF"><div><div><blockquote type="cite"><div><blockquote type="cite">
<div style="font-size:10pt;font-family:arial,helvetica,sans-serif">
<div>
<div style="background-color:transparent"><font face="arial, helvetica, sans-serif"><br>
</font></div>
<div style="background-color:transparent"><font face="arial, helvetica, sans-serif">Anyone with
other thoughts? Solutions? Patches?</font></div>
<div><font face="arial, helvetica, sans-serif"><br>
</font></div>
<div><font face="arial, helvetica, sans-serif">PS:
I'm sorry if this shows up as a duplicate, I sent this
email yesterday afternoon and it didn't appear to show up
on the list.</font></div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Geomoose-users mailing list
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a>
</pre>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Geomoose-users mailing list</span><br><span><a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a></span><br>
<span><a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a></span><br></div></blockquote></div></div></div><br>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
<br></blockquote></div></div><br>
<br>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Dean R Anderson </div>
<div>IT Director </div>
<div>Polk County</div><br>
</div></div>