<html>
<head>
</head>
<body style="margin-top: 4px; line-height: normal; margin-bottom: 1px; font-variant: normal; margin-right: 4px; margin-left: 4px">
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Benoit,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I'm old school in all this, so my ideas about a generic approach to things will likely seem old fashioned.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">My first stab at putting together a gesture based interface would be to use some sort of control overlay in the map area. This is mostly to provide instant feedback to the users more than anything.</font> </p>
<br> <br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Some important points (I think):</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">** Symbols for zooming in (+) and out (-) that are right on the map it self. This might actually be considered a failsafe mode, where all other modes don't work for a device, and would use essentially existing capabilities as far as user controls go in a mapping environment. Dragging seems to be a universal capability (so far), that can be implemented on (nearly) all devices.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">** Some sort of (fairly comprehensive) device type detection (or user setup control for a device type) will need to be in place.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">** With the building of a "failsafe" mode, and making it always available, the process of adding the gesture aspects seem to fall into the category of add-on. As an aside here, with the advent of Netbook / Tablet devices becoming more prevalent, there may be some room here to add in some key-macro navigation tools as well as an optional navigation toolset, but this is likely only interesting to myself. But if this type of approach of allowing for more than one type of navigation toolset were used, I think the different platform specifics can be more easily approached. Am I talking about a navigation conduit here? Something that is standardized in some form, that many different types of navigation tools could be developed against? There are certain work processes that might require direct access to a navigation tool in a very specific manner for example, that a framework like this might help with during the development.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">** Associated with the navigation are layer choosers of some sort. Displaying many layer option (or even many of anything) is a problem on a smaller form factor device. I think this is an associated and just as important aspect of the gesture controls (for mapping) as is the navigation. While most map based solutions may only present a few layers to the end user, I have systems in place that have hundreds of layers available, and it's very difficult to present this type of information to the typical user, let alone ones you might have the option of doing a little one on one training with.</font> </p>
<br> <br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I would prefer to use a common set of code to accomplish this all with some sort of auto-detection of device on the client side. The gestures themselves seem to be varied in their implementation across vendor products to one degree or another. Is there room here for some sort of user settings/preferences (like in a desktop application) where the user can decide (based on the device capabilities) what gestures can be enabled. There could be defaults for known devices.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br> <br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> Benoit Quartier <benoit.quartier@camptocamp.com> wrote:<br> </p>
<table border="0" bgcolor="#f3f3f3" style="margin-top: 0; margin-bottom: 0; font-size: 1em; margin-right: 0; margin-left: 15px">
<tr>
<td>
<div style="padding-left: 7px; border-left: solid 1px #050505">
<p style="margin-bottom: 0; margin-top: 0">
Bob,<br><br> </p>
<div class="gmail_quote">
<p style="margin-bottom: 0; margin-top: 0">
On Tue, Dec 21, 2010 at 5:40 PM, Bob Basques <span dir="ltr"><<a href="mailto:Bob.Basques@ci.stpaul.mn.us">Bob.Basques@ci.stpaul.mn.us</a>></span> wrote:<br> </p>
<blockquote class="gmail_quote" style="margin-top: 0pt; margin-bottom: 0pt; border-left: 1px solid rgb(204, 204, 204); margin-right: 0pt; margin-left: 0; padding-left: 0">
<div style="margin-top: 4px; line-height: normal; margin-bottom: 1px; font-variant: normal; margin-right: 4px; margin-left: 4px">
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Benoit,</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I couldn't get the zooming to work at all on the N900. But I don't count that as a fault.</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I understand the complexities here, especially with regard to the multi-touch aspects vs single touch enabled devices. I think that in the near term the gesture aspects are going to NEED to be targeted at vendor specifics in order to take full advantage of each of them. Hopefully this will flesh out to a standard from the best available, but, in the near term, I'm interested in seeing a process that works for single touch (Could be all phone/mobile devices??) as a foundational chunk of coding. Hopefully this approach would get as many functional mobile devices accounted for as possible. Then it makes sense to attack the vendor specific (extra) capabilities. It seems to be easier to design for the masses where possible (from my experience), and then to enhance for the specialties, don't you think?</font> </p>
</div>
</blockquote>
<div>
<p style="margin-bottom: 0; margin-top: 0">
Yes, I fully agree. That's why we didn't begin with Apple gestures. But as you wrote, in the near term, we will need to implement these vendor specifics gestures.<br><br>It would be great to have a set of single touch events that works on all (as much as possible) devices and, additionally, a set of vendor specific gesture. What would they be? Double tap to zoom in, triple tap to zoom out?<br> </p>
</div>
<div>
<br>
</div>
<blockquote class="gmail_quote" style="margin-top: 0pt; margin-bottom: 0pt; border-left: 1px solid rgb(204, 204, 204); margin-right: 0pt; margin-left: 0; padding-left: 0">
<div style="margin-top: 4px; line-height: normal; margin-bottom: 1px; font-variant: normal; margin-right: 4px; margin-left: 4px">
<br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I think there are options available for addressing these ideas, if anyone else is interested.</font> </p>
</div>
</blockquote>
<div>
<p style="margin-bottom: 0; margin-top: 0">
I am interested but I am not sure to understand what you mean? Could you please elaborate?<br><br><br>
</p>
</div>
</div>
</div>
</td>
</tr>
</table>
</body>
</html>