I don't understand why this is bubbling up to the top of hacker news. I presume it is because of high demand and hopes for a native graphing tool, but is there some other reason I am missing? I ask because the project looks to be very early-stage. I see only very simplistic box-and-arrows charts which wouldn't be sufficient for anything but the most basic of ideas -- certainly not for publications or a professional presentation. And the information about its future path and goals is slight-to-none. The team has a very long road ahead to replace full-featured products like LucidChart or OmniGraffle.
[edit: grammar]
Generic support for a solo-developer working on a slick MacOS app. At least that's why I started following the project on Twitter a couple of days ago.
Because options are good? I use Visio on Windows but am constantly needing to do simpler stuff on the Mac at home, and even though PowerPoint works and I have an old OmniGraffle license, I'd love to have something "in between".
I've been looking over a year for something reasonably good and not as messy as Omni. I didn't upvote and it might be manipulated but I did enter my email.
I love how everyone spends years drawing diagrams with mouse torture in visio, OmniGraffle, licid, etc.
eventually everyone will find out about plantuml (puml) which generates diagrams of all kinds via a simple source file and wonder how they could ever live without it.
+ It's all plaintext. I love working with plaintext for all the usual benefits, so this fits.
+ PUML renderer is technically a free-to-download JAR, so it can presumably[0] integrate well with my Org-mode life.
Cons:
- Try to draw anything more complicated than three boxes and an arrow, and you'll be spending 90% of the time fighting the layout engine.
- It's even worse when you have your own opinion about the desired layout. No way to do that reliably, the result is very brittle.
I generally like it, but I'd like it 100x more if there was a way to explicitly pin some component to absolute coordinates. Or at least a better way for giving layout hints than soft constraints introduced through invisible links.
--
EDIT: A random idea if anyone is developing something PUML-like:
How about separating out layouting a bit, and letting me type in something like that:
Basically, I wish I could draw a picture representing the rough layout of key image components, and have this as a hard constraint on positioning other elements.
--
[0] - Presumably, because I gave up on it after couple large-ish diagrams, just before my use has reached the threshold above which I consider Emacs integration.
Mermaid js does that though, and many notetaking apps integrate with it
Personally Draw.io is the best freeapp already out there (online based or desktop), but lucidchart for paid is great too (much better print capabilities)
Not so sure about that - I spent a few weeks this spring trying to badger PlantUML into generating the diagrams I wanted to include in a piece of documentation, and I'd much rather have used an ordinary mouse-based graphics tool where I could have simply put things where I wanted them to go.
Back in my day, everyone just used graphviz. Heck, OmniGraffle's diagram support was (is?) based on graphviz. Have things gotten much better since then? Graphviz was always hard to beat.
I’ve been using OmniGraffle for this purpose for ten plus years. They’re gone downhill since moving into the App Store but there certainly are diagramming tools for Mac...
Hi!
Here is Lukas, the founder of Diagrams. We launched our website on Monday and announced it on Twitter only. I must say I’m astonished to see us on position three of Hacker News today!
At this time we’re in the middle of the development. However, this week’s support really encourages us to work even harder on a perfect product. And we’re also very happy to have several offers from developers and designers who offered collaboration!
It’s great to read your feedback in form of ideas, expectations and questions. You can be assured we read them all attentively. Please keep on posting. We will try to give as many answers as possible in future blog posts.
We also got several requests for beta testing - we will announce the opportunity to apply for an upcoming beta phase via our mailing list, which you can enter here: https://diagrams.app/
ASCII export, so I can put nice diagrams in comments and docstrings. Also possibly (assuming those nice diagrams are unambiguous) a parsing bridge which lets me convert them into data.
As one of the developers that at least contributes to yEd Live (our in-browser equivalent; yEd is based on our Java library which I'm not working on), thank you :-)
That being said, as a UX guy I always love to look at competitors and find ways how editing can be improved or streamlined (and yEd has many features already, so some parts of it can be more complicated than I'd like).
I looked at yEd, and dropped it because it doesn't seem to support rotating shapes. I was quite surprised, since that is a fundamental feature of most drawing applications.
So here's a question I've been wanting to figure out for ages:
Are there any resources you recommend for learning to make good diagrams? Ie, I love documenting things but I don't have experience in drawing diagrams. I don't know conventions for displaying order of execution, what arrows should indicate (in A->B is A giving information to be? is B requesting information from A? etc).
Are there any good tutorials/classes/whatever on drawing good diagrams? Good at conveying information, but also consistent with what educated people would expect?
Check out interaction diagrams for what you describe. Two parties (A and B) would be represented as two columns, moving down the diagram means moving forward in time. The arrow going from one to the other is a message (either an actual message or a function call or something). So A->B means A is signaling (the text and context describe how) B. If B is requesting information, you'd have two arrows. First B<-A, and then A->B with the response (attempted plain text version):
t A B
0 | |
1 |---->| A sends data to B
2 | |
3 |<----| B requests more information from A
4 |---->| A responds
A and B could be people, processes, classes/objects, servers, whatever. The interaction points are described with the context of the diagram and text. (NB: t is not meant to be explicit here, I've included it to illustrate the passage of time going down the diagram.)
I have this exact same question. I've found some conventions over the years that have been helpful, but haven't found anything comprehensive.
With regards to what the arrows indicate, I've done dotted line arrows are synchronous, with a solid arrowhead meaning request body and an outlined arrowhead being the response. Then used solid black line with a single solid arrowhead for an asynchronous request.
That's really nice, usually when I start playing with something like this the UI glitches out or is just un-intuitive but this one is pretty solid, nice work.
and the diagrams generated are easily integrated into MediaWiki installations, with full editability.
draw.io online is a free-to-license web application for everyone. It is completely free to use for any purpose, there is no premium pay-for functionality, watermarking, or other limitations. You own the content you produce with draw.io and may use it for any purpose, including commercially. We don’t sell your personal information or data. We don’t store your data. You own your data and the application is open source.
So, are you actually getting access to the Alpha when you sign up or are we just getting grabbed to someday down the line get Beta access?
I'd advise you to post this again when you have an actual software to show, that people can test out. I won't sign up for anything and I believe a lot of people don't really want anymore newsletters and sales pitches in their inbox.
A few people have mentioned alternative diagramming software projects as well as a desire for ASCII output. To this end, I'll throw in a mention of Graphviz[0] and Graph::Easy[1]. While I have not used the latter, I have used Graphviz/DOT and can recommend giving it consideration.
I’m still waiting for the missing “free” diagram editor for Mac. Or, even better: “Open source”.
Because most decent Mac apps become shareware once they hit version 1.0.
Also, there’s no doubt in my mind that all these utility apps will be web-based in the future. Google Docs and Google Drawings are great examples of this.
Having said that, I wish you the best of luck with your project.
In the meantime before this launches, shout out to the people over at https://whimsical.co/ for launching this product earlier this year. I've been using that (browser based), and loving it. Excited to see what this app is once it launches.
[+] [-] elwell|7 years ago|reply
Yes, it is missing. Please repost when it exists.
[+] [-] yarick|7 years ago|reply
[+] [-] unknown|7 years ago|reply
[deleted]
[+] [-] jackhack|7 years ago|reply
[+] [-] mtmail|7 years ago|reply
[+] [-] rcarmo|7 years ago|reply
[+] [-] csomar|7 years ago|reply
[+] [-] unknown|7 years ago|reply
[deleted]
[+] [-] gcb0|7 years ago|reply
eventually everyone will find out about plantuml (puml) which generates diagrams of all kinds via a simple source file and wonder how they could ever live without it.
[+] [-] TeMPOraL|7 years ago|reply
+ It's all plaintext. I love working with plaintext for all the usual benefits, so this fits.
+ PUML renderer is technically a free-to-download JAR, so it can presumably[0] integrate well with my Org-mode life.
Cons:
- Try to draw anything more complicated than three boxes and an arrow, and you'll be spending 90% of the time fighting the layout engine.
- It's even worse when you have your own opinion about the desired layout. No way to do that reliably, the result is very brittle.
I generally like it, but I'd like it 100x more if there was a way to explicitly pin some component to absolute coordinates. Or at least a better way for giving layout hints than soft constraints introduced through invisible links.
--
EDIT: A random idea if anyone is developing something PUML-like:
How about separating out layouting a bit, and letting me type in something like that:
And then continue with regular PUML code: Basically, I wish I could draw a picture representing the rough layout of key image components, and have this as a hard constraint on positioning other elements.--
[0] - Presumably, because I gave up on it after couple large-ish diagrams, just before my use has reached the threshold above which I consider Emacs integration.
[+] [-] swaggyBoatswain|7 years ago|reply
Personally Draw.io is the best freeapp already out there (online based or desktop), but lucidchart for paid is great too (much better print capabilities)
[+] [-] petecooper|7 years ago|reply
http://plantuml.com
[+] [-] marssaxman|7 years ago|reply
[+] [-] seanmcdirmid|7 years ago|reply
[+] [-] donatj|7 years ago|reply
I’ve been using OmniGraffle for this purpose for ten plus years. They’re gone downhill since moving into the App Store but there certainly are diagramming tools for Mac...
[+] [-] snipem|7 years ago|reply
[+] [-] gowld|7 years ago|reply
[+] [-] lukaskubanek|7 years ago|reply
At this time we’re in the middle of the development. However, this week’s support really encourages us to work even harder on a perfect product. And we’re also very happy to have several offers from developers and designers who offered collaboration!
It’s great to read your feedback in form of ideas, expectations and questions. You can be assured we read them all attentively. Please keep on posting. We will try to give as many answers as possible in future blog posts.
We also got several requests for beta testing - we will announce the opportunity to apply for an upcoming beta phase via our mailing list, which you can enter here: https://diagrams.app/
Have a good time. Lukas
[+] [-] lukaskubanek|7 years ago|reply
[+] [-] masklinn|7 years ago|reply
ASCII export, so I can put nice diagrams in comments and docstrings. Also possibly (assuming those nice diagrams are unambiguous) a parsing bridge which lets me convert them into data.
[+] [-] gregoire|7 years ago|reply
[+] [-] nosequel|7 years ago|reply
[+] [-] thegambit|7 years ago|reply
https://www.yworks.com/products/yed
[+] [-] ygra|7 years ago|reply
That being said, as a UX guy I always love to look at competitors and find ways how editing can be improved or streamlined (and yEd has many features already, so some parts of it can be more complicated than I'd like).
[+] [-] khendron|7 years ago|reply
[+] [-] therealmarv|7 years ago|reply
[+] [-] clawoo|7 years ago|reply
[+] [-] molszanski|7 years ago|reply
[+] [-] asdkhadsj|7 years ago|reply
Are there any resources you recommend for learning to make good diagrams? Ie, I love documenting things but I don't have experience in drawing diagrams. I don't know conventions for displaying order of execution, what arrows should indicate (in A->B is A giving information to be? is B requesting information from A? etc).
Are there any good tutorials/classes/whatever on drawing good diagrams? Good at conveying information, but also consistent with what educated people would expect?
[+] [-] Jtsummers|7 years ago|reply
https://en.wikipedia.org/wiki/Unified_Modeling_Language
Check out interaction diagrams for what you describe. Two parties (A and B) would be represented as two columns, moving down the diagram means moving forward in time. The arrow going from one to the other is a message (either an actual message or a function call or something). So A->B means A is signaling (the text and context describe how) B. If B is requesting information, you'd have two arrows. First B<-A, and then A->B with the response (attempted plain text version):
A and B could be people, processes, classes/objects, servers, whatever. The interaction points are described with the context of the diagram and text. (NB: t is not meant to be explicit here, I've included it to illustrate the passage of time going down the diagram.)[+] [-] Phil987|7 years ago|reply
With regards to what the arrows indicate, I've done dotted line arrows are synchronous, with a solid arrowhead meaning request body and an outlined arrowhead being the response. Then used solid black line with a single solid arrowhead for an asynchronous request.
[+] [-] sbhat7|7 years ago|reply
1. http://www.fmc-modeling.org/quick-intro
2. https://c4model.com/
[+] [-] aratno|7 years ago|reply
https://whimsical.co/flowcharts/
[+] [-] betageek|7 years ago|reply
[+] [-] delib|7 years ago|reply
[+] [-] eddyg|7 years ago|reply
The types of diagrams you can create is quite extensive: https://about.draw.io/features/examples/
and the diagrams generated are easily integrated into MediaWiki installations, with full editability.
draw.io online is a free-to-license web application for everyone. It is completely free to use for any purpose, there is no premium pay-for functionality, watermarking, or other limitations. You own the content you produce with draw.io and may use it for any purpose, including commercially. We don’t sell your personal information or data. We don’t store your data. You own your data and the application is open source.
Code here: https://github.com/jgraph/drawio
[+] [-] akuji1993|7 years ago|reply
I'd advise you to post this again when you have an actual software to show, that people can test out. I won't sign up for anything and I believe a lot of people don't really want anymore newsletters and sales pitches in their inbox.
[+] [-] khannate|7 years ago|reply
[+] [-] copperx|7 years ago|reply
[+] [-] AdieuToLogic|7 years ago|reply
0 - http://graphviz.org/
1 - https://codeyarns.com/2017/10/21/how-to-convert-dot-graph-to...
[+] [-] foxes|7 years ago|reply
https://github.com/otfried/ipe
It would be nice to improve the interface a bit.
[+] [-] turnersd|7 years ago|reply
[+] [-] pyman|7 years ago|reply
Because most decent Mac apps become shareware once they hit version 1.0.
Also, there’s no doubt in my mind that all these utility apps will be web-based in the future. Google Docs and Google Drawings are great examples of this.
Having said that, I wish you the best of luck with your project.
[+] [-] bluetidepro|7 years ago|reply
[+] [-] zumu|7 years ago|reply