From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by hurricane.the-brannons.com (Postfix) with ESMTPS id A555177AA1 for ; Sun, 8 Sep 2019 11:28:25 -0700 (PDT) Received: by mail-wr1-x436.google.com with SMTP id q17so6722685wrx.10 for ; Sun, 08 Sep 2019 11:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=hOmeghCQe97J6ZmSGIof4l9NaB8GTtEotkzmrvNpk90=; b=Wpjl3ILwz65xyk6gfNQgxjPyw4UNwxbAXw34sWi+ythpzbQ6em9cAALQmLzZmK7W3V iACfPc1YjbH0Ohy534jmB/i8mixsfymsfm9eeBWZV3dcufSQanJKMwqW8gjQ9I9RJx/d ozHx+NiYgXxmGny9EtglPmS6VsV522g2lhiziB6Pr0Gk50h+o3pisDd9f9E4GCkMvA4w nOkrIfzJVt3VY0bK45uUSSsnIYe9qFsq/yjd2qZPg8SgHo3nFEX3S+n+zgoS7mkV4jRC 8IYZtM+HUmU259uNBua0uljMCAPJkBnkqzNsWY+ej7tcI+gSGB6oe14x1fsjO7mgnRk6 tYTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=hOmeghCQe97J6ZmSGIof4l9NaB8GTtEotkzmrvNpk90=; b=q7H3TElMSVATXNKrObXB+y/eVEruqbUPDkwqPv05h6uL11mRHRBhMoN1wUq7uf3Gu9 zQVtWDN5kctP1k+uKTaI+kVUuGryXwEQFlzlnPJCYgyIPWXR2hM36yTZRA5Zay+X1kku T/5dAhSoAcO+51rphwBh6xQXrB/I0T43AdKzg4Vx9TKGPUD+tYPbP72ip/jq5E8xe0yV 1UX+icNWR3M8GMZV641yC6NZhDCY/ilDeErV60wvh3wcbJIMcN/1QBhBLRVVUdYuA7MI S6WV+Lt93gRGqdncbJThIPWLDkWCAAZwfL78nAXNcwABmygOGa3+Zdh1VB3Xvc5VIEn4 I83w== X-Gm-Message-State: APjAAAX8ovIpb8uz9O2BmnD8Qfcd+QSqOeS5KlEEBmZ2DjTiC6DEc7wm agiUx6gB7JVEEOiaXD6z1UM= X-Google-Smtp-Source: APXvYqyH9kCvPJ5PjNPNrQExSjFwlY8Jl1nww1i/qCup1zr4sh8ZBnMBfXiRlXJDaTJW2392KX55hw== X-Received: by 2002:adf:f543:: with SMTP id j3mr16480777wrp.243.1567967304216; Sun, 08 Sep 2019 11:28:24 -0700 (PDT) Received: from toaster (43.77.155.90.in-addr.arpa. [90.155.77.43]) by smtp.gmail.com with ESMTPSA id y12sm4252094wrn.74.2019.09.08.11.28.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 08 Sep 2019 11:28:22 -0700 (PDT) Date: Sun, 8 Sep 2019 19:28:15 +0100 From: Adam Thompson To: Karl Dahlke Cc: edbrowse-dev@edbrowse.org Subject: Re: [edbrowse-dev] Playing With Colors Message-ID: <20190908182815.GA2774@toaster> References: <20190807090036.eklhad@comcast.net> X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190807090036.eklhad@comcast.net> User-Agent: Mutt/1.10.1 (2018-07-13) On Sat, Sep 07, 2019 at 09:00:36AM -0400, Karl Dahlke wrote: > Well it's just an experiment. > If we don't like it I can comment out a couple lines and it sort of goes away. > If we do like it then I need to document it. > > Not sure when I'd even use it, except for those sites that say > refer to the blue section below > or > your entry is invalid please refer to the items marked in red > This happens sometimes but not often. Still it's a cool idea, particularly when talking to people and you get instructions like "click the completely uninformatively (but purple) named link, enter 42 into the green box and then type a selection of random words into the blue box but in no way fill in the pink one, click the red button and not the green one and then you've completed some mandatory HR/business related thing" (and yes that's how I feel when I get some emails about how to use some web apps at work). At least I can now work out which parts of the web page they're referring to. > Colors (from the css sheets) are almost always rgb values which is borderline useless, > so I convert them to the closest standard color. Good thinking, though it may be worth being able to display the rgb values as well just in case something's odd on a particular page (unless it's a lot of work to have that as an option, even more obscure I suppose). > I'm using nonascii (for the first time) symbols to demark a color section, > and I sort of like that but sort of don't, > but we're so badly overloading the ascii symbols that I don't know how long we can keep doing that. > I should probably use other unicodes to demark invisible sections, hover sections, frames, etc. > > The ease of use depends on how you set up your adapter, > which is the nice thing about moving to higher unicodes. > You can have your adapter say > color start, color end > or just start end, or in out, or whatever. > Probably anything is better than double less than or whatever it says by default. I know speakup says "double left angle" and "double right angle" and as a speakup user I'm fairly happy you've gone for a unicode it (or more correctly the espeak soft synth) understands. I guess that's my one concern with going non-ascii particularly if we start using the more odd corners of unicode. However I agree with the decision to explore this. > To play with it, browse any site, > and type colors > a toggle command, > which means colors+ and colors- will work. > You'll see things like > > :red≪{contact us}≫ > > Or color start and end around a whole menu or section, etc. > Have fun, and send me feedback. Yeah, will do.