<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<b>Updates:</b><br>
<ul>
<li><font face="Helvetica, Arial, sans-serif">documented how to
change the first pag<font face="Helvetica, Arial, sans-serif">e:
</font></font><a class="moz-txt-link-freetext" href="http://nodeshot.readthedocs.org/en/latest/topics/ui.html#change-the-first-page">http://nodeshot.readthedocs.org/en/latest/topics/ui.html#change-the-first-page</a><br>
<br>
</li>
<li>closed #203: <a class="moz-txt-link-freetext" href="https://github.com/ninuxorg/nodeshot/issues/203">https://github.com/ninuxorg/nodeshot/issues/203</a></li>
</ul>
<p><b>Other improvements you should notice:</b><br>
</p>
<p>You can take a look at the automatically updated instances:<br>
</p>
<ul>
<li><a class="moz-txt-link-freetext" href="https://ninux.nodeshot.org/">https://ninux.nodeshot.org/</a> (might be a bit slower because
it's hosted inside our network in Rome and the uplink is not as
fast as the following link, plus the virtualizer is often under
high load)<br>
<br>
</li>
<li><a class="moz-txt-link-freetext" href="https://votaspot.publicwifi.it">https://votaspot.publicwifi.it</a> (this is surely faster but the
data is not from ninux)</li>
</ul>
<p>What you should notice:<br>
</p>
<ul>
<li>the first page should load much faster<br>
<br>
</li>
<li>all the data fetched from the server is cached in memory for
subsequent requests, (JS only, no persistence on page reloads
yet, but will come), so if you go back and forth between pages
you already loaded previously, the change should be
instantaneous<br>
<br>
</li>
<li>map and satellite tiles available by default<br>
<br>
</li>
<li>leaving the mouse on a map object should show a little tooltip
to hint the name of the node<br>
<br>
</li>
<li>switching between map view and node details and back to map
view is very smooth<br>
<br>
</li>
<li>you can now search an address from the top bar, you should
recognize the difference between an address and a node by the
icon; the geocoding is triggered only if the query contains some
special strings which are listed here:
<a class="moz-txt-link-freetext" href="http://nodeshot.readthedocs.org/en/latest/topics/ui.html#nodeshot-ui-address-search-triggers">http://nodeshot.readthedocs.org/en/latest/topics/ui.html#nodeshot-ui-address-search-triggers</a></li>
</ul>
<p><b>Question on </b><b>NODESHOT_UI_ADDRESS_SEARCH_TRIGGERS:<br>
</b></p>
<p>These are the default special triggers (which can be changed on
settings.py):<br>
</p>
<ul>
<li>','</li>
<li>'st.'<br>
</li>
<li>' street'<br>
</li>
<li>' square'<br>
</li>
<li>' road'<br>
</li>
<li>'via '<br>
</li>
<li>'viale '<br>
</li>
<li>'piazza '<br>
</li>
<li>'strada '<br>
</li>
<li>'plaza'<br>
</li>
<li>'calle '</li>
</ul>
<p>Note the space in some words, like ' street' has a space at the
beginning which should avoid triggering the geocoding request if
you are loading for a node named "streetnode".<br>
</p>
<p>Do you think any word is missing? Or anything that could improve?
I encourage you to try this feature and let me know. I think it's
a good usability improvement as many people were getting confused
when they did not find an address by searching on the top bar.<br>
</p>
<p><b>Next step:<br>
</b></p>
<p>I really want to get this done ASAP:
<a class="moz-txt-link-freetext" href="https://github.com/ninuxorg/nodeshot/issues/200">https://github.com/ninuxorg/nodeshot/issues/200</a><br>
</p>
<p>After that's done, and some form of reusable UI generator is
implemented, I'll generate all the main missing features of the UI
as fast as I can, then I'll finally work on links, devices,
interfaces and collection of metrics (statistics).<br>
</p>
<p>Federico<br>
</p>
</body>
</html>