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;
        bh=/Z3a0f9fMqDvIr8BHoF64bI6+M51ysOFZRqcbWlPR2g=;
        b=NJ/9DszRvLHE8fwtfPjdiAN+0zIs+AjR5+6yZLBv6AHtUglW6ScWhJdYF6cNbyuOE7
         QD7v3njnj8ezzYCtpQR8YlKxjrAoRihzTiTm/O+SXgkmP2zrMhTeeCZSgb4kwLHy87QP
         i/ATD3U6Y2PFI/KhXunTsqSnsCgPGBiMdq59ggan+3C35P/12cZmH2CU6YmUSvVi+caR
         jthsgEx8V0hFMFQRO7TbRKkaFkqKnZmaZOmgQDh5JJTlSR83p45CdPl/KyOtxSUcvmC2
         LHse3VIITQWiP4RMS2/t5VA4aXmv9bPgZ2iWaLEjUMQ7Bqzd/rBjI3xxqCUdHAnn9qSj
         gssA==
MIME-Version: 1.0
In-Reply-To: <87wqvhd4tw.fsf@gmail.com>
References: <87wqvhd4tw DOT fsf AT gmail DOT com>
Date: Tue, 15 Jan 2013 10:40:52 +0100
Message-ID: <CACwWb3Bdxc36D9mhS3_2wmh+pe=VRGEnKJLWTp+Y3kk_thauBw@mail.gmail.com>
Subject: Re: [geda-user] geda-skeleton-project: Lowering the cost of a
 starting a gEDA project
From: Levente <leventelist AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=e89a8f642aa8b9e10804d3508e93
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

--e89a8f642aa8b9e10804d3508e93
Content-Type: text/plain; charset=ISO-8859-1

I also wrote some Makefiles and scripts for a project skeleton creation. I
call it pskel. :-)

http://git.logonex.eu/?p=utils4geda.git;a=tree;hb=HEAD

Levente

On Sun, Jan 13, 2013 at 6:34 AM, Ben Gamari <bgamari DOT foss AT gmail DOT com> wrote:

> In my experience, assembling the framework for efficiently integrating
> gschem, pcb, gnetlist, and the like is one of the more significant
> barriers one must pass in adopting gEDA. While the highly modular nature
> of the gEDA toolchain offers power and flexibility, a fair amount of
> machinery is necessary to make all of these tools work cohesively. This
> is especially challenging for people unfamiliar with gEDA and its
> philosophy.
>
> This weekend I took some time to distill a skeleton gEDA project from
> one of my recent designs. The resulting tree can now be found on
> Github[1] and includes,
>
>   * a script to automate the initial configuration of the project
>   * a Makefile for performing some common tasks (e.g. generating
>     tragesym symbols, updating the pcb layout, and exporting gerbers)
>   * some documentation describing use of the initialization script and
>     Makefile
>   * further discussion to clarify a few common questions about the
>     toolchain
>
> I'm hoping folks will find this useful, if even as only an example of
> how one might structure a gEDA project. Having used the toolchain for
> some time now, it is frustrating to see that so many open hardware
> projects continue to be designed in Eagle and the like. It is my goal
> that this release will lower the barrier to entry of our excellent
> toolchain and facilitate adoption by casual users.
>
> If you can see any way the project or its documentation might be
> improved, I'd be happy to consider pull requests or feedback.
>
> Cheers,
>
> - Ben
>
>
> [1] https://github.com/bgamari/skeleton-geda-project
>
>

--e89a8f642aa8b9e10804d3508e93
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I also wrote some Makefiles and scripts for a project skeleton creation. I =
call it pskel. :-)<br><br><a href=3D"http://git.logonex.eu/?p=3Dutils4geda.=
git;a=3Dtree;hb=3DHEAD">http://git.logonex.eu/?p=3Dutils4geda.git;a=3Dtree;=
hb=3DHEAD</a><br>
<br>Levente<br><br><div class=3D"gmail_quote">On Sun, Jan 13, 2013 at 6:34 =
AM, Ben Gamari <span dir=3D"ltr">&lt;<a href=3D"mailto:bgamari DOT foss AT gmail DOT c=
om" target=3D"_blank">bgamari DOT foss AT gmail DOT com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
In my experience, assembling the framework for efficiently integrating<br>
gschem, pcb, gnetlist, and the like is one of the more significant<br>
barriers one must pass in adopting gEDA. While the highly modular nature<br=
>
of the gEDA toolchain offers power and flexibility, a fair amount of<br>
machinery is necessary to make all of these tools work cohesively. This<br>
is especially challenging for people unfamiliar with gEDA and its<br>
philosophy.<br>
<br>
This weekend I took some time to distill a skeleton gEDA project from<br>
one of my recent designs. The resulting tree can now be found on<br>
Github[1] and includes,<br>
<br>
=A0 * a script to automate the initial configuration of the project<br>
=A0 * a Makefile for performing some common tasks (e.g. generating<br>
=A0 =A0 tragesym symbols, updating the pcb layout, and exporting gerbers)<b=
r>
=A0 * some documentation describing use of the initialization script and<br=
>
=A0 =A0 Makefile<br>
=A0 * further discussion to clarify a few common questions about the<br>
=A0 =A0 toolchain<br>
<br>
I&#39;m hoping folks will find this useful, if even as only an example of<b=
r>
how one might structure a gEDA project. Having used the toolchain for<br>
some time now, it is frustrating to see that so many open hardware<br>
projects continue to be designed in Eagle and the like. It is my goal<br>
that this release will lower the barrier to entry of our excellent<br>
toolchain and facilitate adoption by casual users.<br>
<br>
If you can see any way the project or its documentation might be<br>
improved, I&#39;d be happy to consider pull requests or feedback.<br>
<br>
Cheers,<br>
<br>
- Ben<br>
<br>
<br>
[1] <a href=3D"https://github.com/bgamari/skeleton-geda-project" target=3D"=
_blank">https://github.com/bgamari/skeleton-geda-project</a><br>
<br>
</blockquote></div><br>

--e89a8f642aa8b9e10804d3508e93--