- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Sean P. DeNigris

Dale Henrichs-3 wrote > I've just gone through a similar process... I still have > not completely forgotten the magic incantations:) If anyone else has any: 1. magic incantations 2. success reports 2. failure reports for /any/ GNU/Linux Distribution/Version, please post them to this thread. I will review and compile everything tomorrow. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Damien Pollet

+1 PetitMarkdown (at least in the state I left it) had an incomplete and contorted grammar, translated from another implementation (the one used by pandoc, I think). I started something to handle indentation, but meh. Jan's extension of PetitParser is the way to go, and it should make the grammar way more readable. On 14 April 2015 at 11:43, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > how complete it is? > we would really like to think on: > > 1) include petitparser in Pharo > 2) allow the writing of class docs in MD format :) > > of course, we are talking about the not-so-near future, but is an idea we > are thinking aboutâ¦ :P > > and in any case, I would like to use a good MD parser for my own stuff :) > > Esteban > > On 14 Apr 2015, at 10:42, Jan KurÅ¡ <kurs(a)iam.unibe.ch> wrote: > > Hey, > > I also created an indentation sensitive extension of PetitParser, I also > included some examples including Markdown. If you load PetitParser, you get > the Markdown example as well. > > There is a short introduction to the indentation: > > http://scg.unibe.ch/research/indentParsing > > Cheers Jan > On Apr 13, 2015 5:24 PM, "H. Hirzel" <hannes.hirzel(a)gmail.com> wrote: > >> Are there any news on this? >> >> --Hannes >> >> On 12/28/14, Norbert Hartl <norbert(a)hartl.name> wrote: >> > I found markdown parsers in smalltalkhub and in the configuration >> browser. >> > >> > http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ >> > <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/> >> > >> > and the one in the configuration browser >> > >> > PPMarkdown >> > >> > If I understand it correctly both are rooted into work Camillo did. The >> one >> > in PharoExtras looks newer to me. So I assume the best would be to copy >> the >> > ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and >> remove >> > the ConfigurationOfPPMarkdown. Right? Or are there any objections? >> > >> > Norbert >> >> > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

April 14, 2015

[pharo-project/pharo-core] da8d8e: 40608

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: da8d8e63d16d9294889744d9a5c672108fbf8878 https://github.com/pharo-project/pharo-core/commit/da8d8e63d16d9294889744d9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-14 (Tue, 14 Apr 2015) Changed paths: R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script607.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script608.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40607.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40608.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40608 new .sources http://files.pharo.org/image/40/40608.zip

April 14, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40608 Home: https://github.com/pharo-project/pharo-core

April 14, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Sean P. DeNigris

Dale Henrichs-3 wrote > The basic trick is to run `ldd` against the plugin/.so files in the vm > directory and IIRC, you get a "not found" message for the missing > libraries and I just tacked :i386 onto library name for `apt-get`... This is getting interesting? Do you think the process could be automated? Like maybe part of the ZeroConf scripts? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 14, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> On 14 Apr 2015, at 10:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > A next try based on 40607 we will: > > -> generate sources from that (DONE) > -> upload to http://files.pharo.org/sources/ <http://files.pharo.org/sources/> > -> upload image (TODO) > -> fix zeroconf (Next) > -> fix build scripts (TODO) > -> do an empty 608 for testing (TODO) > DONE! Marcus

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Esteban Lorenzano

how complete it is? we would really like to think on: 1) include petitparser in Pharo 2) allow the writing of class docs in MD format :) of course, we are talking about the not-so-near future, but is an idea we are thinking aboutâ¦ :P and in any case, I would like to use a good MD parser for my own stuff :) Esteban > On 14 Apr 2015, at 10:42, Jan KurÅ¡ <kurs(a)iam.unibe.ch> wrote: > > Hey, > > I also created an indentation sensitive extension of PetitParser, I also included some examples including Markdown. If you load PetitParser, you get the Markdown example as well. > > There is a short introduction to the indentation: > > http://scg.unibe.ch/research/indentParsing <http://scg.unibe.ch/research/indentParsing> > Cheers Jan > > On Apr 13, 2015 5:24 PM, "H. Hirzel" <hannes.hirzel(a)gmail.com <mailto:hannes.hirzel@gmail.com>> wrote: > Are there any news on this? > > --Hannes > > On 12/28/14, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > > I found markdown parsers in smalltalkhub and in the configuration browser. > > > > http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/> > > <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/>> > > > > and the one in the configuration browser > > > > PPMarkdown > > > > If I understand it correctly both are rooted into work Camillo did. The one > > in PharoExtras looks newer to me. So I assume the best would be to copy the > > ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and remove > > the ConfigurationOfPPMarkdown. Right? Or are there any objections? > > > > Norbert >

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Jan KurÅ¡

Hey, I also created an indentation sensitive extension of PetitParser, I also included some examples including Markdown. If you load PetitParser, you get the Markdown example as well. There is a short introduction to the indentation: http://scg.unibe.ch/research/indentParsing Cheers Jan On Apr 13, 2015 5:24 PM, "H. Hirzel" <hannes.hirzel(a)gmail.com> wrote: > Are there any news on this? > > --Hannes > > On 12/28/14, Norbert Hartl <norbert(a)hartl.name> wrote: > > I found markdown parsers in smalltalkhub and in the configuration > browser. > > > > http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ > > <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/> > > > > and the one in the configuration browser > > > > PPMarkdown > > > > If I understand it correctly both are rooted into work Camillo did. The > one > > in PharoExtras looks newer to me. So I assume the best would be to copy > the > > ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and remove > > the ConfigurationOfPPMarkdown. Right? Or are there any objections? > > > > Norbert > >

April 14, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

Hi, A next try based on 40607 we will: -> generate sources from that (DONE) -> upload to http://files.pharo.org/sources/ <http://files.pharo.org/sources/> -> upload image (TODO) -> fix zeroconf (Next) -> fix build scripts (TODO) -> do an empty 608 for testing (TODO) > On 13 Apr 2015, at 15:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We have to generate a new .source file. We will do that for 40606. > > This means that there will be two versions of 40606: one that has a V3 Sources and one with a V4 source. > To not get confused, the best is to wait for 607. > > Marcus

April 14, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40607 Home: https://github.com/pharo-project/pharo-core

April 14, 2015