gEDA-dev: New diagram (attempt at UML)

[John Doty]

On Apr 5, 2007, at 11:06 AM, Peter Clifton wrote:

> On Thu, 2007-04-05 at 09:53 -0700, Steve Meier wrote:
>> My take on mutiple pages within one file is that it might conflict  
>> with
>> re-usibility. What if I have a schamtic which is an element of  
>> several
>> pages or even several different projects?
>>
>> On the other hand what if as part of a project management  
>> resolution we
>> tar or jar the files together? Would that occamplish the same thing?
>> Would it have the same above issue?
>>
>> Steve Meier
>
> Some sort of archive is ok, but if this were for a whole design, you
> still have to resolve the question of which schematic pages correspond
> to what sub-circuit in the hierarchy.
>
> I see your point about re-usability though, and not "necessarily"
> wanting to encapsulate the pages within another file.
>
> But - I don't see how encapsulating the pages of one "sub-circuit"
> levels of hierarchy into a single file is too much of a problem. If
> you're sub-circuit is suitably abstracted, it will be re-usable as is.
> If not, you can still copy-paste components from it.

Another thing I'm worried about is that in trying to integrate the  
environment, you'll break the relationship with the standard Unix  
automation. I make a lot of use of makefiles in big designs, both for  
updating things like SPICE subcircuit files when needed, as well as  
auto-generating project documentation using print.scm to create  
drawings that are then incorporated with text and figures from other  
sources. I'd hate to see this kind of thing turned into a manual GUI  
operation.

John Doty              Noqsi Aerospace, Ltd.
jpd at noqsi.com