- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Territorial

by H. Hirzel

On 9/6/16, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 06/09/16 06:24, HernÃ¡n Morales Durand wrote: >> >> I am happy to announce the release of Territorial, a new Smalltalk >> library for Geographical Information Retrieval in geopolitical objects. > > Nice. Please tell us about your license choice - https://github.com/hernanmd/Territorial - documentation includes as well a license at the end. > Stephan > > > >

Sept. 6, 2016

Re: [Pharo-users] [ANN] Territorial

by Serge Stinckwich

On Tue, Sep 6, 2016 at 6:24 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > I am happy to announce the release of Territorial, a new Smalltalk library > for Geographical Information Retrieval in geopolitical objects. Great ! At the moment, I don't have immediate needs of this but this might change in the future. > Blog post with details: > http://80738163270632.blogspot.com/2016/08/territorial.html The link does not work, apparently the correct link is : http://80738163270632.blogspot.fr/2016/09/territorial.html > User Manual: http://bit.ly/2c4RrCJ Nice documentation ! I see you are using github. Try to setup a CI job and maybe put your code also on github. Ask me if you need help. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 6, 2016

Re: [Pharo-users] [ANN] Territorial

by Stephan Eggermont

On 06/09/16 06:24, HernÃ¡n Morales Durand wrote: > > I am happy to announce the release of Territorial, a new Smalltalk > library for Geographical Information Retrieval in geopolitical objects. Nice. Please tell us about your license choice Stephan

Sept. 6, 2016

Re: [Pharo-users] [ANN] Territorial

by Sven Van Caekenberghe

Wow ! > On 06 Sep 2016, at 06:24, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > I am happy to announce the release of Territorial, a new Smalltalk library for Geographical Information Retrieval in geopolitical objects. > > Blog post with details: http://80738163270632.blogspot.com/2016/08/territorial.html > > User Manual: http://bit.ly/2c4RrCJ > > If you like it or have comments, different usage scenarios, improvement ideas, collaboration opportunities, etc. please don't hesitate to contact me. I hope you find it useful. > > Regards, > > HernÃ¡n >

Sept. 6, 2016

[ANN] Territorial

by HernÃ¡n Morales Durand

I am happy to announce the release of Territorial, a new Smalltalk library for Geographical Information Retrieval in geopolitical objects. Blog post with details: http://80738163270632.blogspot .com/2016/08/territorial.html User Manual: http://bit.ly/2c4RrCJ If you like it or have comments, different usage scenarios, improvement ideas, collaboration opportunities, etc. please don't hesitate to contact me. I hope you find it useful. Regards, HernÃ¡n

Sept. 6, 2016

Re: [Pharo-users] difficult to kill objects - pesky hanging pointersTo

by Ben Coman

Ohhh... nice... shiny... That is much easier to remember. Thanks Andres. cheers -ben On Tue, Sep 6, 2016 at 5:21 AM, Andres Valloud <avalloud(a)smalltalk.comcastbiz.net> wrote: > So why doesn't two-way become: help, e.g. > > ClassOfObjectsThatMustDie allInstances first become: String new > > As soon as that do-it unwinds there won't be any references to what the new > string became (the new string wasn't referenced further), so... > > > On 9/5/16 8:50 , Ben Coman wrote: >> >> Sometimes its *really* hard to kill some objects. It seems that >> inspecting a list of pointersTo creates additional hanging references. >> This was frustrating me just now, so I finally hacked a way forward. >> Sharing it in case its useful to others, and also I can find it again >> searching the list. This needs to run for each object. >> >> Smalltalk garbageCollect. >> target := ClassOfObjectsThatMustDie allInstances first. >> SystemNavigation default allObjectsDo: [ :e | >> (e isKindOf: Association) ifTrue: [ e value = target ifTrue: [ e >> value: nil ] ]. >> (e isKindOf: Array) ifTrue: [ 1 to: e size do: [ :i | (e at: i) = >> target ifTrue: [ e at: i put: nil ] ] ] >> ]. >> target := nil. >> Smalltalk garbageCollect. >> >> cheers -ben >> >> >

Sept. 6, 2016

Re: [Pharo-users] PunQlite problems

by PBKResearch

Hi - just tried a further experiment, with more mysterious results. I created a database in memory with a subset of my data. This time the program will retrieve the values as well as the keys. However, the value presented is just the first 1024 bytes, i.e. the first buffer full. In addition, in the majority of cases the correct bytes are each followed by three zero bytes, e.g. the data begins: 3C 00 00 00 68 00 00 00 74 00 00 00 6D 00 00 00 6C 00 00 00 20 00 00 00 63 00 00 00 6C 00 00 00 Rather than the expected: 3C 68 74 6D 6C 20 63 6C. This affects 75 of the 88 cases in my trial database. I presume the insertion of the zero bytes took place in the writing stage, but I have no idea what is going on. Are there any known problems with PunQLite on pharo 5? Hello I am using Moose 6.0 (Pharo 5.0 Latest update: #50761) on Windows 10. I have installed PunQLite following the instructions in https://github.com/mumez/PunQLite. I have run all the examples that involve using files, and everything seems OK. I have tried creating a database using my own data, which seemed to run OK. The database will display its keys successfully, but whenever I try to retrieve a value I get PqFetchError. The debug information shows that an ffi fetch operation has given a return value of -10. I have searched for any information on unQLite return codes, but so far I have nothing. I tried the PqDatabaseBrowser in the Tools section. This recognised the database, opened it and displayed all the keys correctly. However, clicking on any key gave the same PqFetchError. Does anyone have any idea of what I have done wrong? Thanks for any help. Peter Kenny

Sept. 5, 2016

PunQlite problems

by PBKResearch

Hello I am using Moose 6.0 (Pharo 5.0 Latest update: #50761) on Windows 10. I have installed PunQLite following the instructions in https://github.com/mumez/PunQLite. I have run all the examples that involve using files, and everything seems OK. I have tried creating a database using my own data, which seemed to run OK. The database will display its keys successfully, but whenever I try to retrieve a value I get PqFetchError. The debug information shows that an ffi fetch operation has given a return value of -10. I have searched for any information on unQLite return codes, but so far I have nothing. I tried the PqDatabaseBrowser in the Tools section. This recognised the database, opened it and displayed all the keys correctly. However, clicking on any key gave the same PqFetchError. Does anyone have any idea of what I have done wrong? Thanks for any help. Peter Kenny

Sept. 5, 2016

Re: [Pharo-users] difficult to kill objects - pesky hanging pointersTo

by Andres Valloud

So why doesn't two-way become: help, e.g. ClassOfObjectsThatMustDie allInstances first become: String new As soon as that do-it unwinds there won't be any references to what the new string became (the new string wasn't referenced further), so... On 9/5/16 8:50 , Ben Coman wrote: > Sometimes its *really* hard to kill some objects. It seems that > inspecting a list of pointersTo creates additional hanging references. > This was frustrating me just now, so I finally hacked a way forward. > Sharing it in case its useful to others, and also I can find it again > searching the list. This needs to run for each object. > > Smalltalk garbageCollect. > target := ClassOfObjectsThatMustDie allInstances first. > SystemNavigation default allObjectsDo: [ :e | > (e isKindOf: Association) ifTrue: [ e value = target ifTrue: [ e > value: nil ] ]. > (e isKindOf: Array) ifTrue: [ 1 to: e size do: [ :i | (e at: i) = > target ifTrue: [ e at: i put: nil ] ] ] > ]. > target := nil. > Smalltalk garbageCollect. > > cheers -ben > >

Sept. 5, 2016

Re: [Pharo-users] MNU PPContext>>identifier in GT Inspector extension

by Alistair Grant

Hi Doru, On Thu, Sep 01, 2016 at 11:51:21AM +0200, Tudor Girba wrote: > Hi, > > I just tried it, and I cannot reproduce the problem. > > Here is the exact script: > http://ws.stfx.eu/KC3BLPA3U0FS > (just paste this in Spotter) I can reproduce the problem with the stable release of Pillar, but not with the development or bleeding edge versions. I swear I tried them before, but... :-( Thanks very much for following up and my apologies for the noise. Cheers, Alistair

Sept. 5, 2016