X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=m0iXb9vTsnFnJauNLdT2rZcmaFuj1UXuZRRkDodB2r4=; b=aPD6zseSKoQnBOXsimKibrF7qhn3H9NWXzIy+gZ5/MVRkwMbLFLIXm8C0K15ICVAAy nDanuPNjZHCX640y1KDI7ylm+WPdwZCXu/knxNGiy6H0g1cqfLzzwnbWq4PEXlxZ7Ioo 09sOJlrCm+hSmv4g0re7uMOs7109Pn/FOvUPrFl9e0J9EKFeP2LOKs4VKJ1BB2fy/Rns b1ZvrrLukRBgWOmk1e3WUwdZ4ylVGoJOtgiZcdsiZWhOCmsG9VwyuttCTLkcg8xvrHbn 7qFj8ymfW4WW6rHNTHCFKa+qZ7sbDLvN+SMBnLKdXcvJJN4QGScwPWBEAAvmwvNqQkXC XLaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=m0iXb9vTsnFnJauNLdT2rZcmaFuj1UXuZRRkDodB2r4=; b=f84P6PoIGxGJ8XV9mmMCQlvVSkh3cc64FfwkUAnQfeDp+C+0xiCJf9xp3x/G8ElkMH u3PWj0B1aJkf4Ga9/TQAfbpCyFJtcY8bb5mkzD3tG+8hqDRwNeTe4ZE5GqU/YTYYcopP FMQdvwcG/ueqg88FUvbFI+cq4NN2VGUdT9BL24yTzoL7TPaajbpq7o3X+gEcveS3CWqe fXucM+oTffK7fjepNkgSNpaySMn3dUi5XZdg7W3NafiEk8Cgx4mSJpTiLdqNcH1Y+Ayr H4Ak3bmx4gLHw1frK6/IhXktp9tRUTuxveTPUFmKJPvtf4ueT5hpZ/Q1DWgDjFc2FTY5 AK+w== X-Gm-Message-State: AE9vXwPiuFbvk8IeZmUn//9QZtFhJxRdAgg7Xo0VYotzPTyOvP/jsEQGYxjzBwUusvXO/HOi16vrYK8wM9I3pg== X-Received: by 10.107.171.133 with SMTP id u127mr5823088ioe.102.1473806395558; Tue, 13 Sep 2016 15:39:55 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20160913183902.GB21178@localhost.localdomain> References: <20160824185818 DOT GD14293 AT localhost DOT localdomain> <20160831221409 DOT GA2585 AT localhost DOT localdomain> <20160906213426 DOT GA10224 AT localhost DOT localdomain> <201609071522 DOT u87FM4aD011791 AT envy DOT delorie DOT com> <20160913183902 DOT GB21178 AT localhost DOT localdomain> From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" Date: Tue, 13 Sep 2016 23:39:54 +0100 Message-ID: Subject: Re: [geda-user] Attribute namespaces (was: Can an attribute be attached to text for later inclusion in gnetlist backend?) To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=94eb2c05a152ad058d053c6b4afe 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 --94eb2c05a152ad058d053c6b4afe Content-Type: text/plain; charset=UTF-8 On 13 Sep 2016 7:41 p.m., "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" wrote: > > On Thu, Sep 08, 2016 at 07:44:21AM +0100, Peter Clifton ( petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote: > > I prefer DJ's color of bike shed for its syntactic similarity to names > > paces in certain programing languages. > > OK, let the separator be '::'. > > > > > The idea is solid, and would be nice to see. > > > > Ideally, backends should be able to communicate a list of attributes they > > consume as a means to help populate lists in the gui (if we ever get to the > > point where there is enough "project" concept to determine at schematic > > capture time what backend(s) the user is targeting.) A configuration file > > entry for target backends might be enough. > > What name would you offer for such a configuration option? This is a little tricky. I guess we need to decide if it needs to have a "project::" namespace or similar, or can be a global scope one! I guess it will evaluate to a list of backend names. Such a configuration might be called "target-backends" or "workflow" or something like that. "load-backend" could be a directive or action, and each backend when loaded would register attributes it uses. Peter --94eb2c05a152ad058d053c6b4afe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 13 Sep 2016 7:41 p.m., "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:
>
> On Thu, Sep 08, 2016 at 07:44:21AM +0100, Peter Clifton (petercjclifton AT googlemail DOT com) [via= geda-user AT delorie DOT com] wrote:=
> > I prefer DJ's color of bike shed for its syntactic similarity= to names
> > paces in certain programing languages.
>
> OK, let the separator be '::'.
>
> >
> > The idea is solid, and would be nice to see.
> >
> > Ideally, backends should be able to communicate a list of attribu= tes they
> > consume as a means to help populate lists in the gui (if we ever = get to the
> > point where there is enough "project" concept to determ= ine at schematic
> > capture time what backend(s) the user is targeting.) A configurat= ion file
> > entry for target backends might be enough.
>
> What name would you offer for such a configuration option?

This is a little tricky. I guess we need to decide if it nee= ds to have a "project::" namespace or similar, or can be a global= scope one!

I guess it will evaluate to a list of backend names. Such a = configuration might be called "target-backends" or "workflow= " or something like that.

"load-backend" could be a directive or action, and= each backend when loaded would register attributes it uses.

Peter

--94eb2c05a152ad058d053c6b4afe--