Mail Archives: geda-user/2017/02/15/15:05:19
--Apple-Mail=_27017DF1-CD18-4A8C-8EE4-CF3AEEEE8730
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Feb 15, 2017, at 11:37 AM, John Griessen (john AT ecosensory DOT com) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On 02/15/2017 11:46 AM, John Doty wrote:
>>> > That kind of setup would attract
>>> > more users that don't want to code on the tools, just use them, =
(and test them=85).
>> I can=92t understand why any such users would choose gEDA
>=20
> Oh, there are tons of engineers that can:
>=20
> see the benefit of a makefile driven method,
> know that customizable matters for driving tools to make layout and =
schematics,
> think that a directory full of files is a plenty good organization =
method for a project,
> can do engineering on linux or windows or OS-X,
> write scripts and makefiles to automate steps of their work,
Yep. Natural gEDA users.
> but stop short of developing the software tool, since they are
> developing circuits or whole products and there's a lot to do=85
Except that many parts of the toolkit they employ are *user* =
contributions, not from the core developers. Consider Scheme =
contributions from Martin Lehmann, Matt Ettus, Dan McMahill, Carlos =
Nieves Onega, Braddock Gaskill, Bill Wilson, Dan White, Takanori =
Miyamoto, Wojciech Kazubski, Bas Gieltjes, Stuart Brorson, Jaume Masip, =
Mike Jarabek, Nuno Sucena, Eduard Moser, Magnus Danielson, Frank =
Thomson, Stefan Petersen, and certainly more whose names are harder to =
find. These are the giants upon whose shoulders we stand. Then there are =
numerous special-purpose scripts. Lots of symbols, some in the =
distribution. Many of these contributions are on gedasymbols.org, not in =
the distribution.
gEDA invites user contributions at all levels. That=92s what I want to =
promote. That=92s why Vladimir and Peter=92s work on making gEDA more =
friendly to scripting is so important.
>=20
> That leaves out people who think makefiles and project dirs are "too =
fussy",
> which still leaves a ton of engineers and some hobbyists.
>=20
> Those hobbyists seem to resemble the hacker/maker type, who does =
microcontroller and app coding.
> There are quite a few of those too.
The essential problem, of course, is that even in this restricted =
landscape, one size does not fit all. Different toolkit personalities =
fit different users: that=92s the advantage we can have. They=92ll still =
be dependent on more advanced users to make the scripts that fit their =
flows. We can=92t count on a few developers to do this.
>=20
> It's not a bleak landscape at all.
>=20
I agree.
>=20
>=20
>=20
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_27017DF1-CD18-4A8C-8EE4-CF3AEEEE8730
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYpLPQAAoJEF1Aj/0UKykR084QAIr/myGM6YfrtEF5m9XRO/vT
PoLy/9hChgalS6tViig6p7OJOT7qii5GWPXSIe5mmg+fF1JZp85iWsQ/PRMcsZd8
ghbqOIy7wEo6pK49b3Mnz9BDd8IfcxZz4VPDZr/RzAVcGLBT38eO8l1Y08nfQHN9
6If/Usm1U4C2nBKqELfGvL/ohKgDZg76nscv6ne+f+GRo6+BCTuSOO3IPa4zUrXb
99x7KHsOjJwx3oPdgZqFJkjnINqWz8eYPneob3zZMPfRY0qeG99cP0A+mtrVp22E
unnjKMR2rXBxmu6yJVE/0bxI1qQXlXwF3z1dL2GfPFNr+z8bzwgu8T7+gZKdkBcs
LnvzbPIRonnrepgnPJHniXuCtBxx4HfXwN3dzwLBG17ekzkka0x9dz/agv4520GZ
IyclbPBBLm210rGowcaHPOp7YEp6tHsFybrU4vas+X9Xcw/vlmScM+Cv6OBIB8Hr
k++bOd2zEIqupMBHnidirmo3cGjzGuPaZLKFlv1OF2R5p1PRMGJ5UkWEvbAyunyG
hm8YUH0NU0imX9KQvzR8OChPKU57vv5Xup7dLd/OxprQr6W7LQ3T2BlI6NrwlB3Y
46rnq57WTuHYZ83j4maio6VD8fQePTujgjsEp3TqKlo3L/XRwZoQ/CXfT+Hf3seR
eKvV8vE4hX0R83ZqnoQp
=xsNe
-----END PGP SIGNATURE-----
--Apple-Mail=_27017DF1-CD18-4A8C-8EE4-CF3AEEEE8730--
- Raw text -