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

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

by Yuriy Tymchuk

Ok, so here it goes. There was a main method: #package:class:category:method: (https://github.com/pharo-project/pharo-core/blob/8a1f79b44b14f8eafaf6d91a8b… <https://github.com/pharo-project/pharo-core/blob/8a1f79b44b14f8eafaf6d91a8b…>). This method was setting a state of the model by sending #selectedPackage:, #selectedClass:, â¦â¦â¦ to self. Each of this 4 methods were announcing if the parameter was not nil. As you may guess #package:class:category:method: was used through the whole system with occasional nil params. I hate working with nils. So what I did was to break the method into 4: #package: #package:class: #package:class:protocol: #package:class:protocol:method: So now there is no nil passing anymore. E.g. if you select only a class, you send #package:class:. Then Iâve moved announcements from #selectedPackage:, #selectedClass:, â¦â¦â¦ to the newly created 4 methods. Also now announcements know the parent scope i.e. NautilusProtocolSelected besides protocol knows also about the class and package that played a role on the selection. This are essentially all the changes. The issue that occurred later (when selecting a package class was not deselected) is because #selectedClass: was doing `self selectedProtocol: nil`, same with protocol. But #selectedPackage: was not âdeselectingâ a class, probably because it was handled by calling `model package: SomePackage class: nil category: nil method: nil` in a first place. > On 05 Sep 2015, at 21:39, stepharo <stepharo(a)free.fr> wrote: > > > > Le 5/9/15 16:49, Yuriy Tymchuk a Ã©crit : >> I can give you a short explanation for the sake of more people knowing how Nautilus works. > Yes please if you have some time. > What I do not like is that we pass nil to indicate that there is no selection. I was thinking that an hierarchy of null objects could help but this is difficult to > foresee if it will make sense. > I also that all the logic update without reselecting is complex. > I started to read the code and also move some condition about the model to the model class :). > I would like to do just a simple pass reading all the code and not changing much to get now yet another better feel of nautilus. > I will also remove the Nautilus help. > I would like to rename the NautilusRefactoring because it is not about nautilus but about RB. > >> >> Regarding diffs and knowledge sharing, we should have a normal code review support with something like gerrit. > > thomas was working on a code review tool and skip is taking over so I hope that we will have it. >> >> Uko >> >>> On 05 Sep 2015, at 15:46, stepharo <stepharo(a)free.fr> wrote: >>> >>> As you wish. Thanks for your time. >>> >>> Now I will get really frustrated because I will not know simply what you did and I will have missed a good occasion >>> to learn something. This is what sending the diff in text simply give us. >>> >>> Stef >>> >>> >>> Le 5/9/15 14:09, Yuriy Tymchuk a Ã©crit : >>>> I found the issue. Fix almost ready. Should I reopen the case, or create a new one? >>>> >>>> Uko >>>> >>>> >>>> >>>>> On 05 Sep 2015, at 13:59, Stephan Eggermont <stephan(a)stack.nl> wrote: >>>>> >>>>> On 05-09-15 08:51, stepharo wrote: >>>>>> Hi >>>>>> >>>>>> I do not know if this is linked to recent changes but we cannot remove >>>>>> classes or move them to another package >>>>> I can move them to another package using drag-and-drop (issue 16488) >>>>> in 50305 >>>>> >>>>> >>>>> Stephan >>>>> >>>>> >>>> >>> >> >> > >

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by Yuriy Tymchuk

Yes, I know, but Stef was referring to deleting a method. Also I donât really know how I can fix the stuff with instance variable. I need to have a separate process in order not to slow down the browsing in Nautilus. Uko > On 07 Sep 2015, at 12:01, Nicolai Hess <nicolaihess(a)web.de> wrote: > > "and add an instance *variable*" :) > > 2015-09-07 12:01 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: > > Just open Nautilus on class "Model" and add an instance. > > > > 2015-09-07 0:56 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Also, when if this kind of error happens again, can you please fuel it out and sent it to me? Having a stack can be helpful in understanding. > > Uko > > > On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > > > > I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method > > but I failed. > > I got again this bug. > > What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. > > But I cannot reproduce it. > > > > Stef > > > > > >

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by Nicolai Hess

"and add an instance *variable*" :) 2015-09-07 12:01 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > Just open Nautilus on class "Model" and add an instance. > > > > 2015-09-07 0:56 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > >> Also, when if this kind of error happens again, can you please fuel it >> out and sent it to me? Having a stack can be helpful in understanding. >> >> Uko >> >> > On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr> wrote: >> > >> > I thought that I could reproduce the QA concurrent access raising a DNU >> when we remove a method >> > but I failed. >> > I got again this bug. >> > What I did was selecting a method in Nautilus and removing this method >> after an implementors and from the message list browser. >> > But I cannot reproduce it. >> > >> > Stef >> > >> >> >> >

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by Nicolai Hess

Just open Nautilus on class "Model" and add an instance. 2015-09-07 0:56 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Also, when if this kind of error happens again, can you please fuel it out > and sent it to me? Having a stack can be helpful in understanding. > > Uko > > > On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr> wrote: > > > > I thought that I could reproduce the QA concurrent access raising a DNU > when we remove a method > > but I failed. > > I got again this bug. > > What I did was selecting a method in Nautilus and removing this method > after an implementors and from the message list browser. > > But I cannot reproduce it. > > > > Stef > > > > >

Sept. 7, 2015

Pillar 1.1.0 released

by Damien Cassou

Cyril Ferlicot and I have polished Pillar 1.0.0 a little. Here is 1.1.0 changelog: - add shebang to generated pillarPostExport.sh - improve pillarPostExport.sh messages a little - HTML exporter - output a <figure> if and only if the Pillar figure has both a caption and a label - LaTeX exporter - output a \begin{figure} if and only if the Pillar figure has both a caption and a label Cyril migrated the list of issues and feature requests from smalltalkhub.com to https://github.com/pillar-markup/pillar/issues Please report issues, describe feature requests and ask questions there. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 7, 2015

Re: [Pharo-dev] Mongo - find object by id

by Sabine Manaa

Hi Stephane, my changes have been integrated into the document by Johan and I checked as ok, so it is done. Regards Sabine 2015-08-18 12:49 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > Hi Stephane, > > ok, I have put all my suggestions in a pull request. Please feel free to > change, delete .... it is only a suggestion. I am interested in feedback! > > Regards > Sabine > > 2015-08-17 14:53 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > >> Hi Steph, >> >> thanks. I am editing my suggestions and tell you when finished. >> >> Regards >> Sabine >> >> 2015-08-16 19:29 GMT+02:00 stepharo <stepharo(a)free.fr>: >> >>> >>> Hi Stephane, >>> >>> I have collected my points to add to the book. >>> >>> Can you give me an entry point how to do a pull request on the paper >>> please? >>> Pillar? Editor? Script? Sounds complicated for the first time. >>> >>> If you can use pillar this is better, else we will do a pass and convert >>> it to pillar >>> Since the chapter is for the book that should be out I'm not that >>> editing it directly is a good. >>> Now what we can do is to work on on a separate file that Johan or >>> Esteban can merge to the chapter once >>> it is finished. >>> >>> What I was thinking about is to have a series of extras section >>> with for example some of the problems and solutions you encountered. >>> >>> >>> How to handle loop within your domain? >>> >>> How to find an object by id? >>> >>> ... >>> >>> The original file is here: >>> >>> >>> https://github.com/SquareBracketAssociates/EnterprisePharo/tree/master/Voya… >>> >>> >>> I created a VoyageAdditionalText.pier that you can edit. >>> >>> And this is easy >>> - you can go to the page >>> - fork the folder >>> - edit in the web the file and send a pull request. >>> >>> if this is not working, we will add you to the project and you can >>> directly edit this file. >>> >>> Regards >>> Sabine >>> >>> >>> >>> 2015-08-13 16:17 GMT+02:00 stepharo <stepharo(a)free.fr>: >>> >>>> >>>> Hi Stephane, >>>> >>>> sure, I am happy to give something back to the community. I dont have >>>> so much time because of my baby but I will try my best. >>>> >>>> Where shall I put it in? >>>> >>>> >>>> You can do pull requests in the paper. This way they will be close to >>>> the original version. >>>> >>>> >>>> Sabina >>>>> >>>>> you know what I would really love from you .... >>>>> this is that you reread the Voyage chapter and make a list of the >>>>> problems you faced and that are not described in the chapter. >>>>> You can write it in any bad ways and we can do a edit phase after, >>>>> >>>>> Why do I ask that? Because I'm stupid in Mongo and I would love to >>>>> have a good doc. >>>>> And only the people facing the problems can spot them nicely. >>>>> I often write doc on things that I do not know but this is not working >>>>> well because I'm slow in that case and .... I could be much better >>>>> doing something else where I'm good at. >>>>> >>>>> Stef >>>>> >>>>> Le 12/8/15 09:40, Sabine Manaa a Ã©crit : >>>>> >>>>>> Hi, >>>>>> >>>>>> on mongo console, this brings me a persons information from mongo db >>>>>> db.Persons.find({"_id" : ObjectId("75b900000000000000000000")}) >>>>>> >>>>>> I try to query the same person from pharo and I do not succeed. >>>>>> >>>>>> This makes my image hanging: >>>>>> RKAPerson selectMany: {('_id' -> (OID >>>>>> value:'75b900000000000000000000'))} >>>>>> >>>>>> also other variations e.g. >>>>>> RKAPerson selectMany: {('_id' -> ('75b900000000000000000000')). } >>>>>> asDictionary. >>>>>> >>>>>> do not work >>>>>> >>>>>> Other queries like >>>>>> RKAPerson selectMany:{('lastName' -> ('Maier')).} asDictionary. >>>>>> or >>>>>> RKAPerson selectMany:{('nextTripNumber' -> (57)).} asDictionary. >>>>>> >>>>>> work fine. >>>>>> >>>>>> How can I query for an object with the object id? >>>>>> >>>>>> Regards >>>>>> Sabine >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://forum.world.st/Mongo-find-object-by-id-tp4842231.html >>>>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>>>> Nabble.com. >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> >

Sept. 7, 2015

WhatsUp from: 2015-09-07 until: 2015-09-20

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-09-20 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by Yuriy Tymchuk

Also, when if this kind of error happens again, can you please fuel it out and sent it to me? Having a stack can be helpful in understanding. Uko > On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr> wrote: > > I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method > but I failed. > I got again this bug. > What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. > But I cannot reproduce it. > > Stef >

Sept. 6, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by Yuriy Tymchuk

I think that it is related to how I was working with Nautilus announcements. Now as announcements are changed, I can improve that. Just give me a bit of time :) Uko > On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr> wrote: > > I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method > but I failed. > I got again this bug. > What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. > But I cannot reproduce it. > > Stef >

Sept. 6, 2015

Did no find yet a way to reproduce QA concurrent access

by stepharo

I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method but I failed. I got again this bug. What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. But I cannot reproduce it. Stef

Sept. 6, 2015