Previous issues

[leotrs]

There are a number of open issues on the original manim repo. A good way to determine a path moving forward for this community fork is to go over those issues and copy them here (the useful ones at least) so that they can be assigned to someone and we can do something about them.

This will also signal to end users that there is a lot of activity on this repository.

[eulertour]

The low hanging fruit here is a way to verify the manim install. Basically something to dry-run a Scene, ensure that the bare minimum to render successfully is actually installed, and give a helpful error like LaTeX/FFmpeg isn't installed, media directory isn't writable, etc.

[leotrs]

@eulertour good suggestion, forked it into its own issue.

Please keep suggesting here old issues that should be copied into the manim-community repo.

[safinsingh]

Possible PRs to look into:

• Fixing a broken stroke width for ZoomedScene: Fixing a broken stroke width for ZoomedScene 3b1b/manim#1073
• Add custom CTeX capabilities: add possibility of custom tex template  3b1b/manim#745
• Add option to fix SVGs with Cairo: Adds option to fix SVGs. 3b1b/manim#330
• Fix NumberPlane construction: Small fix to NumberPlane construction 3b1b/manim#909
• Add Physics Engine support (possibly as an add-on?): Add Physics Engine Support 3b1b/manim#818
• Add dependency check script: add dependency check script 3b1b/manim#636

[TonyCrane]

Possible PRs to look into:

• Fixing a broken stroke width for ZoomedScene: Fixing a broken stroke width for ZoomedScene 3b1b/manim#1073

• Add custom CTeX capabilities: add possibility of custom tex template  3b1b/manim#745

• Add option to fix SVGs with Cairo: Adds option to fix SVGs. 3b1b/manim#330

• Fix NumberPlane construction: Small fix to NumberPlane construction 3b1b/manim#909

• Add Physics Engine support (possibly as an add-on?): Add Physics Engine Support 3b1b/manim#818

• Add dependency check script: add dependency check script 3b1b/manim#636

Also 3b1b#1071 This pr fixes some serious bugs of Text() and Code(), but the effect of some of the latter commits is not good. Can we keep only the part of the commits that fixed the bugs before?

[NavpreetDevpuri]

Also 3b1b#1071 This pr fixes some serious bugs of Text() and Code(), but the effect of some of the latter commits is not good. Can we keep only the part of the commits that fixed the bugs before?

which commit's effect is not good ?

[TonyCrane]

which commit's effect is not good ?

The last few are to resolve Transform's commits.
I don't think they are necessary, and they are more difficult to understand and not easy to use.

[NavpreetDevpuri]

I think they are necessary because

• Resolve Transformations. Without that Transformations seems ugly.
• Open a ability to access chars differently as visible sub-mobjects.
• Open abilities to new modifications something like Text.words and Text.lines. I will do that.
• Add more functionalities to Text()

As you said "more difficult to understand" i want to ask you that what if Grant Sanderson thinks the same Did he able to make manim? there are so many things that seems difficult to understand.

Is using Text.chars or remove_invisible_chars() seems difficult ?

Without those modifications someone may post an issue saying "Hey this Text transformations is wrong".

[leotrs]

Thanks everyone for bringing up all these previous issues. I think this issue has achieved the purpose of gathering all of these. So I'm going to ask the participants @NavpreetDevpuri @safinsingh @eulertour @tony031218 to feel free to take any of those issues you have listed and open them again here in this repo. We can come back to this list for future reference. But I'm closing this for now.

In particular, @tony031218 and @NavpreetDevpuri please continue your discussion in a new issue dedicated to 3b1b#1071 :)