- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PetitMarkdown

by Esteban Lorenzano

> On 14 Apr 2015, at 15:51, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 14.04.2015 um 14:24 schrieb Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>>: >> >> On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr <mailto:Christophe.Demarey@inria.fr>> wrote: >> >> Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : >> >> > 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 :) >> >> I would prefer pillar for class / packages comments >> >> I was quite surprised there are any MD defendants considering the pillar push. But since diversity is (often) a good think maybe having something like gt-inspector there would be cool where you can add this in whatever format you want. (And maybe one day someone will write pillar to morphic/whatever converter and it would be even cooler.) >> > It is a difficult topic. I agree with anyone that MarkDown is not a good format for parsing. Pillar is the right thing to do here. But there is one point of MarkDown that is hard to beat. A MarkDown text is always good to read, eben while writing. In something like a class comment it would be easy to use. What we don't want is to write system documentation in a format that you need to convert first before you can see the result. It is either having a wysiwyg editor for those things with pillar below or a simple format that can both. > > my 2 cents, thatâs actually my main point too, yes. Esteban > > norbert

April 14, 2015

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

by Dale Henrichs

On 4/14/15 3:46 AM, Sean P. DeNigris wrote: > 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? > This _is_ all software so automation should be possible:) The thing about this is there are choices that need to be made: - do you want x11 installed or do you intend to run headless and don't want x11 client - do you want ssl installed - do you want freetype installed For the casual user, the answer to each of those should be yes, but for a user setting up a vm for production, I assume that they want to control what is installed on that box and/or there may be restrictions as to what they may install...I use the zeronconf scripts (unless I find that I can't) in an environment where the user is making the choice about whether or not x11 client/server is installed ... a separate (optional) osPrereq url to install prereqs for the vm would be a nice feature ... Dale

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Norbert Hartl

> Am 14.04.2015 um 14:24 schrieb Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > > On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr <mailto:Christophe.Demarey@inria.fr>> wrote: > > Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : > > > 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 :) > > I would prefer pillar for class / packages comments > > I was quite surprised there are any MD defendants considering the pillar push. But since diversity is (often) a good think maybe having something like gt-inspector there would be cool where you can add this in whatever format you want. (And maybe one day someone will write pillar to morphic/whatever converter and it would be even cooler.) > It is a difficult topic. I agree with anyone that MarkDown is not a good format for parsing. Pillar is the right thing to do here. But there is one point of MarkDown that is hard to beat. A MarkDown text is always good to read, eben while writing. In something like a class comment it would be easy to use. What we don't want is to write system documentation in a format that you need to convert first before you can see the result. It is either having a wysiwyg editor for those things with pillar below or a simple format that can both. my 2 cents, norbert

April 14, 2015

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

by Sven Van Caekenberghe

Works fine for me too, great work, thanks (again), Marcus. > On 14 Apr 2015, at 15:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Yuppee. I changed the Moose build to package the Pharo40.sources and it works fine. > > Doru > > On Tue, Apr 14, 2015 at 12:45 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> 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/ >> -> upload image (TODO) >> -> fix zeroconf (Next) >> -> fix build scripts (TODO) >> -> do an empty 608 for testing (TODO) >> > > > DONE! > > Marcus > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

April 14, 2015

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

by Tudor Girba

Yuppee. I changed the Moose build to package the Pharo40.sources and it works fine. Doru On Tue, Apr 14, 2015 at 12:45 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 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/ > -> upload image (TODO) > -> fix zeroconf (Next) > -> fix build scripts (TODO) > -> do an empty 608 for testing (TODO) > > > > DONE! > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"

April 14, 2015

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

by phil＠highoctane.be

Le 14 avr. 2015 15:08, "Christophe Demarey" <Christophe.Demarey(a)inria.fr> a Ã©crit : > > For CentOs65, Phil has these instructions: https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-in… > The only problem is the libc version an also some package names not exactly the same as the one for other distribs (ubuntu). Check for the README.md in the repo. Also this (old) http://philippeback.be/2014/02/pharovm-now-running-on-debian-wheezy/ > I also set up a job to build the vm for cent OS 6: https://ci.inria.fr/pharo/view/all/job/PharoVM-CentOs6/ > > Christophe. > > Le 14 avr. 2015 Ã 12:48, Sean P. DeNigris a Ã©crit : > > > 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 Jan KurÅ¡

Regarding completeness, it is not great. It was implement with an emphasiz on the indentation/prefix-related part (the hard one, I hope) so quoted blocks and and lists are almost complete (with arbitrary nesting). I did not need the other stuff, so there is a basic support for headers, paragraphs and code blocks. I followed the commonmark spec ( http://spec.commonmark.org/0.17/) If there is an interest to use PetitParser/CommonMark in Pharo, I can spend some time on it. I guess, I would be able to parse majority of the examples (I am not sure about all the corner cases). Cheers, Jan On 14 April 2015 at 14:24, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > >> >> Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : >> >> > 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 :) >> >> I would prefer pillar for class / packages comments >> > > I was quite surprised there are any MD defendants considering the pillar > push. But since diversity is (often) a good think maybe having something > like gt-inspector there would be cool where you can add this in whatever > format you want. (And maybe one day someone will write pillar to > morphic/whatever converter and it would be even cooler.) > > Peter > > >

April 14, 2015

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

by Christophe Demarey

For CentOs65, Phil has these instructions: https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-in… The only problem is the libc version an also some package names not exactly the same as the one for other distribs (ubuntu). I also set up a job to build the vm for cent OS 6: https://ci.inria.fr/pharo/view/all/job/PharoVM-CentOs6/ Christophe. Le 14 avr. 2015 Ã 12:48, Sean P. DeNigris a Ã©crit : > 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 Peter UhnÃ¡k

On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > > Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : > > > 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 :) > > I would prefer pillar for class / packages comments > I was quite surprised there are any MD defendants considering the pillar push. But since diversity is (often) a good think maybe having something like gt-inspector there would be cool where you can add this in whatever format you want. (And maybe one day someone will write pillar to morphic/whatever converter and it would be even cooler.) Peter

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Christophe Demarey

Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : > 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 :) I would prefer pillar for class / packages comments

April 14, 2015