December 2018 - Pharo-users

Re: [Pharo-users] Voyage

by Norbert Hartl

I added PBKDF2 to the cryptography repository on github a while ago. One reason why I migrated cryptography in the first place Norbert > Am 02.12.2018 um 15:59 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > > > >> On Sun 2 Dec 2018 at 15:38, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> There was a cryptography version on GitHub, isnât? >> > > Yes, but we need someone with the rights to write on PBKDF2 on StHub, or migrate it in github aswell to fix the issue. > >> >>> On 2 Dec 2018, at 15:31, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> >>> >>> >>> On Sun 2 Dec 2018 at 15:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> There is indeed a problem because cryptography package is still using an old API: #ifNotNilDo: that does not exists anymore in Pharo. >>>> You are probably seen something like this: >>>> >>>> <Screenshot 2018-12-02 at 15.02.19.png> >> >>> >>> >>> I looked at it last time and the problem is that one of the dependency hosted on StHub still depends on the StHub version of Cryptography. >>> >>> http://smalltalkhub.com/#!/~UdoSchneider/PBKDF2/ >>> >>> But not many people can write on this project I think. >>> >>>> >>>> >>>> (And this is a bug) >>>> Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, then save and select âproceedâ. >>>> >>>> That will allow voyage to load properly. >>>> >>>> Cheers, >>>> Esteban >>>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >> > -- > Cyril Ferlicot > https://ferlicot.fr

Dec. 2, 2018

Re: [Pharo-users] How to take care that the + before a number is ignored

by Ben Coman

On Sun, 2 Dec 2018 at 17:49, Roelof Wobben <r.wobben(a)home.nl> wrote: > Hello, > > I have a collection that looks like this : > > sampleData1 > "comment stating purpose of message" > > ^ #( -8 > +7) > > I want to add those numbers up but the code chokes at the + > To get some insight, do.... #( -8 +7) inspect You will notice three elements when I think you expected two. So perhaps you need... x := #( -8 +7) reject: [:y | y = #+]. and then #inject:into: "x" cheers -ben > > so I did this : > > FrequencyFinderData new class sampleData1 inject: 0 into: [:sum :each > | (each ~= $+) ifTrue: [sum + each asInteger] ] > > so when the each is not a + it must count it but still the code chokes > at the + > > Where do I think wrong ? > > Roelof > > >

Dec. 2, 2018

Re: [Pharo-users] Voyage

by Cyril Ferlicot

On Sun 2 Dec 2018 at 15:38, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > There was a cryptography version on GitHub, isnât? > > Yes, but we need someone with the rights to write on PBKDF2 on StHub, or migrate it in github aswell to fix the issue. > On 2 Dec 2018, at 15:31, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > > On Sun 2 Dec 2018 at 15:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> There is indeed a problem because cryptography package is still using an >> old API: #ifNotNilDo: that does not exists anymore in Pharo. >> You are probably seen something like this: >> >> <Screenshot 2018-12-02 at 15.02.19.png> >> > > > I looked at it last time and the problem is that one of the dependency > hosted on StHub still depends on the StHub version of Cryptography. > > http://smalltalkhub.com/#!/~UdoSchneider/PBKDF2/ > > But not many people can write on this project I think. > > >> >> (And this is a bug) >> Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, >> then save and select âproceedâ. >> >> That will allow voyage to load properly. >> >> Cheers, >> Esteban >> >> -- > Cyril Ferlicot > https://ferlicot.fr > > > -- Cyril Ferlicot https://ferlicot.fr

Dec. 2, 2018

Re: [Pharo-users] UFFI and opaque(ish) types

by Ben Coman

One option could be to create a small shared library that you compile for each platform that just exported the member offsets... https://www.embedded.com/design/prototyping-and-development/4024941/Learn-a… You first FFI to that read struct member offsets and dynamically create the definitions for your target library. I haven't tried it in practice. cheers -ben P.S. Occasionally I dream about compilers being able to embed a pre-compiled header declaration block in the library for FFI users to iterate... https://clang.llvm.org/docs/PCHInternals.html#declarations-block On Sun, 2 Dec 2018 at 17:04, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Phil and Esteban, > > Thanks for your replies. > > I've realised that I badly worded my question. By "opaque" I meant that > it is difficult to determine the underlying type of the > variables, but I still want to be access the values of typeA and typeB > in my example structure. > > Phil, I had a look through your XMPP code, if it does show an example of > actually retrieving a structure member such as "typeA" in my example, my > apologies and please let me know where it is. > > Thanks again, > Alistair > > > On Fri, 30 Nov 2018 at 23:46, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > On 30 Nov 2018, at 19:50, phil--- via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > > > > From: "phil(a)highoctane.be" <phil(a)highoctane.be> > > Subject: Re: [Pharo-users] UFFI and opaque(ish) types > > Date: 30 November 2018 at 19:50:03 CET > > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > > > > Inherit from FFIOpaqueObject > > > > + initialize TypeMap > > > > I have a few here: > > > > https://github.com/Pharophile/XmppTalk > > > > > https://github.com/Pharophile/XmppTalk/tree/master/packages/XmppTalk-Extern… > > > https://github.com/Pharophile/XmppTalk/blob/master/packages/XmppTalk-LibStr… > > > > HTH > > Phil > > > > > > Yes, as he says/shows :) > > > > Esteban > > > On Fri, Nov 30, 2018 at 2:39 PM Alistair Grant <akgrant0710(a)gmail.com> > wrote: > >> > >> How are opaque(ish) types normally handled in UFFI (or FFI)? > >> > >> E.g. if I want to use libstuff which defines the following structure: > >> > >> struct stuffstruct { > >> typeA a; > >> typeB b; > >> } stufftype; > >> > >> > >> I might know they're integers, but not the size, signed vs. unsigned, > >> etc. > >> > >> The definitions of typeA and typeB are buried in multiple layers of > >> header files, dependent on #if tests, can be different sizes on > >> different platforms (e.g. Linux vs. MacOS), etc.? > >> > >> Is this documented somewhere? > >> > >> Thanks, > >> Alistair > >

Dec. 2, 2018

Re: [Pharo-users] Voyage

by Esteban Lorenzano

There was a cryptography version on GitHub, isnât? > On 2 Dec 2018, at 15:31, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > > On Sun 2 Dec 2018 at 15:08, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > There is indeed a problem because cryptography package is still using an old API: #ifNotNilDo: that does not exists anymore in Pharo. > You are probably seen something like this: > > <Screenshot 2018-12-02 at 15.02.19.png> > > > I looked at it last time and the problem is that one of the dependency hosted on StHub still depends on the StHub version of Cryptography. > > http://smalltalkhub.com/#!/~UdoSchneider/PBKDF2/ <http://smalltalkhub.com/#!/~UdoSchneider/PBKDF2/> > But not many people can write on this project I think. > > > > (And this is a bug) > Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, then save and select âproceedâ. > > That will allow voyage to load properly. > > Cheers, > Esteban > > -- > Cyril Ferlicot > https://ferlicot.fr <https://ferlicot.fr/>

Dec. 2, 2018

Re: [Pharo-users] Voyage

by Cyril Ferlicot

On Sun 2 Dec 2018 at 15:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > There is indeed a problem because cryptography package is still using an > old API: #ifNotNilDo: that does not exists anymore in Pharo. > You are probably seen something like this: > > I looked at it last time and the problem is that one of the dependency hosted on StHub still depends on the StHub version of Cryptography. http://smalltalkhub.com/#!/~UdoSchneider/PBKDF2/ But not many people can write on this project I think. > > (And this is a bug) > Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, > then save and select âproceedâ. > > That will allow voyage to load properly. > > Cheers, > Esteban > > -- Cyril Ferlicot https://ferlicot.fr

Dec. 2, 2018

Re: [Pharo-users] How to take care that the + before a number is ignored

by Benoit St-Jean

Wasn't sure, I'm on Squeak right now!!Â loll ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) On Sunday, December 2, 2018, 6:26:12 a.m. EST, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > On 2 Dec 2018, at 12:14, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-users] How to take care that the + before a number is ignored > Date: 2 December 2018 at 12:14:10 GMT+1 > To: pharo-users(a)lists.pharo.org > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > You can do solve the problem without the "lines" variable but, believe me, you want to keep those lines in a collection.Â It's gonna be a lot easier down the road! > > Hint (to solve the problem) : look at what "lines" contain (instances of which class).Â That class has everything you need to parse those '+2' and '-8' ...Â ;) > > > | fileÂ | > > lines := OrderedCollection new. > > file := StandardFileStream readOnlyFileNamed: 'day.1.input'. That is a deprecated class in Pharo 7. > [file atEnd] whileFalse: [lines add: file nextLine]. > file close. Here is a better way: Array streamContents: [ :lines | Â 'file.log' asFileReference readStreamDo: [ :in | Â Â [ in atEnd ] whileFalse: [ lines nextPut: in nextLine ] ] ] > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) > > > On Sunday, December 2, 2018, 6:09:42 a.m. EST, Roelof Wobben <r.wobben(a)home.nl> wrote: > > > Op 2-12-2018 om 11:55 schreef Benoit St-Jean via Pharo-users: > > Nope, only the part how I can read the file. > > > Roelof > > > >

Dec. 2, 2018

Re: [Pharo-users] How to take care that the + before a number is ignored

by Benoit St-Jean

Exactly! It's easier to manipulate that OrderedCollection that to open/reopen the file.Â It'll be VERY handy for problem #2 where you will need to iterate multiple times on the data!Â ;) ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) On Sunday, December 2, 2018, 7:15:06 a.m. EST, Roelof Wobben <r.wobben(a)home.nl> wrote: Op 2-12-2018 om 12:19 schreef Benoit St-Jean via Pharo-users: oke, and if I understand your code files is then the variable that holds the file. Roelof

Dec. 2, 2018

Re: [Pharo-users] Voyage

by Esteban Lorenzano

There is indeed a problem because cryptography package is still using an old API: #ifNotNilDo: that does not exists anymore in Pharo. You are probably seen something like this: (And this is a bug) Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, then save and select âproceedâ. That will allow voyage to load properly. Cheers, Esteban > On 2 Dec 2018, at 12:39, Sanjay Minni <sm(a)planage.com> wrote: > > I am unable to load Voyage-Mongo and Voyage-Memory in Pharo 7.0.0rC1 > > tried using the scipt below and also thru the Catalog Browser entries for > Voyage > any pointers > > > CyrilFerlicot wrote >> Le 16/11/2018 Ã 02:02, horrido a Ã©crit : >>> I'm trying to load Voyage for MongoDB and I'm having great difficulty. >>> The >>> docs seem to be out of date. >>> >>> What are the current instructions for doing this? >>> >>> The docs also refer to "Configurations Browser" in World Menu/Tools, but >>> there is no longer any such thing. >>> >>> >> >> Hi, >> >> Voyage-Mongo >> >> Metacello new >> repository: 'github://pharo-nosql/voyage/mc'; >> baseline: 'Voyage'; >> onConflictUseIncoming; >> load: 'mongo tests'. >> >> Voyage-UnQLite >> >> Metacello new >> repository: 'github://pharo-nosql/voyage/mc'; >> baseline: 'Voyage'; >> onConflictUseIncoming; >> load: 'unqlite tests'. >> >> Voyage-Memory >> >> Metacello new >> repository: 'github://pharo-nosql/voyage/mc'; >> baseline: 'Voyage'; >> onConflictUseIncoming; >> load: 'memory tests'. >> >> Should work. >> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >> >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> >> >> signature.asc (836 bytes) >> <http://forum.world.st/attachment/5088985/0/signature.asc> > > > > > > ----- > cheers, > Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 2, 2018

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

by Esteban Lorenzano

> On 2 Dec 2018, at 12:00, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 2 Dec 2018, at 11:31, Hilaire <hilaire(a)drgeo.eu> wrote: >> >> Hi Ichi, >> >> If you are learning Pharo I suggest you to not follow this way for now >> as it may result in cognitive overload and frustration. > > Although the workflow described below does indeed work, it > > (1) assumes you already know how to handle a classic VCS on the command line > (2) does not give you elementary diff tools in the IDE that understand your programming language > > So I don't think it is 'the (better) way to go'. > > In my experience, using Iceberg in the image, combined with the GitHub Web UI and the git command line tools, works really well, once you 'get' it. Yes, there is a learning curve as with anything. Yes, as Sven said, Hilaireâs approach can work better for people that already knows Monticello, and because of that they are initially more confortable with it. Today, I would suggest you to start with iceberg: declare your project, add your packages and do commits/pushs from there. Yes, you need some insight of what is git and how it work. But Iâd argue thatâs something you will need with anything :) Esteban > >> If you just want to save your code on some repo, use Metacello to create >> a tonel repository, then do code revision the way you use to do it >> (command line, third party GUI application). >> >> Your workflow will be: >> >> 1. Create a tonel report from Monticello: click on '+Repository' and >> chose tonel://, then select the direcotory in your host to save the code. >> >> 2. On this repo do Add to package to add your code (hope it works in >> released P7, does not on my Pharo7.0-32bit-0c5ade3). >> >> 2. Do the code versioning in the way you use to do it and with the tool >> you want. (git, svn, bzr, CLI, GUI) >> >> 3. Each time you want to save code change, go to Monticello and save >> dirty package >> >> 4. make the commit with your versioning system >> >> Hilaire >> >> >> Le 01/12/2018 Ã 12:10, Ichiseki a Ã©crit : >>> Hi, >>> You are not alone. >>> I have the same impression that Metacello+Git+Iceberg is something very >>> difficult to grasp. >>> It is getting hard to keep the pace with a constant evolving Pharo system. >>> best >>> ichi >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> > >

Dec. 2, 2018