split notedeck into crates

This splits notedeck into crates, separating the browser chrome and
individual apps:

* notedeck: binary file, browser chrome
* notedeck_columns: our columns app
* enostr: same as before

We still need to do more work to cleanly separate the chrome apis
from the app apis. Soon I will create notedeck-notebook to see what
makes sense to be shared between the apps.

Some obvious ones that come to mind:

1. ImageCache

We will likely want to move this to the notedeck crate, as most apps
will want some kind of image cache. In web browsers, web pages do not
need to worry about this, so we will likely have to do something similar

2. Ndb

Since NdbRef is threadsafe and Ndb is an Arc<NdbRef>, it can be safely
copied to each app. This will simplify things. In the future we might
want to create an abstraction over this? Maybe each app shouldn't have
access to the same database... we assume the data in DBs are all public
anyways, but if we have unwrapped giftwraps that could be a problem.

3. RelayPool / Subscription Manager

The browser should probably maintain these. Then apps can use ken's
high level subscription manager api and not have to worry about
connection pool details

4. Accounts

Accounts and key management should be handled by the chrome. Apps should
only have a simple signer interface.

That's all for now, just something to think about!

Signed-off-by: William Casarin <jb55@jb55.com>

crates/notedeck_columns/src/actionbar.rs

@@ -0,0 +1,163 @@
+use crate::{
+    column::Columns,
+    muted::MuteFun,
+    note::NoteRef,
+    notecache::NoteCache,
+    notes_holder::{NotesHolder, NotesHolderStorage},
+    profile::Profile,
+    route::{Route, Router},
+    thread::Thread,
+};
+use enostr::{NoteId, Pubkey, RelayPool};
+use nostrdb::{Ndb, Transaction};
+
+#[derive(Debug, Eq, PartialEq, Copy, Clone)]
+pub enum NoteAction {
+    Reply(NoteId),
+    Quote(NoteId),
+    OpenThread(NoteId),
+    OpenProfile(Pubkey),
+}
+
+pub struct NewNotes {
+    pub id: [u8; 32],
+    pub notes: Vec<NoteRef>,
+}
+
+pub enum NotesHolderResult {
+    NewNotes(NewNotes),
+}
+
+/// open_thread is called when a note is selected and we need to navigate
+/// to a thread It is responsible for managing the subscription and
+/// making sure the thread is up to date. In a sense, it's a model for
+/// the thread view. We don't have a concept of model/view/controller etc
+/// in egui, but this is the closest thing to that.
+#[allow(clippy::too_many_arguments)]
+fn open_thread(
+    ndb: &Ndb,
+    txn: &Transaction,
+    router: &mut Router<Route>,
+    note_cache: &mut NoteCache,
+    pool: &mut RelayPool,
+    threads: &mut NotesHolderStorage<Thread>,
+    selected_note: &[u8; 32],
+    is_muted: &MuteFun,
+) -> Option<NotesHolderResult> {
+    router.route_to(Route::thread(NoteId::new(selected_note.to_owned())));
+
+    let root_id = crate::note::root_note_id_from_selected_id(ndb, note_cache, txn, selected_note);
+    Thread::open(ndb, note_cache, txn, pool, threads, root_id, is_muted)
+}
+
+impl NoteAction {
+    #[allow(clippy::too_many_arguments)]
+    pub fn execute(
+        self,
+        ndb: &Ndb,
+        router: &mut Router<Route>,
+        threads: &mut NotesHolderStorage<Thread>,
+        profiles: &mut NotesHolderStorage<Profile>,
+        note_cache: &mut NoteCache,
+        pool: &mut RelayPool,
+        txn: &Transaction,
+        is_muted: &MuteFun,
+    ) -> Option<NotesHolderResult> {
+        match self {
+            NoteAction::Reply(note_id) => {
+                router.route_to(Route::reply(note_id));
+                None
+            }
+
+            NoteAction::OpenThread(note_id) => open_thread(
+                ndb,
+                txn,
+                router,
+                note_cache,
+                pool,
+                threads,
+                note_id.bytes(),
+                is_muted,
+            ),
+
+            NoteAction::OpenProfile(pubkey) => {
+                router.route_to(Route::profile(pubkey));
+                Profile::open(
+                    ndb,
+                    note_cache,
+                    txn,
+                    pool,
+                    profiles,
+                    pubkey.bytes(),
+                    is_muted,
+                )
+            }
+
+            NoteAction::Quote(note_id) => {
+                router.route_to(Route::quote(note_id));
+                None
+            }
+        }
+    }
+
+    /// Execute the NoteAction and process the NotesHolderResult
+    #[allow(clippy::too_many_arguments)]
+    pub fn execute_and_process_result(
+        self,
+        ndb: &Ndb,
+        columns: &mut Columns,
+        col: usize,
+        threads: &mut NotesHolderStorage<Thread>,
+        profiles: &mut NotesHolderStorage<Profile>,
+        note_cache: &mut NoteCache,
+        pool: &mut RelayPool,
+        txn: &Transaction,
+        is_muted: &MuteFun,
+    ) {
+        let router = columns.column_mut(col).router_mut();
+        if let Some(br) = self.execute(
+            ndb, router, threads, profiles, note_cache, pool, txn, is_muted,
+        ) {
+            br.process(ndb, note_cache, txn, threads, is_muted);
+        }
+    }
+}
+
+impl NotesHolderResult {
+    pub fn new_notes(notes: Vec<NoteRef>, id: [u8; 32]) -> Self {
+        NotesHolderResult::NewNotes(NewNotes::new(notes, id))
+    }
+
+    pub fn process<N: NotesHolder>(
+        &self,
+        ndb: &Ndb,
+        note_cache: &mut NoteCache,
+        txn: &Transaction,
+        storage: &mut NotesHolderStorage<N>,
+        is_muted: &MuteFun,
+    ) {
+        match self {
+            // update the thread for next render if we have new notes
+            NotesHolderResult::NewNotes(new_notes) => {
+                let holder = storage
+                    .notes_holder_mutated(ndb, note_cache, txn, &new_notes.id, is_muted)
+                    .get_ptr();
+                new_notes.process(holder);
+            }
+        }
+    }
+}
+
+impl NewNotes {
+    pub fn new(notes: Vec<NoteRef>, id: [u8; 32]) -> Self {
+        NewNotes { notes, id }
+    }
+
+    /// Simple helper for processing a NewThreadNotes result. It simply
+    /// inserts/merges the notes into the thread cache
+    pub fn process<N: NotesHolder>(&self, thread: &mut N) {
+        // threads are chronological, ie reversed from reverse-chronological, the default.
+        let reversed = true;
+        thread.get_view().insert(&self.notes, reversed);
+    }
+}