This repo contains the source code for the computer version of Anki.
If you'd like to try development builds of Anki but don't feel comfortable building the code, please see https://betas.ankiweb.net/#/
For more information on building, please see Development.
Our package maintainer decided to drop anki (having been stuck at 2.1.35 for months) from the official Arch Linux repos to the AUR, with the reasoning:
Dropping since they completely redid the build system yet again, but this time replaced it with bazel, which appears to be a rather unreasonable build system that no other TU seemed to understand either.
If you look at the anki packages in different distros, the majority are badly out of date.
The only exception is FreeBSD games/anki, whose maintainer is particularly tenacious; but if you look at the build files, and the packager's comments, it appears awfully tedious.
Edit: In the case of NixOS, they provide two versions of the package: the default build-from-source one stuck at 2.1.15 and anki-bin at 2.1.47 (= no building & uses official binaries & larger installation size).
So, is Anki too hard to build? Are packagers held back because of it?
This is pretty much untested. My plan is to do the apkg import part next, then add extensive roundtrip tests and fix it up. What do you think so far? Should I do anything differently?
This is a continuation of #1704.
Re https://github.com/ankitects/anki/pull/1989#issuecomment-1200142622: I followed your idea of lumping everything together in _vars.scss - the $vars map contains CSS properties and color themes - but it will still generate two separate output files (props.py and colors.py).
The gray tones I hand-picked myself:
gray: (
0: #fcfdfe,
1: #f2f5f8,
2: #dde1e7,
3: #aeb5be,
4: #7a818a,
5: #4a5058,
6: #2d3138,
7: #181b1f,
8: #101215,
9: #0b0c0e,
),
They reach much further into the dark end of the spectrum. The window background is tone 7 in dark mode, so we can have darker borders and shadows.
The other colors are from the Tailwind CSS v3 palette. There are some extra colors included that aren't currently in use.
As I've mentioned in the other PR, I'm not comfortable picking a fine range of colors myself, but maybe someone in the forum is up for the task - if it's even needed (Tailwind CSS is licensed under MIT). I would recommend sticking to that palette and just curating the colors from there.
Useful info from the Tailwind docs:
If you’re wondering how to automatically generate the 50–900 shades of your own custom colors, bad news — color is complicated and despite trying dozens of different tools, we’ve yet to find one that does a good job generating color palettes like this automatically.
We picked all of Tailwind’s default colors by hand, meticulously balancing them by eye and testing them in real designs to make sure we were happy with them.
Two useful tools we can recommend are Palettte and ColorBox — they won’t do the work for you but their interfaces are well-designed for doing this sort of work.
If you're wondering how this would look with future editor changes, here I cherry-picked this PR into my fresh-fields branch and removed the button borders:
The fusion buttons look out of place and would need changing, of course.
Known issue:
title attribute do not adjust to dark mode properly.This is a WIP about refactoring the deckoptions.
Some points which should be improved by this:
Some points of interest:
.container, .row, and .col classes.HelpPopup, the label handling, and RevertButton from the individual components. Making it obvious, that these are individual components, and can stand on their own. Of course this creates a lot of verbose code like this:<Row>
<Col size={7}>
{tr.schedulingMaximumInterval()}
<HelpPopup html={marked(tr.deckConfigMaximumIntervalTooltip())} />
</Col>
<Col size={5}>
<SpinBox
min={1}
max={365 * 100}
bind:value={$config.maximumReviewInterval}
/>
<RevertButton
defaultValue={defaults.maximumReviewInterval}
bind:value={$config.maximumReviewInterval}
/>
</Col>
</Row>
I could wrap these up into their own respective components, let's say SpinBoxRow, CheckBoxRow, etc., as to avoid boilerplate.
deckoptions-base.scss, will have to check after #1202 is merged. (EDIT: was tested on mobile)First of all, I'm sorry for opening yet another PR. After the Tag Editor, and potential worries about extensibility, I thought that the Toolbar would be a better target for trying out ways to make Svelte components extensible.
/ts/editor-toolbar.IconButton for buttons which have a big iconCommandIconButton for icon buttons, which are based on document.execCommand (they support the notion of being active)LabelButton for buttons, which have a text label (like "Fields...")SelectButton, which have a <select> menu.DropdownMenu, which is a menu with text items (like the More button currently on AnkiDesktop)ButtonDropdown, which can contain a set of buttons, like the Mathjax button on AnkiMobile currently.Showing off the toolbar, with two unused features: SelectButton and ButtonDropdown:
flex-flow in ButtonGroup. This could also be turned into a parameter for the whole toolbar.
The Toolbar exposes its API in two ways:
editorToolbar is a new global in the editor. It contains the Svelte components which were used to create the buttons, and it also methods updateActiveButtons, and clearActiveButtons, which are exposed via the Module Context of CommandIconButton.svelte.document.getElementById("editorToolbar"), exposes the buttons and menus as Svelte stores, which can be used to update the buttons and menus reactively. This way you can even listen to changes to the toolbar.Todos (feel free to edit):
bridgeCommand. I think only the fields, cards, attachment, and record button will actually still need it. Does that sound right?size.CommandIconButton.svelte). (Exchanged with @ts-expect-error)RawButton / passing string as buttonBoldButton etc. (I instead used dynamicComponent which is more a reiteration on withLazyAttributes with better type support)Unknowns:
editor.py can be removedhtml-filter, which would then be used within editor-toolbar).Updates:
As discussed, this implements rudimentary CSV and JSON (Mnemosyne) importing. I've also explored CSV metadata encoding, because it's tightly coupled with the import GUI. Below is a list of questions/todos that will need an answer at some point, but for some it probably makes sense to collect more information first. I will keep updating this list. I wonder what makes the most sense to implement next. The GUI? Exporting? Or polish up the existing routines first?
GetCsvMetadata.Bazel brought a lot of nice things to the table, such as rebuilds based on content changes instead of modification times, caching of build products, detection of incorrect build rules via a sandbox, and so on. Rewriting the build in Bazel was also an opportunity to improve on the Makefile-based build we had prior, which was pretty poor: most dependencies were external or not pinned, and the build graph was poorly defined and mostly serialized. It was not uncommon for fresh checkouts to fail due to floating dependencies, or for things to break when trying to switch to an older commit.
For day-to-day development, I think Bazel served us reasonably well - we could generally switch between branches while being confident that builds would be correct and reasonably fast, and not require full rebuilds (except on Windows, where the lack of a sandbox and the TS rules would cause build breakages when TS files were renamed/removed).
Bazel achieves that reliability by defining rules for each programming language that define how source files should be turned into outputs. For the rules to work with Bazel's sandboxing approach, they often have to reimplement or partially bypass the standard tools that each programming language provides. The Rust rules call Rust's compiler directly for example, instead of using Cargo, and the Python rules extract each PyPi package into a separate folder that gets added to sys.path.
These separate language rules allow proper declaration of inputs and outputs, and offer some advantages such as caching of build products and fine-grained dependency installation. But they also bring some downsides:
I was hopeful that after the initial setup work, things would be relatively smooth-sailing. Unfortunately, that has not proved to be the case. Things frequently broke when dependencies or the language rules were updated, and I began to get frustrated at the amount of Anki development time I was instead spending on build system upkeep. It's now about 2 years since switching to Bazel, and I think it's time to cut losses, and switch to something else that's a better fit.
The new build system is based on a small build tool called Ninja, and some custom Rust code in build/. This means that to build Anki, Bazel is no longer required, but Ninja and Rust need to be installed on your system. Python and Node toolchains can be automatically downloaded like in Bazel.
This new build system should result in faster builds in some cases:
As an example of the differences, when testing with the mold linker on Linux, adding a new message to tags.proto (which triggers a recompile of the bulk of the Rust and TypeScript code) results in a compile that goes from about 22s on Bazel to about 7s in the new system. With the standard linker, it's about 9s.
Some other changes of note:
If you're upgrading from Bazel, updated usage instructions are in docs/development.md and docs/build.md. A summary of the changes:
Appears to be an issue on both Windows and Mac. I've tried two different Windows 10 machines, a Windows 11 machine, an Intel Mac, and an ARM Mac, but have not been able to reproduce it on any of those devices.
Presumably it's occurring in deferred_delete_and_garbage_collection() or the subsequent timer firing. If a dev is able to reproduce the issue on their machine, they could try experimenting with manually destroying specific properties such as _page/assigning a new blank page to see if that makes any difference.
The first linked report above says they're only seeing this in 6.3.0, though there have been reports in previous Anki versions of similar issues that I could not reproduce either. So it's not clear whether this is a new bug introduced in 6.3.0, or whether it's a race condition that has just started affecting other users due to changes in timing.
Qt are only going to release 6.2.5 to commercial customers, which means we're stuck on 6.3.x now if we want the pasting/IME fixes coming in 6.3.1.
qt6The main purpose of this PR is to make descriptive comments available to theme authors.
E.g.:
colors: (
fg: (
...
subtle: (
"Placeholder text, icons in idle state",
(
light: palette(darkgray, 6),
dark: palette(lightgray, 3),
),
),
...
),
),
Results in:
Add-on authors will also be able to access these descriptions with color.comment, as the colors are now dictionaries instead of tuples in Python. I imagine it would be practical for theme-editing GUIs.
Take 2. Closes #1079. Disclaimer: This is not supposed to go with 2.1.45. So be free to ignore it, while .45 is not out yet.
Notes:
I tried to emulate the visuals of the tag editor on iOS, and the functionality of the tag editor on Desktop. Two ways you can see this is using arrows keys, to navigate between the tags, and using backspace (or delete) to delete beyond tags.
WithAutocomplete is a very general component, that could also be reused in a wide variety of scenarios. I actually thought it could be useful, when we implement the NoteType / Deck selector in Svelte, and we don't go with a modal.
The Tag badge (same icon as in browser) is clickable, and replaces exposes the "Focus Tags" shortcut. Clicking the badge behaves slightly different from the shortcut. Clicking the badge will always focus the new tag input, whereas the shortcut toggles it.
nowrap, we could also set the tags nowrap, and make the "AddTag" icon sticky, that way users could still easy add new tags, even thought the end of the tags is beyond the viewport.The autocomplete currently has one randomly generated item. This shows you when the suggestions would update.
Instead of Ctrl+Tab, just Tab will navigate the menu. Ctrl+Tab is reserved on macOS (App switcher).
Tab + Shift-Tab + Enter. However Up + Down + Right works just as well. Selecting an autocompletion item will move the caret to the end of the tag, and pressing right will open a new tag to the right (if the tag is the last one).The autocomplete navigates bottom to top when it is a dropup (most relevant item will be at the bottom).
Entering a duplicate will highlight the old one and discard the new one.
Todos:
row instead of row-reverse) (Autocomplete for the tag editor will always be a dropup now)nowrap version.This is pretty much finished, except the CSS rules of PlainTextBadge, where positions are not yet fully calculated, but hard-coded.
I'm off for the next three days, so I wanted to put this out there quickly for you to test.
I'm using anki Version 2.1.54 (b6a7760c) and it doesn't support semi space character (ZERO WIDTH NON-JOINER) with uni code U+200C it's an important part of my language ( persian ). is there a way to use it or can it be added in future ?
This adds a gallery similar to this one to the debug dialog.
It allows users to change the styling approach across the application via a dropdown and see the effects immediately on various Qt widgets.
There are three choices:
If the "Force Style" box is checked, the style will be kept across profiles.
@tatsumoto-ren I don't know how much of the GTK theme Anki should pick up. Please tell me if the "Native/Fusion" options are working for you. The UI looks the same as on 2.1.49 for me. Missing styles for the "Anki" option will be added in future PRs.
This PR fixes a regression with the toolbar that occurred in 2.1.55.
Main problems with the current look:
New version (screencast):
https://user-images.githubusercontent.com/69171671/209826215-75684d24-4811-4353-b02a-7d1a1a7b2e9f.mp4
The toolbar buttons behave more similarly to what was in 2.1.54 and earlier. Because add-ons often print on the toolbar, it is important to keep it compact, so the paddings were reduced.
I have seen a PR that makes it possible to hide the toolbar. I think it's fine for someone who don't use any addons that add extra buttons to the toolbar. However, without this PR those who want the toolbar to stay visible would have to accept its intrusive look.
There are probably alternative ways to fix the issue, but I would assume they require more work. For example, the toolbar could be moved to a completely different location.
Yes/no buttons would be clearer as eg. "Discard" and "Keep Editing", and the prompt will probably need to be changed to something like "Discard current input?". This will probably require adding some new translation strings.
https://forums.ankiweb.net/t/saving-changes-to-evaluation-exit/25546
Text copied from QTextEdit/QPlainTextEdit widgets (e.g. in the card layouts, add-on config, deck description screens) contains Paragraph Separator characters instead of line feeds/carriage returns.
This can be reproduced in the 2.1.55 and the latest main. It's a Qt bug (QTBUG-107004). I'm just creating this issue to bring it to attention.
qt6If updating from Anki 2.1.49 or below, please see the 2.1.50 change notes first.
Lots of UI improvements, thanks to Matthias:
mw.pm.set_force_custom_styles(True).V3 scheduler improvements, thanks to Rumo:
Import/export improvements, thanks to Rumo:
Other improvements:
introduced:x now ignores manual reschedulings (thanks to Rumo).Fixes:
If updating from Anki 2.1.49 or below, please see the 2.1.50 change notes first.
A new CSV importer & exporter, thanks to Rumo:
Update to Qt 6.3.1:
Fixes & improvements:
If updating from Anki 2.1.49 or below, please see the 2.1.50 change notes first.
<br> tags in MathJax are now handled correctly (thanks to Henrik).If updating from Anki 2.1.49 or below, please see the 2.1.50 change notes first.
< and > symbols in MathJax (thanks to Henrik).field_filter hook can now check if it's running for the question or answer side (thanks to Abdo).av_player_will_play_tags hook (thanks to Abdo).This build also includes a new implementation of apkg importing and exporting, thanks to Rumo. Some advantages:
The new functionality is hidden behind a feature flag, and not active by default.
You can try it out by using mw.pm.set_new_import_export(True) in the debug console.
To revert to the old behaviour, replace True with False.
Things to note:
File>Create Backup before trying it out.
Any testing/feedback you can provide would be appreciated.If updating from Anki 2.1.49 or below, please see the 2.1.50 change notes first.
Changes:
Fixes:
<b> and <i> formatting tags, instead of <strong> and <em>.Windows:
macOS:
Linux:
sudo apt install zstd
tar xaf anki-2.1.50-linux-qt6.tar.zstd
Please see the notes for your platform:
The V1 scheduler is no longer supported. If you have not yet updated to V2 or V3, you will be prompted to update when you attempt to review cards in 2.1.50.
This release includes a number of improvements to the V3 scheduler, mostly thanks to Rumo:
Most of these changes are thanks to Henrik.
[anki:tts lang=en_US]Here is {{Field1}} and {{Field2}}[/anki:tts] (thanks to Rumo). There are no plans to deprecate the
old TTS syntax - either can be used.parent tag, while not matching
ones tagged with parent::child: tag:re:^parent$.target=_blank work (thanks to Danish).<div> being left behind when deleting field contents (thanks to Hikaru).note: and card: searches no longer do a substring match (thanks to Rumo).:/icons/foo.jpg should become
icons:foo.jpg.pip install 'aqt[qt6]'mw.progress.timer() should now be passed a parent argument, as the
previous default of using mw prevents the timers from being freed after they
are no longer active. If you want a permanent timer, pass mw in as the parent.Changes to the v3 scheduler:
Other changes:
For add-on developers:
Undo handling:
Scheduling changes:
Browser changes, mostly thanks to Rumo:
Editor changes, mostly thanks to Henrik:
State handling:
The deck options screen has been reimplemented:
Other features:
[...] in cloze deletions is now read as "blank" by TTS (thanks to Rumo).Fixes:
A big thank you to everyone who contributed, including people who contributed translations, and those who helped test out the beta releases and provided feedback.
Add-on authors, there are some notes on porting add-ons to 2.1.45 available.
Source code(tar.gz)Browser improvements:
Editing improvements:
<br> tags will now be used by default instead of the previous <div>
tags, which solves some issues with multiple lines in cloze deletions and
MathJax (thanks to Henrik).Search improvements:
one two becomes
"one" AND "two") (thanks to Rumo).Graph improvements:
Scheduler improvements:
Reworked the Reschedule tool:
Other changes:
Fixes:
For developers:
For developers:
For developers:
Notable changes:
Bugfixes:
For developers:
Thanks to all the people who have contributed bugfixes and code/doc updates: Abdo, Lukkea, Akshara, Kelciour, David, Henrik, Colin, Johan, Piotr, Andreas, Arthur, Alan, RumovZ, Cecini, Soren, Krish, ianki, Cyphar and kaczmarj, in no particular order.
Thanks also to all of the people who have contributed translations for this and previous releases: https://i18n.ankiweb.net/contributors/
Source code(tar.gz)This is the last Anki version that supports 32 bit Windows machines, and macOS 10.12 and older. If you use either of those, please pick the -alternate version.
* in searches.2.1.28 is a big update with changes in a number of areas.
A reworked graphs screen:
Reworked syncing:
Card generation changes:
Card template screen:
Scheduling:
Empty cards screen:
Database check:
Unicode normalization:
If you are studying rare CJK characters and wish to prevent them from being converted into modern equivalents, the following in the debug console will stop Anki from normalizing note text.
mw.col.conf["normalize_note_text"] = False
The standard Windows build has troubles with the AltGr key. This is fixed in the 2.1.29 beta, or a workaround is available.
The standard Mac build currently does not support native dark mode. If you previously enabled it from the terminal, please either try the 2.1.29 beta, or undo the change with the following terminal command:
defaults write net.ankiweb.dtop NSRequiresAquaSystemAppearance -bool yes
Other changes:
2.1.27 was reserved for a bugfix update that did not eventuate.
Source code(tar.gz)(build tag on PyPi: 6046bbc7)
A free and open-source chess improvement app that combines the power of Lichess and Anki. Chessli Project Activity & Issue Tracking PyPI Build & Healt
Anki Retirement Addon Allow users to suspend, tag, delete, or move cards that reach a specific retirement interval Supports Anki version 2.1.45 Licens
Card History At A Glance Stop having to press card browser and ctrl+i for every card and then WINCING to see it's history of reviews FEATURES Visualiz
RpkConverter This tool is used to convert rpk file to Anki apkg. 如果遇到任何问题，请发起issue，并描述情况。如果转换rpk出现问题，请将文件发到邮箱 ssqyang [AT] outlook.com，我会debug并修复问题。 下
Leetcode Anki card generator Summary By running this script you'll be able to generate Anki cards with all the leetcode problems. I personally use it
Cirq is a Python library for writing, manipulating, and optimizing quantum circuits and running them against quantum computers and simulators. Install
QType Framework To Ease Operating with Quantum Computers Concept # define an array of 15 cubits:
my anki plugin if you have found this by accident, you should probably run away this is nothing more than a hackers attempt at an MVP anki plugin I re
Ankiniser A Python3.8 script to convert your favorite TV series into an Anki deck. How to install? Download the script with git or download it manualy
ruin-wordle Wordle is fun, so let's ruin it with computers. Metrics This repository assesses two metrics about each algorithm: Success: how many of th
Anki-HanyuShuipingKaoshi Anki Cards for the HSK vocabulary Chinese-German Das Deck baut auf folgenden Quellen auf: China Endecken Wortschatz von wohok
PyToQlik is a library that allows you to integrate Qlik Desktop with Jupyter notebooks. With it you can: Open and edit a Qlik app inside a Ju
「天目」 -- Amenoma 简体中文 | English 「天目流的诀窍就是滴水穿石的耐心和全力以赴的意志」 扫描背包中的圣遗物，并导出至 json 格式。之后可导入圣遗物分析工具( 莫娜占卜铺 、 MingyuLab 、 Genshin Optimizer 进行计算与规划等。 已支持 原神2.
Turtle ?? The only purpose of a byte-sized application is to help you create .desktop entry files for downloaded applications. As of usual with elemen
Yomiko Comics/doujinshi reader application. Web-based, will work on desktop and tablet devices with swipe interface. Scans one or more directories of
firefox-installer Install Firefox from Mozilla.org easily, complete with .desktop file creation. Dependencies Python 3 Python LXML Debian/Ubuntu: sudo
PyDrop An Airdrop alternative for cross-platform users only for desktop with Python, -version 1.0 with less effort, just as a practice. ##############
Desktop background wallpaper, based on current weather and time A python script that changes your computer's desktop background based on current weath
Kenobi-Server WIP Opensource desktop application for Kenobi. Download the apple watch app to get started. What is this repo? It's repo for the opensou
93 Nov 23, 2022
3 Dec 23, 2022
11 Dec 19, 2022
9 Nov 1, 2021
150 Dec 25, 2022
3.6k Jan 7, 2023
2 Jun 6, 2022
1 Nov 2, 2021
37 Nov 3, 2022
11 Feb 11, 2022
1 Jan 7, 2022
16 Sep 9, 2022
475 Dec 30, 2022
14 Dec 29, 2022
26 Aug 10, 2022
7 Nov 4, 2022
6 Mar 25, 2022
1 Nov 16, 2021
9 Oct 8, 2022