On Thursday 24 November 2016 10:08:42 Jim Craig wrote: > Progress report. I have the graphics area drawing, panning and zooming > how I like it. Currently I am just drawing the entire active > configuration on a single design sheet. I plan on keeping this overall > design sheet for the final application. It gives a good overview of > the entire configuration. However, it may get pretty cluttered up on a > large configuration. > > Just for reference I am attaching a PDF printout of the Gmoccapy sim > config design layout. This design layout was initially auto-generated > (Components and signals were placed automatically). Then I used the > drag functionality to drag the components around to the most logical > places and then regenerated the signal paths automatically. No signals > were manually relocated on this layout. > > To declutter I am adding some functionality. Signals can be added to a > selection which then colors them to clearly show which pins they > connect to and the routing of the signal. This feature is shown in the > PDF. Another feature that I plan to add for further clarity of > subsections of the design is the ability to "Isolate" selected signals > and selected components. This would mean that if a component is > selected and isolated only the signals that are connected to that > component will be shown. Any components that are attached to the > selected component signals will also be shown. If a signal is selected > and isolated then only that signal and the connected components would > be shown. I think these features will greatly help navigate a large > configuration. > > For further decluttering the components only show pins that have > signals connected to them. This simplifies the overall design layout > as there can be many pins that are not used taking up space. To > connect a signal to an unused pin you would right click on the > component and select the pin from a context menu > > Some additional features I will be adding is the ability to right > click on a component and select from a context menu to show the man > page for that component. This will cut down on time to look up > documentation for what you are working on. Another feature is to add a > context menu option that will pull up a halmeter for each of the > selected signals if requested. > > I also have to write the code to save the locations of components and > signals to an external file for future use. > > Once I get the above functionality added I will work on processing the > .ini file and the subsequent .hal files to separate the overall config > into separate design layouts that represent each .hal file > individually. This will require adding cross page connectors to jump a > signal from one design layout to another. This will also require > creating a subcomponent item which will take a component like and2 > that can be initialized with count =15 or names = * and split the > component into subcomponents that represent each instance of the main > component. This is to simplify signal routing and allow subcomponents > to be on .hal file design layouts in which they were not initialized. > > Anyway I am very interested in your comments or suggestions. There is > a lot left to complete this program but I feel that I am making pretty > good progress to this point. > > At what point should I commit this to the project so that others can > play with it? > > Happy Thanksgiving, to all of you and for those that don't celebrate I > am sure I will eat enough Turkey for you as well. > > Thanks, > > Jim
One immediate thing I see is the missing rockhopper curved lines, all in the same color, these are more visible, and the ability to highlight/isolate/colorize a signal will be at least as handy as sliced bread. Rockhopper's vector output is nice in that you can make it as big as you need, but the inability of the firefox to blow it up far enough to see the details has me blowing a day each time I use it, printing it out in x pages by y pages then carefully trimming the edges of multiple sheets of 11x17 paper (yes, I have a printer that big) and taping them together on at least half a sheet of light plywood, just to get a big enough output scale that I can actually read the modules name. Paper shrinkage being the random thing it is, getting 6 sheets of copy paper trimmed & cut so the lines truly fit is a job my back screams about. I've done it on 8.5x11 paper, which is why I bought the 11x17 (that includes a scanner that big, with an ADF, which unfortunately does not do duplex, while the printer does at 8.5x11. Commit time? ASAP, I like it. I think it will be a useful tool indeed. Many thanks, Jim Craig Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
