Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Offray Vladimir Luna Cárdenas]

Thanks both, Alex and Doru for your quick answers. I'm using Manjaro
Cinnamon Edition[1]. If you need any help with 32 bits over 64 bits
systems, let me know.

[1] https://manjaro.org/community-editions/

Cheers,

Offray


On 14/11/17 12:46, Aliaksei Syrel wrote:
> Offray, which edition of Manjaro do you have? (XFCE, KDE or Gnome)
>
> Cheers,
> Alex
>
> On 14 November 2017 at 18:41, Aliaksei Syrel  > wrote:
>
> Hi Offray,
>
> I agree with your point of view. It is in our best interests to
> make it work as smoothly as possible, ideally automagically :)
> Now I will try to install Pharo6.1 on Manjaro Linux in order to
> see if there is something that needs to be noted in README.md.
>
> One of the biggest problems on linux for me is installation of
> 32bit libs on 64 bit distro. That is why I will test 64bit Pharo
> on 64bit Manjaro Linux with Moz2D and without it.
> I will let you know
>
> Cheers,
> Alex
>
> On 14 November 2017 at 18:25, Offray Vladimir Luna Cárdenas
> > wrote:
>
> Alex,
>
> I understand that frustration on installation could be
> motivated by other issues instead of GT Documenter, but if the
> team ask to use "|Iceberg enableMetacelloIntegration: true."
> |in the project readme, where it also says that is supported
> for Pharo 6.1 and 7.0, is natural to think that something is
> wrong with documentation and/or in the project's expectations
> about its intended users and their will to invest the effort,
> time and motivation for "living in the edge". I understand
> that if we want stuff to be improved it should be tested, but
> also that not all the people that is willing to test stuff for
> Pharo 6.1 needs to live in such edge. Or the project is
> sending a message that is not giving the bests firsts
> impressions, or is going to users which are not intended . I
> would go for a smooth install first and then for collaboration
> with git. I'll make a pull request with the proposal for a
> better documentation, but my understanding about how you can
> go from the first (user of GT Documenter) to the second
> (developer using Git integration) is not clear.
>
> GT Tools has been pretty empowering. I have told that several
> times and I don't think that I have wrote a single line of
> code in their repos. But is getting more difficult just to
> test and use them and I think that is related with the idea
> that my user *needs* to be also my co-developer, starting with
> their ssh git key pair. If we don't make easier to contribute
> by just making easier to install, there will be no evolution
> either.
>
> Cheers,
>
> Offray
>
>
> On 14/11/17 11:45, Aliaksei Syrel wrote:
>> Hi Offray,
>>
>> I understand your frustration, but with all respect, the fact
>> that you have problems with Iceberg does not mean that GT
>> Documenter or any other GT tool is responsible for described
>> problems.
>>
>> Most complains about bloc, brick, whatever is because of
>> unrelated stuff. It is a little bit disappointing. Especially
>> for me, as one of the maintainers. But it is ok, I got used
>> to it :)
>>
>> I don’t remember when last time I used stable Pharo (not
>> because it does not exist), simply live on the edge since
>> Pharo4. If no one will use Git and report problems Iceberg
>> will never progress. If no one will use Bloc it will never
>> get “there”. Unfortunately, living on the edge is dangerous,
>> requires effort, motivation and time.
>>
>> The script that Doru provided works flawlessly on OSX, we
>> load it almost everyday. !! Bloc is tested on CI and builds
>> are green on Windows, Linux and OSX !!. If computer (CI)
>> manages to install it, I am pretty sure human can do it too.
>> Looks like there is something missing in your configuration,
>> something tiny :) Error handling in Iceberg can be definitely
>> improved, but it is a different story.
>>
>> P.S. Documenter can be installed without enabled Iceberg
>> integration. This is how CI does it. You will just not be
>> able to contribute.
>>
>> Cheers,
>> Alex
>>
>> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna Cárdenas
>> > wrote:
>>
>> I have been just trying to install GT Documenter and is
>> really frustrating (I have been unable to install it even
>> for the first time!).
>>
>> This was the list of errors I 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Aliaksei Syrel]

Offray, which edition of Manjaro do you have? (XFCE, KDE or Gnome)

Cheers,
Alex

On 14 November 2017 at 18:41, Aliaksei Syrel  wrote:

> Hi Offray,
>
> I agree with your point of view. It is in our best interests to make it
> work as smoothly as possible, ideally automagically :)
> Now I will try to install Pharo6.1 on Manjaro Linux in order to see if
> there is something that needs to be noted in README.md.
>
> One of the biggest problems on linux for me is installation of 32bit libs
> on 64 bit distro. That is why I will test 64bit Pharo on 64bit Manjaro
> Linux with Moz2D and without it.
> I will let you know
>
> Cheers,
> Alex
>
> On 14 November 2017 at 18:25, Offray Vladimir Luna Cárdenas <
> offray.l...@mutabit.com> wrote:
>
>> Alex,
>>
>> I understand that frustration on installation could be motivated by other
>> issues instead of GT Documenter, but if the team ask to use "Iceberg
>> enableMetacelloIntegration: true." in the project readme, where it also
>> says that is supported for Pharo 6.1 and 7.0, is natural to think that
>> something is wrong with documentation and/or in the project's expectations
>> about its intended users and their will to invest the effort, time and
>> motivation for "living in the edge". I understand that if we want stuff to
>> be improved it should be tested, but also that not all the people that is
>> willing to test stuff for Pharo 6.1 needs to live in such edge. Or the
>> project is sending a message that is not giving the bests firsts
>> impressions, or is going to users which are not intended . I would go for a
>> smooth install first and then for collaboration with git. I'll make a pull
>> request with the proposal for a better documentation, but my understanding
>> about how you can go from the first (user of GT Documenter) to the second
>> (developer using Git integration) is not clear.
>>
>> GT Tools has been pretty empowering. I have told that several times and I
>> don't think that I have wrote a single line of code in their repos. But is
>> getting more difficult just to test and use them and I think that is
>> related with the idea that my user *needs* to be also my co-developer,
>> starting with their ssh git key pair. If we don't make easier to contribute
>> by just making easier to install, there will be no evolution either.
>>
>> Cheers,
>>
>> Offray
>>
>> On 14/11/17 11:45, Aliaksei Syrel wrote:
>>
>> Hi Offray,
>>
>> I understand your frustration, but with all respect, the fact that you
>> have problems with Iceberg does not mean that GT Documenter or any other GT
>> tool is responsible for described problems.
>>
>> Most complains about bloc, brick, whatever is because of unrelated stuff.
>> It is a little bit disappointing. Especially for me, as one of the
>> maintainers. But it is ok, I got used to it :)
>>
>> I don’t remember when last time I used stable Pharo (not because it does
>> not exist), simply live on the edge since Pharo4. If no one will use Git
>> and report problems Iceberg will never progress. If no one will use Bloc it
>> will never get “there”. Unfortunately, living on the edge is dangerous,
>> requires effort, motivation and time.
>>
>> The script that Doru provided works flawlessly on OSX, we load it almost
>> everyday. !! Bloc is tested on CI and builds are green on Windows, Linux
>> and OSX !!. If computer (CI) manages to install it, I am pretty sure human
>> can do it too. Looks like there is something missing in your configuration,
>> something tiny :) Error handling in Iceberg can be definitely improved, but
>> it is a different story.
>>
>> P.S. Documenter can be installed without enabled Iceberg integration.
>> This is how CI does it. You will just not be able to contribute.
>>
>> Cheers,
>> Alex
>>
>> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna Cárdenas <
>> offray.l...@mutabit.com> wrote:
>>
>>> I have been just trying to install GT Documenter and is really
>>> frustrating (I have been unable to install it even for the first time!).
>>>
>>> This was the list of errors I got and steps I followed, in almost
>>> sequential order, just to get a (bittersweet!) taste of GT Documenter:
>>>
>>>- 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I
>>>go to GitHub, follow the five pages of documentation to get my SSH
>>>credentials that start at [1], then, because I still get the same error, 
>>> go
>>>to the Iceberg FAQ [2], try to surpass the erro,r via command line and
>>>doesn't work, so I go to the Iceberg settings and try the manual
>>>configuration, going to the next item
>>>
>>>[1] https://help.github.com/articles/generating-a-new-ssh-key-an
>>>d-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
>>>
>>> 
>>>[2] https://github.com/pharo-vcs/iceberg/blob/master/README.md
>>>
>>>- Now I get "Instance of LGitCredentialsSSH 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Aliaksei Syrel]

Hi Offray,

I agree with your point of view. It is in our best interests to make it
work as smoothly as possible, ideally automagically :)
Now I will try to install Pharo6.1 on Manjaro Linux in order to see if
there is something that needs to be noted in README.md.

One of the biggest problems on linux for me is installation of 32bit libs
on 64 bit distro. That is why I will test 64bit Pharo on 64bit Manjaro
Linux with Moz2D and without it.
I will let you know

Cheers,
Alex

On 14 November 2017 at 18:25, Offray Vladimir Luna Cárdenas <
offray.l...@mutabit.com> wrote:

> Alex,
>
> I understand that frustration on installation could be motivated by other
> issues instead of GT Documenter, but if the team ask to use "Iceberg
> enableMetacelloIntegration: true." in the project readme, where it also
> says that is supported for Pharo 6.1 and 7.0, is natural to think that
> something is wrong with documentation and/or in the project's expectations
> about its intended users and their will to invest the effort, time and
> motivation for "living in the edge". I understand that if we want stuff to
> be improved it should be tested, but also that not all the people that is
> willing to test stuff for Pharo 6.1 needs to live in such edge. Or the
> project is sending a message that is not giving the bests firsts
> impressions, or is going to users which are not intended . I would go for a
> smooth install first and then for collaboration with git. I'll make a pull
> request with the proposal for a better documentation, but my understanding
> about how you can go from the first (user of GT Documenter) to the second
> (developer using Git integration) is not clear.
>
> GT Tools has been pretty empowering. I have told that several times and I
> don't think that I have wrote a single line of code in their repos. But is
> getting more difficult just to test and use them and I think that is
> related with the idea that my user *needs* to be also my co-developer,
> starting with their ssh git key pair. If we don't make easier to contribute
> by just making easier to install, there will be no evolution either.
>
> Cheers,
>
> Offray
>
> On 14/11/17 11:45, Aliaksei Syrel wrote:
>
> Hi Offray,
>
> I understand your frustration, but with all respect, the fact that you
> have problems with Iceberg does not mean that GT Documenter or any other GT
> tool is responsible for described problems.
>
> Most complains about bloc, brick, whatever is because of unrelated stuff.
> It is a little bit disappointing. Especially for me, as one of the
> maintainers. But it is ok, I got used to it :)
>
> I don’t remember when last time I used stable Pharo (not because it does
> not exist), simply live on the edge since Pharo4. If no one will use Git
> and report problems Iceberg will never progress. If no one will use Bloc it
> will never get “there”. Unfortunately, living on the edge is dangerous,
> requires effort, motivation and time.
>
> The script that Doru provided works flawlessly on OSX, we load it almost
> everyday. !! Bloc is tested on CI and builds are green on Windows, Linux
> and OSX !!. If computer (CI) manages to install it, I am pretty sure human
> can do it too. Looks like there is something missing in your configuration,
> something tiny :) Error handling in Iceberg can be definitely improved, but
> it is a different story.
>
> P.S. Documenter can be installed without enabled Iceberg integration. This
> is how CI does it. You will just not be able to contribute.
>
> Cheers,
> Alex
>
> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna Cárdenas <
> offray.l...@mutabit.com> wrote:
>
>> I have been just trying to install GT Documenter and is really
>> frustrating (I have been unable to install it even for the first time!).
>>
>> This was the list of errors I got and steps I followed, in almost
>> sequential order, just to get a (bittersweet!) taste of GT Documenter:
>>
>>- 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I
>>go to GitHub, follow the five pages of documentation to get my SSH
>>credentials that start at [1], then, because I still get the same error, 
>> go
>>to the Iceberg FAQ [2], try to surpass the erro,r via command line and
>>doesn't work, so I go to the Iceberg settings and try the manual
>>configuration, going to the next item
>>
>>[1] https://help.github.com/articles/generating-a-new-ssh-key-
>>and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
>>
>> 
>>[2] https://github.com/pharo-vcs/iceberg/blob/master/README.md
>>
>>- Now I get "Instance of LGitCredentialsSSH class did not understand
>>#ifTrue:ifFalse:". I try to make sense of it in the debugger, but is
>>something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS:
>>
>> '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit'
>>

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Offray Vladimir Luna Cárdenas]

Hi Doru,


On 14/11/17 11:36, Tudor Girba wrote:
> Hi Offray,
>
> There are two issues that I take from your email. So, please allow me to 
> address them separately:
>
> 1. The process of installing the new GT (with Documenter)
> GT is meant to load in Pharo 6.1. It is tested tested automatically several 
> times a day both on Windows (Appveyor) and on Linux (Travis CI), and we load 
> it automatically on Mac when we develop. Other people managed to load it as 
> well. That does not mean that there are no problems, but it does mean that 
> there are no problems that we are aware of. So, we need to understand what 
> the issue is.
> From your email I understand that you are using Pharo 6.1. Is it the latest 
> image and VM?

This is what about says: "Pharo 6.0 Latest update: #60510", but is Pharo
6.1. I don't know if that gives any info on the VM or how to get it.

> What is the operating system?

Manjaro Linux

> What is the exact loading snippet that you used?

The one in the thread I'm answering. Is the same in the Readme fro
gtoolkit. https://github.com/feenkcom/gtoolkit

> Now, please bare in mind that GT relies on the common way of organizing 
> GitHub projects. So, what you describe seems to have to do with Iceberg, not 
> with GT. For example, did you manage to load any other Pharo project from 
> GitHub?
>
> 2. There is something about silence which I do not understand. I do not 
> remember a particular question that you asked and you got no answer to. If 
> there was one, I am sorry. Please repost it.

I have done. Was about giving feedback to the Pillar editor. But also
happened at the beginning when I tried to get feedback on the Moose
list. In fact I prefer to post questions here. There is a lot of overlap
between both lists, but here I have a better answers ratio.

Cheers,

Offray

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Stephane Ducasse]

For git / iceberg first time users:
Please read the tip and tricks booklet available on http://books.pharo.org

On Tue, Nov 14, 2017 at 5:45 PM, Aliaksei Syrel  wrote:
> Hi Offray,
>
> I understand your frustration, but with all respect, the fact that you have
> problems with Iceberg does not mean that GT Documenter or any other GT tool
> is responsible for described problems.
>
> Most complains about bloc, brick, whatever is because of unrelated stuff. It
> is a little bit disappointing. Especially for me, as one of the maintainers.
> But it is ok, I got used to it :)
>
> I don’t remember when last time I used stable Pharo (not because it does not
> exist), simply live on the edge since Pharo4. If no one will use Git and
> report problems Iceberg will never progress. If no one will use Bloc it will
> never get “there”. Unfortunately, living on the edge is dangerous, requires
> effort, motivation and time.
>
> The script that Doru provided works flawlessly on OSX, we load it almost
> everyday. !! Bloc is tested on CI and builds are green on Windows, Linux and
> OSX !!. If computer (CI) manages to install it, I am pretty sure human can
> do it too. Looks like there is something missing in your configuration,
> something tiny :) Error handling in Iceberg can be definitely improved, but
> it is a different story.
>
> P.S. Documenter can be installed without enabled Iceberg integration. This
> is how CI does it. You will just not be able to contribute.
>
> Cheers,
> Alex
>
> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna Cárdenas
>  wrote:
>>
>> I have been just trying to install GT Documenter and is really frustrating
>> (I have been unable to install it even for the first time!).
>>
>> This was the list of errors I got and steps I followed, in almost
>> sequential order, just to get a (bittersweet!) taste of GT Documenter:
>>
>> 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I go to
>> GitHub, follow the five pages of documentation to get my SSH credentials
>> that start at [1], then, because I still get the same error, go to the
>> Iceberg FAQ [2], try to surpass the erro,r via command line and doesn't
>> work, so I go to the Iceberg settings and try the manual configuration,
>> going to the next item
>>
>> [1]
>> https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
>> [2] https://github.com/pharo-vcs/iceberg/blob/master/README.md
>>
>> Now I get "Instance of LGitCredentialsSSH class did not understand
>> #ifTrue:ifFalse:". I try to make sense of it in the debugger, but is
>> something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS:
>> '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit'
>> exists and is not an empty directory. I delete that directory and try an
>> installation... again
>> Now I get: "Instance of FileReference did not understand #notEmpty". I try
>> to make sense of it in the debugger. My user is git, my public and private
>> ssh keys are not empty. Despite of not making sense of all I understand that
>> is trying to clone something at g...@github.com:feenkcom/gtoolkit.git. I go
>> to my image dir and then to `iceberg/feenkcom/gtoolkit/`. There is a git
>> repository there, but is empty.
>> Now I wonder, maybe if I can just clone the directory there, but how I say
>> Iceberg to load it? So I run now only the Metacello part. Same error and
>> solution that the last time but now for gtoolkit-visualizer, Brick,
>> gtoolkit-examples, Bloc and Sparta.
>> After getting my ssh keys, overcome config problems in shell and the Pharo
>> settings, chasing these errors and solving them by cloning the repositories
>> manually, I'm, a couple of hours later, ready to test GT Documenter, but
>> with the last Iceberg's duplicated repository message about Sparta I give
>> up. Is not nice to start your day accumulating frustration... that sets a
>> bad mood for the rest of it, and you need to actively fight against.
>>
>> I have thought that Git is overcomplicated for most of the developers'
>> tasks and communities. I don't know if the root of previous issues is in the
>> "Iceberg enableMetacelloIntegration: true" line, but having to get your pair
>> of keys working to just install software is overkill for the common user
>> (and when LibGit errors are present, the documented solutions don't work
>> seamlessly). Maybe a more sensitive solution would be just to use libgit,
>> without any ssh auth to clone repositories and its prerequisites or even
>> better, some download that goes to the files in the tip (or other) version
>> without all this overhead.
>>
>> Anyway, as I said, I have been unable to test GT Documenter properly and
>> getting feedback over GT Tools from the team usually requires a lot of
>> effort in my case (insisting on getting answers or getting none). And that
>> is just to test a promising tech that still doesn't offer 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Aliaksei Syrel]

Hi Offray,

I understand your frustration, but with all respect, the fact that you have
problems with Iceberg does not mean that GT Documenter or any other GT tool
is responsible for described problems.

Most complains about bloc, brick, whatever is because of unrelated stuff.
It is a little bit disappointing. Especially for me, as one of the
maintainers. But it is ok, I got used to it :)

I don’t remember when last time I used stable Pharo (not because it does
not exist), simply live on the edge since Pharo4. If no one will use Git
and report problems Iceberg will never progress. If no one will use Bloc it
will never get “there”. Unfortunately, living on the edge is dangerous,
requires effort, motivation and time.

The script that Doru provided works flawlessly on OSX, we load it almost
everyday. !! Bloc is tested on CI and builds are green on Windows, Linux
and OSX !!. If computer (CI) manages to install it, I am pretty sure human
can do it too. Looks like there is something missing in your configuration,
something tiny :) Error handling in Iceberg can be definitely improved, but
it is a different story.

P.S. Documenter can be installed without enabled Iceberg integration. This
is how CI does it. You will just not be able to contribute.

Cheers,
Alex

On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna Cárdenas <
offray.l...@mutabit.com> wrote:

> I have been just trying to install GT Documenter and is really frustrating
> (I have been unable to install it even for the first time!).
>
> This was the list of errors I got and steps I followed, in almost
> sequential order, just to get a (bittersweet!) taste of GT Documenter:
>
>- 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I
>go to GitHub, follow the five pages of documentation to get my SSH
>credentials that start at [1], then, because I still get the same error, go
>to the Iceberg FAQ [2], try to surpass the erro,r via command line and
>doesn't work, so I go to the Iceberg settings and try the manual
>configuration, going to the next item
>
>[1]
>
> https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
>[2] https://github.com/pharo-vcs/iceberg/blob/master/README.md
>
>- Now I get "Instance of LGitCredentialsSSH class did not understand
>#ifTrue:ifFalse:". I try to make sense of it in the debugger, but is
>something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS:
>
> '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit'
>exists and is not an empty directory. I delete that directory and try an
>installation... again
>- Now I get: "Instance of FileReference did not understand #notEmpty".
>I try to make sense of it in the debugger. My user is git, my public and
>private ssh keys are not empty. Despite of not making sense of all I
>understand that is trying to clone something at
>g...@github.com:feenkcom/gtoolkit.git. I go to my image dir and then to
>`iceberg/feenkcom/gtoolkit/`. There is a git repository there, but is 
> empty.
>- Now I wonder, maybe if I can just clone the directory there, but how
>I say Iceberg to load it? So I run now only the Metacello part. Same error
>and solution that the last time but now for gtoolkit-visualizer, Brick,
>gtoolkit-examples, Bloc and Sparta.
>- After getting my ssh keys, overcome config problems in shell and the
>Pharo settings, chasing these errors and solving them by cloning the
>repositories manually, I'm, a couple of hours later, ready to test GT
>Documenter, but with the last Iceberg's duplicated repository message about
>Sparta I give up. Is not nice to start your day accumulating frustration...
>that sets a bad mood for the rest of it, and you need to actively fight
>against.
>
> I have thought that Git is overcomplicated for most of the developers'
> tasks and communities. I don't know if the root of previous issues is in
> the "Iceberg enableMetacelloIntegration: true" line, but having to get your
> pair of keys working to just install software is overkill for the common
> user (and when LibGit errors are present, the documented solutions don't
> work seamlessly). Maybe a more sensitive solution would be just to use
> libgit, without any ssh auth to clone repositories and its prerequisites or
> even better, some download that goes to the files in the tip (or other)
> version without all this overhead.
>
> Anyway, as I said, I have been unable to test GT Documenter properly and
> getting feedback over GT Tools from the team usually requires a lot of
> effort in my case (insisting on getting answers or getting none). And that
> is just to test a promising tech that still doesn't offer saving features
> (just and awesome preview). I think that a more sensible approach for a
> good documentation toolkit for now is on Spec and creating custom syntax
> highlighters 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Tudor Girba]

What operating system are you on? What version of Pharo do you use? Is it 32b 
or 64b?

Cheers,
Doru


> On Nov 14, 2017, at 5:33 PM, Offray Vladimir Luna Cárdenas 
>  wrote:
> 
> 
> 
> On 14/11/17 10:36, Offray Vladimir Luna Cárdenas wrote:
> 
> [...]
>> I have thought that Git is overcomplicated for most of the developers'
>> tasks and communities. I don't know if the root of previous issues is
>> in the "Iceberg enableMetacelloIntegration: true" line, but having to
>> get your pair of keys working to just install software is overkill for
>> the common user (and when LibGit errors are present, the documented
>> solutions don't work seamlessly). Maybe a more sensitive solution
>> would be just to use libgit, without any ssh auth to clone
>> repositories and its prerequisites or even better, some download that
>> goes to the files in the tip (or other) version without all this
>> overhead. 
> 
> In fact, using "Iceberg enableMetacelloIntegration: false" produce a
> smoother installing experience. Putting this as the first line of the
> script doesn't help to most of the users if we want to enable easy
> feedback. Anyway, after a mostly successful installation, Moz2D
> installation failed, downloading a ~20Mb file and after that saying:
> "Moz2D library is not installed correctly. Select Proceed to continue,
> or close this window to cancel the operation." That made most of the
> examples non functional because of the lack of Moz2D or because some
> deprecation.
> 
> Any other way to install Moz2D on Manjaro/Arch Linux or to disable it an
> still be able to use Pillar preview features?
> 
> Cheers,
> 
> Offray
> 
> 

--
www.tudorgirba.com
www.feenk.com

"When people care, great things can happen."

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Tudor Girba]

Hi Offray,

There are two issues that I take from your email. So, please allow me to 
address them separately:

1. The process of installing the new GT (with Documenter)
GT is meant to load in Pharo 6.1. It is tested tested automatically several 
times a day both on Windows (Appveyor) and on Linux (Travis CI), and we load it 
automatically on Mac when we develop. Other people managed to load it as well. 
That does not mean that there are no problems, but it does mean that there are 
no problems that we are aware of. So, we need to understand what the issue is.
From your email I understand that you are using Pharo 6.1. Is it the latest 
image and VM?
What is the operating system?
What is the exact loading snippet that you used?
Now, please bare in mind that GT relies on the common way of organizing GitHub 
projects. So, what you describe seems to have to do with Iceberg, not with GT. 
For example, did you manage to load any other Pharo project from GitHub?

2. There is something about silence which I do not understand. I do not 
remember a particular question that you asked and you got no answer to. If 
there was one, I am sorry. Please repost it.

Cheers,
Doru



> On Nov 14, 2017, at 4:36 PM, Offray Vladimir Luna Cárdenas 
>  wrote:
> 
> I have been just trying to install GT Documenter and is really frustrating (I 
> have been unable to install it even for the first time!).
> 
> This was the list of errors I got and steps I followed, in almost sequential 
> order, just to get a (bittersweet!) taste of GT Documenter:
> 
>   • 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I go 
> to GitHub, follow the five pages of documentation to get my SSH credentials 
> that start at [1], then, because I still get the same error, go to the 
> Iceberg FAQ [2], try to surpass the erro,r via command line and doesn't work, 
> so I go to the Iceberg settings and try the manual configuration, going to 
> the next item
> 
> [1] 
> https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
> [2] https://github.com/pharo-vcs/iceberg/blob/master/README.md
> 
>   • Now I get "Instance of LGitCredentialsSSH class did not understand 
> #ifTrue:ifFalse:". I try to make sense of it in the debugger, but is 
> something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS: 
> '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit'
>  exists and is not an empty directory. I delete that directory and try an 
> installation... again
>   • Now I get: "Instance of FileReference did not understand #notEmpty". 
> I try to make sense of it in the debugger. My user is git, my public and 
> private ssh keys are not empty. Despite of not making sense of all I 
> understand that is trying to clone something at 
> g...@github.com:feenkcom/gtoolkit.git. I go to my image dir and then to 
> `iceberg/feenkcom/gtoolkit/`. There is a git repository there, but is empty.
>   • Now I wonder, maybe if I can just clone the directory there, but how 
> I say Iceberg to load it? So I run now only the Metacello part. Same error 
> and solution that the last time but now for gtoolkit-visualizer, Brick, 
> gtoolkit-examples, Bloc and Sparta.
>   • After getting my ssh keys, overcome config problems in shell and the 
> Pharo settings, chasing these errors and solving them by cloning the 
> repositories manually, I'm, a couple of hours later, ready to test GT 
> Documenter, but with the last Iceberg's duplicated repository message about 
> Sparta I give up. Is not nice to start your day accumulating frustration... 
> that sets a bad mood for the rest of it, and you need to actively fight 
> against.
> I have thought that Git is overcomplicated for most of the developers' tasks 
> and communities. I don't know if the root of previous issues is in the 
> "Iceberg enableMetacelloIntegration: true" line, but having to get your pair 
> of keys working to just install software is overkill for the common user (and 
> when LibGit errors are present, the documented solutions don't work 
> seamlessly). Maybe a more sensitive solution would be just to use libgit, 
> without any ssh auth to clone repositories and its prerequisites or even 
> better, some download that goes to the files in the tip (or other) version 
> without all this overhead.
> 
> Anyway, as I said, I have been unable to test GT Documenter properly and 
> getting feedback over GT Tools from the team usually requires a lot of effort 
> in my case (insisting on getting answers or getting none). And that is just 
> to test a promising tech that still doesn't offer saving features (just and 
> awesome preview). I think that a more sensible approach for a good 
> documentation toolkit for now is on Spec and creating custom syntax 
> highlighters with SmaCC[3], that is well documented and works today.
> [3] 
> 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Offray Vladimir Luna Cárdenas]

On 14/11/17 10:36, Offray Vladimir Luna Cárdenas wrote:

[...]
> I have thought that Git is overcomplicated for most of the developers'
> tasks and communities. I don't know if the root of previous issues is
> in the "Iceberg enableMetacelloIntegration: true" line, but having to
> get your pair of keys working to just install software is overkill for
> the common user (and when LibGit errors are present, the documented
> solutions don't work seamlessly). Maybe a more sensitive solution
> would be just to use libgit, without any ssh auth to clone
> repositories and its prerequisites or even better, some download that
> goes to the files in the tip (or other) version without all this
> overhead. 

In fact, using "Iceberg enableMetacelloIntegration: false" produce a
smoother installing experience. Putting this as the first line of the
script doesn't help to most of the users if we want to enable easy
feedback. Anyway, after a mostly successful installation, Moz2D
installation failed, downloading a ~20Mb file and after that saying:
"Moz2D library is not installed correctly. Select Proceed to continue,
or close this window to cancel the operation." That made most of the
examples non functional because of the lack of Moz2D or because some
deprecation.

Any other way to install Moz2D on Manjaro/Arch Linux or to disable it an
still be able to use Pillar preview features?

Cheers,

Offray

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Offray Vladimir Luna Cárdenas]

I have been just trying to install GT Documenter and is really
frustrating (I have been unable to install it even for the first time!).

This was the list of errors I got and steps I followed, in almost
sequential order, just to get a (bittersweet!) taste of GT Documenter:

  * 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I
go to GitHub, follow the five pages of documentation to get my SSH
credentials that start at [1], then, because I still get the same
error, go to the Iceberg FAQ [2], try to surpass the erro,r via
command line and doesn't work, so I go to the Iceberg settings and
try the manual configuration, going to the next item

[1]

https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
[2] https://github.com/pharo-vcs/iceberg/blob/master/README.md

  * Now I get "Instance of LGitCredentialsSSH class did not understand
#ifTrue:ifFalse:". I try to make sense of it in the debugger, but is
something I cannot. Anyway, I rerun it and now I get:
LGit_GIT_EEXISTS:

'/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit'
exists and is not an empty directory. I delete that directory and
try an installation... again
  * Now I get: "Instance of FileReference did not understand #notEmpty".
I try to make sense of it in the debugger. My user is git, my public
and private ssh keys are not empty. Despite of not making sense of
all I understand that is trying to clone something at
g...@github.com:feenkcom/gtoolkit.git. I go to my image dir and then
to `iceberg/feenkcom/gtoolkit/`. There is a git repository there,
but is empty.
  * Now I wonder, maybe if I can just clone the directory there, but how
I say Iceberg to load it? So I run now only the Metacello part. Same
error and solution that the last time but now for
gtoolkit-visualizer, Brick, gtoolkit-examples, Bloc and Sparta.
  * After getting my ssh keys, overcome config problems in shell and the
Pharo settings, chasing these errors and solving them by cloning the
repositories manually, I'm, a couple of hours later, ready to test
GT Documenter, but with the last Iceberg's duplicated repository
message about Sparta I give up. Is not nice to start your day
accumulating frustration... that sets a bad mood for the rest of it,
and you need to actively fight against.

I have thought that Git is overcomplicated for most of the developers'
tasks and communities. I don't know if the root of previous issues is in
the "Iceberg enableMetacelloIntegration: true" line, but having to get
your pair of keys working to just install software is overkill for the
common user (and when LibGit errors are present, the documented
solutions don't work seamlessly). Maybe a more sensitive solution would
be just to use libgit, without any ssh auth to clone repositories and
its prerequisites or even better, some download that goes to the files
in the tip (or other) version without all this overhead.

Anyway, as I said, I have been unable to test GT Documenter properly and
getting feedback over GT Tools from the team usually requires a lot of
effort in my case (insisting on getting answers or getting none). And
that is just to test a promising tech that still doesn't offer saving
features (just and awesome preview). I think that a more sensible
approach for a good documentation toolkit for now is on Spec and
creating custom syntax highlighters with SmaCC[3], that is well
documented and works today.

[3]
https://medium.com/@juliendelplanque/hacking-a-simple-syntactic-highlighter-around-specs-textmodel-44ba2e2b1ab9

I understand that community is trying its best, but expressing how
current offerings are not mature and constructive criticism can help on
that. At the moment my feeling is that if you want to try the new shinny
alpha stuff from GT Documenter, you will need to be prepared for a lot
of frustration and silence.

Cheers,

Offray

On 10/11/17 12:41, Tudor Girba wrote:
> Hi,
>
> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for 
> Pillar working on top of Bloc.
>
> You can get it by loading:
>
> Iceberg enableMetacelloIntegration: true.
> Metacello new
>baseline: 'GToolkit';
>repository: 'github://feenkcom/gtoolkit/src';
>load.
>
> For example, you can then inspect:
> 'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillar’ 
> asFileReference
>
> Cheers,
> Doru
>
>
>> On Nov 10, 2017, at 12:58 PM, H. Hirzel  wrote:
>>
>> A note:
>>
>> Tudor Girba wrote:
>>    Fri, Aug 25, 2017 at 1:31 PM
>> Reply-To: Any question about pharo is welcome 
>> To: Any question about pharo is welcome 
>>
>> Hi,
>>
>> As mentioned in an announcement about 10 days ago, we are building a
>> Pillar editor with inline viewing abilities in Bloc. 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Stephane Ducasse]

Sean why don't you try because this is the moment to push bloc people
to produce simpler better solution.
I should do it too. I know.

Stef

On Sun, Nov 12, 2017 at 3:58 AM, Sean P. DeNigris  wrote:
> Tudor Girba-2 wrote
>> That would be another renderer, but it is not difficult to build. That is
>> something we’ll do soon.
>
> It would be nice to be able to toggle codes on/off like WS Word
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Sean P. DeNigris]

Tudor Girba-2 wrote
> That would be another renderer, but it is not difficult to build. That is
> something we’ll do soon.

It would be nice to be able to toggle codes on/off like WS Word



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Stephane Ducasse]

Hannes
We will start to repackage pillar model so finding a mini pillar is
interesting to us.
Let let us know.

Stef

On Sat, Nov 11, 2017 at 7:51 AM, Tudor Girba  wrote:
> Hi,
>
>
>> On Nov 10, 2017, at 9:20 PM, Sean P. DeNigris  wrote:
>>
>> Tudor Girba-2 wrote
>>> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for
>>> Pillar working on top of Bloc.
>>
>> Two questions after playing with it:
>> 1. Can one save a live-edited file?
>
> The saving action is not implemented yet.
>
>> 2. Is it possible to make the markup codes invisible? That would seem more
>> appropriate e.g. in a read-only context.
>
> That would be another renderer, but it is not difficult to build. That is 
> something we’ll do soon.
>
> Cheers,
> Doru
>
>>
>>
>> -
>> Cheers,
>> Sean
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Beauty is where we see it."
>
>
>
>
>

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Tudor Girba]

Hi,


> On Nov 10, 2017, at 9:20 PM, Sean P. DeNigris  wrote:
> 
> Tudor Girba-2 wrote
>> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for
>> Pillar working on top of Bloc.
> 
> Two questions after playing with it:
> 1. Can one save a live-edited file?

The saving action is not implemented yet.

> 2. Is it possible to make the markup codes invisible? That would seem more
> appropriate e.g. in a read-only context.

That would be another renderer, but it is not difficult to build. That is 
something we’ll do soon.

Cheers,
Doru

> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 

--
www.tudorgirba.com
www.feenk.com

"Beauty is where we see it."

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Ben Coman]

On Sat, Nov 11, 2017 at 4:20 AM, Sean P. DeNigris 
wrote:

> Tudor Girba-2 wrote
> > As shown at ESUG, GT Documenter offers an advanced viewer (and editor)
> for
> > Pillar working on top of Bloc.
>
> Two questions after playing with it:
> 1. Can one save a live-edited file?
> 2. Is it possible to make the markup codes invisible? That would seem more
> appropriate e.g. in a read-only context.
>

Which markup codes do you mean?
Markup like this still conveys useful information in text mode... ""this is
important""

cheers -ben


>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
>

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Sean P. DeNigris]

Tudor Girba-2 wrote
> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for
> Pillar working on top of Bloc.

Two questions after playing with it:
1. Can one save a live-edited file?
2. Is it possible to make the markup codes invisible? That would seem more
appropriate e.g. in a read-only context.



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Stephane Ducasse]

Ok let know.
Guille worked the complete week on pillar (mainly archetype and the
outputer part) and made **giant** steps.
He removed most of the need for using make and we will do another
cleaning first but first
release Pharo 7.0.0 and its documentation.
After we will remove magritte.

Stef


On Fri, Nov 10, 2017 at 11:33 AM, H. Hirzel  wrote:
> Hello
>
> In the thread 'including Pillar in Pharo image by default' it was
> suggested by Stephane Ducasse to include a subset of Pillar in the
> Pharo image[1] .
>
> I'd like to extend that proposal a little bit it in order  to do very
> simple presentations. This should allow to describe at least part of
> the slides used in the MOOC course [3].
>
> This will be  _a possible_ solution to the question  brought up in the
> thread 'Writing "powerpoint" like presentations in Pharo?'.
>
> Another use is to write instructions with executable content within
> the image ("Assistants").
>
> So below is the a proposal for a Pillar syntax _subset_ for class
> comments and _simple_ presentations.
> The numbering scheme follows the 'Pillar syntax cheat sheet' [2]
>
>
>
>
> MINI PILLAR SYNTAX (a subset of Pillar)
>
> 1. Headers
>
> !Header 1
> !!Header 2
> !!!Header 3
>
>
> 2. Lists
>
> - Unordered List
> # Ordered list
>
>
>
> 5. Emphasis
>
> ""bold""
>
>
> 6. Code blocks
>
>  [[[
>  Transcript show: 'Hello World'.
>  \]]]
>
>
> 9. Annotation
>
> ${slide:title=About Pharo}$
>
>
>
>
> Next week I plan to implement the rendering of this 'Mini Pillar' in
> Morphic using the Morphic API subset that works in Pharo and Squeak.
>
> A renderer using Bloc would also be nice. [4]
>
> Comments, suggestions, code snippets and other help is welcome.
>
> Regards
> Hannes
>
>
>
>
> --
> [1] Pillar subset for class comments
>
> Stephane Ducasse
>    Fri, Aug 11, 2017 at 7:09 PM
> To: Any question about pharo is welcome 
>
> Tx cyril
>
> For class comment I image that we want
>
> !
>
> -
> -
> *url*
> and bold
> [[[
>
> ]]]
>
> Did I miss something.
>
> Stef
>
>
>
>
>
> --
> [2]
> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet
> --
>
>
> 1. Headers
>
> !Header 1
> !!Header 2
> !!!Header 3
> Header 4
> !Header 5
> !!Header 6
>
> 2. Lists
>
> - Unordered List
> # Ordered list
>
> 3. Table
>
> |! Left |! Right |! Centered
> |{Left |}Right| Centered
>
>
> 4. Description
> Note
> on a new line
>
> ;head
> :item
>
>
> 5. Emphasis
>
> ""bold""
> ''italic''
> --strikethrough--
> __underscore__
> ==inline code==
> @@subscript@@
> ^^sub-script^^
>
> 6. Code blocks
>
>  [[[lab­el=­hel­loS­cri­pt|­cap­tio­n=How to print Hello
> World|­lan­gua­ge=­Sma­lltalk
>  Transcript show: 'Hello World'.
>  \]]]
>
>
> 7. Raw
>
>
> {{{latex:
> this is how you inject raw \LaTeX in your output file
> }}}
>
> {{{mar­kdown:
> this is how you inject raw `markdown` in your output file
> }}}
>
> {{{html:
> this is how you inject raw ­htm­l in your output file
> }}}
>
>
> 8. Links
>
> Anchor @anchor (new line)
> Internal link *anchor*
> External link *Google>http://google.com*
> Image +Caption>file://image.png|width=50|label=label+
>
>
> 9. Annotation
> Note
> on a new line
>
> Annotation @@note this is a note
> Todo item @@todo this is to do
>
>
> 10. Comments
>
> % each line starting with % is commented
>
>
> 11. References
>
> This document is copied from
> http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> [3] Example pillar code for slides
> --
>
> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-Templates/SlideExample.pillar
>
> {
> "title":"To the Roots of Objects",
> "subtitle":"Learning from beauty",
> "author":"Stephane Ducasse",
> "complement":"http://stephane.ducasse.free.fr/  
> stephane.duca...@inria.fr"
> }
>
>
> ${toc:depthLevel=2|level=0|highlight=0}$
>
> %Les sections ne sont pas des titres de slide mais définnissent la
> structure du doucment. Il est possible de rajouter
> "renderStructureAsSlide":false dans pillar.conf pour ne pas créer de
> slide à partir d'un titre.
>
>
> ${slide:title=License}$
>
> +>file://figures/CreativeCommons.png|width=50|label=figCreativeCommons+
>
>
> ! Introduction
>
> %
> ${toc:depthLevel=1|level=0|highlight=1}$
>
>
> 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[Tudor Girba]

Hi,

As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for 
Pillar working on top of Bloc.

You can get it by loading:

Iceberg enableMetacelloIntegration: true.
Metacello new
   baseline: 'GToolkit';
   repository: 'github://feenkcom/gtoolkit/src';
   load.

For example, you can then inspect:
'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillar’ asFileReference

Cheers,
Doru


> On Nov 10, 2017, at 12:58 PM, H. Hirzel  wrote:
> 
> A note:
> 
> Tudor Girba wrote:
> Fri, Aug 25, 2017 at 1:31 PM
> Reply-To: Any question about pharo is welcome 
> To: Any question about pharo is welcome 
> 
> Hi,
> 
> As mentioned in an announcement about 10 days ago, we are building a
> Pillar editor with inline viewing abilities in Bloc. Here is how it
> looked like. Please note the embedded picture. We continued working on
> it since then and we will probably announce the next version this
> weekend:
> 
> 
> Maybe there is now enough progress to do simple presentations in Bloc?
> 
> 
> On 11/10/17, H. Hirzel  wrote:
>> Hello
>> 
>> In the thread 'including Pillar in Pharo image by default' it was
>> suggested by Stephane Ducasse to include a subset of Pillar in the
>> Pharo image[1] .
>> 
>> I'd like to extend that proposal a little bit it in order  to do very
>> simple presentations. This should allow to describe at least part of
>> the slides used in the MOOC course [3].
>> 
>> This will be  _a possible_ solution to the question  brought up in the
>> thread 'Writing "powerpoint" like presentations in Pharo?'.
>> 
>> Another use is to write instructions with executable content within
>> the image ("Assistants").
>> 
>> So below is the a proposal for a Pillar syntax _subset_ for class
>> comments and _simple_ presentations.
>> The numbering scheme follows the 'Pillar syntax cheat sheet' [2]
>> 
>> 
>> 
>> 
>> MINI PILLAR SYNTAX (a subset of Pillar)
>> 
>> 1. Headers
>> 
>>!Header 1
>>!!Header 2
>>!!!Header 3
>> 
>> 
>> 2. Lists
>> 
>>- Unordered List
>># Ordered list
>> 
>> 
>> 
>> 5. Emphasis
>> 
>>""bold""
>> 
>> 
>> 6. Code blocks
>> 
>> [[[
>> Transcript show: 'Hello World'.
>> \]]]
>> 
>> 
>> 9. Annotation
>> 
>> ${slide:title=About Pharo}$
>> 
>> 
>> 
>> 
>> Next week I plan to implement the rendering of this 'Mini Pillar' in
>> Morphic using the Morphic API subset that works in Pharo and Squeak.
>> 
>> A renderer using Bloc would also be nice. [4]
>> 
>> Comments, suggestions, code snippets and other help is welcome.
>> 
>> Regards
>> Hannes
>> 
>> 
>> 
>> 
>> --
>> [1] Pillar subset for class comments
>> 
>> Stephane Ducasse
>> Fri, Aug 11, 2017 at 7:09 PM
>> To: Any question about pharo is welcome 
>> 
>> Tx cyril
>> 
>> For class comment I image that we want
>> 
>> !
>> 
>> -
>> -
>> *url*
>> and bold
>> [[[
>> 
>> ]]]
>> 
>> Did I miss something.
>> 
>> Stef
>> 
>> 
>> 
>> 
>> 
>> --
>> [2]
>> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet
>> --
>> 
>> 
>> 1. Headers
>> 
>>!Header 1
>>!!Header 2
>>!!!Header 3
>>Header 4
>>!Header 5
>>!!Header 6
>> 
>> 2. Lists
>> 
>>- Unordered List
>># Ordered list
>> 
>> 3. Table
>> 
>>|! Left |! Right |! Centered
>>|{Left |}Right| Centered
>> 
>> 
>> 4. Description
>> Note
>> on a new line
>> 
>>;head
>>:item
>> 
>> 
>> 5. Emphasis
>> 
>>""bold""
>>''italic''
>>--strikethrough--
>>__underscore__
>>==inline code==
>>@@subscript@@
>>^^sub-script^^
>> 
>> 6. Code blocks
>> 
>> [[[lab­el=­hel­loS­cri­pt|­cap­tio­n=How to print Hello
>> World|­lan­gua­ge=­Sma­lltalk
>> Transcript show: 'Hello World'.
>> \]]]
>> 
>> 
>> 7. Raw
>> 
>> 
>>{{{latex:
>>this is how you inject raw \LaTeX in your output file
>>}}}
>> 
>>{{{mar­kdown:
>>this is how you inject raw `markdown` in your output file
>>}}}
>> 
>>{{{html:
>>this is how you inject raw ­htm­l in your output file
>>}}}
>> 
>> 
>> 8. Links
>> 
>>Anchor @anchor (new line)
>>Internal link *anchor*
>>External link *Google>http://google.com*
>>Image +Caption>file://image.png|width=50|label=label+
>> 
>> 
>> 9. Annotation
>> Note
>> on a new line
>> 
>>Annotation @@note this is a note
>>Todo item @@todo this is to do
>> 
>> 
>> 10. Comments
>> 
>>% each line starting with % is commented
>> 
>> 
>> 11. References
>> 
>> This document is copied from
>> http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/
>> 

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

[H. Hirzel]

A note:

Tudor Girba wrote:
  Fri, Aug 25, 2017 at 1:31 PM
Reply-To: Any question about pharo is welcome 
To: Any question about pharo is welcome 

Hi,

As mentioned in an announcement about 10 days ago, we are building a
Pillar editor with inline viewing abilities in Bloc. Here is how it
looked like. Please note the embedded picture. We continued working on
it since then and we will probably announce the next version this
weekend:


Maybe there is now enough progress to do simple presentations in Bloc?


On 11/10/17, H. Hirzel  wrote:
> Hello
>
> In the thread 'including Pillar in Pharo image by default' it was
> suggested by Stephane Ducasse to include a subset of Pillar in the
> Pharo image[1] .
>
> I'd like to extend that proposal a little bit it in order  to do very
> simple presentations. This should allow to describe at least part of
> the slides used in the MOOC course [3].
>
> This will be  _a possible_ solution to the question  brought up in the
> thread 'Writing "powerpoint" like presentations in Pharo?'.
>
> Another use is to write instructions with executable content within
> the image ("Assistants").
>
> So below is the a proposal for a Pillar syntax _subset_ for class
> comments and _simple_ presentations.
> The numbering scheme follows the 'Pillar syntax cheat sheet' [2]
>
>
>
>
> MINI PILLAR SYNTAX (a subset of Pillar)
>
> 1. Headers
>
> !Header 1
> !!Header 2
> !!!Header 3
>
>
> 2. Lists
>
> - Unordered List
> # Ordered list
>
>
>
> 5. Emphasis
>
> ""bold""
>
>
> 6. Code blocks
>
>  [[[
>  Transcript show: 'Hello World'.
>  \]]]
>
>
> 9. Annotation
>
> ${slide:title=About Pharo}$
>
>
>
>
> Next week I plan to implement the rendering of this 'Mini Pillar' in
> Morphic using the Morphic API subset that works in Pharo and Squeak.
>
> A renderer using Bloc would also be nice. [4]
>
> Comments, suggestions, code snippets and other help is welcome.
>
> Regards
> Hannes
>
>
>
>
> --
> [1] Pillar subset for class comments
>
> Stephane Ducasse
>  Fri, Aug 11, 2017 at 7:09 PM
> To: Any question about pharo is welcome 
>
> Tx cyril
>
> For class comment I image that we want
>
> !
>
> -
> -
> *url*
> and bold
> [[[
>
> ]]]
>
> Did I miss something.
>
> Stef
>
>
>
>
>
> --
> [2]
> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet
> --
>
>
> 1. Headers
>
> !Header 1
> !!Header 2
> !!!Header 3
> Header 4
> !Header 5
> !!Header 6
>
> 2. Lists
>
> - Unordered List
> # Ordered list
>
> 3. Table
>
> |! Left |! Right |! Centered
> |{Left |}Right| Centered
>
>
> 4. Description
> Note
> on a new line
>
> ;head
> :item
>
>
> 5. Emphasis
>
> ""bold""
> ''italic''
> --strikethrough--
> __underscore__
> ==inline code==
> @@subscript@@
> ^^sub-script^^
>
> 6. Code blocks
>
>  [[[lab­el=­hel­loS­cri­pt|­cap­tio­n=How to print Hello
> World|­lan­gua­ge=­Sma­lltalk
>  Transcript show: 'Hello World'.
>  \]]]
>
>
> 7. Raw
>
>
> {{{latex:
> this is how you inject raw \LaTeX in your output file
> }}}
>
> {{{mar­kdown:
> this is how you inject raw `markdown` in your output file
> }}}
>
> {{{html:
> this is how you inject raw ­htm­l in your output file
> }}}
>
>
> 8. Links
>
> Anchor @anchor (new line)
> Internal link *anchor*
> External link *Google>http://google.com*
> Image +Caption>file://image.png|width=50|label=label+
>
>
> 9. Annotation
> Note
> on a new line
>
> Annotation @@note this is a note
> Todo item @@todo this is to do
>
>
> 10. Comments
>
> % each line starting with % is commented
>
>
> 11. References
>
> This document is copied from
> http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> [3] Example pillar code for slides
> --
>
> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-Templates/SlideExample.pillar
>
> {
>   "title":"To the Roots of Objects",
>   "subtitle":"Learning from beauty",
>   "author":"Stephane Ducasse",
>   "complement":"http://stephane.ducasse.free.fr/ 
> stephane.duca...@inria.fr"
> }
>
>
> ${toc:depthLevel=2|level=0|highlight=0}$
>
> %Les sections ne sont pas des titres de slide mais définnissent la
> structure du doucment. Il est possible de rajouter
> "renderStructureAsSlide":false dans pillar.conf