<html>
<head>
</head>
<body style="font-variant: normal; line-height: normal; margin-left: 4px; margin-right: 4px; margin-bottom: 1px; margin-top: 4px">
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">All,</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Suggestions . . . (i'm interested in implementing any and all of these scenarios BTW . . .)</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<b><font size="3" face="Comic Sans MS">NAVIGATION:</font></b><font size="3" face="Comic Sans MS"></font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<b><u><font size="3" face="Comic Sans MS">Multi-touch operation:</font></u></b><font size="3" face="Comic Sans MS"></font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** Pinching in/out = Zoom in/out </font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS"> Seems to be the easiest to relate to a user. Although it's not obvious to everyone (yet) this this type of functionality is/should be in every touch mapping interface.</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** Touch drag = drag the map</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<b><u><font size="3" face="Comic Sans MS">DEFAULT operation (Single touch/tap mode):</font></u></b> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I'm going to suggest a push to get a single touch interface as far as possible before addressing the multi-touch side. Reason being that the results would be useful on everything. Should this be considered the DEFAULT (failover) design, when nothing else works?</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** Touch drag = drags the map</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** Tap "+" symbol = Zoom in</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** Tap "-" symbol = Zoom out</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** ALTERNATE Zoom in/out - Could use a slider bar along an edge for in/out zooming, could use the same function(s) for map dragging to zoom with, would make code smaller.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<b><u><font size="3" face="Comic Sans MS">Auto-track operation:</font></u></b><font size="3" face="Comic Sans MS"></font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** GPS (or tracking point) data stream reading. = Centers the map on current location</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** Should be configurable for use with either the Multi-touch and/or DEFAULT operation modes for zooming above.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">NOTES:</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">** I would personally like to be able to turn on / off any of the tools in the interface above both as a developer, and as an end user, and have all of these controls available all of the time if feasible, possibly via some user settings, either at the session level and/or via some sort of server side storage mechanism, maybe all that's needed is a standard for storing the data, and let the developers decide where the settings come from.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I've got more ideas, but I'll sit quiet for a while.</font> </p>
<br> <br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
>>> Benoit Quartier <benoit.quartier@camptocamp.com> wrote:<br> </p>
<table style="margin-left: 15px; margin-right: 0; margin-bottom: 0; margin-top: 0; font-size: 1em" bgcolor="#f3f3f3" border="0">
<tr>
<td>
<div style="padding-left: 7px; border-left: solid 1px #050505">
<p style="margin-top: 0; margin-bottom: 0">
Hi All,<br><br>At Camptocamp, we talked a lot, internally and with our customers, about what would be expected from a mobile version of OpenLayers.<br>Let me share our thoughts and feel free to comment. and discuss them:<br><br>- Pan performance enhancement<br>In mobile devices, resources (network bandwidth, CPU, memory) are very limited and pan performances is an important part of the user experience.<br><br>- Touch Screen Interface<br>Most mobile devices are touch enabled. There are different levels of touche support, which are mostly vendor dependant.<br>Depending on the device OS/browser capabilities, different level of touch support could be provided.<br>1. Monotouch (these should work on all touch enable devices):<br>1. Pan by sliding the finger on the screen<br>2. Zoom In by double taping<br>3. Zoom Out ?by triple taping? (triple taping seems bad, but what else?)<br>2. Multitouch Simple<br>1. Zoom In by taping with two fingers<br>2. Zoom Out by double clicking with two fingers<br>3. Multitouch Gesture<br>1. Pinch to zoom out and zoom in<br><br>(In most of the current Android phones, multitouch is not supported in the browser)<br><br><br>- Use of Mobile Device Hardware<br>Access to the mobile device hardware is described by some w3c proposal specifications.<br><br>1. Localisation API: access the device position. (giving a way to easyliy update it while the user is moving would be interesting)<br>2. Orientation API: keep the north up (ref: Proposal for orientation API (from magnetometer): <a href="http://dev.w3.org/geo/api/spec-source-orientation.html">http://dev.w3.org/geo/api/spec-source-orientation.html</a> )<br><br><br>- Use of HTML5 offline storage capabilities<br><br>1. Local storage of part of the map for offline use<br>(2. Offline edition of features for later synchronisation (dependant on the above point)<br><br><br>Camptocamp already did work on the pan performance enhancement, touch navigation and basic use of the localisation API.<br>Our work is published on the osgeo trac: <a href="http://trac.osgeo.org/openlayers/ticket/3000">http://trac.osgeo.org/openlayers/ticket/3000</a>; it can hopefully serve as a basis for further development.<br>@Jennie Fletcher: do you plan to publish your work on offline mode?<br>I also read on the list that someone did implement “gesture zoom” on Apple devices; is there any plan to make this work public?<br><br>Benoît<br><br> </p>
<div class="gmail_quote">
<p style="margin-top: 0; margin-bottom: 0">
2011/2/8 Cédric MOULLET <span dir="ltr"><<a href="mailto:cedric.moullet@gmail.com">cedric.moullet@gmail.com</a>></span><br> </p>
<blockquote style="margin-left: 0; margin-right: 0pt; margin-bottom: 0pt; margin-top: 0pt; padding-left: 0; border-left: 1px solid rgb(204, 204, 204)" class="gmail_quote">
<p style="margin-top: 0; margin-bottom: 0">
Hi,<br>I forward an email that Jennie Fletcher, who will attend the mobile code sprint, tried to send to this list.<br>Cédric<br><br><i>As this is my first mail I should probably introduce myself, I'm Jennie and I'm a Software Engineer for Edina and have been making use of OpenLayers for many years, along with MapFish, ExtJS etc.<br style="font-style: italic"><br style="font-style: italic">Recently I have been working on a mobile mapping application, adapting the HTML5 local browser caching in the TouchMapLite Framework (using PanoJS for animation) and was wondering if this functionality might be useful for OpenLayers.<br style="font-style: italic"><br style="font-style: italic">The ability to be able to access mapping offline is really important for some of the use cases we support, for example school field trips in areas where 3G connectivity is poor. Given the cost and unreliability of mobile networks I think offline access is a compelling feature to include. It also increases the kinds of device that the application can run on, for example, wifi devices such as iPod and non 3G iPad models.<br style="font-style: italic"><br style="font-style: italic">I have implemented examples using Web SQL Database (<a href="http://dev.w3.org/html5/webdatabase/" target="_blank">http://dev.w3.org/html5/webdatabase/</a>) and Web Storage (<a href="http://dev.w3.org/html5/webstorage/" target="_blank">http://dev.w3.org/html5/webstorage/</a>). There are advantages and disadvantages to both these. My overall impression was that the Web SQL Database provided more flexibility and greater functionality and better mobile browser support (but is unsupported in ie and ff for example), while Web Storage was more restrictive but had better support in non-mobile browsers.<br style="font-style: italic"><br style="font-style: italic">For mobile application development we have decided to go with Web SQL Database, however the spec for this is no longer being maintained and it looks likely that the IndexedDB standard will take it's place in future versions, however there isn't currently any support for this in current browsers.<br style="font-style: italic"><br style="font-style: italic">I'll be coming to the code sprint in Lausanne and I'm keen to discuss where I might be able to help.<br style="font-style: italic"><font color="#888888"><br style="color: #888888; font-style: italic">Jennie <span>Fletcher</span>.<br style="color: #888888; font-style: italic"></font></i><br><br> </p>
<div class="gmail_quote">
<p style="margin-top: 0; margin-bottom: 0">
2011/2/3 Cédric MOULLET <span dir="ltr"><<a href="mailto:cedric.moullet@gmail.com" target="_blank">cedric.moullet@gmail.com</a>></span> </p>
<div>
<div>
<br>
</div>
<div class="h5">
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
<blockquote style="margin-left: 0; margin-right: 0pt; margin-bottom: 0pt; margin-top: 0pt; padding-left: 0; border-left: 1px solid rgb(204, 204, 204)" class="gmail_quote">
<p style="margin-top: 0; margin-bottom: 0">
Hi,<br>I collected the requirements of various swiss OpenLayers users and I created a "wish" feature list here: <a href="http://trac.osgeo.org/openlayers/wiki/mobile" target="_blank">http://trac.osgeo.org/openlayers/wiki/mobile</a>.<br>Some aspects are directly related to OpenLayers and other are related more to UI components. So, this will be probably necessary to also discuss the usage of mobile UI libraries like Sencha Touch or JQuery Mobile.<br>All these points have not the same priority and I consider as mandatory the points Map Navigation, Map Layers, Geolocate, Layer Selector, Multilingual and Multiple coordinate system.<br>Swisstopo will deliver before the code sprint a mockup describing the future mobile version of <a href="http://map.geo.admin.ch/" target="_blank">http://map.geo.admin.ch/</a> in order to give an idea of what we would like to reach.<br>I'm happy to discuss these points and don't hesitate other points or your point of view.<br>Best regards.<br>Cédric </p>
<div>
<div>
<br>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
<br>
</p>
<div class="gmail_quote">
<p style="margin-top: 0; margin-bottom: 0">
On Thu, Jan 27, 2011 at 7:45 PM, Bob Basques <span dir="ltr"><<a href="mailto:Bob.Basques@ci.stpaul.mn.us" target="_blank">Bob.Basques@ci.stpaul.mn.us</a>></span> wrote:<br> </p>
<blockquote style="margin-left: 0; margin-right: 0pt; margin-bottom: 0pt; margin-top: 0pt; padding-left: 0; border-left: 1px solid rgb(204, 204, 204)" class="gmail_quote">
<div style="font-variant: normal; line-height: normal; font-family: Comic Sans MS; margin-left: 4px; margin-right: 4px; margin-bottom: 1px; font-weight: normal; margin-top: 4px; font-style: normal; font-size: 12pt">
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">All,</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I'm sure there are folks already thinking like this, but I just wanted to make sure that HTML5 and CSS3 are looked at hard for making things that will be compatible. There are some interesting capabilities there already. Lot's of new and potentially very interesting products to come out of all this.</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<div>
<div>
<br>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
>>> Tim Schaub <<a href="mailto:tschaub@opengeo.org" target="_blank">tschaub@opengeo.org</a>> wrote:<br> </p>
<table style="margin-left: 15px; margin-right: 0pt; margin-bottom: 0pt; margin-top: 0pt; font-size: 1em" bgcolor="#f3f3f3" border="0">
<tr>
<td>
<div style="padding-left: 7px; border-left: 1px solid rgb(5, 5, 5)">
<p style="margin-top: 0; margin-bottom: 0">
Hi<br><br>As you may already know a code sprint on mobile development will take<br>place in Lausanne Switzerland from feb 21 to feb 25 [1].<br><br>Lots of people have shown interest in mobile support in OpenLayers, and<br>interesting discussions already occurred on the mailing lists [2].<br><br>This email aims to encourage further discussions on the topic, to get<br>ideas and directions for the code sprint. Everyone is invited to create<br>and participate in discussions. This is a rather new topic so any idea,<br>experience to share, or code to show, can benefit the code sprint and<br>the OpenLayers project.<br><br>Tickets and patches have recently been created [3]. These patches maybe<br>a starting point for the sprint, so now is probably a good time to<br>provide comments and feedback on them.<br><br>A page has been created on the OpenLayers wiki [4]. This is where we'll<br>be collecting information regarding the sprint content. Feel free to<br>edit it, and add information you deem useful.<br><br>We're looking forward to discussions.<br><br>Thanks.<br><br>[1] <<a href="http://wiki.osgeo.org/wiki/Lausanne_Code_Sprint_2011" target="_blank">http://wiki.osgeo.org/wiki/Lausanne_Code_Sprint_2011</a>><br>[2]<br><<a href="http://www.mail-archive.com/openlayers-dev@lists.osgeo.org/msg00494.html" target="_blank">http://www.mail-archive.com/openlayers-dev@lists.osgeo.org/msg00494.html</a>><br>[3] <<a href="http://trac.osgeo.org/openlayers/ticket/3000" target="_blank">http://trac.osgeo.org/openlayers/ticket/3000</a>><br>[4] <<a href="http://trac.osgeo.org/openlayers/wiki/mobile" target="_blank">http://trac.osgeo.org/openlayers/wiki/mobile</a>><br><br>--<br>Tim Schaub<br>OpenGeo - <a href="http://opengeo.org" target="_blank">http://opengeo.org</a><br>Expert service straight from the developers.<br>_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@lists.osgeo.org" target="_blank">Dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br> </p>
</div>
</td>
</tr>
</table>
</div>
</div>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@lists.osgeo.org" target="_blank">Dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br><br> </p>
</blockquote>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br clear="all">
<br>
</p>
</div>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<font color="#888888">--<br style="color: #888888"></font> </p>
<div>
<p style="margin-top: 0; margin-bottom: 0">
Political blog: <a href="http://cedricmoullet.blogspot.com/" target="_blank">http://cedricmoullet.blogspot.com/</a><br>Welcome to my world: <a href="http://www.cedricmoullet.com/" target="_blank">http://www.cedricmoullet.com/</a><br>My Linked In profile: <a href="http://www.linkedin.com/in/cedricmoullet" target="_blank">http://www.linkedin.com/in/cedricmoullet</a><br>Twitter: <a href="http://twitter.com/cedricmoullet" target="_blank">http://twitter.com/cedricmoullet</a> </p>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
Home sweet home: <a href="http://map.geo.admin.ch/?crosshair=bowl&zoom=11&X=185241.24219&Y=561288.90625&bgOpacity=0&selectedNode=node_ch.swisstopo.fixpunkte-lage1" target="_blank">http://map.geo.admin.ch/?crosshair=bowl&zoom=11&X=185241.24219&Y=561288.90625&bgOpacity=0&selectedNode=node_ch.swisstopo.fixpunkte-lage1</a> </p>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
</blockquote>
</div>
</div>
</div>
<div>
<div>
<br>
</div>
<div class="h5">
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br clear="all">
<br>
--<br> </p>
<div>
<p style="margin-top: 0; margin-bottom: 0">
Political blog: <a href="http://cedricmoullet.blogspot.com/" target="_blank">http://cedricmoullet.blogspot.com/</a><br>Welcome to my world: <a href="http://www.cedricmoullet.com/" target="_blank">http://www.cedricmoullet.com/</a><br>My Linked In profile: <a href="http://www.linkedin.com/in/cedricmoullet" target="_blank">http://www.linkedin.com/in/cedricmoullet</a><br>Twitter: <a href="http://twitter.com/cedricmoullet" target="_blank">http://twitter.com/cedricmoullet</a> </p>
</div>
<div>
<p style="margin-top: 0; margin-bottom: 0">
Home sweet home: <a href="http://map.geo.admin.ch/?crosshair=bowl&zoom=11&X=185241.24219&Y=561288.90625&bgOpacity=0&selectedNode=node_ch.swisstopo.fixpunkte-lage1" target="_blank">http://map.geo.admin.ch/?crosshair=bowl&zoom=11&X=185241.24219&Y=561288.90625&bgOpacity=0&selectedNode=node_ch.swisstopo.fixpunkte-lage1</a> </p>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
</p>
</div>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br><br> </p>
</blockquote>
</div>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br clear="all">
<br>
--<br>Benoît Quartier<br><br>Camptocamp SA<br>PSE-A, Parc Scientifique EPFL<br>CH-1015 Lausanne<br><br>Tel: +41 21 619 10 40<br>Fax: +41 21 619 10 00<br><br>
</p>
</div>
</td>
</tr>
</table>
</body>
</html>