Mail Archives: geda-user/2015/12/24/10:18:44
--fBT78PV5vI5fyuAn
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
John Doty wrote:
> Except that the user needs to be comfortable with SQL.
Or anything that can sit on top.
> With our .sch format, users choose whatever language they are
> comfortable with from a long list: AWK, Python, Perl, =E2=80=A6
I'm not at all comfortable with our .sch format. It appears to
create structure using very strange positional-dependent semantics.
Or is that .sym?
> I want to liberate users, not control them.
The argument doesn't hold because users must learn the .sch format
in order to work with it by hand. This remains true for any format.
One important point is that reusing any existing representation makes
it more likely for users to already be familiar with that format or
language, as opposed to the 0 probability for gEDA-proprietary (open)
formats. Structure must still be understood, but that should be more
in the application domain (EE) rather than in the data storage domain.
//Peter
--fBT78PV5vI5fyuAn
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iD8DBQFWfAy/hR3Q0dhIfEgRArMvAKDU5aAwSHn5r3+XEcttGlcynM9NmQCgvHxP
WtdPEC9v+WwIGbWNfmhYWnk=
=17IX
-----END PGP SIGNATURE-----
--fBT78PV5vI5fyuAn--
- Raw text -