Friedrich von Never

While I have nothing against that, I think that generally we shouldn't collect **all** common TeX extensions and squash them into our XML files. I'm a fan of more component-wise...

Clarify, please. What kind of documentation do our contributors need?

Okay, I'll try to elaborate myself. We need sort of architectural document that will describe the current structure of the project. Major topics include: - [ ] `TexRenderer` and its'...

@charlesroddie I've decided to move the discussion about F# port to another issue: #111. And feel free to ask questions disregard we decide to port the code to F# or...

We have already started writing the documentation in markdown format. So, yeah, it's definitely a good choice for a project hosted on GitHub.

It isn't still clear what kind of support we can offer to Avalonia. Probably we could add the control like your `FormulaControl` (see #23). Anyways, it seems that it depends...

Hello, @Happypig375! Your request totally makes sense. Could you please raise another issue about Xamarin Forms? I'd like to support it, although I've no knowledge of Xamarin at all. I'd...

Okay, here's the current plan. - [x] create a branch for Avalonia stuff (and we will then proceed to work on that branch using PRs with the usual branching policy,...

@rstm-sf, initial plan is just make it public, but, if you have any particular improvements for API, then feel free to apply them and drop me a PR. Regarding the...

@ahopper, no worries, we're still working on this project. @rstm-sf, which of that it a problem? I believe we could easily update our markup and add `x:Class`, right? Aaand is...