Agreed on both counts,<div><br></div><div>As someone that has worked extensively in the field with various Trimble, Leica, ArcPad interfaces and versions, along with some latest GIS apps for iPhone.</div><div><br></div><div>
If there is a Push to get QGIS ported to Mobile, it has the chance (in these early stages) to eclipse any of the offerings I have seen, used, or disposed of.</div><div><br></div><div>1. Developer or User - Decide whether QGIS Mobile will be built for developers or for end users. </div>
<div> Dev's can handle quirks with the following 3 and 4, Users can and will not.</div><div><br></div><div>2. Tablet And/Or Phone - Each platform has their strengths and weakness. Developing for Both demands very thoughtful User Interface, or flexibility to change to its new platform.</div>
<div><br></div><div>3. Stability - Stability is the hammer for the nail, without it, it can cause more harm than good.</div><div><br></div><div>4. Usability - Find one, two or even three things desired for QGIS Mobile and do it very very very well.</div>
<div><br></div><div>I would love to see a mobile version of a GIS app that could fill the void that exists today. Leica and Trimble make good data collection units that are both very expensive but very stable. ArcPad is dangerous in my opinion given it's horrendous stability issues. Some of the GIS apps for iPhone show promise but in their desire to add more features, some of their core features have suffered with bugs, and app crashes. Added Features are great when they work and do not pull down the original stable release, unless of course as a developer and tinkerer stability does not matter as much.</div>
<div><br></div><div>Love to hear how QGIS Mobile evolves!</div><div><br></div><div>Mars</div><div><br><br><div class="gmail_quote">On Thu, Jun 2, 2011 at 10:59 AM, Ivan Mincik <span dir="ltr"><<a href="mailto:ivan.mincik@gmail.com">ivan.mincik@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 class="im">On Thu, Jun 2, 2011 at 11:57 AM, Paolo Cavallini <<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>> wrote:<br>
> I found this reading inspiring and thought-provoking:<br>
> <a href="http://daringfireball.net/2011/06/windows_8_fundamentally_flawed" target="_blank">http://daringfireball.net/2011/06/windows_8_fundamentally_flawed</a><br>
> In short, it may not make much sense to have QGIS running on a mobile device, it<br>
> seems more appropriate to rethink at least the interface from scratch.<br>
> All the best.<br>
<br>
</div>That I was talking about in my earlier post, when mobile discussion<br>
started. It make a sense to port some good libraries, but GUI must be<br>
completely different.<br>
When starting any mobile project, one should ask a question, which<br>
kind of libraries is need. First, one should look for some more native<br>
libraries (Java in case of Android) and in case they are not suitable,<br>
think about porting some foreign libs.<br>
<br>
The question is, what kind of features we need in our mobile app ? Do<br>
we need something which does not exists for example in Nutiteq Map<br>
libs [1]?<br>
<br>
1 - <a href="https://github.com/rorist/maps-lib-nutiteq" target="_blank">https://github.com/rorist/maps-lib-nutiteq</a><br>
<font color="#888888"><br>
Ivan<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br></div>