accesskit VS zotero

If you were to implement this yourself, i'd look into either swash or cosmic-text for the text rendering stack (this is one of the things you really don't want to write from the ground up). For accessibility, AccessKit has quickly become the standard for communicating with crossplatform accessibility APIs in rust GUI. lightningcss (or its lower level counterpart cssparser) are both decent options for CSS parsing. Taffy handles some of what browsers offer for a layout engine, but is still being worked on.

> Fleet relies on the Java AWT/Swing framework to get a window from an operating system, but it doesn’t use the Java platform for managing its GUI components besides one JFrame and JPanel on top of it.

This is a terrible decision that is going to bite them in the long run. Doing things this way makes it far, far more difficult to implement accessibility, and regulations on this are only going to get stricter.

Implementing accessibility for a framework like that would involve three separate implementations for three separate platforms and the need to interface with D-Bus, COM and Objective C, from Java. I imagine that the latter two would be particularly difficult, considering how bad Java's FFI support is. It's not just calling methods either, you'd actually need to implement your own classes that conform to the relevant COM interfaces / Objective C protocols. There are libraries that can help with this[1], but I don't think they would work particularly well for something as complex as a code editor.

[1] https://github.com/AccessKit/accesskit

fltk-accesskit is an accesskit integration crate for fltk-rs, the gui crate. It's implemented as an external crate to allow for more experimentation before stabilizing the api, especially since fltk is at version 1.4.

Libraries for a lot of this stuff exist (albeit in many cases not very mature yet):

- https://github.com/pop-os/cosmic-text does text layout (which Taffy explicitly considers out of scope)

- https://github.com/AccessKit/accesskit does accessibility

- https://github.com/servo/rust-cssparser does value-agnostic CSS parsing (it will parse the general syntax but leaves value parsing up to the user, meaning you can easily add support for whatever properties you what). Libraries like https://github.com/parcel-bundler/lightningcss implement parsing for the standard css properties.

- There are crates like https://github.com/BurntSushi/bstr and https://docs.rs/wtf8/latest/wtf8/ for working with non-unicode text

We are planning to add a C API to Taffy, but tbh I feel like C is not very good for this kind of modularised approach. You really want to be able to expose complex APIs with enforced type safety and this isn't possible with C.

There are a number of up-and-coming Rust-based frameworks in this niche:

- https://github.com/iced-rs/iced (probably the most usable today)

- https://github.com/vizia/vizia

- https://github.com/marc2332/freya

- https://github.com/linebender/xilem (currently very incomplete but exciting because it's from a team with a strong track record)

What is also exciting to me is that the Rust GUI ecosystem is in many cases building itself up with modular libraries. So while we have umpteen competing frameworks they are to a large degree all building and collaborating on the same foundations. For example, we have:

- https://github.com/rust-windowing/winit (cross-platform window creation)

- https://github.com/gfx-rs/wgpu (abstraction on top of vulkan/metal/dx12)

- https://github.com/linebender/vello (a canvas like imperative drawing API on top of wgpu)

- https://github.com/DioxusLabs/taffy (UI layout algorithms)

- https://github.com/pop-os/cosmic-text (text rendering and editing)

- https://github.com/AccessKit/accesskit (cross-platform accessibility APIs)

In many cases there a see https://blessed.rs/crates#section-graphics-subsection-gui for a more complete list of frameworks and foundational libraries)

Using HarfBuzz makes sense. But if you're looking for a pure-Rust alternative, I hear cosmic-text (made by Pop!_OS) is good. There's also AccessKit for accessibility.

There are efforts to support a cross platform accessibility library:

https://github.com/AccessKit/accesskit

egui is an easy-to-use immediate mode GUI for Rust, and I just released 0.20. It's a big release!

There is now support for AccessKit (https://github.com/AccessKit/accesskit) which brings accessibility to egui (a first for an immediate mode GUI?).

There is also better table support, nicer keyboard shortcut handling, better looking text in light mode (still not great, but better).

See more in the changelog: https://github.com/emilk/egui/blob/master/CHANGELOG.md

Try it out at www.egui.rs

Maybe try Zotero[1]. There are many addons which can do what you need.

[1]https://www.zotero.org/

And next time, you use a real literature management program like zotero (some university libraries offer classes, there is a r/zotero, etc) or jabref to create a proper bibtex file with the references. It is not that difficult, and keeps you sane (esp. if a paper has to be formatted for a different publisher). See e.g. learnlatex.

Zotero | Remote | Full-Time or Part-Time | https://www.zotero.org

Zotero is an open-source project that develops software to help people collect, organize, annotate, cite, and share their research. Our software is recommended by most universities and used by millions of students, scholars, scientists, and researchers worldwide.

We're looking for a JavaScript developer to work on Zotero "translators" — the pieces of code that let people click a button in their browser toolbar on any webpage and save high-quality metadata and files to their Zotero libraries. If you like web scraping, APIs, data formats, and exploring sites in the browser devtools, this would be up your alley. As a core Zotero developer, you'll also have the ability to work across Zotero's vast ecosystem and help shape the future of the project.

This is an open-ended contract role that can scale up and down in hours based on availability and workload.

https://www.zotero.org/jobs

Zotero is your answer, it even auto generates your citations.

https://www.zotero.org/

Apparently there are plugins for Logseq and Obsidian as well.

Zotero - Price: Free Free and open-source reference manager that helps you collect, organize, and cite your research sources.

I use the free and open source Zotero which I think you'd find very calibre-like and manage notes and concept linking with org-roam in emacs.

If you can't hold the urge to know, you can check on the Zotero web library if all of your things are still there

Resources: ZOTERO. Zotero is a free (you can pay to get more storage), open-source citation manager with optional browser plugins. IT WILL FORMAT CITATIONS FOR YOU. (sometimes you have to edit them, but most of the time it can pull metadata and format things correctly on its own). You can sort your references into folders or with tags, read and annotate PDF copies on your computer or in a mobile app, and make notes - which I used to keep track of specific quotations I wanted to use.

You can also use online resources like The Encyclopedia of Archaeological Sciences, that I think is mostly free or the Handbook of Archaeological Sciences which I think is also mostly free. If you can't get a hold of those things you can also email the authors/editors and they might send you a free copy or look them up on Academia.edu and see if they have a free version. Also, if you don't already, use Google Scholar, it's the best resource for finding free articles and topics to read. It's also never too early to start using something like Zotaro, Mendeley, or Endnote to keep track of your readings and help you with citations/references in papers. You can literally download the citation, import it into one of those systems and it automatically formats your referencing.