X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=1/xuVuwL6W59EMW72hl0DA1IIw6OcULL/ru41QBXIQk=;
	b=xAyx0ShRbVedAgIoZLhQ63aays54oTY3zSStWzF7q79H2jTgI2BekInjC36CFAcPgs
	wFBik0FDn+7dlutl6oYomkiCe1KVyg0mcyvq+rXeDDU9SywoMfrxAkRa+ysk/D3prndJ
	wGd4v2IaFhLZi8T6s2LynPQyBqtH1G+ObGDwy5OmNensrCDyYBhfrpS2ehqByvlQuTV3
	YKsWrMQz8sEcpQMkUr8fleG2R+hmJyeySIWBo/MXfMpN/fiPc8efq6H6C+GBYP84TPil
	sD5JLrVaIDkPGb0Qk/2/OBHZ5XmEjV+VLkTmLTUveMYWf9V0vKRWdi7ZICiInUhAbKYS
	mR1w==
MIME-Version:	1.0
X-Received:	by 10.112.160.73 with SMTP id xi9mr21505761lbb.92.1440441264348;
	Mon, 24 Aug 2015 11:34:24 -0700 (PDT)
In-Reply-To:	<55DADE5A.4020902@jump-ing.de>
References:	<55D8D8B8 DOT 7050907 AT jump-ing DOT de>
	<20150822230549 DOT 3750 DOT qmail AT stuge DOT se>
	<55D9A5AE DOT 9090604 AT jump-ing DOT de>
	<C2FC0AF3-DFDB-4799-87F7-039614405DCD AT noqsi DOT com>
	<55D9BC06 DOT 9060106 AT iae DOT nl>
	<55D9C34A DOT 2090709 AT jump-ing DOT de>
	<C55E2A02-99F7-402C-953F-8E844004D61B AT noqsi DOT com>
	<201508232341 DOT t7NNfl9O012371 AT envy DOT delorie DOT com>
	<CF6D95DF-9FBF-48F6-8E68-458A2BC14CAF AT noqsi DOT com>
	<CAM2RGhS9QqDq2dZLwt7LfUFwQouCaX-SuxEu0U2ofNrxuttmhg AT mail DOT gmail DOT com>
	<55DA8231 DOT 4010904 AT mcmahill DOT net>
	<55DADE5A DOT 4020902 AT jump-ing DOT de>
Date:	Mon, 24 Aug 2015 14:34:24 -0400
Message-ID:	<CAM2RGhRd+JgbaxpM9wbqXYLWRrtc6FAw9ubwM42JFTytf8yEng@mail.gmail.com>
Subject:	Re: [geda-user] Antifork
From:	"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t7OIYUvX013001
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, Aug 24, 2015 at 5:05 AM, Markus Hitter (mah AT jump-ing DOT de) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> Am 24.08.2015 um 04:32 schrieb Dan McMahill (dan AT mcmahill DOT net) [via geda-user AT delorie DOT com]:
>> If anyone wants to try and run with it, I have ideas that I started
>> implementing the framework for, on how to get that "make me a pcb"
>> and "simulate" button without it being so restrictive as to break the
>> tool for others.  The basic idea was make sure that gschem had a well
>> defined interface for something like a simulator.  The simulator
>> would provide a file that basically says:
>>
>> - I need a menu with these options
>> - Here is a set of attributes that the user will need a dialog to
>> configure (btw, look at the dialogs in PCB for the export HID's.
>> Those are not hard coded in the GTK or Lesstif HID's but are
>> created on the fly).
>> - Here is what should be run when the user clicks "simulate" or
>> "send to pcb" or whatever.
>
> Sounds pretty complicated. There's a little known tool 'xgsch2pcb' which does all the neccessary stuff already. It has three buttons:
>
> 1. Open schematic.

But most of us use more than one schematic. I have some that I use for
just simulation, others that are just for pcb and some that are
shared. Plus I have fairly involved simulations that the makefiles and
etc automate.

> 2. Open attribute editor.

A few of my workflows do not involve that.

> 3. Open layout.

Not all of my workflows end here. Heck a lot of them end at 1 others
end at spice or multiple spice engines if I am doing tests of the
simulators themselves.

> Looking from the gschem perspective, 1. is obsolete, because the schematic is open already when gschem runs.
>
> No. 2. is redundant, but sometimes convenient.
>
> Clicking 3. checks wether the schematic is newer than the layout and offers to update it. I'm not even sure how it does this, it just works.
>
> That's all. It works nicely with current gschem and pcb. The only problem is, only few people know it and one can easily forget to start with the tool instead of starting with the schematics. Moving these two buttons into gschem would solve both and make the workflow even a bit simpler.
>
> xgsch2pcb has served me very well over the years, never had to touch the command line. Why should I? xgsch2pcb knows better on how to transport information from here to there.

If that has worked so well I suggest you stick with it and leave gschem alone.

>
> Markus
>
> --
> - - - - - - - - - - - - - - - - - - -
> Dipl. Ing. (FH) Markus Hitter
> http://www.jump-ing.de/



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/

- Raw text -