April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PetitMarkdown

by Damien Cassou

phil(a)highoctane.be <phil(a)highoctane.be> writes: > Customer opinion on the output: why are figures not where I expect them to > be? they are where the *reader* expects them to be :-). The author of TeX thought that a machine can best decide where to put a figure because when you write the TeX source you don't know where in the page a particular figure will be placed when rendered as PDF: each time you add a paragraph somewhere, you move everything after it. > Most of the figures are HD screenshots. Moving them around sucks. why? > I'll try the no label thing. But labels are useful. Labels (i.e., identifiers) are useful only when you reference a figure from the text. Captions (i.e., explaining texts) are useful to describe the figure. > HTML export is not doing that. yes, because HTML has not notion of page. PDF is very nice for printing and LaTeX makes sure that figures are nicely placed on the paper. HTML is not meant to be printed. If you print an HTML page, the result is often ugly. > LaTeX is an interim tool to get the PDF output. Would it be possible > to use Artefact instead? probably, but don't expect it to look nice because the (La)TeX authors are experts in the domain and we are not. I already talked about that with Olivier (on CC) and I think he agreed IIRC. > LaTeX toolchain is *huge*. agree. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] PetitMarkdown

by Stephan Eggermont

On 16/04/15 12:07, phil(a)highoctane.be wrote: > Customer opinion on the output: why are figures not where I expect them > to be? > > Most of the figures are HD screenshots. Moving them around sucks. > I'll try the no label thing. But labels are useful. > HTML export is not doing that. > LaTeX is an interim tool to get the PDF output. Would it be possible to > use Artefact instead? Not without creating extremely ugly documentation, at the current state of Artefact layouting. Line breaking is primitive, support for other than base-14 fonts is missing, pngs are rendered, not embedded. > LaTeX toolchain is *huge*. Yeah, it is. The best object model for documentation is that of Framemaker. Current machines should be fast enough to run something like that in Smalltalk instead of c now, 20 years later. Stephan

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Damien Cassou

Kasper Osterbye <kasper(a)itu.dk> writes: > *>pharo://Class/method* you don't need the $>. This should be fine: *pharo://Class/method* -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Damien Cassou

kilon alios <kilon.alios(a)gmail.com> writes: > thank you Damien, will give a look , may I also use configuration browser ? > is it up to date ? you can use the configuration browser to get Pillar, but not the nautilus patch. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] [ANN] Pharo 4.0 is released!

by Torsten Bergmann

What a nice release! Future is wide open ... and we have to/will shape it. While we can enjoy the shiny Pharo 4.0 release please remember that I already created: http://smalltalkhub.com/#!/~Pharo/Pharo50Inbox http://smalltalkhub.com/#!/~Pharo/Pharo50 to wait for even more powerful stuff ;) Also do not forget to put working configurations of your projects into http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo40 Thx T.

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by kilon alios

thank you Damien, will give a look , may I also use configuration browser ? is it up to date ? On Thu, Apr 16, 2015 at 11:16 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > kilon alios <kilon.alios(a)gmail.com> writes: > > > ok, but where and which repo ? Smalltalkhub ? GitHub ? Is part of Pillar > ? > > How I install these packages ? > > load a Pillar image from > https://ci.inria.fr/pharo-contribution/job/Pillar (using the launcher > for example :-)) and load Pillar-TextRenderer and > Pillar-NautilusProofOfConcept in this order from the pillar repository > (already in monticello). > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

April 16, 2015

Re: [Pharo-dev] [ANN] Pharo 4.0 is released!

by Norbert Hartl

Hurrrray!!!! Congrats you guys for the hard work!!!! Norbert > Am 16.04.2015 um 11:29 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Please spread widely. > Sorry for multiple posts. > > (this post can be see here: http://pharo.org/news/pharo-4.0-released <http://pharo.org/news/pharo-4.0-released>) > > Dear World, > > Pharo 4.0 (http://www.pharo.org <http://www.pharo.org/>) is here. > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > Many things have changed in Pharo. Here are some highlights: > - Inspector/Playground/Spotter are new moldable development tools for inspecting, coding and searching objects. > - Slots model instance variables as first class entities and enable meta-programming on this level. > - ShoreLine reporter introduces a way to report system errors and collect statistics, that we will use for future improvements > - Dark theme. > > These are just the more prominent highlights, but the details are just as important. We have closed 1697 issues in Pharo 4. Take a moment to go through a more detailed recount of the progress: > > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md <https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md> > Pharo is improving on many fronts, but one of the most prominent changes is the addition of moldable tools for inspection and search. These tools provide extension mechanisms that allow every object to define ways in which it can be understood effectively. To provide an idea of the impact of the already existing extensions, the map below shows the Pharo classes grouped in packages, highlighting in red those parts of the system that have at least one such custom view coming with the main distribution. The spread of these extensions shows that moldability is powerful mechanism that can be used in many contexts. > > > > Remember that Pharo is your platform. We thank all the contributors of this release: > > Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin > > And all those who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... > > Pharo 4.0 is another big step. And, the best is yet to come. > > Enjoy! > The Pharo Team > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki

April 16, 2015

Re: [Pharo-dev] [Vm-dev] [ANN] Pharo 4.0 is released!

by phil＠highoctane.be

Le 16 avr. 2015 11:56, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > > Great job! > > Thank you everyone for the contributions, support and trust. One more out of the door. That's great. Anyone interested in doing a podcast episode on this releasr? Chime in. Phil > > Cheers, > Doru > > > On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> Please spread widely. >> Sorry for multiple posts. >> >> (this post can be see here: http://pharo.org/news/pharo-4.0-released) >> >> Dear World, >> >> Pharo 4.0 (http://www.pharo.org) is here. >> >> Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. >> >> Many things have changed in Pharo. Here are some highlights: >> - Inspector/Playground/Spotter are new moldable development tools for inspecting, coding and searching objects. >> - Slots model instance variables as first class entities and enable meta-programming on this level. >> - ShoreLine reporter introduces a way to report system errors and collect statistics, that we will use for future improvements >> - Dark theme. >> >> These are just the more prominent highlights, but the details are just as important. We have closed 1697 issues in Pharo 4. Take a moment to go through a more detailed recount of the progress: >> >> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md >> >> Pharo is improving on many fronts, but one of the most prominent changes is the addition of moldable tools for inspection and search. These tools provide extension mechanisms that allow every object to define ways in which it can be understood effectively. To provide an idea of the impact of the already existing extensions, the map below shows the Pharo classes grouped in packages, highlighting in red those parts of the system that have at least one such custom view coming with the main distribution. The spread of these extensions shows that moldability is powerful mechanism that can be used in many contexts. >> >> >> Remember that Pharo is your platform. We thank all the contributors of this release: >> >> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin >> >> And all those who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... >> >> Pharo 4.0 is another big step. And, the best is yet to come. >> >> Enjoy! >> The Pharo Team >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

April 16, 2015

Re: [Pharo-dev] PetitMarkdown

by phil＠highoctane.be

Le 16 avr. 2015 10:41, "Damien Cassou" <damien.cassou(a)gmail.com> a Ã©crit : > > > Christophe Demarey <Christophe.Demarey(a)inria.fr> writes: > > > Le 14 avr. 2015 Ã 22:51, phil(a)highoctane.be a Ã©crit : > > > >> I hate the figures not going where I want due to the LaTeX generation in Pillar. > > > > There should be options to place it where you want. Maybe a pillar expert could answer? > > this is not possible and, in my opinion, not desired. > > The following explains my reasons but requires some LaTeX knowledge to > be understood. > > LaTeX does a really good job a placing figures at nice locations. For > example, if your paragraph ends with 2 lines at the top of a page and > you place a figure after this paragraph, LaTeX will make sure the figure > appears at the top of a page and not after the 2 lines: this is because > it would be ugly to have 2 lines, then a figure, then the rest of the > text. > > In LaTeX, you have to make sure to always write things like "as can be > seen in Figure 3" instead of "as can be seen in the figure below" > because you can never be sure of the exact location of your figures. > > Please note that if in Pillar you don't specify any label you could > reference from your text, then the figure will be placed by LaTeX at the > exact location where you put it in Pillar. This is because, in this > case, there is no way to write "as can be seen in Figure 3" when there > is no label. Customer opinion on the output: why are figures not where I expect them to be? Most of the figures are HD screenshots. Moving them around sucks. I'll try the no label thing. But labels are useful. HTML export is not doing that. LaTeX is an interim tool to get the PDF output. Would it be possible to use Artefact instead? LaTeX toolchain is *huge*. Phil > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill >

April 16, 2015

Re: [Pharo-dev] [Vm-dev] [ANN] Pharo 4.0 is released!

by Tudor Girba

Great job! Thank you everyone for the contributions, support and trust. Cheers, Doru On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Please spread widely. > Sorry for multiple posts. > > (this post can be see here: http://pharo.org/news/pharo-4.0-released) > > Dear World, > > Pharo 4.0 (http://www.pharo.org) is here. > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > Many things have changed in Pharo. Here are some highlights: > - Inspector/Playground/Spotter are new moldable development tools for > inspecting, coding and searching objects. > - Slots model instance variables as first class entities and enable > meta-programming on this level. > - ShoreLine reporter introduces a way to report system errors and collect > statistics, that we will use for future improvements > - Dark theme. > > These are just the more prominent highlights, but the details are just as > important. We have closed 1697 issues in Pharo 4. Take a moment to go > through a more detailed recount of the progress: > > > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > > Pharo is improving on many fronts, but one of the most prominent changes > is the addition of moldable tools for inspection and search. These tools > provide extension mechanisms that allow every object to define ways in > which it can be understood effectively. To provide an idea of the impact of > the already existing extensions, the map below shows the Pharo classes > grouped in packages, highlighting in red those parts of the system that > have at least one such custom view coming with the main distribution. The > spread of these extensions shows that moldability is powerful mechanism > that can be used in many contexts. > > > Remember that Pharo is your platform. We thank all the contributors of > this release: > > Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, > Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury > Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, > Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei > Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, > Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane > Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, > Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, > Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, > Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max > Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot > Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, > Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, > Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian > Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, > Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin > > And all those who contributed indirectly, by reporting bugs, participating > in discussion threads, providing feedback... > > Pharo 4.0 is another big step. And, the best is yet to come. > > Enjoy! > The Pharo Team > > > -- www.tudorgirba.com "Every thing has its own flow"

April 16, 2015