Hi Nehal,
Op ma 25 jun. 2018 om 13:29 schreef Nehal :
> While observing new changes made in picolisp wiki css, I observed on
> https://picolisp.com/wiki/?PCE:
>
> 1. *Numbering* error of headings. 3 comes after 4 again!
>
Corrected.
2. "On Rosettacode you can find a wealth of examples on a
Thx. Manuel!
Op ma 25 jun. 2018 om 14:09 schreef Manuel Cano :
> Hi,
>
> I've corrected the missing quote: ...known "Perl Cookbook.
>
> :)
>
>
> Kind regards,
> Manu
>
> 2018-06-01 17:19 GMT+02:00 Arie van Wingerden :
>
>> The first section of PLEAC (Strings) is now at about 76% ready
>>
>> Some
Hi,
I've corrected the missing quote: ...known "Perl Cookbook.
:)
Kind regards,
Manu
2018-06-01 17:19 GMT+02:00 Arie van Wingerden :
> The first section of PLEAC (Strings) is now at about 76% ready
>
> Some examples are rewritten a little, in order to make it easier for
> people to just copy
Hi Arie,
While observing new changes made in picolisp wiki css, I observed on
https://picolisp.com/wiki/?PCE:
1. *Numbering* error of headings. 3 comes after 4 again!
2. "On Rosettacode you can find a wealth of examples on a huge *scala*
of common programming problems." Perhaps you wanted to
Hi Arie,
On Wed, Jun 13, 2018 at 09:36:09AM +0200, Arie van Wingerden wrote:
> Added that example.
> You'd like it :)
Thanks! :)
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Added that example.
You'd like it :)
2018-06-13 9:22 GMT+02:00 Arie van Wingerden :
> Hi Alex,
>
> please be aware that all those examples were (long ago) created by
> yourself :)
> So all creadits go to you!
>
> I only transfer them to the Wiki, with a nice layout and as simple to use
> as
Hi Alex,
please be aware that all those examples were (long ago) created by yourself
:)
So all creadits go to you!
I only transfer them to the Wiki, with a nice layout and as simple to use
as possible.
So, I only did change a few things :)
Having references to all functions used is a nice thing
On Tue, Jun 12, 2018 at 04:39:34PM +0200, Arie van Wingerden wrote:
> the 'hashes' section is now ready.
Very good again!
For "Inverting a Hash" there is - besides your version of 'cons'ing CDRs and
CARs to an inverted association list - now also a direct way: The 'rassoc'
(reverse assoc)
Hi Alex,
> Is this intended? Or is the third line missing? ;)
>
Indeed; corrected :)
In "4.3.1. Iterate over a list" you could put in addition to the 'for' loop:
>
>(mapc println mylist) # Probably better Mylist
>
Done and done.
> Note that instead of
>
>: (for I (length lst)
>
Hi Alex,
the 'hashes' section is now ready.
Please have a look :)
Best,
Arie
Hi Arie,
> the page on "Arrays" is ready. This was quite abit of work :)
Looks very good! I'm really impressed!
> @Alex Would you please check this page?
Sure :)
It says
This is the first line.
And this the second.
A fourth line.
Is this intended? Or is the third line missing? ;)
Hi all,
the page on "Arrays" is ready. This was quite abit of work :)
In this case I had to dive in a few times and with some great help I
learned a lot from that.
My mindset had to change quite a bit. I worked with other Lisps, which
(almost) all were lexically scoped.
Now I saw quite a few
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 :
> Hi Arie,
>
> keep on doing as
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
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 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.
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
Hi,
I'll have a look first and will let know!
Thx,
Arie
2018-06-10 7:15 GMT+02:00 Alexander Burger :
> On Sun, Jun 10, 2018 at 07:04:44AM +0200, Alexander Burger wrote:
> > In the DB GUI of the wiki (you get there after logging in, and going to
> "My
> > account"), there is a menu entry
On Sun, Jun 10, 2018 at 07:04:44AM +0200, Alexander Burger wrote:
> In the DB GUI of the wiki (you get there after logging in, and going to "My
> account"), there is a menu entry "Upload". Here you can upload another logo or
> CSS file.
Another, probably simpler and safer way, is if you send me a
Hi Olaf and Arie,
> 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
>
> Maybe there is a way to define classes etc. and use those.
> I guess Alex would
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
Maybe there is a way to define classes etc. and use those.
I guess Alex would be the one
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
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
Nice!
Thx.
Arie
2018-06-05 7:33 GMT+02:00 Alexander Burger :
> Hi Arie,
>
> > now the first 2 parts (Strings and Numbers) are complete.
> >
> > Here and there I had to change things a little and also to add a few
> > comments.
>
> Very nice, and well done! A huge piece of work. I think it looks
Hi Arie,
> now the first 2 parts (Strings and Numbers) are complete.
>
> Here and there I had to change things a little and also to add a few
> comments.
Very nice, and well done! A huge piece of work. I think it looks all OK, I could
not find any obvious mistake.
This is becoming a really
Hi Alex,
now the first 2 parts (Strings and Numbers) are complete.
Here and there I had to change things a little and also to add a few
comments.
Sometimes it totally wasn't obvious what kind of input a function expected
(at least for newcomers).
Please have a look and check if things are as
Hi Alex,
thx. for taking time to check!!!
I corrected those points you mention.
Thx. to you too :)
Because I now just try to do this stuff fast, I only have a bit of time to
look at functions in more detail.
I really am impressed by the many useful functions.
Also nice that strings and
Hi Arie,
> The first section of PLEAC (Strings) is now at about 76% ready.
> ...
> Some examples are rewritten a little, in order to make it easier for people
> to just copy and paste the code to see what happens.
>
> I took great effort to verify each and every example.
Pefect! Indeed a *lot*
The first section of PLEAC (Strings) is now at about 76% ready.
Some examples are rewritten a little, in order to make it easier for people
to just copy and paste the code to see what happens.
I took great effort to verify each and every example.
Also I added a reference to all used functions
OK. Now I understand it better.
Well, I'll go for incorporating the PLEAC docs first. At the moment I
already did about 45% of the 'strings' part, so there is progress every
day :)
After that I'll start going over all the wiki pages available and see if I
can come up with a good, accessible and
Arie,
You should probably search for PicoLisp docs on the PicoLisp wiki before
searching Google. There's already tons of links to my docs:
https://picolisp.com/wiki/?documentation
"PicoLisp Libraries - several PicoLisp libraries: unit..."
https://picolisp.com/wiki/?interfacing
"For
Hi Alexander,
for now I added a link to your (very nice) stuff.
Be assured that I intend to change stuff for the better :)
Thx,
Arie
2018-05-31 13:21 GMT+02:00 Arie van Wingerden :
> Hi Alexander,
>
> you are right :-)
> Because I just dived in to help and also reorder stuff, I had to start
Hi Alexander,
you are right :-)
Because I just dived in to help and also reorder stuff, I had to start
somewhere.
I intend to e.g. remove the link to PLEAC when its separate pages on the
Wiki are complete.
As I hadn't encountered your page yet, I just didn't know.
I just fast searched Google
I'm also not sure why there's a link to Alexander Burger's twitter, the
t-shirt, and "Hire a guru" on that page. What does that even have to do
with "Documentation" and "Examples" ?
Perhaps I can suggest moving those links to the home page, and moving
all external "documentation" links to that
Hi Arie,
I'm just curious, how is this (PLEAC) different from the "Other
resources" section of the Documentation page?
https://picolisp.com/wiki/?Documentation
It seems there's a lot of duplicate links. Also there is missing my
"EXPLAIN.md" documents, ex:
On Sun, May 27, 2018 at 05:03:19PM +0200, Arie van Wingerden wrote:
> Hi all,
>
> started to put all PLEAC examples in the Wiki, inorder to preserve the
> material in case PLEAC vanishes sometime, because it is not updated often
> anymore. You could say that is was substituted in some way by the
Hi all,
started to put all PLEAC examples in the Wiki, inorder to preserve the
material in case PLEAC vanishes sometime, because it is not updated often
anymore. You could say that is was substituted in some way by the famous
"Rosetta Code".
Since this it quite a bit of work, I started with the
36 matches
Mail list logo
