July 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Voyage] #selectOne: and #selectMany: with a block as the argument

by Bernat Romagosa

Hi Esteban, I installed MongoQueries-NicolasPetton.6, but I did it manually, should I have used some Monticello configuration perhaps? Thanks! 2013/7/4 Esteban Lorenzano <estebanlm(a)gmail.com> > Hi :) > > can you check if you have the "MongoQueries" package installed? > > cheers, > Esteban > > ps: please notice that in anycase you will not be able to execute > > [ :each | each name first = $X ] > > because the MongoQueries package just translates the block into a > mongo-query which is a dictionary (a JSON expression). But you will found > some ways to help you, some special keywords like #in: and #where: (you can > see how they work in the tests) > > > > On Jul 4, 2013, at 2:17 PM, Bernat Romagosa < > tibabenfortlapalanca(a)gmail.com> wrote: > > Hi! > > I realize probably only Esteban will be able to answer, but I prefer to > write to the list so the mail is logged and other people can benefit from > it. > > I'm trying to use blocks as arguments for #*selectOne:* and #*selectMany:*, > but it doesn't seem to work. Here's my code: > > MyClass selectOne: { #name -> 'Some name' } asDictionary. > MyClass selectOne: [ :each | each name = 'Some name' ]. > > > The first one works, but the second one raises a *VOMongoConnectionError* > . > > Also: > > MyClass selectMany: { #name -> 'Some name' } asDictionary. > MyClass selectMany: [ :each | each name = 'Some name' ]. > > > The first does work, the second one doesn't, which prevents me from > writing more useful stuff like: > > MyClass selectMany: [ :each | each name first = $P ]. > > Any idea why this could be failing? I've the latest stable version loaded > via: > > Gofer it > url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; > package: 'ConfigurationOfVoyageMongo'; > load. > (Smalltalk at: #ConfigurationOfVoyageMongo) load. > > Thanks! :) > > Bernat. > > -- > Bernat Romagosa. > > > -- Bernat Romagosa.

July 4, 2013

Re: [Pharo-users] [Voyage] #selectOne: and #selectMany: with a block as the argument

by Esteban Lorenzano

Hi :) can you check if you have the "MongoQueries" package installed? cheers, Esteban ps: please notice that in anycase you will not be able to execute [ :each | each name first = $X ] because the MongoQueries package just translates the block into a mongo-query which is a dictionary (a JSON expression). But you will found some ways to help you, some special keywords like #in: and #where: (you can see how they work in the tests) On Jul 4, 2013, at 2:17 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > Hi! > > I realize probably only Esteban will be able to answer, but I prefer to write to the list so the mail is logged and other people can benefit from it. > > I'm trying to use blocks as arguments for #selectOne: and #selectMany:, but it doesn't seem to work. Here's my code: > > MyClass selectOne: { #name -> 'Some name' } asDictionary. > MyClass selectOne: [ :each | each name = 'Some name' ]. > > The first one works, but the second one raises a VOMongoConnectionError. > > Also: > > MyClass selectMany: { #name -> 'Some name' } asDictionary. > MyClass selectMany: [ :each | each name = 'Some name' ]. > > The first does work, the second one doesn't, which prevents me from writing more useful stuff like: > > MyClass selectMany: [ :each | each name first = $P ]. > > Any idea why this could be failing? I've the latest stable version loaded via: > > Gofer it > url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; > package: 'ConfigurationOfVoyageMongo'; > load. > (Smalltalk at: #ConfigurationOfVoyageMongo) load. > > Thanks! :) > > Bernat. > > -- > Bernat Romagosa.

July 4, 2013

[Voyage] #selectOne: and #selectMany: with a block as the argument

by Bernat Romagosa

Hi! I realize probably only Esteban will be able to answer, but I prefer to write to the list so the mail is logged and other people can benefit from it. I'm trying to use blocks as arguments for #*selectOne:* and #*selectMany:*, but it doesn't seem to work. Here's my code: MyClass selectOne: { #name -> 'Some name' } asDictionary. MyClass selectOne: [ :each | each name = 'Some name' ]. The first one works, but the second one raises a *VOMongoConnectionError*. Also: MyClass selectMany: { #name -> 'Some name' } asDictionary. MyClass selectMany: [ :each | each name = 'Some name' ]. The first does work, the second one doesn't, which prevents me from writing more useful stuff like: MyClass selectMany: [ :each | each name first = $P ]. Any idea why this could be failing? I've the latest stable version loaded via: Gofer it url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; package: 'ConfigurationOfVoyageMongo'; load. (Smalltalk at: #ConfigurationOfVoyageMongo) load. Thanks! :) Bernat. -- Bernat Romagosa.

July 4, 2013

Re: [Pharo-users] Pharo 2.0 and ODBC

by Stephan Eggermont

Good to see it working. Where do I find the announcements of changes to the VM? In Pharo-Dev there are the nice mails by Marcus for the image changes. Stephan

July 4, 2013

Re: [Pharo-users] Pharo 2.0 and ODBC

by Friedrich Dominicus

StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> writes: > Thanks for your feedback. > We would love to provide a better infrastructure. It just takes time. Well I remember Matinez writing about hacking the vm. Something about how to debug the VM and libraries and FFI, would have helped me (I guess) I'm not that afraid of C but at the edge between Pharo Smalltalk and C libraries ... Well I guess that simple is not something for the faint of heart ;-) Regards Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

July 4, 2013

Re: [Pharo-users] Pharo 2.0 and ODBC

by StÃ©phane Ducasse

Thanks for your feedback. We would love to provide a better infrastructure. It just takes time. Stef On Jul 4, 2013, at 12:02 PM, Friedrich Dominicus <frido(a)q-software-solutions.de> wrote: > To everyone intersted/involved. I downloaded a new virtual machine today > and the same code which has crashed the virtual machine, simply works on > the new Virtual machine. The machine I'm using is: > 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 31 2013 > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 31 2013 > git://gitorious.org/cogvm/blessed.git Commit: 0f562e0afe14e533470278943b5d65d42ea133c2 Date: 2013-05-30 16:38:08 +0200 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14595 > ' > > So well it seems it was not my 32-bit libraries but something broken > withing Pharo and/or the FFI area. I'm sorry, but I do not know the > changes applied to my last used VirtualMachine > > Anyway i can use the ODBC stuff from withing Pharo on my Linux box now > to access an .mdb file > > Regards > Friedrich > > -- > Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim > Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus >

July 4, 2013

Re: [Pharo-users] Pharo 2.0 and ODBC

by Friedrich Dominicus

To everyone intersted/involved. I downloaded a new virtual machine today and the same code which has crashed the virtual machine, simply works on the new Virtual machine. The machine I'm using is: 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 31 2013 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 31 2013 git://gitorious.org/cogvm/blessed.git Commit: 0f562e0afe14e533470278943b5d65d42ea133c2 Date: 2013-05-30 16:38:08 +0200 By: Igor Stasenko <siguctua(a)gmail.com> Jenkins build #14595 ' So well it seems it was not my 32-bit libraries but something broken withing Pharo and/or the FFI area. I'm sorry, but I do not know the changes applied to my last used VirtualMachine Anyway i can use the ODBC stuff from withing Pharo on my Linux box now to access an .mdb file Regards Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

July 4, 2013

Re: [Pharo-users] documentation for refactoring tools in Pharo 2

by StÃ©phane Ducasse

On Jul 4, 2013, at 12:04 AM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Is there any documentation on the changes between 1.4 and 2 for the > refactoring tools? Or how to use them effectively to refactor code? > > I'm familiar with Lukas Renggli's writing on them and used them > regularly in 1.4. > > I'm just trying to use the RBParseTreeRewriter from within a workspace > but with it limited to a package or class heirarchy. Normally nothing change. In addition gisela is working on a new tool to help us as well as a documentation. > > Thanks > > Paul >

July 4, 2013

Re: [Pharo-users] Another 32-bit on a 64 bit machine question.

by Friedrich Dominicus

Mariano Martinez Peck <marianopeck(a)gmail.com> writes: > Yes, there was an old SerialPlugin bug which I think it was reported > byÂ Friedrich DominicusÂ himself...but I am not sure if it was > integrated. Sorry for the noise but there still is a problem in the code. At least here I can show you: sp := SerialPort new. sp openPort: '/dev/ttyUSB0' SerialPort(Object)>>error: SerialPort>>openPort: UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: SmalltalkEditor>>evaluateSelectionAndDo: in Block: [rcvr class evaluatorClass new... but sp := SerialPort new. sp openPort: '/dev//ttyUSB0' works !!! Two / instead of just one I've not the slightes idea on why two slashes are needed. I just found out by accident. Can anyone confirm that? Regards Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

July 4, 2013

Re: [Pharo-users] documentation for refactoring tools in Pharo 2

by Marcus Denker

On Jul 4, 2013, at 12:04 AM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Is there any documentation on the changes between 1.4 and 2 for the > refactoring tools? Or how to use them effectively to refactor code? > > I'm familiar with Lukas Renggli's writing on them and used them > regularly in 1.4. > > I'm just trying to use the RBParseTreeRewriter from within a workspace > but with it limited to a package or class hierarchy. > There should be no changes on that level. The difference just is that we use another UI. Marcus

July 4, 2013