Re: Bus Object

On Thu, Jul 8, 2010 at 1:44 PM, William Van Hecke <[email protected]> wrote:

> On Jul 8, 2010, at 8:58, Alan Hawrylyshen wrote:
> > I think this isn't about the object form as much as it is behavior.
> > If you extend a bus, it will not move the connected components
> proportionally -- as happens now.
> > Can this behaviour be changed? If so, how? That would make me stop using
> mscgen and other ugly tools for my MSC / network diagrams :-)
>
> Would it work to use a long table of small objects? Then you could drag to
> add more cells to the end of the table without affecting the existing
> cells._______________________________________________
> OmniGraffle-Users mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/omnigraffle-users
>


The h3c site has a simple example..

http://www.h3c.com/portal/res/200806/03/20080603_627191_image004_607206_1285_0.gif

A main line; from which connectors extend with one end permanently anchored
to the main line, but not one spot.  The mainline end of the connector
changes position of the mainline in an attempt to remain perpendicular.  If
the connector is being pull to an object in a position that does not allow
for the connector to remain perpendicular, then I'd like to see configurable
behavior there.   Either the connector should attempt to remain straight, or
it should effectively extend the mainline and elbow to stay perpendicular.

I've seen a version of the bus object in visio that has two connector
'spots'.  When you grab a spot and pull, a connector is created.  The effect
is to have a bus object with infinite connectors, rather than the 5 or so
visio tends to include by default.

I need to be able to label the mainline.  I tend to label them with
subnet/mask, VLAN ID, and description; 192.168.0.0/24 VLAN 620 Front-end
DMZ.

A feature that visio does not have, but would be nice, is a label of the bus
connector.  I could place hostname and/or IPs on the connectors;
www.site.com<CR>192.168.0.1.

When I design/diagram networks, I create a layer 1/2 diagram for the
switching, VLANs, physical connections, spanning-tree etc; and a layer 3
diagram for the routing, routing protocols....   Most of the time, the layer
3 is the most important for troubleshooting, thus some kind of bus object
needs to be available.

It seems to me that some of the functionality is already present based on
the Video Tutorial - An Introduction to OmniGraffle 5.  When the speaker
creates the Org Chart, the connecting lines seem to appear like a bus..   I
need a similar look, without the automatic re-arrangement behavior or the
need to build an outline.

Thoughts?