begin cleaning up mesh library layer so that it could be split someday

src/mesh/NodeDB.h

@@ -0,0 +1,98 @@
+#pragma once
+
+#include <Arduino.h>
+#include <assert.h>
+
+#include "MeshTypes.h"
+#include "mesh-pb-constants.h"
+
+extern DeviceState devicestate;
+extern MyNodeInfo &myNodeInfo;
+extern RadioConfig &radioConfig;
+extern ChannelSettings &channelSettings;
+extern User &owner;
+
+/// Given a node, return how many seconds in the past (vs now) that we last heard from it
+uint32_t sinceLastSeen(const NodeInfo *n);
+
+class NodeDB
+{
+    // NodeNum provisionalNodeNum; // if we are trying to find a node num this is our current attempt
+
+    // A NodeInfo for every node we've seen
+    // Eventually use a smarter datastructure
+    // HashMap<NodeNum, NodeInfo> nodes;
+    // Note: these two references just point into our static array we serialize to/from disk
+    NodeInfo *nodes;
+    pb_size_t *numNodes;
+
+    int readPointer = 0;
+
+  public:
+    bool updateGUI = false;            // we think the gui should definitely be redrawn, screen will clear this once handled
+    NodeInfo *updateGUIforNode = NULL; // if currently showing this node, we think you should update the GUI
+    bool updateTextMessage = false;    // if true, the GUI should show a new text message
+
+    /// don't do mesh based algoritm for node id assignment (initially)
+    /// instead just store in flash - possibly even in the initial alpha release do this hack
+    NodeDB();
+
+    /// Called from service after app start, to do init which can only be done after OS load
+    void init();
+
+    /// write to flash
+    void saveToDisk();
+
+    // Reinit radio config if needed, because sometimes a buggy android app might send us bogus settings
+    void resetRadioConfig();
+
+    /// given a subpacket sniffed from the network, update our DB state
+    /// we updateGUI and updateGUIforNode if we think our this change is big enough for a redraw
+    void updateFrom(const MeshPacket &p);
+
+    /// @return our node number
+    NodeNum getNodeNum() { return myNodeInfo.my_node_num; }
+
+    size_t getNumNodes() { return *numNodes; }
+
+    /// if returns false, that means our node should send a DenyNodeNum response.  If true, we think the number is okay for use
+    // bool handleWantNodeNum(NodeNum n);
+
+    /* void handleDenyNodeNum(NodeNum FIXME read mesh proto docs, perhaps picking a random node num is not a great idea
+    and instead we should use a special 'im unconfigured node number' and include our desired node number in the wantnum message.
+    the unconfigured node num would only be used while initially joining the mesh so low odds of conflicting (especially if we
+    randomly select from a small number of nodenums which can be used temporarily for this operation).  figure out what the lower
+    level mesh sw does if it does conflict?  would it be better for people who are replying with denynode num to just broadcast
+    their denial?)
+    */
+
+    /// Called from bluetooth when the user wants to start reading the node DB from scratch.
+    void resetReadPointer() { readPointer = 0; }
+
+    /// Allow the bluetooth layer to read our next nodeinfo record, or NULL if done reading
+    const NodeInfo *readNextInfo();
+
+    /// pick a provisional nodenum we hope no one is using
+    void pickNewNodeNum();
+
+    /// Find a node in our DB, return null for missing
+    NodeInfo *getNode(NodeNum n);
+
+    NodeInfo *getNodeByIndex(size_t x)
+    {
+        assert(x < *numNodes);
+        return &nodes[x];
+    }
+
+    /// Return the number of nodes we've heard from recently (within the last 2 hrs?)
+    size_t getNumOnlineNodes();
+
+  private:
+    /// Find a node in our DB, create an empty NodeInfo if missing
+    NodeInfo *getOrCreateNode(NodeNum n);
+
+    /// read our db from flash
+    void loadFromDisk();
+};
+
+extern NodeDB nodeDB;