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

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