[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gEDA-dev: Proposal for a gschem Tools menu for list of scripts
Hi Al Davis,
I forgot to mention, if we only need the filename
as a parameter, the current menu already can
accomodate it, since there is already a scheme
function for it. It is the multiple parameters
which I am thinking about to accomocate.
Thanks again.
Best Regards,
Paul Tan
-----Original Message-----
From: Paul Tan <pt75234@aim.com>
To: geda-dev@moria.seul.org
Sent: Fri, 23 Nov 2007 11:48 am
Subject: Re: gEDA-dev: Proposal for a gschem Tools menu for list of
scripts
Hi Al Davis,
Very true and great advice we can all learn from.
I am glad that gEDA so far has so much potential
because of its flexibility to accomodate lots
of new flexible features. Its all due to you
and others great work, care and considerations
to make it happen.
I hope we can define and implement an easy to use,
flexible, generic menu driven application integration
interface to accomodate many good downstream
tools which will make gEDA more advance, productive
and popular in the EDA fields. Whichever way
we might decide to implement, if we can accomodate a
few additional user input parameters, it would be
perfect.
Best Regards,
Paul Tan
-----Original Message-----
From: al davis <ad151@freeelectron.net>
To: geda-dev@moria.seul.org
Sent: Fri, 23 Nov 2007 10:32 am
Subject: Re: gEDA-dev: Proposal for a gschem Tools menu for list of
scripts
A few more notes ....
What I sent in the last mail was without looking at the existing
files, to show how clear it could be ..
It could use a scheme-like syntax and be just as clear.
New points are:
1. External programs easily.
2. Small, easy to comprehend files, each with a dedicated
purpose.
Lots of programs have huge config files, and a GUI to manage
them. The GUI is a cover for the hugeness of the file.
If there is a GUI to manage the config, it is important that the
files can be manually edited also, and remain compatible with
the GUI. The generated files must be easily readable, so they
can be used to teach the text file format. The generated files
should be at least as readable as good manually created files.
Actually, that "GUI" is not necessarily graphic. Anything that
wraps the real files fits. As an example .. "autoconf"
and "automake" wrap the Makefile like a GUI but without
graphics. It has the same problems as a GUI, hiding what is
really happening, without the advantages.
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
________________________________________________________________________
Check Out the new free AIM(R) Mail -- Unlimited storage and
industry-leading spam and email virus protection.
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
________________________________________________________________________
Check Out the new free AIM(R) Mail -- Unlimited storage and
industry-leading spam and email virus protection.
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev