X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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=tDrJlP08XQSvFEsvRlvAZv8ZRaXQWHzk0AeTUQbmk6U=; b=Wn8rF4vk5ImMQd+zBN0TdBA7LCyXggylWYLXEn37hys4/VLwFPpnSk+XL2l8vXMEhU z1OvXto+2Wujm6j8PL5YWVf68WAYKlrSvBp5m3f+r6Cv2/XzfD05hr5+1Wur5mwZLDsJ D64CzukYM9lC5knMUz5BAVtL08/6qgyrMH11fSPm/QTGI3vCp2wunCz22F5M9NjhMnrE fFAY71vViaUE3tXJKF+R19dQ6Gg7f6UcM2cjSyekFgmAabA/eY7RBI9H2/+xHGZRJvxL zeFWfzgRLS+ye3FOaomQGA8lTEE4UBJ43+LtRT9S8SKLQapcHOhevmI6KIxFFiMN5mm/ PWyw== MIME-Version: 1.0 X-Received: by 10.107.135.95 with SMTP id j92mr37102500iod.20.1423077496100; Wed, 04 Feb 2015 11:18:16 -0800 (PST) In-Reply-To: References: <1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk> <20150202152654 DOT GA13336 AT cuci DOT nl> <54CFD589 DOT 9040702 AT xs4all DOT nl> <20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan> <20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de> Date: Wed, 4 Feb 2015 10:18:15 -0900 Message-ID: Subject: Re: [geda-user] FOSDEM From: Britton Kerin To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t14JILH4029515 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 Precedence: bulk On Wed, Feb 4, 2015 at 9:39 AM, John Doty wrote: > > On Feb 3, 2015, at 10:27 PM, Ouabache Designworks > wrote: > > If we could get all the eda teams currently supporting their own tool flows > to contribute to a single open source solution then we would all be a lot > better off. > > > There isn’t a single solution that will satisfy everybody. Many users want > an integrated tool, but that is never going to scale well to complex > projects with a lot of top level automation. Does anybody really imagine > that a single flow can efficiently cover projects from afternoon throwaways > to complex boards for space flight to mixed-signal ASICs? geda-gaf in If they both use PCB boards, there's no reason that those aspects of both projects couldn't share a lot more code than they do now, and do it without disturbing simulation etc. that others are doing. I wouldn't have to be an integrated tool. I think there are really just four things that everyone does: 1. Get or make schematic symbols. Many times this is a box with pins 2. Get or make footprints 3. Hook symbols to footprints 4. Save reusable, pre-layed-out subcircuits somehow There's the light-versus-heavy symbol issue which involves genuinely different approaches on steps 1-3, but probably both could be accommodated in one widely shared solution. Besides this there really isn't much variation in the above so its sort of maddening that everyone gets to re-invent it. Britton