September 2016 - Pharo-users

Re: [Pharo-users] [Moose-dev] [ann] pillar support in gtinspector

by Nicolai Hess

2016-09-14 22:47 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi Nicolai, > > Did you commit your changes with the highlight of == code? > > Cheers, > Doru > > No, but I just saw that I misinterpreted the "==", first I thought this is for "inline code" as it was used in some class comment like that. But it is actually a more general formatting tag for "monospaced font" - we actually don't need to do code highlighting for this text, just use a monospace font resp. code font. > > > On Sep 6, 2016, at 4:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > > > 2016-08-29 21:41 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > > > I updated the Pillar support in GTInspector. Some of the extensions > already exist in the default Pillar #development version. If you want to > play with the full support, you can load it like this: > > > > Gofer new > > smalltalkhubUser: 'Moose' project: 'PetitParser'; > > package: 'PetitAnalyzer'; > > package: 'PetitIndent'; > > package: 'PetitIslands'; > > smalltalkhubUser: 'Moose' project: 'GToolkit'; > > package: 'GT-InspectorExtensions-Pillar'; > > load > > > > Then you can just inspect a book folder and you get this: > > > > <inspector-pillar.png> > > > > I did not integrate this in the main Pillar yet because this is an older > implementation based on a limited island parser. As now Pillar has a full > parser based on PetitParser, the next step is to move the highlighting > logic to use this parser instead of the island parser. From my > measurements, the speed of the two parsers is about the same, so from a > user perspective there will be not much changes. > > > > It pains me that we are editing Pillar in outside tools, and now we > should no longer have to do that. Of course, this is not the most ideal > tool support for Pillar but I think it is a reasonable start. > > > > Cheers, > > Doru > > > > > > nice! > > > > I just played a bit with the code to apply larger different font sizes > for the headings and > > use the code styler for inlined code ("=="). > > > > Maybe we should use a different code styler or add a way to instruct the > styler to ignore unknown classes or uknown selectors :) > > > > > > > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Problem solving should be focused on describing > > the problem in a way that makes the solution obvious." > > > > > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Obvious things are difficult to teach." > > > > > >

Sept. 15, 2016

Re: [Pharo-users] Extending live coding beyond Pharo

by Dimitris Chloupis

It's not a trick or slow , it's actually a standard feature and blazing fast. Its a feature that has existed for several decades now . It's called "exception". There are three types of exceptions. 1) language exception. This type of exception is handled by the language and it can involve both an error or even a normal running code. Usually they are handled by a library or VM. 2) OS system exceptions. This exception is handled by the operation system itself and its what debuggers usually use to capture crashes. In Windows they are called "structured exceptions" https://msdn.microsoft.com/en-us/library/windows/desktop/ms680657(v=vs.85).… In UNIX type OS they are called "signals and traps" http://www.tutorialspoint.com/unix/unix-signals-traps.htm 3) hardware exception. This exception is handled directly by the CPU. http://www.internals.com/articles/protmode/interrupts.htm If you are interested in the internals of live coding and exception handling this guy made a series of videos how to make a game from scratch using no library and has 3 videos on the subject that show himself coding these features https://m.youtube.com/watch?v=WMSBRk5WG58 https://m.youtube.com/watch?v=oijEnriqqcs https://m.youtube.com/watch?v=xrUSrVvB21c The only trick is not to let the DLL have any of its own memory, instead the main executable keeps its memory in one place, in this case a struct is used, and the memory is passed as reference via a pointer to DLL. The DLL in turn passes pointers to its functions to the executable, and the executable passes also pointers to its functions to the DLL that the DLL may want to use as callbacks. In short code and memory is passed around only as reference. This is just very basic C/C++ coding using DLLs nothing special about it. Storing the code inside Pharo image is very easy todo , after all we store graphics files in the image. But it's not really necessary or useful. If you decide to keep everything in image you lose a lot of tools that can make your life a lot easier, like coding tools, debuggers etc that averages C coder uses. If you want to do trigger those things from inside Pharo you can use OSProcess to do so as we do with git , see gitfiletree. If you want real time compiling without the need to force the user to install a compiler or increase the size of the Pharo installation you can use CI or a online service that provides compilations of DLLs via the Internet. Pharo of course already has this ability because it uses CI to build its VM and image in order to provide you with a download link. So basically you have all those tools already available to you. Tracking changes can happen at file level so you don't need to do that in image either. The videos I linked clearly illustrate the process. The only catch is that you cannot makes this automatic because live coding and real time compiling depends a lot on the structure of the code and this is not something you can predict. Also it's a good idea the user knows what he is doing because else he will run into trouble fast. For example people who use Slang are VM developers and they both know the VM internals and how to code in C. The same way that in order to code in Pharo you have to know Pharo. If you don't want to hack the Pharo executable then you can simple use one DLL to load another DLL , this way the first DLL will act as container/sandbox for the second DLL and replicate much of the same workflow I mentioned for the executable. After all DLLs are very similar to executables. On Thu, 15 Sep 2016 at 06:03, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, Sep 15, 2016 at 3:38 AM, Dimitris Chloupis > <kilon.alios(a)gmail.com> wrote: > > Live coding on Pharo is great, easy , simple and working out of the box. > An > > extremely useful tool to be able to code an application while it runs, > > change and improve code with no interruptions. > > > > However there will be cases that Pharo wont be enough, that can be > because > > pharo code is not as fast as you want it to be, or plainly you found a > great > > library in C or C++ you wanna use from Pharo and there is literally a > ton of > > them. However there is a catch , you kiss goodbye to live coding , you > say > > hello to slow compiles and crashes because of bad memory management. > > > > Unfortunately that is the nature of C/C++. However live coding is gaining > > ground lately and more and more languages use it for super fast > development. > > Some C++ coders have wondered whether they can bring this feature back to > > C++ and they have succeed. > > > > One example is Unreal game engine I am using .It can compile code on the > fly > > and load it back even though the game is keep running. It calls this > > process "hot reloading". > > > > But for people that dont want to bother with Unreal there is this project > > > > http://runtimecompiledcplusplus.blogspot.gr/ > > > > The nice things about this is that not only it allows for live coding and > > very fast compiles but also its able to catch crashes with system > > exceptions, in a case of a crash the application keeps running because > the > > crashy code is exchanged with the previous version of the code that did > not > > crash and the crash is captured with an exception, you can use the > debugger > > to debug it , correct the code and continue like you would with Pharo. > > > > There are disadvantages though, because RCPP makes no compromises when it > > comes to performance that means that it needs a very specific way of > coding > > to accomodate for live coding, usually a main loop should exist and > there is > > an API that must be used to track changes to the files and reload code on > > demand. But generally it does work very well and its also used by > commercial > > projects all around the world. > > > > This will be a real nice addition to the toolbox of people who like to > > extend Pharo with C/C++ but do not want to live the comforts of live > coding > > and have low tolerance for slow compile times and crashes. > > Nice idea. I've been wondering if there might be some way of having a > SafeFFI for use during development and by newbies. After all, gdb > doesn't crash when the program its hosting crashes I guess there is > *some* trick could be used. It could even be a *lot* slower and still > be useful, to be turned off at deployment. > > Actually just last night I was contemplating what a Pharo system might > be like with FFI-libclang dynamically compiling in-Image C code, > (re-)linking it into a dynamic library and immediately calling those > functions using FFI again. My very first graduate programming job was > a company developing satellite image processing software that got a > lot of their speed by generating/compiling/linking/loading C functions > for filter-chains to apply to the huge data sets. > > Maybe something like... > > Behavior subclass: #CLanguageDescription > instanceVariableNames: 'index translationUnit' > classVariableNames: '' > package: 'ExternalLanguage-C' > "Provide compatibility to integrate equivalent of C files in our > System Browser. > - class-pane==>C-file, method-pane==>types and functions" > > ProtoObject subclass: #CLanguageRootHierarchy > instanceVariableNames: '' > classVariableNames: '' > package: 'ExternalLanguage-C' > "My subclasses are instances of CLanguageDescription compiled > by a C compiler such that pure C syntax can be used. > i.e. positional function arguments f(a,b)" > > At a minimum, it might bring FFI function callout definitions closer > to pure cut and paste. (Although the current UFFI callout format is > pretty good.) > > A *lot* further stretch... you might store all the VM platform sources > inside the image, as well as the generated C code from slang > primitives. Updating the slang method immediately re-generates the C > code, compiles it and updates the dynamic library. Dependencies > could be tracked at a finer level that standard file based makefile, > such that an update to a platform C type or function declaration would > be linked to other types and functions using (based on AST analysis > and the minimum set recompiled immediately. Unit tests for platform > sources would be Smalltalk based FFI callouts invoked from TestRunner. > > (But I know... its easy to dream. harder to do.) > cheers -ben > >

Sept. 15, 2016

Re: [Pharo-users] Pharo users count / estimate ?

by Marcus Denker

> On 14 Sep 2016, at 17:15, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Hi all, > > for some silly report that I need to write I wanted to add an estimate of how many people worldwide use Pharo. I tried to find number of downloads of e.g. Pharo 5 to use that as a basis for estimation but I could not find this info online. Does the Pharo team have any usable statistics that can be shared ? > We have no information. Marcus

Sept. 15, 2016

Re: [Pharo-users] double dispatch example

by Ben Coman

http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org On Thu, Sep 15, 2016 at 10:04 AM, Melanie Tarr <melanie.tarr(a)gmail.com> wrote: > Can someone please tell me how to unsubscribe from this list, > > Kind Regards > Melanie > > On Tue, Sep 13, 2016 at 10:16 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: >> >> Hi Stef! >> >> Plenty of examples: >> >> - Converting money >> - Paper, Stone, Scissor >> - A canvas containing triangle, circle, box has to be printed, on an html >> canvas or PDF. (Very close to the Visitor design pattern, but simpler) >> >> Here are the lectures I use: >> https://dl.dropboxusercontent.com/u/31543901/TMP/DoubleDispatch.zip >> >> (One of them is highly inspired from a lecture from Oscar) >> >> Hope it helps! >> >> Cheers, >> Alexandre >> >> > On Sep 13, 2016, at 7:33 AM, stepharo <stepharo(a)free.fr> wrote: >> > >> > Hi >> > >> > If you happen to know a double dispatch situation in Pharo, I'm >> > interested since I'm revisiting my lecture. >> > >> > >> > Stef >> > >> > >> >> >

Sept. 15, 2016

Re: [Pharo-users] Extending live coding beyond Pharo

by Ben Coman

On Thu, Sep 15, 2016 at 3:38 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Live coding on Pharo is great, easy , simple and working out of the box. An > extremely useful tool to be able to code an application while it runs, > change and improve code with no interruptions. > > However there will be cases that Pharo wont be enough, that can be because > pharo code is not as fast as you want it to be, or plainly you found a great > library in C or C++ you wanna use from Pharo and there is literally a ton of > them. However there is a catch , you kiss goodbye to live coding , you say > hello to slow compiles and crashes because of bad memory management. > > Unfortunately that is the nature of C/C++. However live coding is gaining > ground lately and more and more languages use it for super fast development. > Some C++ coders have wondered whether they can bring this feature back to > C++ and they have succeed. > > One example is Unreal game engine I am using .It can compile code on the fly > and load it back even though the game is keep running. It calls this > process "hot reloading". > > But for people that dont want to bother with Unreal there is this project > > http://runtimecompiledcplusplus.blogspot.gr/ > > The nice things about this is that not only it allows for live coding and > very fast compiles but also its able to catch crashes with system > exceptions, in a case of a crash the application keeps running because the > crashy code is exchanged with the previous version of the code that did not > crash and the crash is captured with an exception, you can use the debugger > to debug it , correct the code and continue like you would with Pharo. > > There are disadvantages though, because RCPP makes no compromises when it > comes to performance that means that it needs a very specific way of coding > to accomodate for live coding, usually a main loop should exist and there is > an API that must be used to track changes to the files and reload code on > demand. But generally it does work very well and its also used by commercial > projects all around the world. > > This will be a real nice addition to the toolbox of people who like to > extend Pharo with C/C++ but do not want to live the comforts of live coding > and have low tolerance for slow compile times and crashes. Nice idea. I've been wondering if there might be some way of having a SafeFFI for use during development and by newbies. After all, gdb doesn't crash when the program its hosting crashes I guess there is *some* trick could be used. It could even be a *lot* slower and still be useful, to be turned off at deployment. Actually just last night I was contemplating what a Pharo system might be like with FFI-libclang dynamically compiling in-Image C code, (re-)linking it into a dynamic library and immediately calling those functions using FFI again. My very first graduate programming job was a company developing satellite image processing software that got a lot of their speed by generating/compiling/linking/loading C functions for filter-chains to apply to the huge data sets. Maybe something like... Behavior subclass: #CLanguageDescription instanceVariableNames: 'index translationUnit' classVariableNames: '' package: 'ExternalLanguage-C' "Provide compatibility to integrate equivalent of C files in our System Browser. - class-pane==>C-file, method-pane==>types and functions" ProtoObject subclass: #CLanguageRootHierarchy instanceVariableNames: '' classVariableNames: '' package: 'ExternalLanguage-C' "My subclasses are instances of CLanguageDescription compiled by a C compiler such that pure C syntax can be used. i.e. positional function arguments f(a,b)" At a minimum, it might bring FFI function callout definitions closer to pure cut and paste. (Although the current UFFI callout format is pretty good.) A *lot* further stretch... you might store all the VM platform sources inside the image, as well as the generated C code from slang primitives. Updating the slang method immediately re-generates the C code, compiles it and updates the dynamic library. Dependencies could be tracked at a finer level that standard file based makefile, such that an update to a platform C type or function declaration would be linked to other types and functions using (based on AST analysis and the minimum set recompiled immediately. Unit tests for platform sources would be Smalltalk based FFI callouts invoked from TestRunner. (But I know... its easy to dream. harder to do.) cheers -ben

Sept. 15, 2016

Re: [Pharo-users] double dispatch example

by Melanie Tarr

Can someone please tell me how to unsubscribe from this list, Kind Regards Melanie On Tue, Sep 13, 2016 at 10:16 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Stef! > > Plenty of examples: > > - Converting money > - Paper, Stone, Scissor > - A canvas containing triangle, circle, box has to be printed, on an html > canvas or PDF. (Very close to the Visitor design pattern, but simpler) > > Here are the lectures I use: > https://dl.dropboxusercontent.com/u/31543901/TMP/DoubleDispatch.zip > > (One of them is highly inspired from a lecture from Oscar) > > Hope it helps! > > Cheers, > Alexandre > > > On Sep 13, 2016, at 7:33 AM, stepharo <stepharo(a)free.fr> wrote: > > > > Hi > > > > If you happen to know a double dispatch situation in Pharo, I'm > interested since I'm revisiting my lecture. > > > > > > Stef > > > > > > >

Sept. 15, 2016

Re: [Pharo-users] What are the best practices for an open source project with Pharo?

by Ben Coman

On Wed, Sep 14, 2016 at 9:22 PM, julius <julius(a)wokabulary.com> wrote: > I'm new to Smalltalk, I did the Inria MOOC and really like the way of how to > construct applications. Still I wonder how development teams approach > development with Pharo. > > Currently I'm thinking of implementing a small idea of mine with Pharo since > Seaside felt quite nice when I experimented a bit. The project would need to > be open source because I want to apply for funding at a initiative that only > supports open source projects. But then I don't have the feeling that the > Monticello approach is the most inviting way to get funding or contributors > considering everyone is used to Github. > I found now the guide to Git with Pharo by Peter Uhnak (thanks for writing > that post!) so maybe this would be a good solution... > > Searching for best practices I read about some projects that make sure > developers always get a new image every day, I wouldn't expect developers to religiously download a new image every day. (But I'd be curious to learn of a documented workflow doing this.) One of the great features of Pharo is the persistency of the Image and its just as easy to update to the latest code using Monticello or github, with the additional benefit that you get a diff of changes to review. The main benefits of daily image builds are CI running unit tests that include the latest Pharo changes, having a stake in the ground of a working system for "new" developers to get up an running, and keeping a deployable end-user product up to date. I personally tend to stick with one Image for a while on one task, and jump to the latest image any time I would be wanting to start with a fresh image anyway. > how could that be implemented > without too much hassle of needing a server with some kind of build system. Do you mean to avoid setting up a server scratch yourself, or even not using someone else's server? Inria (who host several of Pharo's core dev team) graciously provide a CI service for the community. https://ci.inria.fr/ > *tl;dr*: how could and should I approach the development of an open source > project with Pharo, considering acceptance of Monticello usage and sharing > of pharo images? Stef's answer here is good. cheers -ben

Sept. 15, 2016

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

by Tudor Girba

Hi, Thanks! It seems to work now. Cheers, Doru > On Sep 15, 2016, at 12:13 AM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > 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." >> >> >> > > -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

Sept. 14, 2016

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

by Johan Fabry

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. 14, 2016

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

by Tudor Girba

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. 14, 2016