September 2013 - Pharo-dev - lists.pharo.org

Pharo Sprint pre-planning until end of year

by Marcus Denker

Hi, On the way back from ESUG we where checking the Calendar for possible Sprint dates. The idea is to have one each months that is a public sprint here in Lille (other sprints will be organized elsewhere, we will do mini-sprints more spontaneously in addition here, too). The dates: 18/10 29/11 20/12 This is always a Friday. Marcus

Sept. 19, 2013

Re: [Pharo-dev] voyage/mongo reset vs. allInstancesDo: #reset

by Sabine KnÃ¶fel

Hi Esteban, in my image, the result of VORepository current is ==>> VOMongoRepository so, VORepository current reset. it is the same as VOMongoRepository reset Cheers Sabine On Thu, Sep 19, 2013 at 12:24 PM, EstebanLM [via Smalltalk] < ml-node+s1294792n4709130h25(a)n4.nabble.com> wrote: > Hi Sabine, > > The right message to reset is: > > VORepository current reset. > > I don't know what "VOMongoRepository reset" does (I need to check it) :P > > Cheers, > Esteban > > > On Sep 19, 2013, at 11:38 AM, Sabine KnÃ¶fel <[hidden email]<http://user/SendEmail.jtp?type=node&node=4709130&i=0>> > wrote: > > > Hi Esteban, all, > > > > in the mongo/voyage tutorial at ESUG, I understood, that > > > > "VOMongoRepository reset" can be used instead of > > "VOMongoRepository allInstancesDo: #reset". > > and the code looks like that ( flush...) > > > > It seems that I can't - I think, using "VOMongoRepository reset" does > _not_ > > reset the cache. > > So, the objects are not read new from database. > > Voyage does not enter the <mongoDescription> methods. > > > > This is not a problem for me, I can also use "VOMongoRepository > > allInstancesDo: #reset", but I want to tell you about that. > > > > To reproduce I did the following, > > 1) read objects from mongo (ClassXXX readAll) > > 2) put halt in one of the <mongoDescription> methods > > 3 a) do "VOMongoRepository reset" and then (ClassXXX readAll) again -> > no > > debugger > > 3 b) do "VOMongoRepository allInstancesDo: #reset" and then (ClassXXX > > readAll) again -> debugger comes up > > ==> so, 3a does not work, 3b works > > > > Regards > > Sabine > > > > > > > > -- > > View this message in context: > http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120.… > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p… > To unsubscribe from voyage/mongo reset vs. allInstancesDo: #reset, click > here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

configurationOfZincHTTPComponents does not load Neo JSON

by Sabine KnÃ¶fel

Hi Sven, all, I just found out, that one class I use, NeoJSONReader suddenly is missing after loading new. Then I recognized, that in configurationOfZincHTTPComponents>>baseline24: there is a project 'XMLSupport' and 'Neo Json' (with NeoJSONReader) but if I load the configurationOfZincHTTPComponents, ==>> both are not loaded. baseline24: spec .... spec project: 'XML Support' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #'stable'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]. spec project: 'Neo JSON' with: [ spec className: 'ConfigurationOfNeoJSON'; versionString: #'stable'; repository: 'http://mc.stfx.eu/Neo' ]. For test, I used load with: Gofer it smalltalkhubUser: 'SvenVanCaekenberghe' project: 'ZincHTTPComponents'; configurationOf: 'ZincHTTPComponents'; loadStable. I am just reading the great new deep into pharo book and the chapter about metacello. It is very helpful to make my own configurationOf in the right way. But in this case, I dont see the reason, why this does not work :-) Can you have a look at it, please? Sabine -- View this message in context: http://forum.world.st/configurationOfZincHTTPComponents-does-not-load-Neo-J… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

Re: [Pharo-dev] [OT] Pharo lighthouse wallpaper

by StÃ©phane Ducasse

I have some pictures of lighthouse that I could give. I love lighthouse. There are so positive. Stef On Sep 19, 2013, at 1:33 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > http://wallpapers5.com/images/wallpapers/71156968/Photography/Cape-Hatteras… > > According to site Image is for personal, non commercial use >

Sept. 19, 2013

Re: [Pharo-dev] voyage/mongo reset vs. allInstancesDo: #reset

by Esteban Lorenzano

Hi Sabine, The right message to reset is: VORepository current reset. I don't know what "VOMongoRepository reset" does (I need to check it) :P Cheers, Esteban On Sep 19, 2013, at 11:38 AM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Esteban, all, > > in the mongo/voyage tutorial at ESUG, I understood, that > > "VOMongoRepository reset" can be used instead of > "VOMongoRepository allInstancesDo: #reset". > and the code looks like that ( flush...) > > It seems that I can't - I think, using "VOMongoRepository reset" does _not_ > reset the cache. > So, the objects are not read new from database. > Voyage does not enter the <mongoDescription> methods. > > This is not a problem for me, I can also use "VOMongoRepository > allInstancesDo: #reset", but I want to tell you about that. > > To reproduce I did the following, > 1) read objects from mongo (ClassXXX readAll) > 2) put halt in one of the <mongoDescription> methods > 3 a) do "VOMongoRepository reset" and then (ClassXXX readAll) again -> no > debugger > 3 b) do "VOMongoRepository allInstancesDo: #reset" and then (ClassXXX > readAll) again -> debugger comes up > ==> so, 3a does not work, 3b works > > Regards > Sabine > > > > -- > View this message in context: http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120.… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Sept. 19, 2013

voyage/mongo reset vs. allInstancesDo: #reset

by Sabine KnÃ¶fel

Hi Esteban, all, in the mongo/voyage tutorial at ESUG, I understood, that "VOMongoRepository reset" can be used instead of "VOMongoRepository allInstancesDo: #reset". and the code looks like that ( flush...) It seems that I can't - I think, using "VOMongoRepository reset" does _not_ reset the cache. So, the objects are not read new from database. Voyage does not enter the <mongoDescription> methods. This is not a problem for me, I can also use "VOMongoRepository allInstancesDo: #reset", but I want to tell you about that. To reproduce I did the following, 1) read objects from mongo (ClassXXX readAll) 2) put halt in one of the <mongoDescription> methods 3 a) do "VOMongoRepository reset" and then (ClassXXX readAll) again -> no debugger 3 b) do "VOMongoRepository allInstancesDo: #reset" and then (ClassXXX readAll) again -> debugger comes up ==> so, 3a does not work, 3b works Regards Sabine -- View this message in context: http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

[update 3.0] #30407

by Marcus Denker

30407 ----- 11631 Disable History navigation buttons in Inspectors when not usable https://pharo.fogbugz.com/f/cases/11631 11413 Make a diff tool to show recategorization as a change properly https://pharo.fogbugz.com/f/cases/11413 11632 Add browse shortcut to critics browser https://pharo.fogbugz.com/f/cases/11632 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.7… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.11… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Tools-Diff-MarcusDe… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.865.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus…

Sept. 19, 2013

Re: [Pharo-dev] if Pharo is key for you

by StÃ©phane Ducasse

Sounds really cool. On Sep 18, 2013, at 9:41 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/9/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> On Sep 18, 2013, at 5:21 PM, phil(a)highoctane.be wrote: >>> What I'd be interested in is any code/framework for GIS open data reading / >>> Google Maps integration / Open Street Map stuff. > > What do you mean by "Google Maps integration"? > > Attached goes a screenshot (*) of the pilot app I'm developing, it has > a small set of JavaScript code on the client handling live updates > coming from a Zinc Websocket (serialized by NeoJson), updates that > were handled before by a Seaside-REST interface, handling requests > coming from mobile clients. > > I plan to implement GeoJSON in my app and use it against the MongoDB > of Voyage, but I didn't have time yet to properly integrate, not to > mention to share it. > > Or by integration you mean Seaside integration? Like generating the > map as if it were a seaside component? > > Regards, > > (*) Sorry it is blurred, I can't disclose more than this. > <Screenshot---Mapa.png>

Sept. 19, 2013

Re: [Pharo-dev] if Pharo is key for you

by Friedrich Dominicus

kilon <thekilon(a)yahoo.co.uk> writes: > How does "extending Pharo help tool " sounds ? :) > > I am struggling to learn how morphic really works, especially > TreeMorph. Well that is a thing I tried more than once, but somehow I never understood on how to make good use for Morphic for me. I checked a lot of tutorial but then even simple things like menues seem to be doable but not for me.. It is strange and not "nice". Regards Friedrich

Sept. 19, 2013

Re: [Pharo-dev] Can't correctly inspect ring definitions

by StÃ©phane Ducasse

>> RGClassDescriptionDefinition should be polymorphic with >> ClassDescription. But #instVarNamed: is protocol of Object, so why to >> override it there? >> >> Concretely, I have instances of RGClassDefinition and I can't: >> >> 1) inspect them as regular objects >> 2) use STON to serialize >> >> Because both use #instVarNamed:, which is answering nil. >> > > To me it looks wrong for RGClassDefinition implementing #instVarNamed:. probably (this is the question of layering) now it also means that we should have a look at the class protocol to access instance variables so that we have an Object API but also a good Class/RingClass API. Stef

Sept. 19, 2013