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

Re: [Pharo-users] Question about dynamic spec

by StÃ©phane Ducasse

Ben I'm still fuzzy after a flood in the flat we rent at 2 in the morning :) but I was thinking that may be we can use this example to explain the dynamic part of spec. So can you take this view also when you look at the code? If this sounds good to you, I will put on the stack that I should look and see how to put it in the Spec chapter. Stef On Jul 8, 2013, at 11:05 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > I've implemented a small UI using the dynamic features of spec and I'd like to know if there isn't a better way to do it. My use case is simple: I have a normal ComposableModel that has two models - a list and a DynamicComposableModel. The DynamicComposableModel should contain a list of buttons that should change every time the user selects an element in the list. I've implemented a demo that can be seen if you download the package DynamicSpec-Examples from http://www.smalltalkhub.com/mc/AndreiChis/Playground/main and execute the code from the class comment of DSChangingButtons. > > My problem is that the widget containing the buttons has to define a spec layout on the class side. I haven't found a way to tell the spec layout to add a widget and use a method on the object for constructing the layout. I've manage to get away by dynamically reconstructing the layout when the selection changes, however it's not that nice because I had to duplicate the layout of the main widget both on the class side and the object side. It would be nice to add a widget to the layout like this: 'aSpec dynamicAdd: modelGetter withSpec: aSymbol ' that would call aSymbol on the object and not on the class. This may or may not make sense :) > > To be concrete, the method DSToolbarModel>>updateButtons will call the method dynamicLayout on it's parent which in turn will call dynamicLayoutWithSpec: on the toolbar. I'd like to avoid this, and when specifying the layout of the parent widget to call a method on the instance side of it subwidgets to get their layout. > > Now I'll end here this rather long email :) > > Cheers, > Andrei

July 9, 2013

Re: [Pharo-users] More than 500MB for windows

by Igor Stasenko

On 8 July 2013 22:43, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Igor, please get this point of view out of your system :). > > First, not all programming languages are like this: You can easily run other VMs (e.g., Java) with more than 3 GB. But, let's not even go there: I can run Pharo with 1Gb on Mac without problems. According to your reasoning we might end up downgrading the Mac VM. Some data does not fit in memory, but if I can get all my data in my image, I will choose to do it. > > I am not saying that we should compare with Java, or that it is the end of the world that the Windows VM is highly restricted. I am simply saying that we should not dismiss this as a problem just because we do not know how, or do not have the resources to solve it right now. > > After all, we are here to change the world :). > Yes, but this topic was raised multiple times already. Maybe we should stop wasting time on it? All you need to do, to change the limit, go to platforms/win32/vm/sqWin32Alloc.h And change this: #ifndef MAX_VIRTUAL_MEMORY #define MAX_VIRTUAL_MEMORY 512*1024*1024 #endif So, if you want more, build VM with any limit you see fit. But there's a reason why in official VM its 512. > Cheers, > Doru -- Best regards, Igor Stasenko.

July 9, 2013

Re: [Pharo-users] Question about dynamic spec

by Andrei Vasile Chis

> It's a bit late today, so I will have a look tomorrow :) > > (If I forget, feel free to insult me ^^) > There's no rush :) Andrei > > I've implemented a small UI using the dynamic features of spec and I'd > like to know if there isn't a better way to do it. My use case is simple: I > have a normal ComposableModel that has two models - a list and > a DynamicComposableModel. The DynamicComposableModel should contain a list > of buttons that should change every time the user selects an element in the > list. I've implemented a demo that can be seen if you download the package > DynamicSpec-Examples from > http://www.smalltalkhub.com/mc/AndreiChis/Playground/main and execute the > code from the class comment of DSChangingButtons. > > My problem is that the widget containing the buttons has to define a spec > layout on the class side. I haven't found a way to tell the spec layout to > add a widget and use a method on the object for constructing the layout. > I've manage to get away by dynamically reconstructing the layout when the > selection changes, however it's not that nice because I had to duplicate > the layout of the main widget both on the class side and the object side. > It would be nice to add a widget to the layout like this: 'aSpec > dynamicAdd: modelGetter withSpec: aSymbol ' that would call aSymbol on the > object and not on the class. This may or may not make sense :) > > To be concrete, the method DSToolbarModel>>updateButtons will call the > method dynamicLayout on it's parent which in turn will > call dynamicLayoutWithSpec: on the toolbar. I'd like to avoid this, and > when specifying the layout of the parent widget to call a method on the > instance side of it subwidgets to get their layout. > > Now I'll end here this rather long email :) > > Cheers, > Andrei > > >

July 8, 2013

Re: [Pharo-users] Question about dynamic spec

by Benjamin

It's a bit late today, so I will have a look tomorrow :) (If I forget, feel free to insult me ^^) Ben On Jul 8, 2013, at 11:05 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > I've implemented a small UI using the dynamic features of spec and I'd like to know if there isn't a better way to do it. My use case is simple: I have a normal ComposableModel that has two models - a list and a DynamicComposableModel. The DynamicComposableModel should contain a list of buttons that should change every time the user selects an element in the list. I've implemented a demo that can be seen if you download the package DynamicSpec-Examples from http://www.smalltalkhub.com/mc/AndreiChis/Playground/main and execute the code from the class comment of DSChangingButtons. > > My problem is that the widget containing the buttons has to define a spec layout on the class side. I haven't found a way to tell the spec layout to add a widget and use a method on the object for constructing the layout. I've manage to get away by dynamically reconstructing the layout when the selection changes, however it's not that nice because I had to duplicate the layout of the main widget both on the class side and the object side. It would be nice to add a widget to the layout like this: 'aSpec dynamicAdd: modelGetter withSpec: aSymbol ' that would call aSymbol on the object and not on the class. This may or may not make sense :) > > To be concrete, the method DSToolbarModel>>updateButtons will call the method dynamicLayout on it's parent which in turn will call dynamicLayoutWithSpec: on the toolbar. I'd like to avoid this, and when specifying the layout of the parent widget to call a method on the instance side of it subwidgets to get their layout. > > Now I'll end here this rather long email :) > > Cheers, > Andrei

July 8, 2013

Question about dynamic spec

by Andrei Vasile Chis

Hi, I've implemented a small UI using the dynamic features of spec and I'd like to know if there isn't a better way to do it. My use case is simple: I have a normal ComposableModel that has two models - a list and a DynamicComposableModel. The DynamicComposableModel should contain a list of buttons that should change every time the user selects an element in the list. I've implemented a demo that can be seen if you download the package DynamicSpec-Examples from http://www.smalltalkhub.com/mc/AndreiChis/Playground/main and execute the code from the class comment of DSChangingButtons. My problem is that the widget containing the buttons has to define a spec layout on the class side. I haven't found a way to tell the spec layout to add a widget and use a method on the object for constructing the layout. I've manage to get away by dynamically reconstructing the layout when the selection changes, however it's not that nice because I had to duplicate the layout of the main widget both on the class side and the object side. It would be nice to add a widget to the layout like this: 'aSpec dynamicAdd: modelGetter withSpec: aSymbol ' that would call aSymbol on the object and not on the class. This may or may not make sense :) To be concrete, the method DSToolbarModel>>updateButtons will call the method dynamicLayout on it's parent which in turn will call dynamicLayoutWithSpec: on the toolbar. I'd like to avoid this, and when specifying the layout of the parent widget to call a method on the instance side of it subwidgets to get their layout. Now I'll end here this rather long email :) Cheers, Andrei

July 8, 2013

Re: [Pharo-users] [ANN] Pharo Launcher

by Tudor Girba

Hi Damien, Nice :). I noticed two issues when playing with it: - there is no feedback while downloading the image. This can be confusing. - the launcher quits when launching another image (I am on Mac). This is actually interesting, but it was surprising. I am not sure what is the right solution here. And a question: How can we get more images available through this interface? Cheers, Doru On Jul 8, 2013, at 10:11 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Dear list, > > Erwan and I are proud to announce the first release of the Pharo > Launcher, a cross-platform application that > > - lets you manage your Pharo images (launch, rename, copy and delete); > - lets you download image templates (i.e., zip archives) from many > different sources (Jenkins, files.pharo.org, and your local cache); > - lets you create new images from any template. > > A screenshot is attached to this email. > > The idea behind the Pharo Launcher is that you should be able to > access it very rapidly from your OS application launcher. As a result, > launching any image is never more than 3 clicks away. > > Download: https://ci.inria.fr/pharo-contribution/job/PharoLauncher/PHARO=30,VERSION=b… > > Please report bugs on the 'Launcher' project at https://pharo.fogbugz.org > > You can contribute to this project. All classes and most methods are > commented. There are unit tests. Please contribute! > > Source code: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher > CI: https://ci.inria.fr/pharo-contribution/job/PharoLauncher > > Things you can do to improve the system: > > - check if a template is already downloaded before downloading it > - add a preference mechanism (for, e.g., quit after launch, definition > of your own template groups, location of downloaded templates and > images) > - put the launcher in the Pharo Ubuntu package so that the launcher > becomes a registered appliation of the system > (https://launchpad.net/~pharo/+archive/stable) > - make sure the pharo launcher does not load your personal scripts > (like fonts and MC configuration) > - add a toolbar to enhance the discoverability of the features > (currently everything is in contextual menus) > - make sure rename and copy actions propose default values > - make sure no debugger pops up when a user press cancels or enter an > invalid name > - propose multiple kinds of sorting (last used, most frequently used, > alphabetically on the name) > - give some information about each template (build date, pharo version) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > <screenshot.png> -- www.tudorgirba.com "To utilize feedback, you first have to acquire it."

July 8, 2013

Re: [Pharo-users] More than 500MB for windows

by Mariano Martinez Peck

I am with Doru here. Today, 500MB is NOTHINGGGGGG. NOTHIIIIIIIIING. NOTHING. A LATOP comes with 8GB. 16x more than the max the VM can allocate. For one of my clients, I have just set up a server with 32GB. It has 64x than the max a Pharo VM can allocate. Really? Going to disk is not always a possibility for many many reasons. And even if it were possible....if I have to spent XXX hours to workaround Pharo because it cannot use more than 500MB, then people will simply move to another language. And finally, wasn't a language like Smalltalk prepare for you and let you only focus in your app blah blah blah.. ? having to go to disk doesn't sound like that... So, Igor, I cannot stand that point of view. I can stand many others, like explaining why it's not Pharo fault, the problem window has, the money/time it would take for an engineer to fix it, etc etc etc. But not your position. Cheers, On Mon, Jul 8, 2013 at 5:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Igor, please get this point of view out of your system :). > > First, not all programming languages are like this: You can easily run > other VMs (e.g., Java) with more than 3 GB. But, let's not even go there: I > can run Pharo with 1Gb on Mac without problems. According to your reasoning > we might end up downgrading the Mac VM. Some data does not fit in memory, > but if I can get all my data in my image, I will choose to do it. > > I am not saying that we should compare with Java, or that it is the end of > the world that the Windows VM is highly restricted. I am simply saying that > we should not dismiss this as a problem just because we do not know how, or > do not have the resources to solve it right now. > > After all, we are here to change the world :). > > Cheers, > Doru > > > On Jul 8, 2013, at 4:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > Same question again. And same answer (i have no other yet). > > > > Why just don't use disk memory? > > I know it is extra effort, but that's what all software does, when it > has to deal with big amounts of data. > > Why in smalltalk it should be different? > > > > Of course, on your place, i would also prefer that there is some magic > fairy waves its magic wand and problem solved, but it is not going to be > solved. > > If today you need >512Mb for your data, tomorrow you will need twice as > much, and after tomorrow it will double again. > > So, let us be realistic: the solution to your problem lies not in VM, > but in a way how to manage the data. > > > > -- > > Best regards, > > Igor Stasenko. > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > > -- Mariano http://marianopeck.wordpress.com

July 8, 2013

Re: [Pharo-users] More than 500MB for windows

by Tudor Girba

Hi, Igor, please get this point of view out of your system :). First, not all programming languages are like this: You can easily run other VMs (e.g., Java) with more than 3 GB. But, let's not even go there: I can run Pharo with 1Gb on Mac without problems. According to your reasoning we might end up downgrading the Mac VM. Some data does not fit in memory, but if I can get all my data in my image, I will choose to do it. I am not saying that we should compare with Java, or that it is the end of the world that the Windows VM is highly restricted. I am simply saying that we should not dismiss this as a problem just because we do not know how, or do not have the resources to solve it right now. After all, we are here to change the world :). Cheers, Doru On Jul 8, 2013, at 4:50 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Same question again. And same answer (i have no other yet). > > Why just don't use disk memory? > I know it is extra effort, but that's what all software does, when it has to deal with big amounts of data. > Why in smalltalk it should be different? > > Of course, on your place, i would also prefer that there is some magic fairy waves its magic wand and problem solved, but it is not going to be solved. > If today you need >512Mb for your data, tomorrow you will need twice as much, and after tomorrow it will double again. > So, let us be realistic: the solution to your problem lies not in VM, but in a way how to manage the data. > > -- > Best regards, > Igor Stasenko. -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

July 8, 2013

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

by StÃ©phane Ducasse

estebanS could you do me one favor: build a kind of list of questions and answers so that I can add that to the voyage chapter? Else I will do it but â¦ Stef On Jul 8, 2013, at 2:38 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > But, as far as I know, Mongo will create an _id key with an Mongo OID > for every document that doesn't have one. > You can use _id without having to use an OID, you can use plain > strings or integers. > > So I guess it is safe to use _id. I'll change it in my tests and then > let you know. > > :) > Esteban A. Maringolo > > > 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >> Because _id is internally used by mongo and I didn't wanted to risk any collision :) >> >> On Jul 8, 2013, at 2:26 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: >> >>> Esteban, >>> >>> Why do you use __id: (double underscore) instead of the _id (single >>> underscore) key? >>> >>> Regards, >>> Esteban A. Maringolo >>> >>> >>> 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> Hi again, >>>> >>>> sadly, there is no direct support for referenced queries yet. >>>> >>>> however, you can workaround the problem by doing: >>>> >>>> >>>> { >>>> 'referenceField.__id' -> (VORepository current keyOf: referenceObject) >>>> } asDictionary. >>>> >>>> or with MongoQueries: >>>> >>>> [ :each | (each at: 'referenceField.__id') = (VORepository current keyOf: >>>> referenceObject) ] >>>> >>>> Some internal info: >>>> in Voyage, all references are kept in mongo as sub-documents with this >>>> structure: >>>> >>>> { >>>> '__id': OID(1234567890). >>>> '#collection': 'theNameOfTheCollection'. >>>> } >>>> >>>> so, you always can construct queries knowing that :) >>>> >>>> Esteban >>>> >>>> On Jul 8, 2013, at 12:58 PM, Bernat Romagosa >>>> <tibabenfortlapalanca(a)gmail.com> wrote: >>>> >>>> Also, how does one query a referenced object? >>>> >>>> MyClass selectMany: { 'project.name' -> 'Test' } asDictionary. "<-- Works >>>> only if project is an embedded object, but it doesn't if it's a reference." >>>> >>>> >>>> 2013/7/8 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>>>> >>>>> Sorry for being lazy, but how does one use logical operators in dictionary >>>>> queries? >>>>> >>>>> I'm trying something like: >>>>> >>>>> (User selectMany: { 'profile.firstName' -> { '$regex' -> '^.*na.*'. >>>>> '$options' -> 'i'} asDictionary } asDictionary). >>>>> >>>>> And I'd like to $or this with: >>>>> >>>>> 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} >>>>> asDictionary. >>>>> >>>>> >>>>> 2013/7/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>>> >>>>>> >>>>>> On Jul 6, 2013, at 11:16 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> sure :) >>>>>>> >>>>>>> I will add a blog post on "voyage advanced queries" too :) >>>>>> >>>>>> too if you want but we could also focus on the chapter because we can be >>>>>> multiple people to edit it >>>>>> while your blog you are alone. >>>>>> >>>>>> Stef >>>>>> >>>>>>> >>>>>>> Esteban >>>>>>> >>>>>>> On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse >>>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>> >>>>>>>> esteban could you take some time to add this information to the Voyage >>>>>>>> chapter? >>>>>>>> >>>>>>>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ >>>>>>>> >>>>>>>> add the information in any format and I can make it run. >>>>>>>> >>>>>>>> >>>>>>>> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> you have different constructions: >>>>>>>>> >>>>>>>>> { $gt: { "number_field": 42 } } >>>>>>>>> >>>>>>>>> and so on... always with dictionaries (bah, json structs). >>>>>>>>> >>>>>>>>> as a query language it kinda sucks... but well... is how it is :) >>>>>>>>> >>>>>>>>> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse >>>>>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>>>> >>>>>>>>>> Ok but how do I map conceptual a query to a dictionary >>>>>>>>>> >>>>>>>>>> Do I guess right that there is an exact match >>>>>>>>>> >>>>>>>>>> selectOne: { id -> 10} asDictionary >>>>>>>>>> >>>>>>>>>> will match id = 10 >>>>>>>>>> >>>>>>>>>> Now we can only do exact mathc? >>>>>>>>>> >>>>>>>>>> name matches: 'stef*' >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo >>>>>>>>>> <emaringolo(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Stef, >>>>>>>>>>> >>>>>>>>>>> You're asking the other Esteban, but having used Voyage and Mongo I >>>>>>>>>>> think I can answer this. >>>>>>>>>>> >>>>>>>>>>> Mongo receives a JSON object to do all the query filtering. For a >>>>>>>>>>> simple lookup it is has a simple structre, as the query gets more >>>>>>>>>>> complex it gets esoteric as well (with "special" MongoDB keys in >>>>>>>>>>> the >>>>>>>>>>> format of "$key"). >>>>>>>>>>> >>>>>>>>>>> Because the simplest map we have to a JSON Object is the >>>>>>>>>>> Dictionary, I >>>>>>>>>>> guess that's why it ends up being converted to a Dictionary, which >>>>>>>>>>> in >>>>>>>>>>> turn gets converted to JSON and/or BSON. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> Esteban A. Maringolo >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>>>>>>>> >>>>>>>>>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano >>>>>>>>>>>> <estebanlm(a)gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> 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) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> esteban >>>>>>>>>>>> how a dictionary is used to work as a block for a query? >>>>>>>>>>>> Can you explain because I would have thought that the first line >>>>>>>>>>>> did not >>>>>>>>>>>> work and the second would work. >>>>>>>>>>>> >>>>>>>>>>>> Stef >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 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. >>>> >>>> >>>> >>>> >>>> -- >>>> Bernat Romagosa. >>>> >>>> >>> >> >> >

July 8, 2013

Re: [Pharo-users] [ANN] Pharo Launcher

by StÃ©phane Ducasse

Thanks! I have to try :) Stef On Jul 8, 2013, at 10:11 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Dear list, > > Erwan and I are proud to announce the first release of the Pharo > Launcher, a cross-platform application that > > - lets you manage your Pharo images (launch, rename, copy and delete); > - lets you download image templates (i.e., zip archives) from many > different sources (Jenkins, files.pharo.org, and your local cache); > - lets you create new images from any template. > > A screenshot is attached to this email. > > The idea behind the Pharo Launcher is that you should be able to > access it very rapidly from your OS application launcher. As a result, > launching any image is never more than 3 clicks away. > > Download: https://ci.inria.fr/pharo-contribution/job/PharoLauncher/PHARO=30,VERSION=b… > > Please report bugs on the 'Launcher' project at https://pharo.fogbugz.org > > You can contribute to this project. All classes and most methods are > commented. There are unit tests. Please contribute! > > Source code: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher > CI: https://ci.inria.fr/pharo-contribution/job/PharoLauncher > > Things you can do to improve the system: > > - check if a template is already downloaded before downloading it > - add a preference mechanism (for, e.g., quit after launch, definition > of your own template groups, location of downloaded templates and > images) > - put the launcher in the Pharo Ubuntu package so that the launcher > becomes a registered appliation of the system > (https://launchpad.net/~pharo/+archive/stable) > - make sure the pharo launcher does not load your personal scripts > (like fonts and MC configuration) > - add a toolbar to enhance the discoverability of the features > (currently everything is in contextual menus) > - make sure rename and copy actions propose default values > - make sure no debugger pops up when a user press cancels or enter an > invalid name > - propose multiple kinds of sorting (last used, most frequently used, > alphabetically on the name) > - give some information about each template (build date, pharo version) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > <screenshot.png>

July 8, 2013

Re: [Pharo-users] NeoCSV on Pharo 1.4 - codepoint MNU?

by phil＠highoctane.be

Thanks Stephan. --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Featured on the Software Process and Measurement Cast http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Mon, Jul 8, 2013 at 5:48 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Some snippets of a working glamour application loading excel files (Moose > 4.8) > MNU on SmallInteger could be a broken VM > > A separate class to represent the csv file, storing the rows: > > ANExcelModel >> on: aFilename > ^self new > rows: (NeoCSVReader on: (FileSystem root / aFilename) > readStream) upToEnd ; > yourself > > The domain model has an announcer letting the browser know when something > changed > > AModel>loadFrom: aFileName > |excel regel | > excel := ANExcelModel on: aFileName . > excel rows allButFirstDo: [ :row | > regel := ANRegel new. > regel thema: (self findIn: row at: 1 key: #thema). > regel onderwerp: (self findIn: row at: 3 key: #onderwerp). > regel addTo: self. > ]. > self announce: ANChanged > > > ANModel>announce: anAnnouncement > ^self announcer announce: anAnnouncement > > > Part of the browser construction, loading a file: > > browser transmit to: #thema; andShow: [ :a | > a list > title: 'Themas'; > display: [ (self model dimensies at: #thema) items > ]; > updateOn: SVChanged from: SVModel default > announcer; > act: [ : b | self loadExcel ] entitled: 'Laad csv'; > selectionAct: [ :list | > self addOnderwerpTo: list selection] > on: $o > entitled: 'Voeg onderwerp toe'. > a text > title: '?'; > display: [ self helpThema ]. > ]. > > > ANBrowser>loadExcel > |excel| > excel := MorphicUIManager new chooseFullFileName: 'Selecteer een > .csv bestand' extensions: nil path: nil preview: nil. > > excel isEmptyOrNil ifFalse:[ > self model loadFrom: excel] > >

July 8, 2013

Re: [Pharo-users] NeoCSV on Pharo 1.4 - codepoint MNU?

by Stephan Eggermont

Some snippets of a working glamour application loading excel files (Moose 4.8) MNU on SmallInteger could be a broken VM A separate class to represent the csv file, storing the rows: ANExcelModel >> on: aFilename ^self new rows: (NeoCSVReader on: (FileSystem root / aFilename) readStream) upToEnd ; yourself The domain model has an announcer letting the browser know when something changed AModel>loadFrom: aFileName |excel regel | excel := ANExcelModel on: aFileName . excel rows allButFirstDo: [ :row | regel := ANRegel new. regel thema: (self findIn: row at: 1 key: #thema). regel onderwerp: (self findIn: row at: 3 key: #onderwerp). regel addTo: self. ]. self announce: ANChanged ANModel>announce: anAnnouncement ^self announcer announce: anAnnouncement Part of the browser construction, loading a file: browser transmit to: #thema; andShow: [ :a | a list title: 'Themas'; display: [ (self model dimensies at: #thema) items ]; updateOn: SVChanged from: SVModel default announcer; act: [ : b | self loadExcel ] entitled: 'Laad csv'; selectionAct: [ :list | self addOnderwerpTo: list selection] on: $o entitled: 'Voeg onderwerp toe'. a text title: '?'; display: [ self helpThema ]. ]. ANBrowser>loadExcel |excel| excel := MorphicUIManager new chooseFullFileName: 'Selecteer een .csv bestand' extensions: nil path: nil preview: nil. excel isEmptyOrNil ifFalse:[ self model loadFrom: excel]

July 8, 2013

Re: [Pharo-users] More than 500MB for windows

by Igor Stasenko

Same question again. And same answer (i have no other yet). Why just don't use disk memory? I know it is extra effort, but that's what all software does, when it has to deal with big amounts of data. Why in smalltalk it should be different? Of course, on your place, i would also prefer that there is some magic fairy waves its magic wand and problem solved, but it is not going to be solved. If today you need >512Mb for your data, tomorrow you will need twice as much, and after tomorrow it will double again. So, let us be realistic: the solution to your problem lies not in VM, but in a way how to manage the data. -- Best regards, Igor Stasenko.

July 8, 2013

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

by Esteban Lorenzano

no, don't do it regular _id are taken as usual. __id fields are references to another collection documents inside one document (something that mongo does not have by itself). And I like like that :) Esteban On Jul 8, 2013, at 2:38 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > But, as far as I know, Mongo will create an _id key with an Mongo OID > for every document that doesn't have one. > You can use _id without having to use an OID, you can use plain > strings or integers. > > So I guess it is safe to use _id. I'll change it in my tests and then > let you know. > > :) > Esteban A. Maringolo > > > 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >> Because _id is internally used by mongo and I didn't wanted to risk any collision :) >> >> On Jul 8, 2013, at 2:26 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: >> >>> Esteban, >>> >>> Why do you use __id: (double underscore) instead of the _id (single >>> underscore) key? >>> >>> Regards, >>> Esteban A. Maringolo >>> >>> >>> 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> Hi again, >>>> >>>> sadly, there is no direct support for referenced queries yet. >>>> >>>> however, you can workaround the problem by doing: >>>> >>>> >>>> { >>>> 'referenceField.__id' -> (VORepository current keyOf: referenceObject) >>>> } asDictionary. >>>> >>>> or with MongoQueries: >>>> >>>> [ :each | (each at: 'referenceField.__id') = (VORepository current keyOf: >>>> referenceObject) ] >>>> >>>> Some internal info: >>>> in Voyage, all references are kept in mongo as sub-documents with this >>>> structure: >>>> >>>> { >>>> '__id': OID(1234567890). >>>> '#collection': 'theNameOfTheCollection'. >>>> } >>>> >>>> so, you always can construct queries knowing that :) >>>> >>>> Esteban >>>> >>>> On Jul 8, 2013, at 12:58 PM, Bernat Romagosa >>>> <tibabenfortlapalanca(a)gmail.com> wrote: >>>> >>>> Also, how does one query a referenced object? >>>> >>>> MyClass selectMany: { 'project.name' -> 'Test' } asDictionary. "<-- Works >>>> only if project is an embedded object, but it doesn't if it's a reference." >>>> >>>> >>>> 2013/7/8 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>>>> >>>>> Sorry for being lazy, but how does one use logical operators in dictionary >>>>> queries? >>>>> >>>>> I'm trying something like: >>>>> >>>>> (User selectMany: { 'profile.firstName' -> { '$regex' -> '^.*na.*'. >>>>> '$options' -> 'i'} asDictionary } asDictionary). >>>>> >>>>> And I'd like to $or this with: >>>>> >>>>> 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} >>>>> asDictionary. >>>>> >>>>> >>>>> 2013/7/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>>> >>>>>> >>>>>> On Jul 6, 2013, at 11:16 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> sure :) >>>>>>> >>>>>>> I will add a blog post on "voyage advanced queries" too :) >>>>>> >>>>>> too if you want but we could also focus on the chapter because we can be >>>>>> multiple people to edit it >>>>>> while your blog you are alone. >>>>>> >>>>>> Stef >>>>>> >>>>>>> >>>>>>> Esteban >>>>>>> >>>>>>> On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse >>>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>> >>>>>>>> esteban could you take some time to add this information to the Voyage >>>>>>>> chapter? >>>>>>>> >>>>>>>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ >>>>>>>> >>>>>>>> add the information in any format and I can make it run. >>>>>>>> >>>>>>>> >>>>>>>> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> you have different constructions: >>>>>>>>> >>>>>>>>> { $gt: { "number_field": 42 } } >>>>>>>>> >>>>>>>>> and so on... always with dictionaries (bah, json structs). >>>>>>>>> >>>>>>>>> as a query language it kinda sucks... but well... is how it is :) >>>>>>>>> >>>>>>>>> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse >>>>>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>>>> >>>>>>>>>> Ok but how do I map conceptual a query to a dictionary >>>>>>>>>> >>>>>>>>>> Do I guess right that there is an exact match >>>>>>>>>> >>>>>>>>>> selectOne: { id -> 10} asDictionary >>>>>>>>>> >>>>>>>>>> will match id = 10 >>>>>>>>>> >>>>>>>>>> Now we can only do exact mathc? >>>>>>>>>> >>>>>>>>>> name matches: 'stef*' >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo >>>>>>>>>> <emaringolo(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Stef, >>>>>>>>>>> >>>>>>>>>>> You're asking the other Esteban, but having used Voyage and Mongo I >>>>>>>>>>> think I can answer this. >>>>>>>>>>> >>>>>>>>>>> Mongo receives a JSON object to do all the query filtering. For a >>>>>>>>>>> simple lookup it is has a simple structre, as the query gets more >>>>>>>>>>> complex it gets esoteric as well (with "special" MongoDB keys in >>>>>>>>>>> the >>>>>>>>>>> format of "$key"). >>>>>>>>>>> >>>>>>>>>>> Because the simplest map we have to a JSON Object is the >>>>>>>>>>> Dictionary, I >>>>>>>>>>> guess that's why it ends up being converted to a Dictionary, which >>>>>>>>>>> in >>>>>>>>>>> turn gets converted to JSON and/or BSON. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> Esteban A. Maringolo >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>>>>>>>> >>>>>>>>>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano >>>>>>>>>>>> <estebanlm(a)gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> 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) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> esteban >>>>>>>>>>>> how a dictionary is used to work as a block for a query? >>>>>>>>>>>> Can you explain because I would have thought that the first line >>>>>>>>>>>> did not >>>>>>>>>>>> work and the second would work. >>>>>>>>>>>> >>>>>>>>>>>> Stef >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 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. >>>> >>>> >>>> >>>> >>>> -- >>>> Bernat Romagosa. >>>> >>>> >>> >> >> >

July 8, 2013

Re: [Pharo-users] [Pharo-dev] MongoTalk: new place on smalltalkhub

by Nicolas Petton

nice! Nico On Jul 8, 2013, at 2:45 PM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Hi, > > I've just created a new team for MongoTalk on SmalltalkHub: > > http://www.smalltalkhub.com/#!/~MongoTalkTeam > > The old repo (http://www.smalltalkhub.com/#!/~francois/MongoTalk) will stay just in case some scripts rely on it but you should update to the new repo: > > http://www.smalltalkhub.com/#!/~MongoTalkTeam/mongotalk > > I've created a version 1.5.1 in the Metacello configuration to reflect the repo migration. > Shout at me if I missed something! > > Cheers, > Fa > > (Many thanks to Norbert for pushing the migration ;) -- Nicolas Petton http://www.nicolas-petton.fr

July 8, 2013

Re: [Pharo-users] NeoCSV on Pharo 1.4 - codepoint MNU?

by Sven Van Caekenberghe

On 08 Jul 2013, at 15:02, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Maybe I'm just doing something silly (like reading binary instead of text). I vaguely remember FileSystem doing something weird like that long ago, maybe in 1.4. In any case, 'file.csv' asFileReference readStream gives a character stream, if you want a binary one, you have to convert explicitly, using #binary. Was there already FileSystem in 1.4 ?

July 8, 2013

Re: [Pharo-users] NeoCSV on Pharo 1.4 - codepoint MNU?

by phil＠highoctane.be

It works now. Looks like that: 1- I needed to do an asString on the content being read. (I'd like to know how to read a text file this way - as a text file) 2- as my separator was $;, not specifying one led NeoCSVReader to fail for some strange reason (it should have given me a single field and values in an array, which it didn't). allObjects | stream reader contents | stream := self allObjectsDataFile asFileReference readStream. contents := stream contents asString. stream close. reader := NeoCSVReader on: contents readStream. reader separator: $;. reader upToEnd.

July 8, 2013

Re: [Pharo-users] NeoCSV on Pharo 1.4 - codepoint MNU?

by phil＠highoctane.be

It complains with a DNU on a SmallInteger codepoint, not a Character. I'll look further. Maybe I'm just doing something silly (like reading binary instead of text). allObjects | stream reader | stream := self allObjectsDataFile asFileReference readStream. reader := NeoCSVReader on: stream. reader upToEnd. allObjectsDataFile ^ self dataLocation / 'Application profile_XXX-AllObjects.csv' dataLocation ^'/Users/philippeback/Documents/HomeHighOctane/Projects_Customers/XXX/Work/Task-StudyAsIs' asPath. Phil On Mon, Jul 8, 2013 at 2:56 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Phil, > > On 08 Jul 2013, at 14:39, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > > > Hello, > > > > I am currently working with a dataset in CSV format and am trying to > load it in to Moose for visualizations with Mondrian. > > > > Now, I am facing an issue with NeoCSV. > > > > I loaded the Configuration in Moose without trouble. > > > > Now, when loading my file, I do get a MNU with SmallInteger codepoint > > > > Is this a Moose issue or a NeoCSV issue ? > > > > I've tried to comment out the codepoint message to see where this was > going but to no avail. > > As far as I know Character>>#codePoint is a standard message, it is in 2.0 > and 3.0, I just checked. Do not tell me you are working in an even older > image ;-) > > #asciiValue would be an alternative I guess > > Sven > > > Clues? > > > > TIA > > > > Phil > > <PharoScreenshot.2.png><PharoScreenshot.1.png> > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > > >

July 8, 2013

Re: [Pharo-users] NeoCSV on Pharo 1.4 - codepoint MNU?

by Sven Van Caekenberghe

Phil, On 08 Jul 2013, at 14:39, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Hello, > > I am currently working with a dataset in CSV format and am trying to load it in to Moose for visualizations with Mondrian. > > Now, I am facing an issue with NeoCSV. > > I loaded the Configuration in Moose without trouble. > > Now, when loading my file, I do get a MNU with SmallInteger codepoint > > Is this a Moose issue or a NeoCSV issue ? > > I've tried to comment out the codepoint message to see where this was going but to no avail. As far as I know Character>>#codePoint is a standard message, it is in 2.0 and 3.0, I just checked. Do not tell me you are working in an even older image ;-) #asciiValue would be an alternative I guess Sven > Clues? > > TIA > > Phil > <PharoScreenshot.2.png><PharoScreenshot.1.png> -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

July 8, 2013

MongoTalk: new place on smalltalkhub

by FranÃ§ois Stephany

Hi, I've just created a new team for MongoTalk on SmalltalkHub: http://www.smalltalkhub.com/#!/~MongoTalkTeam The old repo (http://www.smalltalkhub.com/#!/~francois/MongoTalk) will stay just in case some scripts rely on it but you should update to the new repo: http://www.smalltalkhub.com/#!/~MongoTalkTeam/mongotalk I've created a version 1.5.1 in the Metacello configuration to reflect the repo migration. Shout at me if I missed something! Cheers, Fa (Many thanks to Norbert for pushing the migration ;)

July 8, 2013

NeoCSV on Pharo 1.4 - codepoint MNU?

by phil＠highoctane.be

Hello, I am currently working with a dataset in CSV format and am trying to load it in to Moose for visualizations with Mondrian. Now, I am facing an issue with NeoCSV. I loaded the Configuration in Moose without trouble. Now, when loading my file, I do get a MNU with SmallInteger codepoint Is this a Moose issue or a NeoCSV issue ? I've tried to comment out the codepoint message to see where this was going but to no avail. Clues? TIA Phil [image: Inline image 2][image: Inline image 1]

July 8, 2013

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

by Esteban A. Maringolo

But, as far as I know, Mongo will create an _id key with an Mongo OID for every document that doesn't have one. You can use _id without having to use an OID, you can use plain strings or integers. So I guess it is safe to use _id. I'll change it in my tests and then let you know. :) Esteban A. Maringolo 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: > Because _id is internally used by mongo and I didn't wanted to risk any collision :) > > On Jul 8, 2013, at 2:26 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > >> Esteban, >> >> Why do you use __id: (double underscore) instead of the _id (single >> underscore) key? >> >> Regards, >> Esteban A. Maringolo >> >> >> 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> Hi again, >>> >>> sadly, there is no direct support for referenced queries yet. >>> >>> however, you can workaround the problem by doing: >>> >>> >>> { >>> 'referenceField.__id' -> (VORepository current keyOf: referenceObject) >>> } asDictionary. >>> >>> or with MongoQueries: >>> >>> [ :each | (each at: 'referenceField.__id') = (VORepository current keyOf: >>> referenceObject) ] >>> >>> Some internal info: >>> in Voyage, all references are kept in mongo as sub-documents with this >>> structure: >>> >>> { >>> '__id': OID(1234567890). >>> '#collection': 'theNameOfTheCollection'. >>> } >>> >>> so, you always can construct queries knowing that :) >>> >>> Esteban >>> >>> On Jul 8, 2013, at 12:58 PM, Bernat Romagosa >>> <tibabenfortlapalanca(a)gmail.com> wrote: >>> >>> Also, how does one query a referenced object? >>> >>> MyClass selectMany: { 'project.name' -> 'Test' } asDictionary. "<-- Works >>> only if project is an embedded object, but it doesn't if it's a reference." >>> >>> >>> 2013/7/8 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>>> >>>> Sorry for being lazy, but how does one use logical operators in dictionary >>>> queries? >>>> >>>> I'm trying something like: >>>> >>>> (User selectMany: { 'profile.firstName' -> { '$regex' -> '^.*na.*'. >>>> '$options' -> 'i'} asDictionary } asDictionary). >>>> >>>> And I'd like to $or this with: >>>> >>>> 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} >>>> asDictionary. >>>> >>>> >>>> 2013/7/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> >>>>> >>>>> On Jul 6, 2013, at 11:16 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>> wrote: >>>>> >>>>>> sure :) >>>>>> >>>>>> I will add a blog post on "voyage advanced queries" too :) >>>>> >>>>> too if you want but we could also focus on the chapter because we can be >>>>> multiple people to edit it >>>>> while your blog you are alone. >>>>> >>>>> Stef >>>>> >>>>>> >>>>>> Esteban >>>>>> >>>>>> On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse >>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>> >>>>>>> esteban could you take some time to add this information to the Voyage >>>>>>> chapter? >>>>>>> >>>>>>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ >>>>>>> >>>>>>> add the information in any format and I can make it run. >>>>>>> >>>>>>> >>>>>>> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> you have different constructions: >>>>>>>> >>>>>>>> { $gt: { "number_field": 42 } } >>>>>>>> >>>>>>>> and so on... always with dictionaries (bah, json structs). >>>>>>>> >>>>>>>> as a query language it kinda sucks... but well... is how it is :) >>>>>>>> >>>>>>>> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse >>>>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>>> >>>>>>>>> Ok but how do I map conceptual a query to a dictionary >>>>>>>>> >>>>>>>>> Do I guess right that there is an exact match >>>>>>>>> >>>>>>>>> selectOne: { id -> 10} asDictionary >>>>>>>>> >>>>>>>>> will match id = 10 >>>>>>>>> >>>>>>>>> Now we can only do exact mathc? >>>>>>>>> >>>>>>>>> name matches: 'stef*' >>>>>>>>> >>>>>>>>> >>>>>>>>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo >>>>>>>>> <emaringolo(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Stef, >>>>>>>>>> >>>>>>>>>> You're asking the other Esteban, but having used Voyage and Mongo I >>>>>>>>>> think I can answer this. >>>>>>>>>> >>>>>>>>>> Mongo receives a JSON object to do all the query filtering. For a >>>>>>>>>> simple lookup it is has a simple structre, as the query gets more >>>>>>>>>> complex it gets esoteric as well (with "special" MongoDB keys in >>>>>>>>>> the >>>>>>>>>> format of "$key"). >>>>>>>>>> >>>>>>>>>> Because the simplest map we have to a JSON Object is the >>>>>>>>>> Dictionary, I >>>>>>>>>> guess that's why it ends up being converted to a Dictionary, which >>>>>>>>>> in >>>>>>>>>> turn gets converted to JSON and/or BSON. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Esteban A. Maringolo >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>>>>>>> >>>>>>>>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano >>>>>>>>>>> <estebanlm(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>> 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) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> esteban >>>>>>>>>>> how a dictionary is used to work as a block for a query? >>>>>>>>>>> Can you explain because I would have thought that the first line >>>>>>>>>>> did not >>>>>>>>>>> work and the second would work. >>>>>>>>>>> >>>>>>>>>>> Stef >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 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. >>> >>> >>> >>> >>> -- >>> Bernat Romagosa. >>> >>> >> > >

July 8, 2013

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

by Esteban Lorenzano

Because _id is internally used by mongo and I didn't wanted to risk any collision :) On Jul 8, 2013, at 2:26 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > Esteban, > > Why do you use __id: (double underscore) instead of the _id (single > underscore) key? > > Regards, > Esteban A. Maringolo > > > 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >> Hi again, >> >> sadly, there is no direct support for referenced queries yet. >> >> however, you can workaround the problem by doing: >> >> >> { >> 'referenceField.__id' -> (VORepository current keyOf: referenceObject) >> } asDictionary. >> >> or with MongoQueries: >> >> [ :each | (each at: 'referenceField.__id') = (VORepository current keyOf: >> referenceObject) ] >> >> Some internal info: >> in Voyage, all references are kept in mongo as sub-documents with this >> structure: >> >> { >> '__id': OID(1234567890). >> '#collection': 'theNameOfTheCollection'. >> } >> >> so, you always can construct queries knowing that :) >> >> Esteban >> >> On Jul 8, 2013, at 12:58 PM, Bernat Romagosa >> <tibabenfortlapalanca(a)gmail.com> wrote: >> >> Also, how does one query a referenced object? >> >> MyClass selectMany: { 'project.name' -> 'Test' } asDictionary. "<-- Works >> only if project is an embedded object, but it doesn't if it's a reference." >> >> >> 2013/7/8 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>> >>> Sorry for being lazy, but how does one use logical operators in dictionary >>> queries? >>> >>> I'm trying something like: >>> >>> (User selectMany: { 'profile.firstName' -> { '$regex' -> '^.*na.*'. >>> '$options' -> 'i'} asDictionary } asDictionary). >>> >>> And I'd like to $or this with: >>> >>> 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} >>> asDictionary. >>> >>> >>> 2013/7/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> >>>> >>>> On Jul 6, 2013, at 11:16 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>> wrote: >>>> >>>>> sure :) >>>>> >>>>> I will add a blog post on "voyage advanced queries" too :) >>>> >>>> too if you want but we could also focus on the chapter because we can be >>>> multiple people to edit it >>>> while your blog you are alone. >>>> >>>> Stef >>>> >>>>> >>>>> Esteban >>>>> >>>>> On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> >>>>>> esteban could you take some time to add this information to the Voyage >>>>>> chapter? >>>>>> >>>>>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ >>>>>> >>>>>> add the information in any format and I can make it run. >>>>>> >>>>>> >>>>>> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> you have different constructions: >>>>>>> >>>>>>> { $gt: { "number_field": 42 } } >>>>>>> >>>>>>> and so on... always with dictionaries (bah, json structs). >>>>>>> >>>>>>> as a query language it kinda sucks... but well... is how it is :) >>>>>>> >>>>>>> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse >>>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>> >>>>>>>> Ok but how do I map conceptual a query to a dictionary >>>>>>>> >>>>>>>> Do I guess right that there is an exact match >>>>>>>> >>>>>>>> selectOne: { id -> 10} asDictionary >>>>>>>> >>>>>>>> will match id = 10 >>>>>>>> >>>>>>>> Now we can only do exact mathc? >>>>>>>> >>>>>>>> name matches: 'stef*' >>>>>>>> >>>>>>>> >>>>>>>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo >>>>>>>> <emaringolo(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Stef, >>>>>>>>> >>>>>>>>> You're asking the other Esteban, but having used Voyage and Mongo I >>>>>>>>> think I can answer this. >>>>>>>>> >>>>>>>>> Mongo receives a JSON object to do all the query filtering. For a >>>>>>>>> simple lookup it is has a simple structre, as the query gets more >>>>>>>>> complex it gets esoteric as well (with "special" MongoDB keys in >>>>>>>>> the >>>>>>>>> format of "$key"). >>>>>>>>> >>>>>>>>> Because the simplest map we have to a JSON Object is the >>>>>>>>> Dictionary, I >>>>>>>>> guess that's why it ends up being converted to a Dictionary, which >>>>>>>>> in >>>>>>>>> turn gets converted to JSON and/or BSON. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Esteban A. Maringolo >>>>>>>>> >>>>>>>>> >>>>>>>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>>>>>> >>>>>>>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano >>>>>>>>>> <estebanlm(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>> 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) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> esteban >>>>>>>>>> how a dictionary is used to work as a block for a query? >>>>>>>>>> Can you explain because I would have thought that the first line >>>>>>>>>> did not >>>>>>>>>> work and the second would work. >>>>>>>>>> >>>>>>>>>> Stef >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 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. >> >> >> >> >> -- >> Bernat Romagosa. >> >> >

July 8, 2013

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

by Esteban Lorenzano

your query is almost fine: the unique problem is with the argument for the $or expression, which should not be another dictionary but a collection: { '$or' -> (Array with: 'profile.firstName' -> { '$regex' -> '^.*na.*'. '$options' -> 'i'} asDictionary with: 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} asDictionary) } asDictionary. On Jul 8, 2013, at 2:16 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > Thanks! The reference thing is exactly what I needed :) > > However, I'm not managing very well with the $or query... how would one add a regex in there? > > I've tried: > > User selectMany: > { > '$or' -> > { > 'profile.firstName' -> { '$regex' -> '^.*na.*'. '$options' -> 'i'} asDictionary. > 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} asDictionary. > } asDictionary > } asDictionary. > > But it's obviously wrong... :( > > > 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com> > Hi, > > something like this: > > { > '$or'-> { > { $field1 -> value1 } asDictionary. "expression 1" > { $field2 -> value2 } asDictionary. "expression 2" > ... > { $fieldN -> valueN } asDictionary. "expression N" > } > } asDictionary > > cheers, > Esteban > > On Jul 8, 2013, at 12:16 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > >> Sorry for being lazy, but how does one use logical operators in dictionary queries? >> >> I'm trying something like: >> >> (User selectMany: { 'profile.firstName' -> { '$regex' -> '^.*na.*'. '$options' -> 'i'} asDictionary } asDictionary). >> >> And I'd like to $or this with: >> >> 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} asDictionary. >> >> >> 2013/7/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >> On Jul 6, 2013, at 11:16 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> > sure :) >> > >> > I will add a blog post on "voyage advanced queries" too :) >> >> too if you want but we could also focus on the chapter because we can be multiple people to edit it >> while your blog you are alone. >> >> Stef >> >> > >> > Esteban >> > >> > On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> > >> >> esteban could you take some time to add this information to the Voyage chapter? >> >> >> >> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ >> >> >> >> add the information in any format and I can make it run. >> >> >> >> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english >> >> >> >> Stef >> >> >> >> >> >> >> >> On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> >>> you have different constructions: >> >>> >> >>> { $gt: { "number_field": 42 } } >> >>> >> >>> and so on... always with dictionaries (bah, json structs). >> >>> >> >>> as a query language it kinda sucks... but well... is how it is :) >> >>> >> >>> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> >> >>>> Ok but how do I map conceptual a query to a dictionary >> >>>> >> >>>> Do I guess right that there is an exact match >> >>>> >> >>>> selectOne: { id -> 10} asDictionary >> >>>> >> >>>> will match id = 10 >> >>>> >> >>>> Now we can only do exact mathc? >> >>>> >> >>>> name matches: 'stef*' >> >>>> >> >>>> >> >>>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>>> >> >>>>> Stef, >> >>>>> >> >>>>> You're asking the other Esteban, but having used Voyage and Mongo I >> >>>>> think I can answer this. >> >>>>> >> >>>>> Mongo receives a JSON object to do all the query filtering. For a >> >>>>> simple lookup it is has a simple structre, as the query gets more >> >>>>> complex it gets esoteric as well (with "special" MongoDB keys in the >> >>>>> format of "$key"). >> >>>>> >> >>>>> Because the simplest map we have to a JSON Object is the Dictionary, I >> >>>>> guess that's why it ends up being converted to a Dictionary, which in >> >>>>> turn gets converted to JSON and/or BSON. >> >>>>> >> >>>>> Regards, >> >>>>> >> >>>>> Esteban A. Maringolo >> >>>>> >> >>>>> >> >>>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>>>>> >> >>>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>>>>> >> >>>>>> 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) >> >>>>>> >> >>>>>> >> >>>>>> esteban >> >>>>>> how a dictionary is used to work as a block for a query? >> >>>>>> Can you explain because I would have thought that the first line did not >> >>>>>> work and the second would work. >> >>>>>> >> >>>>>> Stef >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> 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. > > > > > -- > Bernat Romagosa.

July 8, 2013

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

by Esteban A. Maringolo

Esteban, Why do you use __id: (double underscore) instead of the _id (single underscore) key? Regards, Esteban A. Maringolo 2013/7/8 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi again, > > sadly, there is no direct support for referenced queries yet. > > however, you can workaround the problem by doing: > > > { > 'referenceField.__id' -> (VORepository current keyOf: referenceObject) > } asDictionary. > > or with MongoQueries: > > [ :each | (each at: 'referenceField.__id') = (VORepository current keyOf: > referenceObject) ] > > Some internal info: > in Voyage, all references are kept in mongo as sub-documents with this > structure: > > { > '__id': OID(1234567890). > '#collection': 'theNameOfTheCollection'. > } > > so, you always can construct queries knowing that :) > > Esteban > > On Jul 8, 2013, at 12:58 PM, Bernat Romagosa > <tibabenfortlapalanca(a)gmail.com> wrote: > > Also, how does one query a referenced object? > > MyClass selectMany: { 'project.name' -> 'Test' } asDictionary. "<-- Works > only if project is an embedded object, but it doesn't if it's a reference." > > > 2013/7/8 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >> >> Sorry for being lazy, but how does one use logical operators in dictionary >> queries? >> >> I'm trying something like: >> >> (User selectMany: { 'profile.firstName' -> { '$regex' -> '^.*na.*'. >> '$options' -> 'i'} asDictionary } asDictionary). >> >> And I'd like to $or this with: >> >> 'profile.surname' -> { '$regex' -> '^.*ve.*'. '$options' -> 'i'} >> asDictionary. >> >> >> 2013/7/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> >>> >>> On Jul 6, 2013, at 11:16 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >>> wrote: >>> >>> > sure :) >>> > >>> > I will add a blog post on "voyage advanced queries" too :) >>> >>> too if you want but we could also focus on the chapter because we can be >>> multiple people to edit it >>> while your blog you are alone. >>> >>> Stef >>> >>> > >>> > Esteban >>> > >>> > On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse >>> > <stephane.ducasse(a)inria.fr> wrote: >>> > >>> >> esteban could you take some time to add this information to the Voyage >>> >> chapter? >>> >> >>> >> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ >>> >> >>> >> add the information in any format and I can make it run. >>> >> >>> >> >>> >> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english >>> >> >>> >> Stef >>> >> >>> >> >>> >> >>> >> On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >>> >> wrote: >>> >> >>> >>> you have different constructions: >>> >>> >>> >>> { $gt: { "number_field": 42 } } >>> >>> >>> >>> and so on... always with dictionaries (bah, json structs). >>> >>> >>> >>> as a query language it kinda sucks... but well... is how it is :) >>> >>> >>> >>> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse >>> >>> <stephane.ducasse(a)inria.fr> wrote: >>> >>> >>> >>>> Ok but how do I map conceptual a query to a dictionary >>> >>>> >>> >>>> Do I guess right that there is an exact match >>> >>>> >>> >>>> selectOne: { id -> 10} asDictionary >>> >>>> >>> >>>> will match id = 10 >>> >>>> >>> >>>> Now we can only do exact mathc? >>> >>>> >>> >>>> name matches: 'stef*' >>> >>>> >>> >>>> >>> >>>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo >>> >>>> <emaringolo(a)gmail.com> wrote: >>> >>>> >>> >>>>> Stef, >>> >>>>> >>> >>>>> You're asking the other Esteban, but having used Voyage and Mongo I >>> >>>>> think I can answer this. >>> >>>>> >>> >>>>> Mongo receives a JSON object to do all the query filtering. For a >>> >>>>> simple lookup it is has a simple structre, as the query gets more >>> >>>>> complex it gets esoteric as well (with "special" MongoDB keys in >>> >>>>> the >>> >>>>> format of "$key"). >>> >>>>> >>> >>>>> Because the simplest map we have to a JSON Object is the >>> >>>>> Dictionary, I >>> >>>>> guess that's why it ends up being converted to a Dictionary, which >>> >>>>> in >>> >>>>> turn gets converted to JSON and/or BSON. >>> >>>>> >>> >>>>> Regards, >>> >>>>> >>> >>>>> Esteban A. Maringolo >>> >>>>> >>> >>>>> >>> >>>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> >>>>>> >>> >>>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano >>> >>>>>> <estebanlm(a)gmail.com> wrote: >>> >>>>>> >>> >>>>>> 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) >>> >>>>>> >>> >>>>>> >>> >>>>>> esteban >>> >>>>>> how a dictionary is used to work as a block for a query? >>> >>>>>> Can you explain because I would have thought that the first line >>> >>>>>> did not >>> >>>>>> work and the second would work. >>> >>>>>> >>> >>>>>> Stef >>> >>>>>> >>> >>>>>> >>> >>>>>> >>> >>>>>> >>> >>>>>> 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. > > > > > -- > Bernat Romagosa. > >

July 8, 2013