Hi Alex,

A very nice piece of lisp code! The only part I didn’t like very much, was the 
yellow color. As usual, I had to tweek the CSS. Here is my variant:

(de tractatus.css ()
   (prinl "html {background-color: #eee;}")
   (prinl "body {margin: auto; max-width: 96ex; border: 1px solid #bbb; font: 
20px serif; background-color: #ffd; padding: 2em 5% 4em 5%;}")
   (prinl "ul {padding-left: 3ex; list-style: none;}")
   (prinl "li {padding: 0.3ex 0;}")
   (prinl "a {text-decoration: none}") )

As I noticed that the clickable lines in the <menu> had tooltips (title), I got 
tempted to check if they were depending on the Accept-Language value 
(no,en-US;q=0.7,en;q=0.3) in my (Firefox) requests, but I didn’t see any 
Norwegian tooltips. Are there other PicoLisp demo apps where the displayed 
texts (or tooltips) are according to the Accept-Language value in the request 
header? I’m just curious. ;-)


> On 7. Mar, 2016, at 19:25, Alexander Burger <a...@software-lab.de> wrote:
> Dear PicoLisp List,
> let me announce a strange little piece of [code?, documentation?,
> pamphlet?] which I wrote up to summarize some of the positions and
> philosophy of PicoLisp.
> In the spirit of Ludwig Wittgenstein I called it
>   Tractatus Pico-Blaesicus
> and it can be accessed at
>   http://picolisp.com/tractatus
> On the top-right of the page is a "Source" link.
> The code is an interesting exercise in itself:
> The HTML entry function 'tractatus' consists mainly of a read-macro
> which parses the embedded plaintext block into a '<menu>' structure,
> with the hierarchy based on the individual indentation levels.
> To have it all together in a single source, the CSS "file" is in fact
> the function 'tractatus.css', as well as the source download link
> 'tractatus.l' (despite their names).
> I suspect that the text is not complete yet, and probably neither
> error-free nor particularly consistent. Let me know what you think
> should be added or changed.
> ♪♫ Alex
> -- 
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to