- Pharo-users - lists.pharo.org

Re: [Pharo-users] Loading Glorp+PostgreSQL

by Tim Mackinnon

Hi Sven - my suggestion would be to simply put it on the links TestClass, it's a minor change that preserves your same flow. I had noticed that Stef had a note at this point as he hadn't understood what you were trying to convey, and I think this simply sorts it. I'll try and submit my fork today so you guys can decide. Or you can take the other charges. I don't mind, as it's been a great way to get back into pharo. I just need to get my seaside bit cleared up (which is surprising as I had predicted glorp and Postgres would be the stumbling block) Tim Sent from my iPhone Sent from my iPhone > On 24 May 2017, at 06:22, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 24 May 2017, at 01:36, Tim Mackinnon <tim(a)testit.works> wrote: >> >> I just forked the booklet today and was working through it. I donât know if your changes were already in there, but most things are working for me. I have hit a few typos and inconsistencies that Iâve noted and I would recommend a change to the unit test bit as it feels weird to add a test assert contract method onto the link class (I think its better on the test class). > > The assert is indeed a bit unconventional but as was explained, it is on purpose / by design. That way it can be shared and used in more places (also outside the unit tests). I would try not to change the actual code to keep the documentation in sync (unless really needed). > >> Tim >> >>>> On 17 May 2017, at 19:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> >>>> On 17 May 2017, at 19:35, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>> >>>> 2017-05-17 11:04 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>> >>>>>> On 17 May 2017, at 16:01, Pierce Ng <pierce(a)samadhiweb.com> wrote: >>>>>> >>>>>> On Tue, May 16, 2017 at 11:58:50AM +0200, Sven Van Caekenberghe wrote: >>>>>>> I am bringing my Reddit example back up to date (https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53…) for an upcoming Pharo Booklet. >>>> >>>>>> I've adapted your Reddit application to work with Glorp-SQLite. It was pretty >>>>>> much simply subclassing RedditDatabaseResource and wiring up #newGlorpSession. >>>>>> It's a nice demo of Glorp's pluggability. >>>>> >>>>> That is cool. We should definitively keep a reference to that. Thanks. >>>> >>>> And it's better to get a non devops savvy user to get started, because >>>> it avoids installing a PgSQL server. >>> >>> Yes and no. >>> >>> On macOS, http://postgresapp.com is dead simple for any user. >>> >>>> Regards! >>>> >>>> Esteban A. Maringolo > >

May 24, 2017

Re: [Pharo-users] Loading Glorp+PostgreSQL

by Sven Van Caekenberghe

> On 24 May 2017, at 01:36, Tim Mackinnon <tim(a)testit.works> wrote: > > I just forked the booklet today and was working through it. I donât know if your changes were already in there, but most things are working for me. I have hit a few typos and inconsistencies that Iâve noted and I would recommend a change to the unit test bit as it feels weird to add a test assert contract method onto the link class (I think its better on the test class). The assert is indeed a bit unconventional but as was explained, it is on purpose / by design. That way it can be shared and used in more places (also outside the unit tests). I would try not to change the actual code to keep the documentation in sync (unless really needed). > Tim > >> On 17 May 2017, at 19:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 17 May 2017, at 19:35, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>> 2017-05-17 11:04 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>>> On 17 May 2017, at 16:01, Pierce Ng <pierce(a)samadhiweb.com> wrote: >>>>> >>>>> On Tue, May 16, 2017 at 11:58:50AM +0200, Sven Van Caekenberghe wrote: >>>>>> I am bringing my Reddit example back up to date (https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53…) for an upcoming Pharo Booklet. >>> >>>>> I've adapted your Reddit application to work with Glorp-SQLite. It was pretty >>>>> much simply subclassing RedditDatabaseResource and wiring up #newGlorpSession. >>>>> It's a nice demo of Glorp's pluggability. >>>> >>>> That is cool. We should definitively keep a reference to that. Thanks. >>> >>> And it's better to get a non devops savvy user to get started, because >>> it avoids installing a PgSQL server. >> >> Yes and no. >> >> On macOS, http://postgresapp.com is dead simple for any user. >> >>> Regards! >>> >>> Esteban A. Maringolo >

May 24, 2017

Re: [Pharo-users] Loading Glorp+PostgreSQL

by Tim Mackinnon

I just forked the booklet today and was working through it. I donât know if your changes were already in there, but most things are working for me. I have hit a few typos and inconsistencies that Iâve noted and I would recommend a change to the unit test bit as it feels weird to add a test assert contract method onto the link class (I think its better on the test class). Tim > On 17 May 2017, at 19:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 17 May 2017, at 19:35, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >> 2017-05-17 11:04 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>>> On 17 May 2017, at 16:01, Pierce Ng <pierce(a)samadhiweb.com> wrote: >>>> >>>> On Tue, May 16, 2017 at 11:58:50AM +0200, Sven Van Caekenberghe wrote: >>>>> I am bringing my Reddit example back up to date (https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53…) for an upcoming Pharo Booklet. >> >>>> I've adapted your Reddit application to work with Glorp-SQLite. It was pretty >>>> much simply subclassing RedditDatabaseResource and wiring up #newGlorpSession. >>>> It's a nice demo of Glorp's pluggability. >>> >>> That is cool. We should definitively keep a reference to that. Thanks. >> >> And it's better to get a non devops savvy user to get started, because >> it avoids installing a PgSQL server. > > Yes and no. > > On macOS, http://postgresapp.com <http://postgresapp.com/> is dead simple for any user. > >> Regards! >> >> Esteban A. Maringolo

May 23, 2017

Re: [Pharo-users] How to use uFFI with String

by horrido

Je comprends enfin... I accidentally came across a StackOverflow answer that suggested the String object is immutable. That makes perfect sense, as I know the C function is actually /*trying*/ to write to the buffer. That gave me the idea to use a ByteArray instead. Now, everything works! horrido wrote > There is shockingly very little documentation on how to use uFFI. In > particular, I have the following situation... > > A shared C lib has the following function: > > void get_machine(char *machine) { > uname(&uname_s); > strcpy(machine, uname_s.machine); > } > > It copies the content of a string value into the buffer passed to it (char > *machine). > > I want to call this function from Pharo, thus: > > buffer := String new: 64. > self ffiCall: #( void get_machine(String buffer) ). > > The buffer never receives the string value (it just contains the 64 > initiialized spaces). > > Clearly, I'm misunderstanding the proper mechanism for doing this. > > [There are other functions in the shared C lib that work fine, such as: > > uint get_uptime() { > sysinfo(&info); > return info.uptime; > } > > Returning integers or floats is no problem. But passing arguments by > reference seems to be verboten.] -- View this message in context: http://forum.world.st/How-to-use-uFFI-with-String-tp4947890p4948144.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 23, 2017

Re: [Pharo-users] Renamed instance attribute by code

by Hilaire

Indeed. Not so funnily, it breaks the class definition of those using traits :( Don't know why. Hilaire Le 23/05/2017 Ã 16:11, HernÃ¡n Morales Durand a Ã©crit : > > (RBRenameInstanceVariableRefactoring > rename: 'oldName' > to: 'newName' > in: MyClass) execute > > 2017-05-23 10:50 GMT-03:00 Hilaire > <hilaire(a)drgeo.eu > <mailto:hilaire@drgeo.eu>>: > > Hello, > > This does not work: > > RBRenameInstanceVariableRefactoring > > rename: 'oldName' > > to: 'newName' > > in: MyClass > -- Dr. Geo http://drgeo.eu

May 23, 2017

Any implementation of GPG for Pharo?

by Casimiro de Almeida Barreto - GMAIL

Good morning, Is there any working implementation of PGP/GNUPG functionality in Pharo. There are some tools for squeak but IÂ´m not sure if they are maintained. Also need password parsing (both Windows and Linux environments). Best regards, Casimiro Barreto

May 23, 2017

Re: [Pharo-users] How to use uFFI with String

by Pierce Ng

On Mon, May 22, 2017 at 01:42:50PM -0700, horrido wrote: > buffer := String new: 64. > self ffiCall: #( void get_machine(String buffer) ). > > The buffer never receives the string value (it just contains the 64 > initiialized spaces). See FFICalloutAPITests>>testPrintString. HTH. Pierce

May 23, 2017

Re: [Pharo-users] Renamed instance attribute by code

by HernÃ¡n Morales Durand

(RBRenameInstanceVariableRefactoring rename: 'oldName' to: 'newName' in: MyClass) execute 2017-05-23 10:50 GMT-03:00 Hilaire <hilaire(a)drgeo.eu>: > Hello, > > This does not work: > > RBRenameInstanceVariableRefactoring > > rename: 'oldName' > > to: 'newName' > > in: MyClass > > > Hilaire > > >

May 23, 2017

Renamed instance attribute by code

by Hilaire

Hello, This does not work: RBRenameInstanceVariableRefactoring rename: 'oldName' to: 'newName' in: MyClass Hilaire

May 23, 2017

Re: [Pharo-users] SquareBracket Associate github org ownership

by Serge Stinckwich

Maybe not everyone need to be owner, but everyone in the org need to be able to commit to all repositories I guess. Having per-repositories policy is a bit annoying. On Tue, May 23, 2017 at 12:30 PM, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > Should I revert everyone to read-only and add people on specific repos? > > On 22 May 2017 at 20:23, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Yes I changed because we should clean from time to time. >> >> On Mon, May 22, 2017 at 9:55 AM, Serge Stinckwich >> <serge.stinckwich(a)gmail.com> wrote: >>> >>> Thank you Damien. Works now ! >>> >>> On Mon, May 22, 2017 at 9:41 AM, Damien Pollet >>> <damien.pollet+pharo(a)gmail.com> wrote: >>> > Should be fixed; there are no per-repo permissions but the default for >>> > all >>> > members changed somehow. >>> > >>> > On 22 May 2017 at 05:35, Serge Stinckwich <serge.stinckwich(a)gmail.com> >>> > wrote: >>> >> >>> >> Dear all, >>> >> >>> >> who is in charge of SquareBracket Associate github org ? I can't >>> >> commit anymore on : >>> >> https://github.com/SquareBracketAssociates/NumericalMethods >>> >> >>> >> Maybe I was owner before and no more now. >>> >> Can someone can change my ownership ? >>> >> Thank you. >>> >> Regards, >>> >> >>> >> -- >>> >> Serge Stinckwich >>> >> UCN & UMI UMMISCO 209 (IRD/UPMC) >>> >> Every DSL ends up being Smalltalk >>> >> http://www.doesnotunderstand.org/ >>> >> >>> > >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UCN & UMI UMMISCO 209 (IRD/UPMC) >>> Every DSL ends up being Smalltalk >>> http://www.doesnotunderstand.org/ >>> >> > -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 23, 2017