December 2017 - Pharo-users

Re: [Pharo-users] Plotting a SMark report

by Alexandre Bergel

Hi HernÃ¡n, Not that I know. But it is trivial to plot that using Roassal. Let us know if you need help on this. Alexandre > On Dec 5, 2017, at 1:09 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi guys, > > I benchmarked five Levenshtein implementations today and just wonder > is there any package or extension which takes a SMark report and plot > a Roassal bar chart? > > This is the best I get so far: > > "Report for: StringExtensionsBenchmark > Benchmark LevPW100kTo > LevPW100kTo total: iterations=10 runtime: 486.6ms +/-4.2 > > Benchmark LevPW1kWith > LevPW1kWith total: iterations=10 runtime: 27.6ms +/-1.3 > > Benchmark LevPW1k > LevPW1k total: iterations=10 runtime: 70.40ms +/-0.82 > > Benchmark LevPW1kTo > LevPW1kTo total: iterations=10 runtime: 4.30ms +/-0.28 > > Benchmark LevPW100k > LevPW100k total: iterations=10 runtime: 8325ms +/-101 > > Benchmark LevPW100kFrom > LevPW100kFrom total: iterations=10 runtime: 1278.1ms +/-4.9 > > Benchmark LevPW100kWith > LevPW100kWith total: iterations=10 runtime: 3309ms +/-75 > > Benchmark LevPW100kToLD > LevPW100kToLD total: iterations=10 runtime: 2222ms +/-17 > > Benchmark LevPW1kLD > LevPW1kLD total: iterations=10 runtime: 19.40ms +/-0.48 > > Benchmark LevPW1kFrom > LevPW1kFrom total: iterations=10 runtime: 11.30ms +/-0.39 > " > > Cheers, > > HernÃ¡n >

Dec. 20, 2017

Re: [Pharo-users] Athens error

by Hilaire

Le 20/12/2017 Ã 21:05, Stephane Ducasse a Ã©critÂ : > Hilaire > > debug drawing error should give you access to the debugger and after > you can get the stack. Like this ? FFICallout>>loaderForArgNamed: FFICallout>>loaderForArgNamed:indirectIndex: FFICallout>>argName:indirectIndex:type:ptrArity: FFIFunctionParser>>parseArgument FFIFunctionParser>>parseArguments FFIFunctionParser>>parseNamedFunction: FFICalloutMethodBuilder>>parseSignature: FFICalloutMethodBuilder>>generate FFICalloutMethodBuilder>>build: FFICalloutAPI>>function:module: AthensCairoSurface class(Object)>>nbCall: AthensCairoSurface class>>primImage:width:height: AthensCairoSurface class>>extent:format: AthensCairoSurface class>>extent: AthensWrapMorph>>createSurface AthensWrapMorph>>initializeForNewSession AthensWrapMorph>>checkSurface AthensWrapMorph>>fullDrawOn: FormCanvas(Canvas)>>fullDraw: FormCanvas(Canvas)>>fullDrawMorph: [ :arg3 | arg3 fullDrawMorph: self ] in AthensWrapMorph(Morph)>>imageForm:forRectangle: in Block: [ :arg3 | arg3 fullDrawMorph: self ] FormCanvas>>translateBy:during: AthensWrapMorph(Morph)>>imageForm:forRectangle: AthensWrapMorph(Morph)>>imageFormForRectangle: AthensWrapMorph(Morph)>>iconOrThumbnail AthensWrapMorph(Morph)>>iconOrThumbnailOfSize: [ :arg3 | tmp1 add: arg3 class name asString target: arg3 selector: #addMorphFrontFromWorldPosition: argument: self topRendererOrSelf. tmp1 lastItem icon: (arg3 iconOrThumbnailOfSize: 16). self owner == arg3 ifTrue: [ tmp1 lastItem emphasis: 1 ] ] in DrGDrawable(Morph)>>addEmbeddingMenuItemsTo:hand: in Block: [ :arg3 | ... Array(SequenceableCollection)>>reverseDo: DrGDrawable(Morph)>>addEmbeddingMenuItemsTo:hand: DrGDrawable(Morph)>>addStandardHaloMenuItemsTo:hand: -- Dr. Geo http://drgeo.eu

Dec. 20, 2017

Re: [Pharo-users] [ANN] OpenSSL-Pharo works on Windows

by Sean Glazier

OK now my cell is finally working again! I can now be reached at 603 957 2705 Kind Regards, Sean Glazier On Wed, Dec 20, 2017 at 2:57 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > great news. > And this is super great that you plan to work on different platforms! > THANKS > > On Wed, Dec 20, 2017 at 8:55 AM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > Hi all, > > > > OpenSSL-Pharo now works on Windows. Tested on Windows 10 with a fresh > 32-bit > > Pharo 6.1 zip package downloaded from pharo.org. On Windows this > library uses > > libeay.dll which is bundled with the Pharo VM. > > > > Metacello new > > baseline: 'OpenSSL'; > > smalltalkhubUser: 'PierceNg' project: 'OpenSSL-Pharo'; > > load. > > > > Pierce > > > > > >

Dec. 20, 2017

Re: [Pharo-users] Iceberg, Git and Package version

by Stephane Ducasse

In iceberg you can specify - latest version when you do not specify anything - a version (but it should be a git tag so you should save you code with a tag - iceberg does not support it right now but you can do it with git) - the hash of your git commit. Does it answer your question? Stef On Wed, Dec 20, 2017 at 7:51 PM, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Hello, > > How are packages versions computed in Iceberg? > > I am looking at the Metacello documentation at 'Deep in Pharo', it says I > can define dependencies at package level and it uses the following format to > identify versions: <dev_name.versionNumber>; which I think is a pattern used > by Monticello, right? However, I can't figure what is the equivalent (if > any) in Iceberg. > > Thanks in Advance, > Vitor

Dec. 20, 2017

Re: [Pharo-users] Athens error

by Stephane Ducasse

Normally the call does not need the sources (if I'm correct in the past it needed to generate the correct method argument or something like that). Can you provide more information? or the image somewhere? Because FFI should improve and we are looking for edge corner bugs. Stef On Wed, Dec 20, 2017 at 8:58 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Tried to build DrGeo app witht the same image used for development. Still > gets red screen of depth on the DrGeo canvas, but with a different error > (screenshot for the curious). Image cleaning were removed, so nothing wrong > comes from there. > > Now, if I copied along the image file Pharo7.0-32bit-f82fc36.source. Canvas > does not get bogus. What the f*k. Image and VM are 64bits > > Pharo is really funny > > > Le 18/12/2017 Ã 21:35, Hilaire a Ã©crit : >> >> In the following day will try with another image... > > > -- > Dr. Geo > http://drgeo.eu >

Dec. 20, 2017

Re: [Pharo-users] Athens error

by Stephane Ducasse

Hilaire debug drawing error should give you access to the debugger and after you can get the stack. On Mon, Dec 18, 2017 at 9:35 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Sadly building the image with a light cleaning, does not grant me access to > the morph menu of the faulty canvas. Still same error as mentionned in > previous screenshot. > > The upper moprh menu can be access, but there is stack trace entry in its > menu (see screesshot). > > In the following day will try with another image... > > > Le 17/12/2017 Ã 20:55, Hilaire a Ã©crit : >> >> May be something else is wrong in the image, in the next days I will try >> to build differently the image application > > > -- > Dr. Geo > http://drgeo.eu >

Dec. 20, 2017

Re: [Pharo-users] Athens error

by Hilaire

Tried to build DrGeo app witht the same image used for development. Still gets red screen of depth on the DrGeo canvas, but with a different error (screenshot for the curious). Image cleaning were removed, so nothing wrong comes from there. Now, if I copied along the image file Pharo7.0-32bit-f82fc36.source. Canvas does not get bogus. What the f*k. Image and VM are 64bits Pharo is really funny Le 18/12/2017 Ã 21:35, Hilaire a Ã©critÂ : > In the following day will try with another image... -- Dr. Geo http://drgeo.eu

Dec. 20, 2017

Re: [Pharo-users] [ANN] OpenSSL-Pharo works on Windows

by Stephane Ducasse

great news. And this is super great that you plan to work on different platforms! THANKS On Wed, Dec 20, 2017 at 8:55 AM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > Hi all, > > OpenSSL-Pharo now works on Windows. Tested on Windows 10 with a fresh 32-bit > Pharo 6.1 zip package downloaded from pharo.org. On Windows this library uses > libeay.dll which is bundled with the Pharo VM. > > Metacello new > baseline: 'OpenSSL'; > smalltalkhubUser: 'PierceNg' project: 'OpenSSL-Pharo'; > load. > > Pierce > >

Dec. 20, 2017

Iceberg, Git and Package version

by Vitor Medina Cruz

Hello, How are packages versions computed in Iceberg? I am looking at the Metacello documentation at 'Deep in Pharo', it says I can define dependencies at package level and it uses the following format to identify versions: <dev_name.versionNumber>; which I think is a pattern used by Monticello, right? However, I can't figure what is the equivalent (if any) in Iceberg. Thanks in Advance, Vitor

Dec. 20, 2017

Re: [Pharo-users] Metacello with Git

by Thierry Goubier

Hi Pierce, Le 20/12/2017 Ã 17:17, Pierce Ng a Ã©critÂ : > On Tue, Dec 19, 2017 at 07:07:16PM -0800, Dale Henrichs wrote: >> I am under the impression that iceberg is able to authenticate with >> SSH keys .... I am not a pharo/iceberg user myself, but it seems >> that iceberg should be able to fill that gap. > > Iceberg does, with RSA keys. Iceberg didn't work for me with ED25519 keys. does command line git work with those ED25519 keys? Regards, Thierry > > Pierce > > >

Dec. 20, 2017