December 2015 - Pharo-users

Re: [Pharo-users] Smallworlds - Interactive Fiction Framework

by stepharo

> I don't know if this is the appropriate venue to do that, but I'd like to > announce that I finished a stable implementation of a framework for > developing Interactive Fiction in Pharo Smalltalk. Yes it is! Do you have a screenshots or something like that? I have no idea what is a Interactive Fiction: a textual adventure game? > > It is based on an old code written by Bob Jarvis for Dolphin, but it has > been changed so much that it is almost something new. > > This is my first project and I'm still working around Metacello and > polishing stuff up. So I appreciate any code contributions, comments or > thoughts about it. > > It is hosted on Smalltalkhub: > (http://smalltalkhub.com/#!/~ericvm/Smallworlds) > > > > -- > View this message in context: http://forum.world.st/Smallworlds-Interactive-Fiction-Framework-tp4868560.h… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Dec. 28, 2015

Re: [Pharo-users] Smallworlds - Interactive Fiction Framework

by stepharo

Le 28/12/15 13:45, ericvm a Ã©crit : > There is an AdventureShell class made with Spec. You use it like this: > > (AdventureShell world: (CDGameWorld new)) openWithSpec. add it to a class comment somewhere :)

Dec. 28, 2015

Re: [Pharo-users] why Pillar

by stepharo

SaÅ¡a have a look at Pillar and you can add footnotes and we will review your code and integrate it. We are just really busy right now. Stef

Dec. 28, 2015

Re: [Pharo-users] Transcendental #new (was Re: why Pillar)

by stepharo

To conclude this thread, Robert I suggest that you stay on a technical discussion. Do not force us to ban you (we will do it if you continue) because people are distracted. Most of us do not understand all these spiritual points and do not want to read about them in such mailing-lists. Stef

Dec. 28, 2015

Re: [Pharo-users] why Pillar

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 28/12/15 10:43, SaÅ¡a JaniÅ¡ka wrote: > On Pon, 2015-12-28 at 10:21 -0500, Offray Vladimir Luna CÃ¡rdenas wrote: > >> That's why I recommending you pandoc's markdown variant. It has >> extensive support for footnotes, bibliographic references, tables, >> latex, a lot of exporting formats and extensibility via exporting and >> manipulating the Abstract Syntax Tree. Pandoc is also used in >> Scholarly markdown and Jupyter projects so you could use the markup >> language variant with more people beyond this community. > But you're aware that you can also use Pandoc's markdown with Nikola? Yes. I'm but if you read the blog post, you'll see that the main reason for choosing grav for almost everything else and Nikola for self hosted Jupyter/IPython noteboks is not the lack of support for pandoc, but themes, skeletons and interactivity. (Details in the referred blog post). > . >> and then Leo Editor[4]. > > I tried that, but, for some reason, it was not compelling-enough to > switch... I used Leo for several years, but nothing beats for me the interactivity and modifiability of a live coding environment like Pharo/Rossal. Cheers, Offray

Dec. 28, 2015

Re: [Pharo-users] why Pillar

by SaÅ¡a JaniÅ¡ka

On Pon, 2015-12-28 at 10:21 -0500, Offray Vladimir Luna CÃ¡rdenas wrote: > That's why I recommending you pandoc's markdown variant. It hasÂ > extensive support for footnotes, bibliographic references, tables,Â > latex, a lot of exporting formats and extensibility via exporting andÂ > manipulating the Abstract Syntax Tree. Pandoc is also used in > ScholarlyÂ markdown and Jupyter projects so you could use the markup > languageÂ variant with more people beyond this community. But you're aware that you can also use Pandoc's markdown with Nikola? > Did you mean this: >Â > http://practicaltypography.com/why-racket-why-lisp.html Yes. >and then Leo Editor[4].Â I tried that, but, for some reason, it was not compelling-enough to switch... Sincerely, Gour --Â What is night for all beings is the time of awakeningÂ for the self-controlled; and the time of awakening forÂ all beings is night for the introspective sage.

Dec. 28, 2015

Re: [Pharo-users] Slack invitation

by SaÅ¡a JaniÅ¡ka

On Pon, 2015-12-28 at 12:04 -0300, Esteban A. Maringolo wrote: > Meanwhile you can join going to: http://192.241.152.94:3000/ Thank you...joined. ;) Sincerely, Gour -- Everyone is forced to act helplessly according to the qualities he has acquired from the modes of material nature; therefore no one can refrain from doing something, not even for a moment.

Dec. 28, 2015

Re: [Pharo-users] why Pillar

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 28/12/15 06:16, SaÅ¡a JaniÅ¡ka wrote: > On Ned, 2015-12-27 at 18:50 -0500, Offray Vladimir Luna CÃ¡rdenas wrote: > > Hiya, > >> Seems that the reasons exposed in this tread are: It predated >> markdown, so was already used inside the community, and gives us >> finer control on the overall markup language, including exporting >> formats. > Nothing against it, but some features like footnotes are simply 'must' > for serious writing, at least in my domain. Yes, that's why I use pandoc's markdown. >> Two projects implement this idea Pandoc[2] > Yeah, Pandoc is great and it would be cool to have Pillar support for > it. You could extend it via Abstract Syntax Trees with Pharo. >> and Grav[3] and both use a combination of markdown and yaml. > Grav looks interesting, but I believe I simply want to leave PHP world. > :-) I did for a lot of time, barely touching anything php related and, as I said in the blog post about Nikola and Grav[1], I dislike the php syntax and pragmatics. But this doesn't prevent the acknowledge and eventual use of really good solutions made on php like dokuwiki, Question2Answer and Grav. What I'm trying to do is to communicate with this solutions without touching too much the php part, just using more standard formats like Json, cvs, markdown and yaml. [1] http://mutabit.com/offray/blog/es/entry/2015-10-06-grav-nikola-both >> My bet is on pandoc (markdown+yaml) for writing almost anything, with >> some advantages over pillar: > My main complaint to markdown is that it is not standard, despite many > attempts (or extensions). That's why I recommending you pandoc's markdown variant. It has extensive support for footnotes, bibliographic references, tables, latex, a lot of exporting formats and extensibility via exporting and manipulating the Abstract Syntax Tree. Pandoc is also used in Scholarly markdown and Jupyter projects so you could use the markup language variant with more people beyond this community. >> b. It has support for bibliographic references, footnotes a a more >> complete feature set. > I wonder how is it that despite being present for so long, it does miss > such features... Well that's the cost of being part of a small community where not all the projects can be developed beyond the interest and limitations of few members. And that's why interaction with broader communities (for example pandoc's one could be wise). > Have you considered to use Pillar markup with Nikola? That's one > option I'm considering if Pillar is going to get things liek footnotes > etc. No. As I said in the previous referred blog post I will use Nikola for self hosted IPython/Jupyter notebooks and Grav mostly everywhere in web publishing. Using padoc's markdown as the default format gives me a lot of interoperability between documentation systems. My bet for mixing pharo related developments and pandoc is via the Abstract Syntax Tree manipulations... at some point. >> Ecstatic have more powerful things like a logic-less >> approach to templating via mustache, that is neutral to the >> underlaying language > That would be another 'pro' for Pillar markup+Nikola, although I belive > Jinja is sufficient for my web needs. What I would like is to integrate Mustache in future web developments using Teapot, and Pharo, but my documentation language in the back end would be the same and more cross-community: markdown + yaml. So mustache and abstract syntax trees is an argument for not caring too much about a tightly integrated and Pharo only markup language. > Btw, let me say that I'm also inspired with Butterick and was > considering to use Racket for my project, but ended up here. :-) Did you mean this: http://practicaltypography.com/why-racket-why-lisp.html I think that racket is a pretty interesting system and Pollen[2] is also interesting for documentation. The idea of document as a program was presented to me in the times when I used TeXmacs[3] and then Leo Editor[4]. Now I'm trying to bridge several ideas of these technologies with the Interactivity of IPython but using the flexibility and understandability of Pharo/Moose/Roassal for my own interactive documentation (alpha state) project[5][6] [2] http://pollenpub.com/ [3] http://texmacs.org/ [4] http://leoeditor.com/ [5] http://mutabit.com/grafoscopio/index.en.html [6] http://mutabit.com/offray/static/blog/output/posts/grafoscopio-idea-and-ini… >> So, while I think that choosing Pharo technologies is better for >> making them more mature, tested and used, I also think that is >> important to choose proper balance to know which combination of Pharo >> technologies and external ones is adequate. > I didn't mention, but I was playing with Golang's Hugo for some time > which is also nice and, to me, preferrable over PHP. Didn't know about that or TOML. As I said, your barely touch php with grav, but the self-containment of Hugo and the easy syntax of TOML seem like good arguments in favor of them for web publishing. The main message here is that you can combine Pharo technologies with non Pharo ones via standard markup languages like markdown or yaml (or toml) and yet get extensibility in Pharo. Cheers, Offray

Dec. 28, 2015

Re: [Pharo-users] Slack invitation

by Esteban A. Maringolo

Meanwhile you can join going to: http://192.241.152.94:3000/ Regards! Esteban A. Maringolo 2015-12-28 12:02 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > It stopped working yesterday. It should be back in a couple of hours. > Issues with my server billing. > > Regards, > Esteban A. Maringolo > > > 2015-12-28 11:42 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> oops, is true. >> I will check with EstebanM what happened. >> >> Esteban >> >> On 28 Dec 2015, at 15:26, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> Strange, there was a button a couple of days ago. >> No idea then... >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> On Dec 28, 2015, at 11:13 AM, SaÅ¡a JaniÅ¡ka <gour(a)atmarama.com> wrote: >> >> On Pon, 2015-12-28 at 11:06 -0300, Alexandre Bergel wrote: >> >> On http://pharo.org/community there is a small Slack button. Maybe >> this automatize the invitation >> >> >> I do use Firefox (V43) on Debian and do not see any button? >> >> >> Sincerely, >> Gour >> >> -- >> >> For him who has conquered the mind, the mind is the best of >> friends; but for one who has failed to do so, his mind will >> remain the greatest enemy. >> >> >> >> >> >> >>

Dec. 28, 2015

Re: [Pharo-users] Slack invitation

by Esteban A. Maringolo

It stopped working yesterday. It should be back in a couple of hours. Issues with my server billing. Regards, Esteban A. Maringolo 2015-12-28 11:42 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > oops, is true. > I will check with EstebanM what happened. > > Esteban > > On 28 Dec 2015, at 15:26, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Strange, there was a button a couple of days ago. > No idea then... > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Dec 28, 2015, at 11:13 AM, SaÅ¡a JaniÅ¡ka <gour(a)atmarama.com> wrote: > > On Pon, 2015-12-28 at 11:06 -0300, Alexandre Bergel wrote: > > On http://pharo.org/community there is a small Slack button. Maybe > this automatize the invitation > > > I do use Firefox (V43) on Debian and do not see any button? > > > Sincerely, > Gour > > -- > > For him who has conquered the mind, the mind is the best of > friends; but for one who has failed to do so, his mind will > remain the greatest enemy. > > > > > > >

Dec. 28, 2015