circR

[Mike Pechkin]

hi all,

I've create cool abstraction.
Works as circular list and after reset can count again from the beginning.
Used in Threefish implementation.
Usage example:
http://pastebin.com/dwSiNQgu

Code:
https://bitbucket.org/mihailp/tankfeeder/src/d38de78a9609d31a917ca73f8b8d9fe302afc5b8/circR.l?fileviewer=file-view-default

Code comments are welcome.

Mike

Re: Tractatus Pico-Blaesicus

[Mike Pechkin]

Do you mean https://en.wikipedia.org/wiki/Merab_Mamardashvili ?
>
> ​Yeap.
​


> And could you please provide us with an English version ?
> The automated translators that I tried produced nothing readable
> (but I guess the original is somewhat «tarabiscoté»).
>
> ​I cant.

Mike
​

Re: Tractatus Pico-Blaesicus

[Christophe Gragnic]

On Tue, Mar 8, 2016 at 9:45 PM, Mike Pechkin  wrote:
> hi,

Hi Mike,

> in the beginning of year I've wrote special preface for Forth or coding in
> general. In memory of Descartes. It describes zero step before coding.
> in Russian:
> https://medium.com/@tankfeeder/preface-8ea1e99d46f1#.yziufldc6
>
> p.s. My philosopher is Mamardashvili

Do you mean https://en.wikipedia.org/wiki/Merab_Mamardashvili ?

And could you please provide us with an English version ?
The automated translators that I tried produced nothing readable
(but I guess the original is somewhat «tarabiscoté»).


chri

-- 

http://profgra.org/lycee/ (site pro)
http://delicious.com/profgraorg (liens, favoris)
https://twitter.com/profgraorg
http://microalg.info (langage de programmation pédagogique)
http://expressions.club/ (structure des expressions mathématiques)
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Tractatus Pico-Blaesicus

[Jakob Eriksson]

Hey, I love this Tractatus!

Very unbiased and fair. (Even acknowledging 2.4!)




On 07/03/16 19:25, Alexander Burger 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 '' 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

Re: Tractatus Pico-Blaesicus

[Mike Pechkin]

hi,

in the beginning of year I've wrote special preface for Forth or coding in
general. In memory of Descartes. It describes zero step before coding.
in Russian:
https://medium.com/@tankfeeder/preface-8ea1e99d46f1#.yziufldc6

p.s. My philosopher is Mamardashvili


Mike



On Mon, Mar 7, 2016 at 8:25 PM, Alexander Burger 
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 '' 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
>

Extending the wiki markup syntax

[Erik Gustafson]

Hi list,

I keep returning to this idea, so I thought I'd do a little
write up and share it with you all.

tldr: A thought experiment about extending the wiki markup
syntax to inclued mechanisms for input forms and DB entity
linkage.


I've been spending a lot of time with the wiki, working on the
new website (more on that in the coming weeks). Along the way,
I've found myself desiring a couple features. Notably, the
ability to attach arbitrary CSS to particular wiki documents.
I imagine attaching a CSS file to a document, much like we can
already attach various media. Then (with some markup extensions)
we could access the classes/id's from that file. Maybe something
like:

   1.myClass{My Header styled with 'myClass'}

   1.myClass.myOtherClass{Another Styled Header}

   1#myId{Header with id 'myId'}


or added to the end...

   1{My Header styled with 'myClass'}.myClass


or as "metadata" inside the braces...

   1{(.myClass .myOtherClass) My Styled Header}


I'm sure many syntax possiblities exist. That led to me
wondering what other things might be possible using a wiki-like
markup, which, taken to its logical extreme, was 'Well couldn't
we write entire GUI's using a markup syntax?' Maybe brackets
could serve as a "frontend" to 'gui':

   [+TextField 40]

   [+Able +PwField '(not *Login) 10
  "Password" ]

   [+E/R +NumField '(nr : home obj) 8]

   [+Button "My Stylish Button" '(doSomething)].stylish


or alternatively,

   +Button.stylish["My Stylish Button '(doSomething)]


Again, many possibilities for the syntax, that was just what
came to mind.


Some variation of the wiki could then be used as a CMS. It
could allow to create PicoLisp DB architectures graphically, as
well as provide the means to build the user facing pages for
manipulating the DB. In a nutshell, it would be a PicoLisp app
for creating PicoLisp apps, with a powerful markup language to
intuitively build dynamic content with little "actual code".

I guess the point of all this would be to further abstract the
application development details. No need to worry about
'action', 'html', or 'form'. Maybe no need to worry about
"coding" at all.

This might be a cool idea because:

  - It could open up PicoLisp application development to a
much wider audience.

  - It might be fun/powerful/fast to create apps this way,
especially non-programmers.

  - If it did open up PL app development to a wider audience,
there could be consulting work for those of us who
actually know what's going on under the hood.


This might be a total flop because:

  - It might not be possible.

  - If it is possible, it would likely be a lot of work to
implement, especially to "get it right".

  - Would anyone actually use it?

  - It goes against the PicoLisp philosophy? There would
certainly be some magic going on behind the scenes...


I wanted to share this, if only so I could stop thinking
about it :) Chime in if you find it interesting!

Thanks and be well,
Erik

Re: Tractatus Pico-Blaesicus

[Alexander Burger]

Hi Erik,

> It didn't occur to me that we could use the "!" syntax
> as you did to generate css. Would something like this work as well, to
> temporarily overide definitions in CSS files?
> 
>(html NIL "My Page" (list *Css "!my-css-tweaks") NIL
>   ... )
> 
> I don't know if that would actually be useful, just thinking aloud.

This should work. However, the browser still believes this is a file,
and it will cache the result instead of calling it each time. So it is
not a dynamic on-the-fly CSS generation.

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

Re: Tractatus Pico-Blaesicus

[Erik Gustafson]

Hi Alex,

>
> 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 '' structure,
> with the hierarchy based on the individual indentation levels.
>

This is really neat! It's great to see a more "substantial" use of a
read-macro in the wild. And I'm impressed (though not surprised) by
how concise the code is :)


> 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).
>

It didn't occur to me that we could use the "!" syntax
as you did to generate css. Would something like this work as well, to
temporarily overide definitions in CSS files?

   (html NIL "My Page" (list *Css "!my-css-tweaks") NIL
  ... )

I don't know if that would actually be useful, just thinking aloud.


> 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.
>

Looks pretty good to me. More links could be added, especially for
the DB/Pilog/App Framework. Maybe some links to examples for
'Equivalence of Code and Data' too, and how it makes the language
more expressive in practice?

I also enjoyed the suspense generated by having to click through the
menu.

Thanks for sharing!

-Erik