Hi Olaf, no problem at all.
For now I'll concentrate on the docs themselves. Hope you can find some time for PicoLisp again. If all goes well I can publish the Arrays section of PLEAC later today :) Best, Arie Op ma 11 jun. 2018 22:31 schreef O.Hamann <o.ham...@gmx.net>: > Hi Arie, > > keep on doing as before, I won't disturb you doing your fine work by > hasseling with my style issues. > > I thought it would be more easy to centralize the special element > formattings you used. > > But I did not realize, that there seems to be no wiki syntax to use css > classes at the moment. > > > So keep on copy-pasting the text-formatting for the especially formatted > text portions, we could fix that later. > > > I tried to check if I would be able to enhance the wiki/lib.l by myself, > > but I stumbled into pil running problems and was not able to install a > fresh picolisp as I did years ago, > > so I have to put this aside for the moment. It seems that I'm out with > coding picolisp for too long. Very sad. > > So I'm looking forward for further nice doc examples written by you, > > and hopefully get more time for picolisping in the future :-) > > > Apologize for the trouble, > > Olaf > > > > On 11.06.2018 12:49, Arie van Wingerden wrote: > > Hi Olaf, > > > > as far as I understood Alex the main CSS file currently used is > > maintained centrally. > > > > If you download https://software-lab.de/wiki.tgz > > <https://software-lab.de/wiki.tgz> you can extract the file 'wiki.css'. > > I guess that that is the current CSS file for the Wiki. > > > > What I am using currently is 2 specialized CSS styles: > > > > 1. ${color: MidnightBlue; font-family: "Arial Black"; font-size: 20px; > > for headings / paragraphs. I don't think that we really need > > different sizes > > > > 2. ${background-color: LightCyan; > > for explanations that deserve to stand out a bit > > Maybe you could use another (light) background color; I am not > > sure about that ... > > > > Since I'm not too acquainted with CSS maybe you could update it and > > send it back to Alex? > > Also, if you have better ideas, I'd like to hear / see them :) > > > > Would you do this? > > > > Thx. > > Arie > > > > > > > > 2018-06-11 9:12 GMT+02:00 O.Hamann <o.ham...@gmx.net > > <mailto:o.ham...@gmx.net>>: > > > > Hi, > > > > I meant a way to collect the formatting into a css class, > > then to mark all relevant pieces of text with this class. > > > > So, perhaps it might be helpful - and would not be too diverse > > from the current usage - if the ${...} structure would > > recognize/refer to css classes? > > (or perhaps I missed sth. and there is already syntax for applying > > css class names to portions of the text? > > then please forget the rest of this post) > > > > I think there is no css attribute 'class', so that it could not be > > mistaken. > > > > Rules which one wins if there css attributes *and* css classes > > mentioned, could be left to the browser - I guess, the element > > formatting will override the class formatting. > > > > There can be more css classes be assigned to one element, > > so sth. like > > class: class-a ; class: class-b ; > > or class: class-a class-b ; > > must be recognized by the parser. > > > > Common css notation of css classes is the dot prefixed to a class > > name, > > so if it would be easier to implement, one could > > simply use .class-a .class-b > > but how to divide this from the element formatting in same structure? > > > > > > Instead of: > > > > ${ Example: > > CSS attributes (*) ${text-align: center; > > } 2{PicoLisp Documentation}} > > > > sth like: > > ${ Example: > > CSS attributes or class names (*) ${text-align: center; > > class: hilited-background; > > } 2{PicoLisp Documentation}} > > > > and defined in css file: > > hilited-background { background-color: black; color: white; } > > > > > > > > > > > > On 09.06.2018 17:40, Arie van Wingerden wrote: > > > > Hi Olaf, > > > > thx! > > > > Per accident I stumbled on the possibility of adding a per > > elemnt CSS > > style, since it wasn't documented at that moment. I added that > > to the > > Wiki doc here: https://picolisp.com/wiki/?help > > <https://picolisp.com/wiki/?help> > > > > Maybe there is a way to define classes etc. and use those. > > I guess Alex would be the one knowing best, since he invented > > this Wiki :) > > > > For now I have no problem with it and I can change things very > > fast. > > > > @Alex Is there a way to do so? > > > > TIA, > > Arie > > > > 2018-06-09 16:20 GMT+02:00 O.Hamann <o.ham...@gmx.net > > <mailto:o.ham...@gmx.net> > > <mailto:o.ham...@gmx.net <mailto:o.ham...@gmx.net>>>: > > > > > > Hi Arie, > > > > I do like your work on the documentation very much, no > > question. > > > > No doubt about the code content, if there sth would be wrong, > > everyone would notice it. > > > > > > But colors and font sizes are, besides look and feel, also a > > matter of individual visual capabilities, > > > > so it might be that one day (as the small picolisp > > community seems > > to be very faithful and gets older with the core :-) ) > > > > s.o. decides to change the coloring of the wiki pages or > > will let > > the reader change the font sizes themselves. > > > > > > Would there be a way to use css classes instead of styling > > each > > element individually? > > > > It would make work easier on both sides writing and changing. > > > > I don't know the wiki docs and if a css class syntax is > > provided > > and I'm very sorry that I did not look it up, > > > > but your progress in work adds so nicely page for page, that > I > > thought I have to say it now, > > > > regardless that I do not have a solution or workaround to > > offer at > > the moment. > > > > > > Perhaps other reader of this list know, if there is already > an > > easy way to express in wiki syntax what will result in sth > > like > > this : > > > > <p class="chapter-intro">....</p> > > > > <div class="examplet-title">....</div> > > > > to match the corresponding css (being defined in same html > > file or > > in extra css file): > > > > chaper-intro { background-color: LightCyan ; } > > > > example-title { color: MidnightBlue; font-family: "Arial > > Black"; > > font-size: 20px; } > > > > > > Greetings, Olaf > > > > > > > > > > On 08.06.2018 15:59, Arie van Wingerden wrote: > > > > Hi, > > > > the last days I did a refresh of parts 1 .. 3 of PLEAC > > docs. > > > > At first I'd tried to get a nice reading experience by > > having > > lightblue backgrounds for paragraph titles and yellow > > backgrounds per example. > > > > Having done it that way, in the I found the reading > > experience > > far from pleasant. > > > > Also I noticed that the H1 .. H6 markup of the Wiki > > are either > > very big and/or faint. So I only use one at the top of > > a page. > > > > I now did the following: > > - use a self specified font (CSS) for headings (not > > too big) > > - copy the paragraph numbers originally used > > - display the "problem description" from the original > > book on > > a very faint color blue. > > > > Personally I think this is a great improvement. Now I can > > continue with peace of heart with the rest of the > > PLEAC docs :) > > > > Hopefully this will make these docvs more accessible. > > Maybe it > > is an idea if I use those headings on other pages as > > well? It > > seems less awkward than those very big letters .. > > > > Best, > > Arie > > > > > > > > -- > > UNSUBSCRIBE: mailto:picolisp@software-lab.de > > <mailto:picolisp@software-lab.de> > > <mailto:picolisp@software-lab.de > > <mailto:picolisp@software-lab.de>>?subject=Unsubscribe > > > > > > > > > > -- > > UNSUBSCRIBE: mailto:picolisp@software-lab.de > > <mailto:picolisp@software-lab.de>?subject=Unsubscribe > > > > > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
