- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PetitMarkdown

by phil＠highoctane.be

Some should cool down. I am using Pillar to write my (internal) docs. And I use markdown too. Both have their uses. Compared to things like RMarkdown, knitr, and RPubs in the R community, what we do have is passable in terms of output. We have a small community, we have to deal with that fact. I hate the figures not going where I want due to the LaTeX generation in Pillar. As for class comments, markdown would make more sense to use when putting files under source control on git and then stored in github because filetree generates README.md files for such comments. It makes for a nice reading there. In that respect, Pillar class comments will be more of a nuisance than a help. For generating web documentation, it is easier to provide markdown so that any web framework will be able to convert (e;g; Showdown.js and 2 lines of code). Furthermore, a lot of Pillar files embed non pillar markup for special things. For me, Pillar is for the books. And speciality applications that use the visitors to produce other stuff (among which Markdown). As for writing stuff, I do md and pillar files in Vim. So much for specific tools that weren't satisfying when writing. Too slow, too cumbersome, not enough power for editing (compared to Vim, yeah, nothing comes close in terms of speed once you know the tricks). Phil On Tue, Apr 14, 2015 at 10:03 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > Whoa. > I genuinely don't understand the fierce emotions here. Why do Pillar and > Markdown have to be opposed? Why is wanting support for better parsing of > MD (a commonly used format around the web, and useful in many projects) > somehow an insult to the work done on Pillar? > > (Incidentally, I don't quite understand why Pillar was created in the > first place. Why have a slightly different and incompatible markdown format > from what the rest of the world is using? But that's not the point. We have > both, and it's easy to support both. What's the problem?) > > > On Tue, Apr 14, 2015 at 3:08 PM, stepharo <stepharo(a)free.fr> wrote: > >> I'm really pissed off. Because nearly nobody tried to write anything >> with pillar and you just talk >> about what you do not know. But thanks this is great to see that we are >> spending our energy for people >> who will never even try to use what we are doing. >> Superb! >> >> No need to reply I will not read this thread anymore. And I should not >> even have because it was so obvious. >> >> And yes I 'm REALLY pissed off. You should also say to cyril that what is >> is doing is hopeless because as soon >> as we will have a stupid markdown parser suddenly it will be great. what >> a shit. >> >> So go and write your documentation in any format and do not expect me to >> look at it. >> I'm fed up about people that want doc on the web and when we spend time >> to migrate from latex to >> pillar to generate html and latex do not even consider what we did. >> >> Stef >> >> 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 Sean P. DeNigris

Dale Henrichs-3 wrote > Ubuntu14.04 tale of the ldd tape Thanks! I'll dig into these 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 Sven Van Caekenberghe

> On 14 Apr 2015, at 22:03, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > > Whoa. > I genuinely don't understand the fierce emotions here. Why do Pillar and Markdown have to be opposed? Why is wanting support for better parsing of MD (a commonly used format around the web, and useful in many projects) somehow an insult to the work done on Pillar? > > (Incidentally, I don't quite understand why Pillar was created in the first place. Why have a slightly different and incompatible markdown format from what the rest of the world is using? But that's not the point. We have both, and it's easy to support both. What's the problem?) Communication is always an issue, especially for newcomers. Pillar was chosen because it is our format, something we control and define, something we can extend anyway we want, not somebody else's format that we can only follow. Incidentally, Pillar precedes MarkDown by years. Furthermore, there is NO MarkDown standard, nor will there ever be. There are slight but annoying differences between the main implementors. It is super hard to write a parser for MD. Anyway, IMHO, the key thing is the underlying document model. > On Tue, Apr 14, 2015 at 3:08 PM, stepharo <stepharo(a)free.fr> wrote: > I'm really pissed off. Because nearly nobody tried to write anything with pillar and you just talk > about what you do not know. But thanks this is great to see that we are spending our energy for people > who will never even try to use what we are doing. > Superb! > > No need to reply I will not read this thread anymore. And I should not even have because it was so obvious. > > And yes I 'm REALLY pissed off. You should also say to cyril that what is is doing is hopeless because as soon > as we will have a stupid markdown parser suddenly it will be great. what a shit. > > So go and write your documentation in any format and do not expect me to look at it. > I'm fed up about people that want doc on the web and when we spend time to migrate from latex to > pillar to generate html and latex do not even consider what we did. > > Stef > >>>> 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] PetitMarkdown

by Dmitri Zagidulin

Whoa. I genuinely don't understand the fierce emotions here. Why do Pillar and Markdown have to be opposed? Why is wanting support for better parsing of MD (a commonly used format around the web, and useful in many projects) somehow an insult to the work done on Pillar? (Incidentally, I don't quite understand why Pillar was created in the first place. Why have a slightly different and incompatible markdown format from what the rest of the world is using? But that's not the point. We have both, and it's easy to support both. What's the problem?) On Tue, Apr 14, 2015 at 3:08 PM, stepharo <stepharo(a)free.fr> wrote: > I'm really pissed off. Because nearly nobody tried to write anything with > pillar and you just talk > about what you do not know. But thanks this is great to see that we are > spending our energy for people > who will never even try to use what we are doing. > Superb! > > No need to reply I will not read this thread anymore. And I should not > even have because it was so obvious. > > And yes I 'm REALLY pissed off. You should also say to cyril that what is > is doing is hopeless because as soon > as we will have a stupid markdown parser suddenly it will be great. what a > shit. > > So go and write your documentation in any format and do not expect me to > look at it. > I'm fed up about people that want doc on the web and when we spend time to > migrate from latex to > pillar to generate html and latex do not even consider what we did. > > Stef > > 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] PetitMarkdown

by Tudor Girba

Hi, MD is a cool exercise for PetitParser exactly because it is a terrible language. Jan did a great job at pushing parsing limits, but that does not mean that we have to jump on it to use it inside Pharo :). Actually, at this point in time, I really do not quite understand why we are still entertaining the idea of MD inside Pharo given all the effort for documenting using Pillar. In any case, as you might know, there already exists support for editing Pillar from inside Pharo ( http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe…) and we will likely develop significantly this support in the IDE. Cheers, Doru On Tue, Apr 14, 2015 at 9:08 PM, stepharo <stepharo(a)free.fr> wrote: > I'm really pissed off. Because nearly nobody tried to write anything with > pillar and you just talk > about what you do not know. But thanks this is great to see that we are > spending our energy for people > who will never even try to use what we are doing. > Superb! > > No need to reply I will not read this thread anymore. And I should not > even have because it was so obvious. > > And yes I 'm REALLY pissed off. You should also say to cyril that what is > is doing is hopeless because as soon > as we will have a stupid markdown parser suddenly it will be great. what a > shit. > > So go and write your documentation in any format and do not expect me to > look at it. > I'm fed up about people that want doc on the web and when we spend time to > migrate from latex to > pillar to generate html and latex do not even consider what we did. > > Stef > > 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 > > > > -- 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 Dale Henrichs

Ubuntu14.04 tale of the ldd tape ... same missing library, same expression to load ... did not actually test sound in either 12.04 or 14.04... HTH, Dale dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ls libB3DAcceleratorPlugin.so libInternetConfigPlugin.so libSqueakFFIPrims.so PharoV10.sources libFT2Plugin.so libJPEGReaderPlugin.so libSqueakSSL.so PharoV20.sources libgcirpc-3.2.0-32.so libJPEGReadWriter2Plugin.so libssh2.so.1.0.1 PharoV30.sources libgcirpc-3.2.4-32.so libRePlugin.so libssl-3.2.0-32.so vm-display-null libgcits-3.2.0-32.so libSDL2-2.0.so.0 libssl-3.2.4-32.so vm-display-X11 libgcits-3.2.4-32.so libSDL2-2.0.so.0.2.1 __MACOSX vm-sound-ALSA libgit2.so.0.21.0 libSDL2DisplayPlugin.so pharo vm-sound-null dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libB3DAcceleratorPlugin.so linux-gate.so.1 => (0xf7741000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7573000) /lib/ld-linux.so.2 (0xf7742000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libFT2Plugin.so linux-gate.so.1 => (0xf77a1000) libfreetype.so.6 => /usr/lib/i386-linux-gnu/libfreetype.so.6 (0xf76e9000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf753b000) libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf7520000) libpng12.so.0 => /lib/i386-linux-gnu/libpng12.so.0 (0xf74f8000) /lib/ld-linux.so.2 (0xf77a2000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf74b2000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libInternetConfigPlugin.so linux-gate.so.1 => (0xf7776000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75b5000) /lib/ld-linux.so.2 (0xf7777000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libJPEGReaderPlugin.so linux-gate.so.1 => (0xf7706000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7544000) /lib/ld-linux.so.2 (0xf7707000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libJPEGReadWriter2Plugin.so linux-gate.so.1 => (0xf76ee000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf750b000) /lib/ld-linux.so.2 (0xf76ef000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libRePlugin.so linux-gate.so.1 => (0xf7750000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7587000) /lib/ld-linux.so.2 (0xf7751000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libSDL2DisplayPlugin.so linux-gate.so.1 => (0xf7771000) libSDL2-2.0.so.0 => not found libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75b1000) /lib/ld-linux.so.2 (0xf7772000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libSDL2-2.0.so.0 linux-gate.so.1 => (0xf7773000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf75d0000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf75cb000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf75ae000) librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf75a5000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf73f7000) /lib/ld-linux.so.2 (0xf7774000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libSqueakFFIPrims.so linux-gate.so.1 => (0xf76f0000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7529000) /lib/ld-linux.so.2 (0xf76f1000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libSqueakSSL.so linux-gate.so.1 => (0xf7706000) libssl.so.1.0.0 => /lib/i386-linux-gnu/libssl.so.1.0.0 (0xf7699000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf74eb000) libcrypto.so.1.0.0 => /lib/i386-linux-gnu/libcrypto.so.1.0.0 (0xf733d000) /lib/ld-linux.so.2 (0xf7707000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7338000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd libssh2.so.1.0.1 linux-gate.so.1 => (0xf77d9000) libcrypto.so.1.0.0 => /lib/i386-linux-gnu/libcrypto.so.1.0.0 (0xf75ed000) libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf75d3000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7424000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf741f000) /lib/ld-linux.so.2 (0xf77da000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd pharo linux-gate.so.1 => (0xf77c1000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf776c000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7767000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf774a000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf759c000) /lib/ld-linux.so.2 (0xf77c2000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-display-null linux-gate.so.1 => (0xf77d0000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf760f000) /lib/ld-linux.so.2 (0xf77d1000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-display-X11 linux-gate.so.1 => (0xf771a000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76d4000) libGL.so.1 => /usr/lib/i386-linux-gnu/mesa/libGL.so.1 (0xf7674000) libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf753f000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7391000) /lib/ld-linux.so.2 (0xf771b000) libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xf7379000) libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf7366000) libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xf7362000) libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf735b000) libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xf7358000) libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xf7340000) libxcb-dri2.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri2.so.0 (0xf733a000) libxcb-dri3.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri3.so.0 (0xf7336000) libxcb-present.so.0 => /usr/lib/i386-linux-gnu/libxcb-present.so.0 (0xf7331000) libxcb-sync.so.1 => /usr/lib/i386-linux-gnu/libxcb-sync.so.1 (0xf732a000) libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf7308000) libxshmfence.so.1 => /usr/lib/i386-linux-gnu/libxshmfence.so.1 (0xf7305000) libXxf86vm.so.1 => /usr/lib/i386-linux-gnu/libXxf86vm.so.1 (0xf72ff000) libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xf72f1000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf72ec000) libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf72e8000) libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf72e1000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-sound-ALSA linux-gate.so.1 => (0xf77b6000) libasound.so.2 => not found libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75f3000) /lib/ld-linux.so.2 (0xf77b7000) dhenrich@ubuntu14:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-sound-null linux-gate.so.1 => (0xf77c0000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7600000) /lib/ld-linux.so.2 (0xf77c1000) On 04/14/2015 03:48 AM, Sean P. DeNigris wrote: > 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 stepharo

I'm really pissed off. Because nearly nobody tried to write anything with pillar and you just talk about what you do not know. But thanks this is great to see that we are spending our energy for people who will never even try to use what we are doing. Superb! No need to reply I will not read this thread anymore. And I should not even have because it was so obvious. And yes I 'm REALLY pissed off. You should also say to cyril that what is is doing is hopeless because as soon as we will have a stupid markdown parser suddenly it will be great. what a shit. So go and write your documentation in any format and do not expect me to look at it. I'm fed up about people that want doc on the web and when we spend time to migrate from latex to pillar to generate html and latex do not even consider what we did. Stef >>> 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

For Ubunutu 12.04 and [VM: NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Mar 19 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Mar 19 2015 https://github.com/pharo-project/pharo-vm.git Commit: 5d3f4b945903184fbcf04be9fb1e0d8ec979c881 Date: 2015-03-12 17:15:25 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14901 The tale of the ldd tape is stuck on the end ... (the libgci* and libssl* .so files are suppplied by GemStone) ... libasound.so.2 looks like it's missing and the following doe s the load: sudo apt-get install libasound2:i386 HTH, Dale dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ls libB3DAcceleratorPlugin.so libInternetConfigPlugin.so libSqueakSSL.so PharoV20.sources libFT2Plugin.so libJPEGReaderPlugin.so libssh2.so.1.0.1 PharoV30.sources libgcirpc-3.1.0.6-32.so libJPEGReadWriter2Plugin.so libssl-3.1.0.6-32.so vm-display-null libgcirpc-3.2.4-32.so libRePlugin.so libssl-3.2.4-32.so vm-display-X11 libgcirpc-3.2.6-32.so libSDL2-2.0.so.0 libssl-3.2.6-32.so vm-sound-ALSA libgcits-3.2.4-32.so libSDL2-2.0.so.0.2.1 __MACOSX vm-sound-null libgcits-3.2.6-32.so libSDL2DisplayPlugin.so pharo libgit2.so.0.21.0 libSqueakFFIPrims.so PharoV10.sources dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libB3DAcceleratorPlugin.so linux-gate.so.1 => (0xf773c000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7574000) /lib/ld-linux.so.2 (0xf773d000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libFT2Plugin.so linux-gate.so.1 => (0xf7760000) libfreetype.so.6 => /usr/lib/i386-linux-gnu/libfreetype.so.6 (0xf76af000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7505000) libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf74ee000) /lib/ld-linux.so.2 (0xf7761000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libInternetConfigPlugin.so linux-gate.so.1 => (0xf774c000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7591000) /lib/ld-linux.so.2 (0xf774d000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libJPEGReaderPlugin.so linux-gate.so.1 => (0xf776d000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75b1000) /lib/ld-linux.so.2 (0xf776e000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libJPEGReadWriter2Plugin.so linux-gate.so.1 => (0xf77b7000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75da000) /lib/ld-linux.so.2 (0xf77b8000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libRePlugin.so linux-gate.so.1 => (0xf779d000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75da000) /lib/ld-linux.so.2 (0xf779e000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libSDL2DisplayPlugin.so linux-gate.so.1 => (0xf77c7000) libSDL2-2.0.so.0 => not found libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf760d000) /lib/ld-linux.so.2 (0xf77c8000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libSDL2-2.0.so.0 linux-gate.so.1 => (0xf76eb000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7564000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf755f000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7543000) librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf753a000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7390000) /lib/ld-linux.so.2 (0xf76ec000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libSqueakFFIPrims.so linux-gate.so.1 => (0xf77cd000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf760c000) /lib/ld-linux.so.2 (0xf77ce000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd libSqueakSSL.so linux-gate.so.1 => (0xf76fa000) libssl.so.1.0.0 => /lib/i386-linux-gnu/libssl.so.1.0.0 (0xf7690000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf74e6000) libcrypto.so.1.0.0 => /lib/i386-linux-gnu/libcrypto.so.1.0.0 (0xf7339000) /lib/ld-linux.so.2 (0xf76fb000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7334000) libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf731e000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-display-null linux-gate.so.1 => (0xf76e6000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf752b000) /lib/ld-linux.so.2 (0xf76e7000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-display-X11 linux-gate.so.1 => (0xf76ef000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76ac000) libGL.so.1 => /usr/lib/i386-linux-gnu/mesa/libGL.so.1 (0xf7653000) libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf751e000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7374000) /lib/ld-linux.so.2 (0xf76f0000) libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xf735e000) libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf734c000) libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xf7348000) libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf7341000) libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xf733e000) libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xf7326000) libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf7305000) libXxf86vm.so.1 => /usr/lib/i386-linux-gnu/libXxf86vm.so.1 (0xf72ff000) libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xf72f1000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf72ec000) libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf72e8000) libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf72e1000) librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf72d8000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-sound-ALSA linux-gate.so.1 => (0xf776e000) libasound.so.2 => not found libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf75b2000) /lib/ld-linux.so.2 (0xf776f000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ ldd vm-sound-null linux-gate.so.1 => (0xf770f000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7556000) /lib/ld-linux.so.2 (0xf7710000) dhenrich@ubuntu12:~/gsDevKitHome/pharo/pharo-vm$ On 04/14/2015 03:48 AM, Sean P. DeNigris wrote: > 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 stepharo

Le 14/4/15 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 :) seriously? With all the efforts and that damien and me are spending on pillar! Thanks a lot for your consideration > > 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 >> <mailto:kurs@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 >> <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/#%21/%7EPharoExtras/PetitMarkdown/> >> > <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ >> <http://smalltalkhub.com/#%21/%7EPharoExtras/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] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by Laurent

Hi Markus, I've updated the package and now it should work. Note that the pkg files are hosted at https://github.com/lolgzs/pharo-aur/ Cheers, Laurent Le lun. 13 avril 2015 Ã 22:56, Markus Schlager <m.slg(a)gmx.de> a Ã©crit : > Hi Laurent, > > On Tue, 18 Mar 2014, Laurent Laffont wrote: > >> There's also a pharo-launcher package that depends on pharo-vm: >> >> $ yaourt pharo-launcher > > Right know this fails raising a 404 File Not Found error: > > --2015-04-13 22:51:47-- > https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage/last… > AuflÃ¶sen des Hostnamens Â»ci.inria.fr (ci.inria.fr)Â« â¦ > 193.51.193.223 > Verbindungsaufbau zu ci.inria.fr (ci.inria.fr)|193.51.193.223|:443 > â¦ verbunden. > HTTP-Anforderung gesendet, auf Antwort wird gewartet â¦ 404 Not Found > 2015-04-13 22:51:47 FEHLER 404: Not Found. > > Markus

April 14, 2015