- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by Damien Pollet

I think the book.pillar root file is the way. On 17 September 2016 at 08:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Great. I also started to use it, and I would be interested in working also > on creating a webpage out of the box. > > It is also unclear to me how to deal with pillar.conf (I did not look at > the code yet.). Should I rely on a book.pillar root class that embeds the > chapter files? Or is there a way to still rely on a declarative way like we > had in pillar.conf to embed those files? > > Cheers, > Doru > > > > On Sep 16, 2016, at 10:02 PM, Damien Pollet <damien.pollet(a)gmail.com> > wrote: > > > > Yes, I will first cleanup the one in the book archetype, and unify it > with the Enterprise & Spec books, since they seem to be the most up-to-date > with Pillar. > > > > On 16 September 2016 at 21:19, stepharo <stepharo(a)free.fr> wrote: > > Damien Pollet started to have a look at the makefile and this is on my > todo to try. > > > > > > Stef > > > > > > Le 15/9/16 Ã 00:13, Johan Fabry a Ã©crit : > > > > Hi Doru, > > > > it looks like thereâs a problem with copySupport.mk, I had the same > problem with the Spec booklet. The file is using Linux only syntax for the > cp command. This was fixed for the Spec booklet after I raised an issue > there, but it seems the fix was not propagated everywhere it needs to be. > Have a look at https://github.com/SquareBracketAssociates/ > BuildingUIWithSpec/blob/master/copySupport.mk and try to update your > copySupport, it may fix your problem. > > > > -- > > Does this mail seem too brief? Sorry for that, I donât mean to be rude! > Please see http://emailcharter.org . > > > > Johan Fabry - http://pleiad.cl/~jfabry > > PLEIAD and RyCh labs - Computer Science Department (DCC) - > University of Chile > > > > On Sep 14, 2016, at 18:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > Ok, I found this document: > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/ > lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html > > > > And now I tried this: > > > > wget --no-check-certificate https://raw.githubusercontent. > com/pillar-markup/pillar/master/download.sh > > chmod +x download.sh > > ./download.sh > > ./pillar archetype book > > > > and I got the book template. But, I do not know how to compile the book. > I tried > > > > make > > > > or > > make book > > > > but I get: > > > > make > > mkdir -p ./book-result > > find . -type d -path ./book-result -prune -o -wholename "*/figures" > -exec cp {} --parents -r ./book-result \; > > cp: ./Chapters/Chapter1/figures is a directory (not copied). > > cp: --parents: No such file or directory > > cp: -r: No such file or directory > > cp: ./figures is a directory (not copied). > > cp: --parents: No such file or directory > > cp: -r: No such file or directory > > cp: ./support/figures is a directory (not copied). > > cp: --parents: No such file or directory > > cp: -r: No such file or directory > > cp -r support/ ./book-result > > cp .latexmkrc ./book-result > > cp: .latexmkrc: No such file or directory > > make: *** [copySupport] Error 1 > > > > > > I must be doing something wrong, but I do not know what. I am on a Mac > 10.11 and I am using bash. Could someone point me in the right direction? > > > > Cheers, > > Doru > > > > > > On Sep 14, 2016, at 10:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > Where can I find the new template system for Pillar? > > > > Cheers, > > Doru > > > > > > On Jul 22, 2016, at 3:41 PM, Thibault ARLOING < > thibault.arloing(a)hotmail.fr> wrote: > > > > Hello, > > > > I'm happy to announce the latest release of Pillar. > > This release has been possible because of the hard work of Damien > Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. > > What did it bring and what are the largest changes ? > > > > â¢ Huge cleaning of code and Dependencies > > â¢ Many bug fixes > > â¢ Huge refactoring of internal parts > > â¢ Extract phase management into an external project > (LightPhaser) > > â¢ Transformers and Phases are all Pipes > > Remove Compilation cycle > > â¢ Remove template handling from Pillar > > â¢ Remove generation of pillarpostExport.sh > > â¢ Pillar now exports files to JSON format > > â¢ Command for pillar archetypes "./pillar archetype book", book > can be replaced by other archetype names (see Pillar documentation) > > â¢ Possibility to load an archetype with a Makefile to compile > pillar files > > Features > > â¢ Check phase to check syntax > > â¢ EPub exporter for e-books (use pillar archetypes for this) > > â¢ Semantic links to Youtube and Wikipedia > > â¢ Citations for LaTeX > > â¢ Structures (see Pillar documentation) > > â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc > > â¢ Improvement of parsing configuration failure message > > Major changes > > â¢ Metadata field in configuration to separate data from > configuration properties > > â¢ Support files in configuration does no longer exists > > â¢ "disableTransformers" property is now named "disabledPhases" > > â¢ AsciiDoc file extension is now ".asciidoc" > > â¢ Pillar now manages one input file, not a collection of input > files anymore > > â¢ Parameter inputFiles is now replaced by inputFile > > The documentation of Pillar will be update as soon as possible to fit > those changes. > > > > Cheers, > > > > Thibault > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Sometimes the best solution is not the best solution." > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "It's not how it is, it is how we see it." > > > > > > > > > > > > > > > > > > > > > > -- > > Damien Pollet > > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- > www.tudorgirba.com > www.feenk.com > > "What is more important: To be happy, or to make happy?" > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Sept. 17, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by Tudor Girba

Hi, Great. I also started to use it, and I would be interested in working also on creating a webpage out of the box. It is also unclear to me how to deal with pillar.conf (I did not look at the code yet.). Should I rely on a book.pillar root class that embeds the chapter files? Or is there a way to still rely on a declarative way like we had in pillar.conf to embed those files? Cheers, Doru > On Sep 16, 2016, at 10:02 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > Yes, I will first cleanup the one in the book archetype, and unify it with the Enterprise & Spec books, since they seem to be the most up-to-date with Pillar. > > On 16 September 2016 at 21:19, stepharo <stepharo(a)free.fr> wrote: > Damien Pollet started to have a look at the makefile and this is on my todo to try. > > > Stef > > > Le 15/9/16 Ã 00:13, Johan Fabry a Ã©crit : > > Hi Doru, > > it looks like thereâs a problem with copySupport.mk, I had the same problem with the Spec booklet. The file is using Linux only syntax for the cp command. This was fixed for the Spec booklet after I raised an issue there, but it seems the fix was not propagated everywhere it needs to be. Have a look at https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/c… and try to update your copySupport, it may fix your problem. > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > On Sep 14, 2016, at 18:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Ok, I found this document: > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > And now I tried this: > > wget --no-check-certificate https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > chmod +x download.sh > ./download.sh > ./pillar archetype book > > and I got the book template. But, I do not know how to compile the book. I tried > > make > > or > make book > > but I get: > > make > mkdir -p ./book-result > find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec cp {} --parents -r ./book-result \; > cp: ./Chapters/Chapter1/figures is a directory (not copied). > cp: --parents: No such file or directory > cp: -r: No such file or directory > cp: ./figures is a directory (not copied). > cp: --parents: No such file or directory > cp: -r: No such file or directory > cp: ./support/figures is a directory (not copied). > cp: --parents: No such file or directory > cp: -r: No such file or directory > cp -r support/ ./book-result > cp .latexmkrc ./book-result > cp: .latexmkrc: No such file or directory > make: *** [copySupport] Error 1 > > > I must be doing something wrong, but I do not know what. I am on a Mac 10.11 and I am using bash. Could someone point me in the right direction? > > Cheers, > Doru > > > On Sep 14, 2016, at 10:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Where can I find the new template system for Pillar? > > Cheers, > Doru > > > On Jul 22, 2016, at 3:41 PM, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: > > Hello, > > I'm happy to announce the latest release of Pillar. > This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. > What did it bring and what are the largest changes ? > > â¢ Huge cleaning of code and Dependencies > â¢ Many bug fixes > â¢ Huge refactoring of internal parts > â¢ Extract phase management into an external project (LightPhaser) > â¢ Transformers and Phases are all Pipes > Remove Compilation cycle > â¢ Remove template handling from Pillar > â¢ Remove generation of pillarpostExport.sh > â¢ Pillar now exports files to JSON format > â¢ Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) > â¢ Possibility to load an archetype with a Makefile to compile pillar files > Features > â¢ Check phase to check syntax > â¢ EPub exporter for e-books (use pillar archetypes for this) > â¢ Semantic links to Youtube and Wikipedia > â¢ Citations for LaTeX > â¢ Structures (see Pillar documentation) > â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc > â¢ Improvement of parsing configuration failure message > Major changes > â¢ Metadata field in configuration to separate data from configuration properties > â¢ Support files in configuration does no longer exists > â¢ "disableTransformers" property is now named "disabledPhases" > â¢ AsciiDoc file extension is now ".asciidoc" > â¢ Pillar now manages one input file, not a collection of input files anymore > â¢ Parameter inputFiles is now replaced by inputFile > The documentation of Pillar will be update as soon as possible to fit those changes. > > Cheers, > > Thibault > -- > www.tudorgirba.com > www.feenk.com > > "Sometimes the best solution is not the best solution." > > -- > www.tudorgirba.com > www.feenk.com > > "It's not how it is, it is how we see it." > > > > > > > > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

Sept. 17, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by Tudor Girba

Hi, > On Sep 16, 2016, at 8:37 PM, stepharo <stepharo(a)free.fr> wrote: > > + 1 > > Changing the language metamodel for simple validated comments is a huge effort for nothing. > Clement is good at VM level but not at other level :) I think there is a misunderstanding :). I do not see any implication to the language meta-model in the remark of Clement. In fact, I expressed exactly the same opinion, that the design of things like PythonDoc comes from the fact that those people do not rely on an IDE, so their design focuses on the only thing they have: source code. Clement remarked that we already have SUnit tests and he suggested that we could just enhance the IDE to present them next to the methods. This might actually be less straightforward with SUnit because it was not made for preserving links to the code, but it can work out of the box with something like GTExamples. Cheers, Doru > Stef > > Le 16/9/16 Ã 14:18, Denis Kudriashov a Ã©crit : >> >> 2016-09-16 13:42 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >> Why don't you just change nautilus to have two text areas, one with the test corresponding to the method and the other one with the method's code ? >> >> You're saying: >> Their values is active documentation that can be automatically validated. >> That can also be applied to test we've already had with SUnit. If the only difference you want is to display the test next to the method, then it's an IDE problem, nothing has to be changed but the IDE. >> >> In python they have no other choices than putting tests in comments because their IDE is a text editor, they cannot create other panes or anything like that. >> >> It is of course true. But Stef suggestion is really much much simpler. It is just convention how to write examples inside comments. Then tools could work with them and Nicolai already provide simple extension for Nautilus. >> We already has a lot of comments with examples inside. Making them discoverable and testable will be nice. >> > -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

Sept. 17, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by stepharo

Le 16/9/16 Ã 21:58, Damien Pollet a Ã©crit : > On 16 September 2016 at 20:42, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Daemons of over-engineering are tempting us because this is cooler > to to design something complex. > > > Dreaming of crazy features is a good thing. Talking from experience, I > prefer that to not dreaming, which is pretty dull. Yes now create a thread: the dreams for a cool documentation system in Pharo and I will follow and add to it happily, What I was asking in this thread is how can we catch a low hanging fruit and get an immmediate impact because it looks so easy to do. Stef > > And over-engineering is of course the wrong path. But the temptation > to do so is revealing of where the system is too complex. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > >

Sept. 17, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by Ben Coman

On Sat, Sep 17, 2016 at 3:45 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-09-16 18:42 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >> Hi All, >> >> >> >> _,,,^..^,,,_ (phone) >> > On Sep 14, 2016, at 10:50 PM, Marcus Denker <marcus.denker(a)inria.fr> >> > wrote: >> > >> > >> >>> >> >>> We can change it back and maybe add support for the reformatter to not >> >>> convert it to the literal array #(3 #+ 4) . >> >> >> >> I do not know in fact this is why I asked :) >> >> Now may be my idea to use pragma to get something like pythondoctest is >> >> a bad idea >> >> but I really want to have literal programming. >> >> What do you think? >> > I like the idea to show examples/tests close to code, but pragmas are >> > not really good... >> > >> >> If we have ' ' then it would be good that the syntax higlighter works >> >> with a special mode inside the ' ' >> > >> > it is just a string. How do you know that it contains code? >> > >> > Would you highlight all string in all code as if it contained code? Or >> > would you add this just for >> > Pragmas? But even there, strings are string, not code. >> > >> > I think we can conclude that pragmas are not a good solution to the >> > problem, as they are far >> > too limited to express code. >> >> I think that's not a safe conclusion. We know from Igor's use of Kieran >> arrays for C signatures in the UFFI, and can easily extrapolate here, that >> arbitrary Smalltalk expressions /can/ be expressed in literal arrays. S >> expressions work for lisp. >> >> In this particular case special casing pretty printing of literal arrays >> in pragmas would be all that's needed to make the code look beautiful. Why >> throw the baby out with the bath water? It would be so easy to make this >> work well. > > > We can try this as well. And it is far more easier to work with this > expressions if they are pragma arguments, than to parse the comment to find > some code within. > On the other hand, it looks much nicer if we have the examples right in the > method doc. you have some text describing the method, some code, some more > text about the reslt. > > >> >> >> The only thing I'd do would be to print like this to make it clear that >> the argument t is a literal Array and not some magic form of code: >> >> <expr: #(3 + 4) result: 7> >> > > Yes, I would like to change this anyway, even for literal arrays for ffi, > calls like > > mouseStateX: x y: y > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: > errorCode> > ^ self nbCall: #( Uint32 SDL_GetMouseState ( int* x , int* y ) ) > > this will be reformatted to > > mouseStateX: x y: y > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: > 'errorCode'> > ^ self nbCall: #(#Uint32 #SDL_GetMouseState #(#int #* #x #, #int #* #y)) errr, yuck! Thats not pretty at all. Is there some way to avoid that? As I've been getting started with FFI its been really nice visually to see a *direct* correspondence between the C header file declaration and the in-Image method. Actually I think it would be useful to go a step further to have positional rather than named parameters for FFI methods. At the moment the method names still end up a bit mangled. This seems feasible since currently an open-round-bracket is invalid syntax if not preceded by an assignment or colon. e.g. myvar := (a + b). "okay" self setVar: (a + b). "okay" self setVar( a + b ). "currently invalid syntax - but could could represent an FFI call" defined like... SomeLibrary class >> setVar( newValue ) ^ self ffiCall: #( int setVar ( int newValue ) But I expect its not something we'd want to leap into. cheers -ben

Sept. 17, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by Damien Pollet

Yes, I will first cleanup the one in the book archetype, and unify it with the Enterprise & Spec books, since they seem to be the most up-to-date with Pillar. On 16 September 2016 at 21:19, stepharo <stepharo(a)free.fr> wrote: > Damien Pollet started to have a look at the makefile and this is on my > todo to try. > > > Stef > > > Le 15/9/16 Ã 00:13, Johan Fabry a Ã©crit : > > Hi Doru, >> >> it looks like thereâs a problem with copySupport.mk, I had the same >> problem with the Spec booklet. The file is using Linux only syntax for the >> cp command. This was fixed for the Spec booklet after I raised an issue >> there, but it seems the fix was not propagated everywhere it needs to be. >> Have a look at https://github.com/SquareBrack >> etAssociates/BuildingUIWithSpec/blob/master/copySupport.mk and try to >> update your copySupport, it may fix your problem. >> >> -- >> Does this mail seem too brief? Sorry for that, I donât mean to be rude! >> Please see http://emailcharter.org . >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD and RyCh labs - Computer Science Department (DCC) - University >> of Chile >> >> On Sep 14, 2016, at 18:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Ok, I found this document: >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBo >>> ok/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html >>> >>> And now I tried this: >>> >>> wget --no-check-certificate https://raw.githubusercontent. >>> com/pillar-markup/pillar/master/download.sh >>> chmod +x download.sh >>> ./download.sh >>> ./pillar archetype book >>> >>> and I got the book template. But, I do not know how to compile the book. >>> I tried >>> >>> make >>> >>> or >>> make book >>> >>> but I get: >>> >>> make >>> mkdir -p ./book-result >>> find . -type d -path ./book-result -prune -o -wholename "*/figures" >>> -exec cp {} --parents -r ./book-result \; >>> cp: ./Chapters/Chapter1/figures is a directory (not copied). >>> cp: --parents: No such file or directory >>> cp: -r: No such file or directory >>> cp: ./figures is a directory (not copied). >>> cp: --parents: No such file or directory >>> cp: -r: No such file or directory >>> cp: ./support/figures is a directory (not copied). >>> cp: --parents: No such file or directory >>> cp: -r: No such file or directory >>> cp -r support/ ./book-result >>> cp .latexmkrc ./book-result >>> cp: .latexmkrc: No such file or directory >>> make: *** [copySupport] Error 1 >>> >>> >>> I must be doing something wrong, but I do not know what. I am on a Mac >>> 10.11 and I am using bash. Could someone point me in the right direction? >>> >>> Cheers, >>> Doru >>> >>> >>> On Sep 14, 2016, at 10:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> Where can I find the new template system for Pillar? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On Jul 22, 2016, at 3:41 PM, Thibault ARLOING < >>>>> thibault.arloing(a)hotmail.fr> wrote: >>>>> >>>>> Hello, >>>>> >>>>> I'm happy to announce the latest release of Pillar. >>>>> This release has been possible because of the hard work of Damien >>>>> Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. >>>>> What did it bring and what are the largest changes ? >>>>> >>>>> â¢ Huge cleaning of code and Dependencies >>>>> â¢ Many bug fixes >>>>> â¢ Huge refactoring of internal parts >>>>> â¢ Extract phase management into an external project >>>>> (LightPhaser) >>>>> â¢ Transformers and Phases are all Pipes >>>>> Remove Compilation cycle >>>>> â¢ Remove template handling from Pillar >>>>> â¢ Remove generation of pillarpostExport.sh >>>>> â¢ Pillar now exports files to JSON format >>>>> â¢ Command for pillar archetypes "./pillar archetype book", >>>>> book can be replaced by other archetype names (see Pillar documentation) >>>>> â¢ Possibility to load an archetype with a Makefile to compile >>>>> pillar files >>>>> Features >>>>> â¢ Check phase to check syntax >>>>> â¢ EPub exporter for e-books (use pillar archetypes for this) >>>>> â¢ Semantic links to Youtube and Wikipedia >>>>> â¢ Citations for LaTeX >>>>> â¢ Structures (see Pillar documentation) >>>>> â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc >>>>> â¢ Improvement of parsing configuration failure message >>>>> Major changes >>>>> â¢ Metadata field in configuration to separate data from >>>>> configuration properties >>>>> â¢ Support files in configuration does no longer exists >>>>> â¢ "disableTransformers" property is now named "disabledPhases" >>>>> â¢ AsciiDoc file extension is now ".asciidoc" >>>>> â¢ Pillar now manages one input file, not a collection of input >>>>> files anymore >>>>> â¢ Parameter inputFiles is now replaced by inputFile >>>>> The documentation of Pillar will be update as soon as possible to fit >>>>> those changes. >>>>> >>>>> Cheers, >>>>> >>>>> Thibault >>>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Sometimes the best solution is not the best solution." >>>> >>>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "It's not how it is, it is how we see it." >>> >>> >>> >>> >> >> > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Sept. 16, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by Damien Pollet

On 16 September 2016 at 20:42, stepharo <stepharo(a)free.fr> wrote: > Daemons of over-engineering are tempting us because this is cooler to to > design something complex. > Dreaming of crazy features is a good thing. Talking from experience, I prefer that to not dreaming, which is pretty dull. And over-engineering is of course the wrong path. But the temptation to do so is revealing of where the system is too complex. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Sept. 16, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by Nicolai Hess

2016-09-16 18:42 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi All, > > > > _,,,^..^,,,_ (phone) > > On Sep 14, 2016, at 10:50 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > > > > >>> > >>> We can change it back and maybe add support for the reformatter to not > convert it to the literal array #(3 #+ 4) . > >> > >> I do not know in fact this is why I asked :) > >> Now may be my idea to use pragma to get something like pythondoctest is > a bad idea > >> but I really want to have literal programming. > >> What do you think? > > I like the idea to show examples/tests close to code, but pragmas are > not really good... > > > >> If we have ' ' then it would be good that the syntax higlighter works > with a special mode inside the ' ' > > > > it is just a string. How do you know that it contains code? > > > > Would you highlight all string in all code as if it contained code? Or > would you add this just for > > Pragmas? But even there, strings are string, not code. > > > > I think we can conclude that pragmas are not a good solution to the > problem, as they are far > > too limited to express code. > > I think that's not a safe conclusion. We know from Igor's use of Kieran > arrays for C signatures in the UFFI, and can easily extrapolate here, that > arbitrary Smalltalk expressions /can/ be expressed in literal arrays. S > expressions work for lisp. > > In this particular case special casing pretty printing of literal arrays > in pragmas would be all that's needed to make the code look beautiful. Why > throw the baby out with the bath water? It would be so easy to make this > work well. > We can try this as well. And it is far more easier to work with this expressions if they are pragma arguments, than to parse the comment to find some code within. On the other hand, it looks much nicer if we have the examples right in the method doc. you have some text describing the method, some code, some more text about the reslt. > > The only thing I'd do would be to print like this to make it clear that > the argument t is a literal Array and not some magic form of code: > > <expr: #(3 + 4) result: 7> > > Yes, I would like to change this anyway, even for literal arrays for ffi, calls like mouseStateX: x y: y <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> ^ self nbCall: #( Uint32 SDL_GetMouseState ( int* x , int* y ) ) this will be reformatted to mouseStateX: x y: y <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: 'errorCode'> ^ self nbCall: #(#Uint32 #SDL_GetMouseState #(#int #* #x #, #int #* #y)) > > > > Marcus > > > > > > > > > > > > > >

Sept. 16, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by stepharo

Damien Pollet started to have a look at the makefile and this is on my todo to try. Stef Le 15/9/16 Ã 00:13, Johan Fabry a Ã©crit : > Hi Doru, > > it looks like thereâs a problem with copySupport.mk, I had the same problem with the Spec booklet. The file is using Linux only syntax for the cp command. This was fixed for the Spec booklet after I raised an issue there, but it seems the fix was not propagated everywhere it needs to be. Have a look at https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/c… and try to update your copySupport, it may fix your problem. > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >> On Sep 14, 2016, at 18:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> Ok, I found this document: >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> And now I tried this: >> >> wget --no-check-certificate https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >> chmod +x download.sh >> ./download.sh >> ./pillar archetype book >> >> and I got the book template. But, I do not know how to compile the book. I tried >> >> make >> >> or >> make book >> >> but I get: >> >> make >> mkdir -p ./book-result >> find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec cp {} --parents -r ./book-result \; >> cp: ./Chapters/Chapter1/figures is a directory (not copied). >> cp: --parents: No such file or directory >> cp: -r: No such file or directory >> cp: ./figures is a directory (not copied). >> cp: --parents: No such file or directory >> cp: -r: No such file or directory >> cp: ./support/figures is a directory (not copied). >> cp: --parents: No such file or directory >> cp: -r: No such file or directory >> cp -r support/ ./book-result >> cp .latexmkrc ./book-result >> cp: .latexmkrc: No such file or directory >> make: *** [copySupport] Error 1 >> >> >> I must be doing something wrong, but I do not know what. I am on a Mac 10.11 and I am using bash. Could someone point me in the right direction? >> >> Cheers, >> Doru >> >> >>> On Sep 14, 2016, at 10:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Where can I find the new template system for Pillar? >>> >>> Cheers, >>> Doru >>> >>> >>>> On Jul 22, 2016, at 3:41 PM, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: >>>> >>>> Hello, >>>> >>>> I'm happy to announce the latest release of Pillar. >>>> This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. >>>> What did it bring and what are the largest changes ? >>>> >>>> â¢ Huge cleaning of code and Dependencies >>>> â¢ Many bug fixes >>>> â¢ Huge refactoring of internal parts >>>> â¢ Extract phase management into an external project (LightPhaser) >>>> â¢ Transformers and Phases are all Pipes >>>> Remove Compilation cycle >>>> â¢ Remove template handling from Pillar >>>> â¢ Remove generation of pillarpostExport.sh >>>> â¢ Pillar now exports files to JSON format >>>> â¢ Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) >>>> â¢ Possibility to load an archetype with a Makefile to compile pillar files >>>> Features >>>> â¢ Check phase to check syntax >>>> â¢ EPub exporter for e-books (use pillar archetypes for this) >>>> â¢ Semantic links to Youtube and Wikipedia >>>> â¢ Citations for LaTeX >>>> â¢ Structures (see Pillar documentation) >>>> â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc >>>> â¢ Improvement of parsing configuration failure message >>>> Major changes >>>> â¢ Metadata field in configuration to separate data from configuration properties >>>> â¢ Support files in configuration does no longer exists >>>> â¢ "disableTransformers" property is now named "disabledPhases" >>>> â¢ AsciiDoc file extension is now ".asciidoc" >>>> â¢ Pillar now manages one input file, not a collection of input files anymore >>>> â¢ Parameter inputFiles is now replaced by inputFile >>>> The documentation of Pillar will be update as soon as possible to fit those changes. >>>> >>>> Cheers, >>>> >>>> Thibault >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Sometimes the best solution is not the best solution." >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "It's not how it is, it is how we see it." >> >> >> > >

Sept. 16, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by stepharo

> Package level doc is quite useful to outline how some things are > working together, something which is quite hard to figure out > except by reading external doc or inferring things by walking > through the code or a running test. > > > > Why don't we have yet package comments ? Just because we are too busy. > I see there is some support for it in PackageManifest, I remember > there was some work (people working) on support for Nautilus, no? Christophe is working on the manifest to support cargo metadata. > maybe something like this, (see attached file) > Nautilus comment pane > on class selection -> show class comment > no class selection -> show package comment (class side #description of > package manifest of this package) > you can even add or change the (package) comment, it will compile a > proper #description method on the manifest class) Yes this is one idea. I would love to have package comment. > > > > Having the ability to read about a package would be very useful. > Basically, this is what Java provides. > > http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javadoc.html#p… > <http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javadoc.html#p…> > > Phil > > > On Thu, Sep 15, 2016 at 8:45 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi all > > I want something similar in the spirit to PythonDocTest > https://docs.python.org/2/library/doctest.html > <https://docs.python.org/2/library/doctest.html> > > I'm talking about > > basename > "Returns the base of the basename, > i.e. > /foo/gloops.taz basename is 'gloops.taz' > / basename is '/'" > > Pragmas do not work well i.e., > basename > "Returns the base of the basename" > <expr: '''/foo/gloops.taz'' asFileReference basename' > result: 'gloops.taz'> > > > We should invent a syntax to be put inside comments and that > we can easily parse because we need to improve > the use and discovery of the library. > > I was thinking about > > basename > "Returns the base of the basename" > " > '/foo/gloops.taz' asFileReference basename > >>> 'gloops.taz' > " > > Do you have any idea? > > I cannot not do anything and just complain that our methods > are not that well documented. > We as a community should take this and build an super cool system. > > I tried and defined >>> on Object to see if it works! > > Object >>> aResultingObject > "If the method comment contains >>> then it is a pharo > documentated test. We can check that it is true." > > " > '/foo/gloops.taz' asFileReference basename > >>> 'gloops.taz' > " > > ^ self = aResultingObject > > > Stef > > > >

Sept. 16, 2016