X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 14 Jul 2015 11:38:19 +0200 (CEST) X-X-Sender: igor2 AT igor2priv To: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] The new to do In-Reply-To: Message-ID: References: <0A5D410F-D1EF-4FC6-AF0F-BB13218B1615 AT icloud DOT com> <20150714084906 DOT GC14371 AT localhost DOT localdomain> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 Tue, 14 Jul 2015, gedau AT igor2 DOT repo DOT hu wrote: > > > On Tue, 14 Jul 2015, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via > geda-user AT delorie DOT com] wrote: > >> On Tue, Jul 14, 2015 at 04:16:06AM +0200, Kai-Martin Knaak wrote: >>> gedau AT igor2 DOT repo DOT hu wrote: >>> >>>> I had such an effort years ago. It was a standalone plugin for PCB >>>> of the time. It used GPMI to support multiple languages - not >>>> requiring all of them installed, but letting the user install >>>> language plugins. It supported all the languages you listed above >>>> (gpmi even has a guile backend!). >>>> >>>> Unfortunately it did not attract any user. I think only a very few >>>> people are actually interested in scripting PCB (other than with the >>>> builtin action language). >>> >>> IMHO, the ability to script just every action and even the UI on a >>> user level is one of the strengths of eagle. I get the impression that >>> scripting is used a lot by seasoned eagle users. The way eagle does it >>> with its own exclusive languages (plural!) is a different story >>> though. I'd recommend a look at freeCAD for a more convincing example >>> on how to tackle scripting in a CAD environment. >>> >>> IMHO, to get widely adopted scripting must be readily available in the >>> default install of the suite. Plus, its use must be covered by the >>> manual, by howtos and by first-steps. When these conditions are met. >>> scripting can get quite an asset. >> >> Let's start? >> >> What a first scripting example would you like to see in the scripting >> how to? > > My personal favorite is awk, but it's not widespread anymore. Also, I will try > to list what'd work even against my personal preferences. Please disregard my previous mail. I thought it was about how to fix scripting, but reading it again I am not sure anymore, maybe the question was more about what features the current system should get.