Also add links to bottom of list to select how many nodes shall be
displayed, and store the selection in localStorage.
The shorter list has much better performance. A long list is not really
useful anyway; rather let the user filter/sort it to display interesting
nodes only.
- rename storePosition to gpsPosition
- don't check for btnGPS.innerHTML contents (this is fragile); check for
this.gpsPosition instead
- fix call to updatePosition() when clicking "Stop following"
- store.getNode() no longer adds new node to the list
- instead, store.createNode() can be used to create an empty new node
- view/node.js now now transfer a local copy of the node object it wants to
modify, rather then modifying the real object from store.list. If the
change is accepted by server, the server will send the new values for the
changed object anyway.
Previously, if the user visited the node page for a nonexistent node but
didn't make any changes, the list view would always throw an exception
because an incomplete node object was contained in the list.
Oliver Gerlich
Martin/Geno