September 2015 - Pharo-users

[ANN] Pillar 1.0.0.

by Ferlicot D. Cyril

Hello guys! I finished 5 months of internship into the RMoD team. I worked on Pillar and I am glad to announce the version 1.0.0! You can find an updated documentation of this version here : https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l…. We decided with Damien Cassou to use Semetic Versioning from now (see: http://semver.org/) I will now explain the main changes I did on Pillar during my internship. For each new feature I added tests and documentation. I will begin with the changes of Pillar's structure - The configuration system is now manage by Cocoon (http://www.smalltalkhub.com/#!/~PharoExtras/Cocoon) -- We now use Magritte in Cocoon - I added Annotations : A syntax extension point - I added Transformers : A way to transform a document model before an export (to add a section structure in HTML for example) - Some small refactoring. -- Improvement of the template management -- Improvement of the Pillar model parameters - Improvement of the document model -- Now the figures and links are two different entity - I begun a PetitPillar (with PetitParser) in order to replace the old parser too complicated. Now I will talk about new features for the users - Improvement of the usability of Pillar under Windows - Beamer and Deck.js exporters - Annotations : -- To include a Pillar file into an other (${inputFile:path}$) (Example: https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/Ente…) -- To create new slides in Beamer and Deck.js (${slide:My Title|label=optional}$) -- To create columns into a Pillar document (currently works in Beamer, Deck.js and HTML) -- â¦ - Transformers -- You can now add a parameter "lineNumber=true" to a script and Pillar will transform them to add the line numbers -- You can now import a script from an other file (see the documentation of the scripts) -- â¦ - Improvement of the errors raised by Pillar - Addition of the inter-files links - Improvement of the title configuration for numbering - No need to make scripts anymore to use Pillar ! -- You can used "defaultExporters" in your configuration to do multiple export (see documentation) -- Pillar generate a script for LaTeX compilation (only for Unix for now) - Possibility to export everything into a different folder (simpler to clean after) -- And possibility to copy some support files For the two previous point you can take example on Enterprise Pharo (https://github.com/SquareBracketAssociates/EnterprisePharo) and Pharo Mooc (https://github.com/SquareBracketAssociates/PharoMooc) This was a really cool internship :) If you have some questions do not hesitate! -- Cyril

Sept. 1, 2015

Re: [Pharo-users] Becoming good at VM development

by Mariano Martinez Peck

BTW, you question is about becoming good at VM development, so actually the compilation of the VM itself is a very very very little part of the whole picture. On Tue, Sep 1, 2015 at 3:37 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 31 Aug 2015, at 21:41, stepharo <stepharo(a)free.fr> wrote: > > Hi > After the effort made by igor stasenko building the VM is a lot simpler > than it used to. > Did you try to compile the Pharo VM on your platform? > Did you experience some problems? > We should probably add a resource page to get started. I do not have the > information but > we can ask esteban. > > > yesâ¦ PharoVM is built as described here: > > https://github.com/pharo-project/pharo-vm/blob/master/README.md > > if you follow those instructions, you will have no problems. > The process is running everyday so it *is* working. > Windows guys can have problems if they change mingw version, etc. They > shouldnât, but since this is over our control, I cannot assure you > anything. > Others problems that have emerged with time (in linux) is people > forgetting they need 32bit library versions to be able to buildâ¦ > > anywayâ¦ that should be enoughâ¦ for most people, once fulfilled > requirements, build VM is as easy as: > > 1) clone > 2) cd image; sh ./newImage.sh ; ./pharo generator.image eval > âPharoVMBuilder build" > 3) cd ../build ; sh build.sh > > cheers, > Esteban > > > Stef > > Thanks to all for your responses. > I am carefully reading the material presented by you. Ideally I will like > to > compile the VM into Chrome's NaCL to run an image under Chrome OS. But > first > things first, as they say. I have to understand the Squeak/Pharo VM. > One question, is Mariano's blog still relevant? It seems to me that Pharo > VM > is not build that way anymore? > > ãããã¨ãã > > > > -- > View this message in context: > http://forum.world.st/Becoming-good-at-VM-development-tp4846536p4847217.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 1, 2015

Flattr added to pharo.org

by Marcus Denker

Hi, We added at Flattr button: http://pharo.org/contribute <http://pharo.org/contribute> Direkt link is: https://flattr.com/thing/4606474/Pharo-Welcome-to-Pharo Marcus

Sept. 1, 2015

Re: [Pharo-users] Becoming good at VM development

by Esteban Lorenzano

> On 31 Aug 2015, at 21:41, stepharo <stepharo(a)free.fr> wrote: > > Hi > After the effort made by igor stasenko building the VM is a lot simpler than it used to. > Did you try to compile the Pharo VM on your platform? > Did you experience some problems? > We should probably add a resource page to get started. I do not have the information but > we can ask esteban. yesâ¦ PharoVM is built as described here: https://github.com/pharo-project/pharo-vm/blob/master/README.md <https://github.com/pharo-project/pharo-vm/blob/master/README.md> if you follow those instructions, you will have no problems. The process is running everyday so it *is* working. Windows guys can have problems if they change mingw version, etc. They shouldnât, but since this is over our control, I cannot assure you anything. Others problems that have emerged with time (in linux) is people forgetting they need 32bit library versions to be able to buildâ¦ anywayâ¦ that should be enoughâ¦ for most people, once fulfilled requirements, build VM is as easy as: 1) clone 2) cd image; sh ./newImage.sh ; ./pharo generator.image eval âPharoVMBuilder build" 3) cd ../build ; sh build.sh cheers, Esteban > > Stef >> Thanks to all for your responses. >> I am carefully reading the material presented by you. Ideally I will like to >> compile the VM into Chrome's NaCL to run an image under Chrome OS. But first >> things first, as they say. I have to understand the Squeak/Pharo VM. >> One question, is Mariano's blog still relevant? It seems to me that Pharo VM >> is not build that way anymore? >> >> ãããã¨ãã >> >> >> >> -- >> View this message in context: http://forum.world.st/Becoming-good-at-VM-development-tp4846536p4847217.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > >

Sept. 1, 2015

Re: [Pharo-users] Becoming good at VM development

by Ben Coman

On Tue, Sep 1, 2015 at 1:49 AM, Ichiseki <is076(a)outlook.com> wrote: > Thanks to all for your responses. > I am carefully reading the material presented by you. Ideally I will like to > compile the VM into Chrome's NaCL to run an image under Chrome OS. But first > things first, as they say. I have to understand the Squeak/Pharo VM. > One question, is Mariano's blog still relevant? It seems to me that Pharo VM > is not build that way anymore? For my own first try at compiling a pharo-vm a few months ago, I found the Mac instructions in the README [1] quite straight forward. My only hiccup was not paying attention to using the recommended SDK version 10.6. [1] https://github.com/pharo-project/pharo-vm cheers -ben

Sept. 1, 2015