Other diagrams format/syntax support

[abnerlee]

Merger other diagrams support request into this issue.

• nomnoml
• MarkVis
• plantuml
• charts
• http://jumly.tmtk.net/
• Wavedrom
• graphviz
• musical ABC notation
• Draw IO
• ECharts
• plotting
• dbdiagram.io

Others

• 2114 other markdown syntax for diagrams

[slavakurilyak]

Support for argument mapping would be great too!

To get started, check out @christianvoigt's argdown

[slavakurilyak]

Support for concept mapping would be nice.

To get started, check out the challenges behind creating concept map akin to markdown

[kid1412621]

+1 for PlantUML

[plimeor]

+1 for plantUML

[stream-iori]

+1 for plantUML

[asdf2014]

+1 for plantUML

[shshsunny]

+1 for tikz

[arjvik]

Can we implement Tikz as well?

https://github.com/kisonecat/tikzjax seems to be a really easy way to implement it

[CapinWinky]

I'm playing around with the Mermaid stateDiagrams and it seems very limited compared to State Machine Cat. They both use PlantUML, so I would imagine there isn't too much different on the Typora side of things.

I guess at some point you have to draw the line and not support every single diagram package out there, but SMCat is just so much better than Mermaid for state diagrams, it would be a shame to not have those features when it seems like such a small swap of one PlantUML project for another.

[mark0725]

+1 for PlantUML

[tan-wei]

+1 for PlantUML and Graphviz

[alhazacod]

We need the tikz package!

[kuitos]

+1 for PlantUML

[EganSolo]

+1 for PlantUML

[zmj64351508]

+1 for PlantUML

[atuchkin]

+1 for PlantUML

[shirayner]

+1 for plantuml

[tttranquilooo]

Why not try chart.js it has a simple grammar and no other dependencies.

[tttranquilooo]

Why not try chart.js it has a simple grammar and no other dependencies.

I mean, comparing to Vega

[knaou]

+1 for Draw IO

[Xilel]

+1 for DrawIO and PlantUML

[HEYRIX]

+1 for Draw.io

[luizgamabh]

+1 for plantuml As it requires a server running, Typora could allow us to setup a plantuml server location in the settings

[AKaisanlahti]

+1 for PlantUML. While that's waiting, you can use a workaround to get something on your docs, even if you can't just embed the code and the diagram in. You can use the PlantUML proxy service (I couldn't get it working when the source was local unfortunately. If someone else can, please comment on your setup) or generate the diagrams even on the fly from your PlantUML source by using inotify or some other watch on the file and then using the image tagging for it. This is what I'm planning on writing when I have the time.

[xxl-game]

+1 for plantuml，if typora supports plantuml, it will be perfert! I have to use typora and vscode at the same time. typora to write article, vscode to draw graph, and preview both of them in a whole page in vscode.

[rgbwoo]

+1 plantuml

[tan-wei]

I think if gnu pic is supported will make it nice to create some notes related to source code.

[elderGinger]

+1 plantuml

[luizgamabh]

up

[tonnyyi]

+1 plantuml

[lanshenghai]

+1 plantuml

[jvanmelckebeke]

As much as I love all the different diagram formats/tools, I think there should be a certain caution to not over-integrate these tools: I believe the philosophy of typora is to provide a very extensive format for writing documents, while keeping the readability of markdown: if you would open the typora .md file in any text editor, everything should still be readable.

What I want to tell is:

• we should use diagram formats which are both readable in raw format (for any user without prior knowledge of the format)
• we should use no overlapping formats (2 formats which result in the same presentation) (imagine searching on stackoverflow for creating chart of type X, and finding answers which use two different formats, it would be a bit confusing for some people)

(disclaimer: I literally found out about this project yesterday meaning I have no grounding at all to withholding the awesome supporters of this awesome project to do the opposite, I am just making a remark and I will love this project whatsoever)

[rezanid]

As much as I love all the different diagram formats/tools, I think there should be a certain caution to not over-integrate these tools: I believe the philosophy of typora is to provide a very extensive format for writing documents, while keeping the readability of markdown: if you would open the typora .md file in any text editor, everything should still be readable.

What I want to tell is:

• we should use diagram formats which are both readable in raw format (for any user without prior knowledge of the format)
• we should use no overlapping formats (2 formats which result in the same presentation) (imagine searching on stackoverflow for creating chart of type X, and finding answers which use two different formats, it would be a bit confusing for some people)

(disclaimer: I literally found out about this project yesterday meaning I have no grounding at all to withholding the awesome supporters of this awesome project to do the opposite, I am just making a remark and I will love this project whatsoever)

Or instead they could simply provide a clean extension format, so people can adopt the editor to their specific workflows. Trying to stick to features that are supported by all the other editors means implementing only the core markdown format which is very limited and that way Typora would lose part of its competitive advantages.

[vassudanagunta]

@jvanmelckebeke

I believe the philosophy of typora is to provide a very extensive format for writing documents, while keeping the readability of markdown: if you would open the typora .md file in any text editor, everything should still be readable.

I agree with you in principle very much. But in this case, because Typora is using CommonMark fenced code blocks and the info string to indicate the "type" of diagram encoded, when the file is opened in other editors that don't know what to do with that type, it degrades very nicely. The code is rendered as-is. One can even edit the code. And when re-opened in Typora nothing is lost.

[nogayama]

+1 plantuml

[9n]

+1 plantuml

[zuisong]

+1 plantuml

[SeeYouQK]

+1 for plantuml

[shirayner]

plantuml +1

[lanmarco]

+1 for DrawIO and PlantUML

[mpowell326]

+1 for plantuml

[harishr1308]

+1 for DrawIO and PlantUML

[luizgamabh]

+1 for PlantUML

[rezanid]

I have made a new feature request that can solve this problem and allow everyone to bring any diagram and file format they want and with minimal effort from Typora team. You can vote for it here: #4157

[chonwhite]

+1 for draw io

[junpayment]

+1 plantuml

[miaozilong]

+1 plantuml

[glenlgd]

+1 PlantUML Since typora does not support plantuml, I had to use vscode.

[davidmlw]

+1 drawio

[gcosta87]

+1 PlantUML