gEDA-dev: New diagram (attempt at UML)

[Steve Meier]

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



On Thu, 2007-04-05 at 10:18 +0200, Timmerman, Bert wrote:
> Hi Peter and all on the list again,
> 
> A bit more of my thoughts on multiple pages in one gschem file, since I
> was in a hurry this morning when writing the former e-mail.
> 
> What I tried to convey was the idea of concatenating pages into one file
> separated by a next page marker.
> 
> This marker is for graphical representation only, it would only
> determine which symbol/net/graphic entity is painted on which canvas
> (page 1, page 2, etc).
> 
> For example: it would mean that an example design like GTAG could be in
> one single file.
> 
> For the internals of gschem I guess it probably wouldn't require a too
> large rewrite of code (OTOH, how would I know, since I'm not at all
> familiar with the codebase, so apply salt where needed ;-)
> 
> It would probably not break any old gschem files, because if there is no
> "next page" marker until the EOF is reached, it would become a single
> page file when it is loaded.
> 
> For gnetlist backends, gsch2pcb et al, this would mean that they
> should/could ignore such a marker, since it has nothing to do with
> hierarchy in itself.
> 
> For gattrib it would probably require more tabs (one for each page in
> the file) or another column stating the page number.
> 
> For printing the printing dialog should be changed to allow for printing
> a single page (current ?), a range of pages, or all pages.
> 
> When hierachy is involved this approach could be used to avoid multiple
> instances of the same circuit to be drawn.
> 
> For instance: page-1.R101, page-2.R101, ...
> 
> Or with multiple files: file-1.page-1.R101, file-1.page-2.R101,
> file-2.page-1.R101, ...
> 
> Or in short: F1.P1.R101, F1.P2.R101, F2.P1.R101, ...
> 
> Added functions for handling pages in a  single file would have to be:
> 
> - Copy/cut/paste page
> 
> - Page next/previous arrows
> 
> - Insert new page here/Delete page/move page before ...
> 
> Maybe a Google SoC project ?
> 
> Just my EUR 0.02
> 
> Kind regards,
> 
> Bert Timmerman.
> 
> -----Original Message-----
> From: geda-dev-bounces at moria.seul.org
> [mailto:geda-dev-bounces at moria.seul.org] On Behalf Of L.J.H. Timmerman
> Sent: Thursday, April 05, 2007 7:06 AM
> To: gEDA developer mailing list
> Subject: Re: gEDA-dev: New diagram (attempt at UML)
> 
> Hi Peter and all on the list,
> 
> About multiple pages: at the end of the schematic file one could add a
> marker for a next page and add the following pages.
> 
> The demo with tabs Ales showed the other days could be a way to display
> the to the user.
> 
> <snip>
> 
> 
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev