![]() ![]() I tried to rotate it, but the arrowhead kept flipping into different positions. I thought it was odd that the line insisted on originating in the center of the canvas, but it became even more strange when I tried to drag the arrow to the desired location. Using the line tool, I drew the line with a right angle and managed to get the arrow on the correct end. I want to draw a simple arrow that starts in the middle of a hallway and either curves or turns at a right angle to indicate a designated doorway. Then, I selected a new layer as layer 2 so I can show furniture and other furnishings in their planned locations. On my first job, I've imported a PDF file containing a floor plan and assigned it as layer 1. (NB: t is not meant to be explicit here, I've included it to illustrate the passage of time going down the diagram.I just purchased OG Standard 5.2. ![]() The interaction points are described with the context of the diagram and text. First BB with the response (attempted plain text version):Ī and B could be people, processes, classes/objects, servers, whatever. If B is requesting information, you'd have two arrows. So A->B means A is signaling (the text and context describe how) B. ![]() The arrow going from one to the other is a message (either an actual message or a function call or something). Two parties (A and B) would be represented as two columns, moving down the diagram means moving forward in time. I'm not the biggest fan of UML everywhere, but one benefit of it is that certain diagram types are standardized.Ĭheck out interaction diagrams for what you describe. in draw.io you get overlapping shapes when you arrange a diagram with rotated nodes, since for the arrange feature all nodes are apparently axis-aligned and not rotated). generic drawing) or may disregard some of the problems (e.g. Other applications may not have the same constraints (graph vs. We have already implemented rotatable nodes as a demo, so simply adding that to yEd Live would be trivial from a technical standpoint, but we like to care about UX as well. After all, automatic layout is one of our main selling points. For yEd Live we are considering to add the feature, but we're still trying to figure out how to lessen the impact where things don't work well together. What you see and edit is always a graph, consisting of nodes and edges.įor yEd the lack of rotating shapes is a deliberate decision based on implementation difficulty (it's based on an older yFiles library version), workarounds are available (importing arbitrary shapes), and the fact that in a graph drawing application there are several things that don't play well with rotated nodes, such as automatic layout and ports. YEd is actually not really a drawing application, as you cannot (easily) draw generic drawings. 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. >īasically, 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. How about separating out layouting a bit, and letting me type in something like that:Īnd then continue with regular PUML code: Or at least a better way for giving layout hints than soft constraints introduced through invisible links.ĮDIT: A random idea if anyone is developing something PUML-like: I generally like it, but I'd like it 100x more if there was a way to explicitly pin some component to absolute coordinates. No way to do that reliably, the result is very brittle. It's even worse when you have your own opinion about the desired layout. 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. + PUML renderer is technically a free-to-download JAR, so it can presumably integrate well with my Org-mode life. I love working with plaintext for all the usual benefits, so this fits. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |