January 2020 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Ramon Leon

On 2020-01-02 10:56 a.m., Sean P. DeNigris wrote: > While I dream of a world where everything is in-image as pure Smalltalk, > given the reality of limited manpower, I think of outside library use as a > way to "cheat" and get a lot more from that limited engineering resource. Agree, I've used the original Markdown.pl implementation for years same as I would any other shell script, via OSProcess markdown: someContent ^UnixProcess pipeString: someContent throughCommand: (FileDirectory default fullPathFor: 'Markdown.pl') Never saw a need to rewrite what already works in its original form. -- RamÃ³n LeÃ³n

Jan. 3, 2020

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Ramon Leon

On 2020-01-02 10:56 a.m., Sean P. DeNigris wrote: > While I dream of a world where everything is in-image as pure Smalltalk, > given the reality of limited manpower, I think of outside library use as a > way to "cheat" and get a lot more from that limited engineering resource. Agree, I've used the original Markdown.pl implementation for years same as I would any other shell script, via OSProcess markdown: someContent ^UnixProcess pipeString: someContent throughCommand: (FileDirectory default fullPathFor: 'Markdown.pl') Never saw a need to rewrite what already works in its original form. -- RamÃ³n LeÃ³n VP of Technology Alliance Reservations Network

Jan. 3, 2020

Re: [Pharo-users] Zeroconf on Ubuntu (14) libz.so.1 error

by Eric Gade

With some help I was able to determine that this is a 32/64 issue. I had been using the zeroconf address for 32bit when I needed the 64bit version from get.pharo.org/64 On a related note, the command `curl get.pharo.org/64 | bash` does not work, since that URL redirects. The wget equivalent works fine. On Thu, Jan 2, 2020 at 8:12 PM Eric Gade <eric.gade(a)gmail.com> wrote: > Hi All, > > I'm getting an inscrutable error when using the regular zeroconf (curl > https://get.pharo.org | bash) and trying to run the resulting ./pharo > script: > > ``` > > ioLoadModule(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/libgit2.so): > libz.so.1: cannot open shared object file: No such file or directory > > ioLoadModule(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/libgit2.so): > libz.so.1: cannot open shared object file: No such file or directory > > tryLoading(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/ > libgit2.so/.libs/,libgit2.so): > stat(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/ > libgit2.so/.libs/) Not a directory > External module not found > ``` > > This is on an Ubuntu server that is (unfortunately) running 14.04 LTS. For > the time being the version is out of my control. > > I have tried something like `apt-get install zlib1g` but the system is > reporting that this is already installed. From this error message I cannot > really tell what the actual problem is and I'm also a little stumped about > how to properly debug it. > > Tips in any direction are much appreciated. Thanks! > > -- > Eric > -- Eric

Jan. 3, 2020

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Kasper Ãsterbye

Just while we are at the notion of markdowns, I have at https://github.com/kasperosterbye/PillarRichTextRender a first build of a pharo based github markdown to pillar. From pillar you can go to html. But just to prove the point of the strength of importing working software from outside using FFI, the markdown parser I am working on currently has two serious limitations: a) it do not do table (because my project really was about rendering pillar inside the image, and could not figure out how to render tables inlined in text). b) image address has to be hard-coded - cannot be relative to some url. â Kasper

Jan. 3, 2020

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Esteban Lorenzano

Hi, Good work :) { #category : #finalization } HdBufferOpaque class >> finalizeResourceData: aHandle [ HdFFILibrary uniqueInstance ffiCall: #(void hoedown_buffer_free (ExternalAddress aHandle)) ] wowâ¦ does this works at all? I admit it is not how it is intended to work :P > On 3 Jan 2020, at 06:24, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Thu, Jan 02, 2020 at 12:56:55PM -0600, Sean P. DeNigris wrote: >> bugs seem to be >> more severe and difficult to diagnose, so we'll see how it goes as FFI use >> becomes more and more common... > > There's a saying about (aspects of) building software which source I > cannot recall: > > If it hurts, do it more frequently. > > I believe FFI should be pushed as much as possible to work out bugs and > develop new capabilities. Looking forward to playing with threaded FFI. +1 FFI introduces a whole new universe of possibilities we cannot reasonable cover in-image nowadays. Now, while *there are* problems still to solve, I think people have the wrong impression the FFI layer is causing most of the bugs around (TTF for example) while this is not true at all :) For example, recent bug around memory corruption was claimed several times it was because of FFI (and even I thought it was around it at the beginning) while in fact it was a problem on how compaction was working. Other example, TTF itself: problems were around when we had a plugin and we still have some with the FFI implementation. But the problem is not around the plugin or the FFI implementation but around the bad usage (not thread safe) we do of it in-image. The reason why people think some problems are FFI related is because we are pushing Pharo in directions not-fully-tested before. The usage of FFI just unveils a lot of problems on how we handle things there were present before, but they were not as visible as they are now. Esteban > > Pierce >

Jan. 3, 2020

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Todd Blanchard

+1 > On Jan 2, 2020, at 9:24 PM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Thu, Jan 02, 2020 at 12:56:55PM -0600, Sean P. DeNigris wrote: >> bugs seem to be >> more severe and difficult to diagnose, so we'll see how it goes as FFI use >> becomes more and more common... > > There's a saying about (aspects of) building software which source I > cannot recall: > > If it hurts, do it more frequently. > > I believe FFI should be pushed as much as possible to work out bugs and > develop new capabilities. Looking forward to playing with threaded FFI. > > Pierce >

Jan. 3, 2020

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Pierce Ng

On Thu, Jan 02, 2020 at 12:56:55PM -0600, Sean P. DeNigris wrote: > bugs seem to be > more severe and difficult to diagnose, so we'll see how it goes as FFI use > becomes more and more common... There's a saying about (aspects of) building software which source I cannot recall: If it hurts, do it more frequently. I believe FFI should be pushed as much as possible to work out bugs and develop new capabilities. Looking forward to playing with threaded FFI. Pierce

Jan. 3, 2020

Zeroconf on Ubuntu (14) libz.so.1 error

by Eric Gade

Hi All, I'm getting an inscrutable error when using the regular zeroconf (curl https://get.pharo.org | bash) and trying to run the resulting ./pharo script: ``` ioLoadModule(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/libgit2.so): libz.so.1: cannot open shared object file: No such file or directory ioLoadModule(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/libgit2.so): libz.so.1: cannot open shared object file: No such file or directory tryLoading(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/ libgit2.so/.libs/,libgit2.so): stat(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/ libgit2.so/.libs/) Not a directory External module not found ``` This is on an Ubuntu server that is (unfortunately) running 14.04 LTS. For the time being the version is out of my control. I have tried something like `apt-get install zlib1g` but the system is reporting that this is already installed. From this error message I cannot really tell what the actual problem is and I'm also a little stumped about how to properly debug it. Tips in any direction are much appreciated. Thanks! -- Eric

Jan. 3, 2020

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Esteban Maringolo

On Thu, Jan 2, 2020 at 3:47 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Tim Mackinnon wrote > > Iâm getting the impression that ffi is getting very easy these days and > > maybe we should use it more to focus on âotherâ things... This said, many > > of our nastiest bugs... > > That said, as you pointed out, bugs seem to be > more severe and difficult to diagnose, so we'll see how it goes as FFI use > becomes more and more common... It seems to have played very well for the Python folks. It should work even better for Pharo. :) Esteban A. Maringolo

Jan. 2, 2020

Re: [Pharo-users] [ANN] Phoedown - Markdown to HTML

by Sean P. DeNigris

Tim Mackinnon wrote > Iâm getting the impression that ffi is getting very easy these days and > maybe we should use it more to focus on âotherâ things... This said, many > of our nastiest bugs... While I dream of a world where everything is in-image as pure Smalltalk, given the reality of limited manpower, I think of outside library use as a way to "cheat" and get a lot more from that limited engineering resource. I look forward to the mythical day where "everything's done" and we can come back around and replace some of these with Smalltalk, but then of course we'll own the maintenance. That said, as you pointed out, bugs seem to be more severe and difficult to diagnose, so we'll see how it goes as FFI use becomes more and more common... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 2, 2020