Re: documentation location

[Jean-Christophe Helary]

> On Jan 5, 2019, at 2:20, Alexander Burger  wrote:
> 
> Hi Jean-Christophe,
> 
>> Here is diff for the whole setting.
> 
> Cool, many thanks for this great improvement!
> 
> 
> I have installed it. And the table in https://picolisp.com/wiki/?help looks 
> very
> nice indeed :)

The point being that the last line on the page, with [04jan19]  [brandelune] is 
*not anymore* styled as a table :)

Now, I'd like to work on the ${} thing.

As I described in the help page, the problem with adding a  around the 
selected string is that it creates an extra block and when applied to inline 
contents it puts that contents on a line of its own.

A better way to implement ${} would be to add the style directly to the 
selected markup and, when there is no markup in the selection, to create a 
styled  element around it.

I wish it were easier to work with an ssh to my old raspberry pi, but for now 
that's all I have...

Ok, that's all for today :) Have all a nice week-end.

Jean-Christophe 
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Jean-Christophe Helary]

Alex,Thank you for your patience. And thank you for the explanations.What I did was check the code that was the closest to what I wanted, it was the code for the  tag, and tried to understand how it was working, and, well, I did not understand everything :)Ok, I have something that works. Here is a screenshot:I have a normal table, with an embedded table in the first cell of the second row and all the style is properly applied.Also, the Edit / Reply /  Revision History / admin items (which are also tables) are not affected by the style :)Here is diff for the whole setting.

tableStyle.diff
Description: Binary data
Jean-Christophe On Jan 4, 2019, at 20:42, Alexander Burger  wrote:Hi Jean-Christophe,I'm not good in CSS, so lets assume your proposal is correct, then("%"  # Table   (let Nm (till "}" T)  (prin "")  (ht:Prin Nm)  (prin "" ) ) )this will not work, as (let Nm (till "}" T) ... terminates on the *next*"}", but the table elements are nested.Can you try this:   ("%"  # Table  (prin "")  (recurse T)  (prin "") )A legal table would be e.g.   %{  ~{ |{a1} |{a1} |{a1} }  ~{ |{b1} |{b1} |{b1} }   }Sorry for the hassle.No problem! :)☺/ A!ex-- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Jean-Christophe Helary---http://mac4translators.blogspot.com @brandelune

Re: documentation location

[Alexander Burger]

Hi Jean-Christophe,

I'm not good in CSS, so lets assume your proposal is correct, then

> ("%"  # Table
>(let Nm (till "}" T)
>   (prin "")
>   (ht:Prin Nm)
>   (prin "" ) ) )

this will not work, as (let Nm (till "}" T) ... terminates on the *next*
"}", but the table elements are nested.


Can you try this:

   ("%"  # Table
  (prin "")
  (recurse T)
  (prin "") )


A legal table would be e.g.

   %{
  ~{ |{a1} |{a1} |{a1} }
  ~{ |{b1} |{b1} |{b1} }
   }


> Sorry for the hassle.

No problem! :)
☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Jean-Christophe Helary]

Alex,

The conclusion of my investigation is

1) tables created in wiki syntax must be different from the tables that are not 
user created
→ adding a class="wiki" to their html should be enough
2) to make sure that the CSS applies only to such tables the CSS should be 
modified this way:

/* Table styles */
→   table.wiki, table.wiki td {
border-collapse: collapse;
border: 1px midnightblue solid;
padding: 3px;
}

I'm sorry I'm not proficient enough in picolisp yet to provide a solution.

I tried:

("%"  # Table
   (let Nm (till "}" T)
  (prin "")
  (ht:Prin Nm)
  (prin "" ) ) )

but the result is not at all what I expected :)

Sorry for the hassle.

Jean-Christophe 

> On Jan 4, 2019, at 1:06, Alexander Burger  wrote:
> 
> On Thu, Jan 03, 2019 at 09:38:04PM +0900, Jean-Christophe Helary wrote:
>> Here is the diff for a very simple css for the table.
>> Basically just this:
>> 
>> /* Table styles */
>> table,td {
>>border-collapse: collapse;
>>border: 1px midnightblue solid;
>>padding: 3px;
>> }
> 
> Cool, that's easy! :)
> 
> Released and installed.
> ☺/ A!ex
> 
> -- 
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune

Re: documentation location

[Jean-Christophe Helary]

>> /* Table styles */
>> table,td {
>>border-collapse: collapse;
>>border: 1px midnightblue solid;
>>padding: 3px;
>> }
> 
> Cool, that's easy! :)
> 
> Released and installed.

Nice ! :)
I just added a table to illustrate the table markup.

It looks like there is a glitch in the table CSS rendering. And I'm not sure it 
is a browser cache issue... I'm investigating and if I find a solution I'll get 
back to you.

In the meanwhile, could you check if there is a 1px border around the table I 
just created?

JC
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Alexander Burger]

On Thu, Jan 03, 2019 at 09:38:04PM +0900, Jean-Christophe Helary wrote:
> Here is the diff for a very simple css for the table.
> Basically just this:
> 
> /* Table styles */
> table,td {
> border-collapse: collapse;
> border: 1px midnightblue solid;
> padding: 3px;
> }

Cool, that's easy! :)

Released and installed.
☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Jean-Christophe Helary]

Alex,

The help page is updated. I guess the emacs mode should be too but I can't do 
that today.

Jean-Christophe 

> On Jan 3, 2019, at 19:11, Alexander Burger  wrote:
> 
> Hi Jean-Christophe,
> 
> On Sun, Dec 30, 2018 at 05:09:45PM +0100, Alexander Burger wrote:
>> Another option could be '%' to open the table. The other two '~' and '|' are
>> also still free.
> 
> So I put an absolutely minimal table syntax into "wiki/lib.l". Better than no
> table at all ;)
> 
> I've installed it on picolisp.com, and also released the sources. Can you try 
> it
> whenever you have time? If good, will you also update the help page 
> accordingly?
> 
> ☺/ A!ex
> 
> -- 
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune

Re: documentation location

[Jean-Christophe Helary]

Alex,Here is the diff for a very simple css for the table.Basically just this:/* Table styles */table,td {    border-collapse: collapse;    border: 1px midnightblue solid;    padding: 3px;}JC

wiki.css.diff
Description: Binary data
On Jan 3, 2019, at 19:11, Alexander Burger  wrote:Hi Jean-Christophe,On Sun, Dec 30, 2018 at 05:09:45PM +0100, Alexander Burger wrote:Another option could be '%' to open the table. The other two '~' and '|' arealso still free.So I put an absolutely minimal table syntax into "wiki/lib.l". Better than notable at all ;)I've installed it on picolisp.com, and also released the sources. Can you try itwhenever you have time? If good, will you also update the help page accordingly?☺/ A!ex-- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Jean-Christophe Helary---http://mac4translators.blogspot.com @brandelune

Re: documentation location

[Jean-Christophe Helary]

Alex,

It works fine. There is just a need for some CSS to make it look better. I'll 
propose something later. I'll update the documentation shortly.

Jean-Christophe 

> On Jan 3, 2019, at 19:11, Alexander Burger  wrote:
> 
> Hi Jean-Christophe,
> 
> On Sun, Dec 30, 2018 at 05:09:45PM +0100, Alexander Burger wrote:
>> Another option could be '%' to open the table. The other two '~' and '|' are
>> also still free.
> 
> So I put an absolutely minimal table syntax into "wiki/lib.l". Better than no
> table at all ;)
> 
> I've installed it on picolisp.com, and also released the sources. Can you try 
> it
> whenever you have time? If good, will you also update the help page 
> accordingly?

--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Jean-Christophe Helary]

> On Dec 31, 2018, at 0:26, Alexander Burger  wrote:

>> It could be:
>> 
>> [{ ~{ |{...} |{...}}
>>   ~{ |{...} |{...}}}
> 
> Not a very good idea. It introduces '[' as a new meta-character. Then you have
> to escape it whenever '[' appears in the normal text, and have to document it 
> as
> a special case. It adds complexity and a new syntax concept.

I'm not sure I understand here. If [ comes before { why would it become a new 
meta-character?
Sorry if that's a trivial question.

> BUT: I'm still not convinced that adding tables to the Wiki markup syntax is a
> good idea. It opens a can of worms. You will quickly need more parameters, 
> like
> captions, table headers, column/row alignments, widths and heights, colspans 
> and
> whatnot. Again, we lose the simplicity of the markup language.

You're absolutely right about that :)


Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune



--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Alexander Burger]

On Sun, Dec 30, 2018 at 11:40:55PM +0900, Jean-Christophe Helary wrote:
> t{ r{ c{...} c{...}}
>r{ c{...} c{...}}}
> Of course, it doesn't have to be t, r, c.

This would work.


> It could be:
> 
> [{ ~{ |{...} |{...}}
>~{ |{...} |{...}}}

Not a very good idea. It introduces '[' as a new meta-character. Then you have
to escape it whenever '[' appears in the normal text, and have to document it as
a special case. It adds complexity and a new syntax concept.


> And from what I'm seeing in lib.l where there is no check regarding whether
>  are within  or ,

Right, because "-{" can  render to  in HTML (or \item in Latex) for both
list types.


> my very non educated guess would be that something like the following would
> work:

> ("t"  # Table
>(_render "table") )
> ("r"  # Table row
>(_render "tr") )
> ("c"  # Table cell
>(_render "td") )
> 
> but then, I don't understand (yet) why you're not using letters for the wiki
> syntax...

For the above reasons. Imagine you have (foo () (println '("t" "u" "v") ... in
the article's text. It would render as a table! So the user has to escape it
with '\', and surely be confused about the many rules.

Currently *only* '{' starts markup, so it is still rather KISS ;)


Letters could indeed be used, but are still a little "dangerous", eg. if one
writes abc{def}ghi in the text. Who knows? ;) I feel that a punctuation
character just before the "{" is more visibly distinct and kind of safer.

So I would rather use some other charaters than "t", "r" and "c".


BUT: I'm still not convinced that adding tables to the Wiki markup syntax is a
good idea. It opens a can of worms. You will quickly need more parameters, like
captions, table headers, column/row alignments, widths and heights, colspans and
whatnot. Again, we lose the simplicity of the markup language.

☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Jean-Christophe Helary]

> On Dec 30, 2018, at 23:11, Alexander Burger  wrote:
> 
> Hi Jean-Christophe,
> 
>> I wanted to use tables for that but could not find them in the wiki syntax...
>> Checking the lib.l in the wiki code I found that it seemed relatively simple
>> to add them.
> 
>> Is it a design choice to not have included them ?
> 
> I never really thought about adding tables. Is it really so simple (not the
> implementation, but the markup syntax)? It would need something like the
> *{ -{...} ...} or +{ -{...} ...} syntax for lists. What would you
> propose?

What about this ?

t{ r{ c{...} c{...}}
   r{ c{...} c{...}}}

Of course, it doesn't have to be t, r, c.
It could be:

[{ ~{ |{...} |{...}}
   ~{ |{...} |{...}}}

And from what I'm seeing in lib.l where there is no check regarding whether 
 are within  or , my very non educated guess would be that 
something like the following would work:


("t"  # Table
   (_render "table") )
("r"  # Table row
   (_render "tr") )
("c"  # Table cell
   (_render "td") )

but then, I don't understand (yet) why you're not using letters for the wiki 
syntax...


Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune



--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Alexander Burger]

Hi Jean-Christophe,

> I wanted to use tables for that but could not find them in the wiki syntax...
> Checking the lib.l in the wiki code I found that it seemed relatively simple
> to add them.

> Is it a design choice to not have included them ?

I never really thought about adding tables. Is it really so simple (not the
implementation, but the markup syntax)? It would need something like the
*{ -{...} ...} or +{ -{...} ...} syntax for lists. What would you
propose?

☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Jean-Christophe Helary]

Alex,

>> On a side note, I just modified the layout of the following page:
>> https://picolisp.com/wiki/?AtMark
>> 
>> instead of using preformated markup I used a more linear flow with a list, 
>> and
>> I put more specific links to the references when it was possible.
> 
> Looks good :)

I wanted to use tables for that but could not find them in the wiki syntax... 
Checking the lib.l in the wiki code I found that it seemed relatively simple to 
add them.

Is it a design choice to not have included them ?


Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune



--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: documentation location

[Alexander Burger]

Hi Jean-Christophe,

> It looks like on debian the documentation is put in
> /usr/share/doc/picolisp/
> 
> is it the standard location on linux ?

In fact the documentation is looked up at "@doc/", i.e. relative to the
installation directory.

So if picolisp is in "/usr/lib/picolisp" (as it is on Debian), it first searches
"/usr/lib/picolisp/doc", which in turn is a symbolic link to
"/usr/share/doc/picolisp/".


> I'm asking because the picolisp mode hosted on melpa looks for the doc at:
> /usr/share/picolisp/doc/
> 
> and obviously doesn't find it...


> On a side note, I just modified the layout of the following page:
> https://picolisp.com/wiki/?AtMark
> 
> instead of using preformated markup I used a more linear flow with a list, and
> I put more specific links to the references when it was possible.

Looks good :)


> There is a code example that looks weird, but I just copied the original table
so I can't say for sure:

> (and
>   and (@ (min @ 5)
>   (prinl @)
>   (gt0 (dec @)) .))

Yes, this looks wrong indeed, seems garbled. Looking into the Revision History,
it was already in the first version by Thorsten (tj), not sure how it was
originally intended ...

☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe