I draw figures for my mathematical lecture notes using Inkscape
castel.dev
castel.dev
You can try out Mathcha[1] which is built to help people without knowing of Latex can easily write down Note (with rich Mathematics symbols/layouts) and it also provide basic Drawing and basic Function Plotting (The Drawing Part no way compare to Inkscape, but hey! you can type Math on Drawing on Mathcha) in single Editor.
Please note that I don't want to tout and advertise Mathcha here, the point is to provide another option for people to try out (I will not say it will provide faster or more powerful than Vim+Latex)
[1] Mathcha website: https://www.mathcha.io/
Disclaimer: I'm creator of Mathcha.
Haven't used it for several years though, so no idea if the WSYIWYG is still up and running.
- LyX: full Latex compiled, and Mix between WYSIWYG and Latex Script. Mainly use to create Latex Document
- Mathcha: can export some parts to Latex (mostly Math mode) but does not guarantee to compile, a full WYSIWYG editor. The goal to just create Document without constraints to Latex format
No, "Africa" is far too huge and varied to generalize about like that. Plenty of African countries have reasonable mobile infrastructure, and low enough costs.
$ apt install lyx
…
Need to get 216 MB of archives.
(This is coming from nothing, LaTeX isn't installed.) At 5Mb/s, that's about 6 minutes. That's not unreasonable for a one-off installation, especially in a country where these speeds are normal. (And 5Mb/s is slow: https://www.speedtest.net/global-index .)vimtutor (type it in the command line)
after that: edit a couple of documents, write down what you want shortcuts to and learn those. Target practice allows you to learn vim quite quick.
- Export to Latex (Mostly for Math Mode, and does not guarantee compiled in complicated case)
- Tikz (for Diagram)
- MathMl (Math Mode only)
- SVG/PNG (Math Mode and Diagram only)
- Save as Html (.zip file)
- Save as PDF (currently supported on Desktop version), but you can use Browser Print and save as PDF
2. Sorry, I don't have clear Road map, mainly I'm working on to add more features specifically on Math (for example Z Specification)
3. Unfortunately there is no one-time payment license now.
I'd use Emacs org-mode now unless the Wiki made was needed to work on with others.
My friend is a math professor, uses tablets with stylus.
Out of the example figures in this post, some of them I would outright not know how to draw. Others I would be able to draw, but I think each of them would take me at least about an hour, maybe more. And this is not out of lack of familiarity with the tool: Inkscape is my go-to tool for vector drawing and what I use most for scientific paper figures, presentation slides, posters, lecture slides, etc. so I have lots of hours of practice with it.
Who is more of an outlier, the author or I? Is it really within the reach of most people to be able to whip up figures like that in a few minutes?
One thing that seems to be missing from these posts though is that this kind of uber-productivity with tools and shortcuts takes serious practice. Even ridiculously talented individuals still need to commit those shortcuts to memory such that they can recall them when needed.
On top of that, there's the learning of aesthetics along the way: what colors to use, what proportions to use, how much margin to set for better-looking illustrations, and so on. This takes serious practice.
There’s no way I’d use it in a lecture.
But I ( native English speaker) struggle ( had to google to write the first sentence ) with which is which in _former_ and _later_. I always imagine the past stretching behind and the first thing mentioned is now further away from me, so it should be the 'later' and the second thing mentioned is now closer to me and should be the 'former'. I've had this conversation enough to know that some people agree and others respond by sharply downgrading their estimation of my intelligence. As a _predominantly symbolic/linguistic_ person I suspect former/later is something you would perceive as effortless.
Though I have hard time taking the visual/auditory/kinaesthetic learning styles seriously, and with no thought as to the contribution to the variation between individuals being learned or innate - symbolic/linguistic/visual seem to be different competencies.
And Gilles Castel seems near the top of the curve on all of them.
Indeed, as you assume, "former" and "later" don't pose any problem for me because I don't imagine anything visual at all when I evoke those concepts, I just think about what they mean in a non-visual way. But I can see why you would struggle if you think visually.
I guess the analogous weakness in my case is the one that manifests when I have hung my coat and forgot to take out e.g. the keys. I know what pocket my keys are in (e.g. suppose they are in the left inner pocket) but I totally struggle to find it when I'm not wearing the coat. Visual thinking seems to really outperform symbolic thinking in that problem, and sometimes memorization of the solution provides a shortcut in similar issues, but there it doesn't work because the coat can be hung in two orientations! So it's usually faster for me to take the coat, put it on, take the keys, and then hang the coat again, and in fact that's exactly what I do, at least if no one outside of friends and family is looking... :)
I'm not sure about learning styles (if a teacher provided a visual schema of a lesson I just translated it to words, or focused more on the oral explanation and ignored the diagram, and still learned it fine, it wasn't such a big deal as some people make it look like), but thinking styles are definitely a thing. I'm not sure if the difference is learned or innate either. In my case, I have always loved reading and read a lot since infancy, so it might be learned.
If the past is behind you, isn't further away earlier in time? The Romans are further back than yesterday, right? So nearer should be later in time?
I often have to stop when doing filesystem datetime comparisons, to work out if I want greater-than or less-than, and picture it as Unix Epoch in seconds, the later time is a greater number, nearer things are closer and bigger and more recent, distant things are smaller, farther and more ancient.
(btw, it's former/latter)
I'd say both.
Is it really within the reach of most people to be able to whip up figures like that in a few minutes?
I'd say no.
This is a question that goes directly to the core of my competence. In general we're living in a pioneers' era where demand trumps offer overwhelmingly.
The tools we have, we don't use them because they're the best possible tools, but because they're the only tools available.
We are in such a need of any tool that works somehow, that we're deceived to think that they're wonderful when they're just slightly better than the rest. The space for improvement is vast, including a tool that would make those diagrams easy for you.
It's also open source and you can compile LaTex directly in the editor to see what it looks like without switching windows.
[0] http://ipe.otfried.org/ [1] https://en.wikipedia.org/wiki/Ipe_(software)
https://github.com/otfried/ipe-wiki/wiki/Showcase#presentati...
I do agree with the author that taking lecture notes for math-heavy classes in LaTeX is quite possible, though I haven't done it since I was an undergraduate. While the author makes use of snippets in a particular text editor setup, I instead relied on extensive use of \def. With sufficient experience and intuition as to when to \def something, I could take notes in many classes faster than everyone writing by hand, and often faster and more clearly than the professor could write: I could insert a common but complicated expression with a few keystrokes, rather than writing it out or using something like ~ to refer to it. I would also use a standard set of \def's to make standard LaTeX faster to type: \beq and \eeq for \begin{equation} and \end{equation}, and so on. This also had the advantage of working in any text editor.
The disadvantage over snippets (I'm not sure how developed they were at the time) was, of course, that my LaTeX was incomprehensible for anyone else reading it, and my style had to change significantly once I started collaborating on projects rather than just writing notes for myself.
I've long used Inkscape for paper and prepared note figures, however, and I've found that many of my colleagues now do as well, after Adobe's transition to a subscription model. In doing so, I am very wary of the pdf+latex export: it doesn't seem as though it can reliably place text exactly, leaving the risk that it looks awkward or has text move when the font; it also makes figures that are not easily reusable in other places (eg, presentations, typesetters making HTML versions of papers, etc). Additionally, the pdf export itself doesn't seem to preserve editing very well. As such, I usually store parallel svg and pdf versions, in the interest of avoiding very non-standard LaTeX packages. However, if I recall correctly, there are packages that allow direct use of Inkscape SVGs in LaTeX.
Unfortunately, all the good editing apps like Sketch and Affinity Designer cost a fortune when you factor in the actual use case. Figma is alright, but the desktop app feels like I am working with a piece of origami.
GIMP doesn't use the XQuartz X11 compatibility layer that Inkscape uses. Work is ongoing according to the Inkscape GitLab [1].
Just buy affinity designer.
Because if not keyframe, it would be something like After Effects for graphics based animation.
affinity designer is $30, one time purchase.
How is that a fortune? Compared to Adobe Illustrator it's essentially free.
Compared to Inkscape, the productivity gains are priceless.
Still $50 is a bargain for a professional level vector illustration app.
I wonder though, are there any alternatives to inscape in which you can draw graphs quickly?
Those of you looking for programmatic diagram generation, I'd you aren't talking math heavy, try it out. I'd you want math diagram generation, I think that might generally be best done with r/octave/d3 inside an emacs org file or jupyter notebook.
yEd [0] might be one. There's also an online version with (currently) a tad reduced feature set [1].
[0] https://www.yworks.com/products/yed [1] https://www.yworks.com/products/yed-live
There are a number of other applications, though. I still like Graphviz for quickly creating a graph structure, but tweaking its layouts can be cumbersome (Note: yEd Live supports rudimentary Graphviz import as well). There's also dia, draw.io, Gliffy, LucidChart, OpenOffice Draw, Omnigraffle. And PowerPoint works to some extent as well.
(Disclaimer: I work for yWorks.)
But I can't imagine sketching my figures in inkscape.
However, my biggest challenge with it, and I've experienced this with other similar software, is how it handles text along a path.
After struggling with this for some time I just took a somewhat brute force approach and made hidden arcs that achieved the target text curvature, despite that arc not being part of the circle.
But the whole idea and execution are phenomenal.
My feeling is that using emacs it could be possibly easier but I will not try to convert a vimmer
One example would be layers. They are saved as standard complient groups of SVGs features. But not all grouped elements form their own layers. So the groups that should be shown as layers do have extra meta data on them. Any standard complient SVG reader while deal with that group correctly, but might not represent it as a layer in it's GUI.
How would you visually represent a layer in a GUI? Layers are logical, not visual, groupings.
Edit: I wasn't considering the editor itself a GUI in this scenario, although it clearly is. I was thinking of the GUI (such as a web browser) where the SVG was being used.
http://wiki.inkscape.org/wiki/index.php/Layer_Dialog
While obviously if you open the SVG in a web browser, layer information is ignored.
(I use the layers dialog in Inkscape on a weekly basis -- and used to in Illustrator as well).
Since Inkscape is a general purpose design app rather than just an SVG editor, it is adding a lot of metadata to the SVG code it generates in order to preserve editing capabilities.
Vide "Simple diagrams of convoluted neural networks" https://medium.com/inbrowserai/simple-diagrams-of-convoluted... with an overview of tools for drawing diagrams for deep learning.
Always there so the skill I developed with it can be put to use efficiently. I love open source so much for this.
Can you link to your thesis?
Inkscape was very difficult to use at the time (IMHO) and had lots of bugs, maybe this improved in the meantime as almost 10 years have passed.
Right..because it's hardly possible to quit fucking vim :(
I've not used this feature in Inkscape, but that's how it seems to work.