- Pharo-users - lists.pharo.org

Re: [Pharo-users] including Pillar in Pharo image by default

by Stephane Ducasse

Cyril the ** can be used to point to another class for example acting as a ref. Stef On Fri, Aug 11, 2017 at 7:15 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 11/08/2017 Ã 19:12, Cyril Ferlicot D. a Ã©crit : >> >> We might want to add some syntax only for class comment and not Pillar >> itself. For example to be able to reference a class in Pharo and get a >> link to the class during the rendering. >> >> I think that we might also want the formats (bold, etc) and the ordered >> list. >> > > I just saw that you said bold after sendingâ¦ > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Aug. 11, 2017

Re: [Pharo-users] FLSerializer in Pharo 6.1

by Stephane Ducasse

Hi johannes do you have an example so that we can try here? Tx On Fri, Aug 11, 2017 at 4:06 PM, Johannes Brauer <brauer(a)nordakademie.de> wrote: > Hi everyone, > > the FLSerializer in Pharo 6.1 doesnât work. I tried the example from the class comment and I always get > > FileException: cannot open file: example.FL. > > Is that a known problem? > > Johannes

Aug. 11, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Cyril Ferlicot D.

Le 11/08/2017 Ã 19:12, Cyril Ferlicot D. a Ã©crit : > > We might want to add some syntax only for class comment and not Pillar > itself. For example to be able to reference a class in Pharo and get a > link to the class during the rendering. > > I think that we might also want the formats (bold, etc) and the ordered > list. > I just saw that you said bold after sendingâ¦ -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 11, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Cyril Ferlicot D.

Le 11/08/2017 Ã 19:09, Stephane Ducasse a Ã©crit : > Tx cyril > > For class comment I image that we want > > ! > > - > - > *url* > and bold > [[[ > > ]]] > > Did I miss something. > > Stef > > > We might want to add some syntax only for class comment and not Pillar itself. For example to be able to reference a class in Pharo and get a link to the class during the rendering. I think that we might also want the formats (bold, etc) and the ordered list. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 11, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Stephane Ducasse

Tx cyril For class comment I image that we want ! - - *url* and bold [[[ ]]] Did I miss something. Stef On Fri, Aug 11, 2017 at 6:57 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 11/08/2017 Ã 18:52, Peter Uhnak a Ã©crit : >> Hi, >> >> I would like to propose including Pillar in the Pharo image by default. >> >> My reasoning: >> >> Since we are moving to git, and most people will use github, gitlab, and the likes, it is expected to include a README.md file (or possibly more extensive documentation) alongside the code. >> >> Which means that people will (and are) writing the README mostly by hand, which of course is problematic, as e.g. code snippets can get deprecated, screenshots become outdated, etc. >> >> As Pillar tries to address these problems, it would make sense to me to include Pillar in the image by default, as anyone using git (which eventually should be everyone) will most likely benefit from writing their documentation in Pillar. >> Similarly using Pillar would open an avenue to provide the documentation in-image, e.g. one exporter for html/markdown, and another one for Pharo's Help system. >> >> I could, of course, install Pillar every time, but considering thats extra effort and in the extra time I can fix the issues by hand, I don't have such an incentive to use Pillar for this. >> >> Questions & Problems: >> >> I don't know by how much would pillar increase the image size. Perhaps there could be (a) "lightweight Pillar" (that would include just pillar & markdown exporter), or (b) we would have different images for different uses. >> >> By different images I mean something along the lines of >> a) developer image - meant to be directly used by developers to create their software >> b) production image - as a foundation for running systems / users >> >> Does this make sense? >> >> Peter >> > > Hi, > > I know that Stephane want to includes a light version of Pillar in the > image. > > Currently he is working on a way to remove Magritte dependency from > Pillar. Another step would be to get a minimal parser not relying on > PetitParser. This parser would parse only a subset of the Pillar syntax > that can be used for writing class comments. If this subset is defined > (I we have the list of all Document Items we want to understand), I can > give a try to make this light parse. > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Aug. 11, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Stephane Ducasse

Let us rephrase it: - I would like to have a mini pillar with a simplified model and visitor to display class comments. - then think about Pharo 70 as the core and birth of a new generation of imageS I will restart to revisit Pillar once I'm done with the Lecture at Prague. Stef On Fri, Aug 11, 2017 at 6:52 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > Hi, > > I would like to propose including Pillar in the Pharo image by default. > > My reasoning: > > Since we are moving to git, and most people will use github, gitlab, and the likes, it is expected to include a README.md file (or possibly more extensive documentation) alongside the code. > > Which means that people will (and are) writing the README mostly by hand, which of course is problematic, as e.g. code snippets can get deprecated, screenshots become outdated, etc. > > As Pillar tries to address these problems, it would make sense to me to include Pillar in the image by default, as anyone using git (which eventually should be everyone) will most likely benefit from writing their documentation in Pillar. > Similarly using Pillar would open an avenue to provide the documentation in-image, e.g. one exporter for html/markdown, and another one for Pharo's Help system. > > I could, of course, install Pillar every time, but considering thats extra effort and in the extra time I can fix the issues by hand, I don't have such an incentive to use Pillar for this. > > Questions & Problems: > > I don't know by how much would pillar increase the image size. Perhaps there could be (a) "lightweight Pillar" (that would include just pillar & markdown exporter), or (b) we would have different images for different uses. > > By different images I mean something along the lines of > a) developer image - meant to be directly used by developers to create their software > b) production image - as a foundation for running systems / users > > Does this make sense? > > Peter >

Aug. 11, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Cyril Ferlicot D.

Le 11/08/2017 Ã 18:52, Peter Uhnak a Ã©crit : > Hi, > > I would like to propose including Pillar in the Pharo image by default. > > My reasoning: > > Since we are moving to git, and most people will use github, gitlab, and the likes, it is expected to include a README.md file (or possibly more extensive documentation) alongside the code. > > Which means that people will (and are) writing the README mostly by hand, which of course is problematic, as e.g. code snippets can get deprecated, screenshots become outdated, etc. > > As Pillar tries to address these problems, it would make sense to me to include Pillar in the image by default, as anyone using git (which eventually should be everyone) will most likely benefit from writing their documentation in Pillar. > Similarly using Pillar would open an avenue to provide the documentation in-image, e.g. one exporter for html/markdown, and another one for Pharo's Help system. > > I could, of course, install Pillar every time, but considering thats extra effort and in the extra time I can fix the issues by hand, I don't have such an incentive to use Pillar for this. > > Questions & Problems: > > I don't know by how much would pillar increase the image size. Perhaps there could be (a) "lightweight Pillar" (that would include just pillar & markdown exporter), or (b) we would have different images for different uses. > > By different images I mean something along the lines of > a) developer image - meant to be directly used by developers to create their software > b) production image - as a foundation for running systems / users > > Does this make sense? > > Peter > Hi, I know that Stephane want to includes a light version of Pillar in the image. Currently he is working on a way to remove Magritte dependency from Pillar. Another step would be to get a minimal parser not relying on PetitParser. This parser would parse only a subset of the Pillar syntax that can be used for writing class comments. If this subset is defined (I we have the list of all Document Items we want to understand), I can give a try to make this light parse. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 11, 2017

including Pillar in Pharo image by default

by Peter Uhnak

Hi, I would like to propose including Pillar in the Pharo image by default. My reasoning: Since we are moving to git, and most people will use github, gitlab, and the likes, it is expected to include a README.md file (or possibly more extensive documentation) alongside the code. Which means that people will (and are) writing the README mostly by hand, which of course is problematic, as e.g. code snippets can get deprecated, screenshots become outdated, etc. As Pillar tries to address these problems, it would make sense to me to include Pillar in the image by default, as anyone using git (which eventually should be everyone) will most likely benefit from writing their documentation in Pillar. Similarly using Pillar would open an avenue to provide the documentation in-image, e.g. one exporter for html/markdown, and another one for Pharo's Help system. I could, of course, install Pillar every time, but considering thats extra effort and in the extra time I can fix the issues by hand, I don't have such an incentive to use Pillar for this. Questions & Problems: I don't know by how much would pillar increase the image size. Perhaps there could be (a) "lightweight Pillar" (that would include just pillar & markdown exporter), or (b) we would have different images for different uses. By different images I mean something along the lines of a) developer image - meant to be directly used by developers to create their software b) production image - as a foundation for running systems / users Does this make sense? Peter

Aug. 11, 2017

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

by TedVanGaalen

.. hard to imagine I am the only one with this problem? -- View this message in context: http://forum.world.st/Pharo-6-0-and-6-1-64-bit-freeze-on-MacMini-tp4957969p… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 11, 2017

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

by TedVanGaalen

thanks for you reply, Esteban well, I can still use Pharo 5 in the mean time, no problem. how/where should I forward this to vm-dev? Regards, have a nice holiday! Ted -- View this message in context: http://forum.world.st/Pharo-6-0-and-6-1-64-bit-freeze-on-MacMini-tp4957969p… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 11, 2017