X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 9 Dec 2020 14:47:10 +0100 (CET) From: Roland Lutz To: "karl AT aspodata DOT se [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] automatically create a .sch file containing a single component? In-Reply-To: <20201209073734.B29CC8512092@turkos.aspodata.se> Message-ID: References: <20201209073734 DOT B29CC8512092 AT turkos DOT aspodata DOT se> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) 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 Wed, 9 Dec 2020, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote: > Regarding: > > > why not The former is easier to work with for XML tools (retrieving an attribute is typically simpler than string manipulation to split the combined coordinates). > (and why do you have two "witdh"s in the example ?) That's an oversight; the second one should be "linewidth". > Or why not > B 0,0 17000,11000 15 0 0 0,-1,-1,0 -1,-1,-1,-1,-1 > which would keep related things together and be visually easier to read. > Or have named arguments for the lesser used args., like > B 0,0 17000,11000 15 0 0 dash=0,-1,-1,0 fill=-1,-1,-1,-1,-1 > which could then be simplified to > B 0,0 17000,11000 15 0 0 > which is a more reasonable size for an argument list. These seem like a good compromise between human and tool parsability. However, I'd prefer not to change the file format as long as I can get away with it. Roland