Proposal for displaying of twisted Pairs #353
Comments
|
The whole file: |
|
I agree to the point that WireViz should have an option to handle twisted pair in a specific way. As I had stated in an earlier comment:
_ @martinrieder in #3 (comment)_ The first thing to discuss is how this would be implemented in the WireViz syntax though. How about introducing a |
|
Yes, I agree this is more of a combination of what is/was already proposed, but I tried to compile it and give a way of how to implement it in graphviz. As for syntax: |
|
Thank's for this nicely presented contribution. It's very good that someone uses ideas from @SnowMB in #3 and taking them further. Be aware that it might be a challenge to combine this with Tutorial 08, but such a combination is perhaps not much used in real life? The dashed lines surrounding each pair might easily be interpreted as a shield around each of these pairs, which is another requested feature discussed in #330, but it should be possible to use each of these two features separately. The suggested cables:
W1:
colors: [RD, BK, IV, BU, GN]
twisted:
- [RD, BK]
- [IV, BU] |
|
@tobiasfalk - my browser wasn't updated with your latest comment while I was writing mine, but I now see we have the same ideas about a possible syntax. |
A small thin line or something else could also work, the dashed line was just my first idea. ´style="dotted"`:
´style="solid"`(could be thiner):
´style="invis"` aka no line (not very clear what is meant):
|
|
@tobiasfalk please also consider coaxial cables, for example inside a VGA monior cable. It may be better to simply call them pairs. There are some special purpose cables that I have worked with, i.e. Twinax or Triax cables that would contain twisted coax lines and double shielding. The latter required each shield to be grounded on opposite ends of the cable. Fancy stuff, but necessary for high EMI requirements... @kvid Thanks for pointing out Tutorial08. I have not practically used it, though I might give it a try. My common use case requires wires of different gauges combined. I prefer to split those up into separate bundles, in order to have some kind of grouping. This idea has also recently been suggested in #268 and #325. Maybe there is not so much difference in having separate groups for (twisted) pairs or any other number of wires that are somehow related. |
|
About Tutorial08, I think just writing the two text lines directly above each other and keeping the wires together could be a good solution.
I think of this more of a "simple" twist (like it is with Ethernet cables, yes they may have a shield per pair, or the old telephone cables), since what I can see the VGA cable for example has a bit more to it than just some twisted pairs, the same is with coax cable. So maybe a changing this to wire pairing of the type "simple" twist. Syntax ?: |
|
@tobiasfalk please also have a look at the many ideas suggested in #56. |
I have not read it completely and only view over it a bit, but this goes pretty fast in to "let's overhaul the whole Wire/Cable system" which could be a good idea or not but is a bit much for this. I would say that the current system does not really Cable's as something that exists and is more of single wires connected to connector or each other. What I wanted to say earlier is that wires can be pared to each other (and then for example twisted or otherwise grouped) and this Issue only treats one special case of pairing wires, but based on this more cases could be added later. And meant: |
|
@tobiasfalk wrote:
That's worth trying out.
I'm not sure what such a Another thing is that this is not valid YAML. The same attribute ( |
|
These pairs than can be part of Cable's, that can not only consist of Wires and Wire pairs but also pull cord and so on(maybe even air pipes). |
Another type could be for example be a shielded twisted pair(CAT 5 or 6 and above) or one could consider a coax or triax cable as paired wires. All these would require a different representation
I do not realy know YAML, sorry |
Twisted pairs is a much talked request and even has the issue number #3.
My Proposal for displaying them for now look like this:
This may not have some fancy twisting of the wires inside the box, but it is clearly distinguishable from not twisted wires (in my opinion even better the really "twisting" the wires, since doing so makes it harder to see what text goes to what wire) and could be used as basis for other types of combining wires with each other.
If #352 is implemented, it would maybe even allow someone to find some kind of "graph viz magic" to twist the wires.
Implementation
This uses the same method of straitening edges as the dashed lines in #350.
The wires are rearranged so that the wires are not spited by their corresponding text, and a Row is added above and below of the wire pair. The Row Above gets the text
Twisted PairorTwisted Pair: <twist rate><twist rateunit>. Then two edges are drawn from the right (east) to the left (west) side of the box to visual split the wire par of the rest, these are always attached to the top (north) of the added rows.Table:
Dashed lines:
The text was updated successfully, but these errors were encountered: