Created a menu action to run create a snapshot and exit anki

[evandrocoan]

It is taking some time to create my snapshot and it is not always desirable to create it when exiting/opening Anki.

[aplaice]

Thanks for this! It's a brilliant solution (or at least workaround) to the issue of snapshots taking a long time.

However, I'd prefer to be careful when adding extra menu items, since:

1. They "clutter up" the menu bar for all CrowdAnki users.

   CrowdAnki already takes up half of the space in the File menu.

2. They provide a suggestion of permanence to the given option. (Users might get used to having the menu action and even once we solve the issue of excruciatingly slow snapshots, they might be unhappy about it being removed.)

3. They might confuse new users. ("Import git repo", "Import from disk" and "Snapshot" are all pretty self-explanatory, but they might wonder why "Snapshot and exit" is needed.)

OTOH for users with a large collection, who snapshot, this new menu item might be a huge "quality of life" improvement.

---

From what I understand, you run the add-on from your own private fork, anyway, so not merging this PR immediately won't significantly inconvenience you.(?)

Hence, I'll wait for (hopefully) some feedback from more people and think about how best to get the upsides of this PR without the (slight) downsides, for a while, before merging.

---

Possible ideas:

1. A nested menu (might be useful in the long run, anyway).
2. Having (configurable) keyboard shortcuts (would definitely be useful, anyway).

[evandrocoan]

but they might wonder why "Snapshot and exit" is needed

I could change it to something like Snapshot and exit Anki (useful for big collections).

From what I understand, you run the add-on from your own private fork

Yes. I in my fork, I added all files to the top-level (evandroforks@e7e80c9) and directly added the PiPY dependencies into the fork code. This way, I can just clone the repository inside Anki addons directory, and the dependency will load directly from source-code.

I wonder how is the standard development workflow. Do you always build an Anki package and install it after changing the code? i.e., would the workflow be:

1. bash package_plugin.sh
2. unzip packagefile.zip -d ~/Anki/addons21/

If this would be the workflow, maybe add it README.md or some development file, as I usually run my Anki addons directly from source-code/git repository cloned directly to my addons directory.

[aplaice]

I could change it to something like Snapshot and exit Anki (useful for big collections).

That helps with 3 (explanation), but makes 1 worse (clutter), so I think the original wording is better.

---

I wonder how is the standard development workflow. Do you always build an Anki package and install it after changing the code? i.e., would the workflow be:

The standard development workflow is described in CONTRIBUTING.md:

1. If you have the production version of CrowdAnki installed - remove it from Anki.
2. Run fetch_dependencies.sh - this will download the dependencies required for CrowdAnki to
   operate and put them into the crowd_anki/dist directory.
3. Add a symlink to the Anki plugins directory (you can find it via Tools>Add-ons>View Files)
   pointing to crowd_anki directory (you should not name the symlink crowd_anki though, see
   #62).

i.e. very close to your current workflow. (The difference is having a symlink vs. having the code directly in the relevant directory, but it's a cosmetic one.)

[aplaice]

In the interest of "perfect" not getting in the way of "better", I'm merging this now. Thanks again for contributing it and not just keeping it in your private fork!

---

I might eventually move this behind an option (i.e. displayed only if a given option is turned on) or into a submenu (e.g. File > CrowdAnki (Advanced) > ...). I'll let you know before I do so.