On 11/25/2016 9:30 AM, John Kasunich wrote:
> This looks like a great start.  I've wanted something like this since
> pretty much day 1 of HAL.  But I never tackled it because I'm definitely
> not a GUI programmer.  (Halscope about killed me, thankfully others
> made it into the nice tool it is today.)
>
> Some comments:
>
> As you and others pointed out, font sizes quickly become a problem.
> Part of the reason is that our pin names tend to be long.  Regular
> schematic programs get around this by using pin numbers and
> reference designators, but I don't think that is an option for HAL.
>
> How about this 2-part suggestion:
>
> Part 1 - every component has a type (such as "or2" or "near", and
> an instance name (such as "or2_0" or "near_speed").  The box at
> the top of the component currently contains only the type.  Make
> that box into a two-line display.  One line displays the component
> type, the other displays the instance name.  That box is already
> almost tall enough to display two lines, so it won't increase the
> size of the symbol much.  (Also, the font could be shrunk a bit
> since the pin-name font is already much smaller).
>
> Your call as to which goes on top - I would lean toward instance
> name on top.  In a schematic, an IC might be described as
> "U1/LM741", where U1 is the instance name.  It is far less common
> to write "LM741/U1".
>
> Part 2 - many if not most pin names start with the instance name.
> For example, component "or2_0" has pins named "or2_0.in0",
> "or2_0.in1", and "or2_0.out".  Part 1 above displays the instance
> name at the top of the component.  So it is redundant to display
> it on every pin.  For any pin, drop all leading characters that match
> the component instance name before displaying the pin name.
> That means instead of "or2_0.in0", the pin name will be "in0".
> And "near_speed.out" becomes "out".  These much shorter pin
> names will allow either a larger font or smaller boxes.
> Again comparing to an electrical schematic - if you want to refer
> to a pin in the overall context, you might say "U1 pin 7".  But on
> the schematic itself, the pin is just labeled "7", because it is clearly
> part of the U1 symbol.
>
What you are describing above is what I am planning for subcomponents. 
As it stands now all pins for the and2 component are listed in a single 
component block no matter how many instances there are. So to keep it 
clear with this setup the and2.0, and2.1 prefix to the pin still needs 
to be shown. Once I get subcomponents working I will be implementing the 
exact changes that you are describing above.

Thanks for the input!

Jim

------------------------------------------------------------------------------
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to